Menu ▾ ▴

No timeStampClient.jar

Open Discussion
Handra
2012-07-21
2013-02-26

  • Handra

    Handra - 2012-07-21

    Hi,

    I find a really strange problem here. I have successfully installed the sign server, configuring, and deploying the timestamp signer. The only problem now is, I cannot find any file named timeStampClient.jar that should be located at dist-client/timestampclient according to the documentation.

    Is there anything I did wrong? Maybe configuration issue?

    Thanks

     

  • Anonymous

    Anonymous - 2012-07-22

    I have no idea but trying this:

    http://signserver.org/installationguide.html#Quick%20start%20demo%20guide

    Anders
    PrumeKey tech support

     

  • Handra

    Handra - 2012-07-23

    Hi Anders,

    After some struggling, I now know that in this version I used (version 3.2.2), the file timeStampClient.jar is no longer exist. The file name now is SignServer-Client-CLI.jar. I think Primekey should update the documentation and the source code inside the signserver client, because when I issued command "java -jar SignServer-Client-CLI.jar", it repilied me with the following response: 

    usage: java -jar [b]timeStampClient.jar[/b] <options> <url>
 -instr <string>      String to be time stamped, if neither instr or
                      infile is given, the client works in test-mode generating it's own
                      message.
...

    Thanks

     

  • Handra

    Handra - 2012-07-23

    Sorry, the command I issued should be "java -jar SignServer-Client-CLI.jar timestamp"

    Thanks

     

  • Handra

    Handra - 2012-07-23

    Additional question,

    From the documentation, when I want to verify a timestamped document, it does not output the calculated hash value of the document like described in the documentation: 

    java -jar SignServer-Client-CLI.jar timestamp -verify -inrep ../../jboss-5.1.0.GA/server/default/log/ejbca.log.2012-07-21.tsp -signerfile ../../ejbca_4_0_11/p12/tsasigner.pem http://localhost:8080/signserver/tsa?workerId=1

    The output it gave me was: 

    INFO  Token was validated successfully.
INFO  Token was generated on: Sun Jul 22 00:00:01 MYT 2012
INFO  Processing took 125 ms

    Any idea??

    Thanks.

    Regards,

    Handra
    - Try the best, do the best, be he best -
    - http://www.handracs.info -

     

  • Markus Kilås

    Markus Kilås - 2012-07-25

    Additional question, From the documentation, when I want to verify a timestamped document, it does not output the calculated hash value of the document like described in the documentation:

    I can not find in the documentation where it says it should output the hash value. Could you send a link or point us to where it is?
    I am not sure the time-stamp client, being mostly intended for simple testing of the SignServer TSA and not being a complete timestamp client, has this feature. As an alternative you could also try the "openssl ts -verify" command.

     

  • Handra

    Handra - 2012-07-25

    Hi Markus,

    Here is the source link. http://wiki.ejbca.org/logsigning#toc7

    Thanks

    Regards,

    Handra
    - Try the best, do the best, be the best -
    - http://www.handracs.info -

     

  • Markus Kilås

    Markus Kilås - 2012-08-13

    Thank you Handra,

    I was able to reproduce the bug and I have registered https://jira.primekey.se/browse/DSS-520 for it.

    BR,
    Markus

     

Log in to post a comment.