[rsyslog-notify] Forum Thread: rsyslogd 8.4.0 using Guardtime signatures - (Mode 'post')

[noreply at adiscon.com]

User: DaGoodBoy 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24962#p24962

Message: 
----------
Hello,

I'm trying to configuring rsyslog to use Guardtime signatures and hit a
snag. I get the [logfile].gtsig after following the configuration
instructions, but it always remains a zero byte file. I also never get the
[logfile].gtstate when I send the rsyslogd process a HUP signal. When I
turn on debugging, rsyslogd forks itself (despite the manpage saying it
won't) so I can't see any additional details after it creates a pid file. I
tried sending USR1 signals to turn on debugging, but it appears to have no
affect in what is output to the logs.

For lack of any better debugging options, I dumped the network traffic to
see if the process is communicating to Guardtime. I discovered that this
url is returning a 401 Unauthorized instead of the data the program seems
to expect in the source code:

<!-- m --><a class="postlink"
href="http://stamper.guardtime.net/gt-signingservice">http://stamper.guardtime.net/gt-signingservice</a><!--
m -->

Have they discontinued public support of this feature? I notice the open
source version of their software is gone (OpenKSI.org). Do I have to sign
up with them to get credentials for accessing the service?

Thanks in advance.

Tony