Petr Vsetecka

edit> double-posted but unable to delete it

I'm not sure why I don't see my second post here but let me reiterate briefly as an answer instead. As for the counter, that is indeed the case. I agree with you on all points, that is exactly what I found out. However, as that is completely unusable for me for any kind of statistics, I concluded I will have to go through server logs to get the information. So that would be the answer I would give to others interested in this topic, just pull it out from the server logs, it's all there (thanks to...

I'm not sure why I don't see my second post here but let me reiterate briefly as an answer instead. As for the counter, that is indeed the case. I agree with you on all points, that is exactly what I found out. However, as that is completely unusable for me for any kind of statistics, I concluded I will have to go through server logs to get the information. So that would be the answer I would give to others interested in this topic, just pull it out from the server logs, it's all there (thanks to...

Hello, I have a SignServer 4.0.0 CE from binaries on WildFly 14 and Java 11 and it works great. I have set up two TimeStamp workers, one for legacy format of timestamps (RFC 3161) and one for current format (RFC 5816). However, I have noticed a problem with the "Signings" counter when displaying status of the workers - they both share the same counter. Where does this counter come from? Is it a query to the database or some inner counter? Can it be separated for each worker (as would be intuitive...

Hello, I am running SignServer 4.0.0 CE on WildFly and have met a strange bug. One server has a habit of eventually (so far two exact measurements of 44 minutes and 21 hours have been made) refusing to issue more TimeStamps and instead returning error 500. After closer examination of the error message, I found out that function org.signserver.server.BaseProcessable.getCryptoToken(BaseProcessable.java:301) returns NullPointerException. So far, my solution to this problem is to call bin/signserver...

Hi Markus, and as always, thank you for good answers. All is clear, I didn't read the RFC properly (shame on me). However, now that I am a little bit smarter, I would like to ask about "precision" of the GeneralizedTime included within timestamp. Can that be configured or does SignServer follow the recommendation of using whole seconds to the T? Best regards, Petr

Hi all, I am using the latest binary release and got the default set-up working (using your example keystores and everything now). I also found this page to help with this problem and that is what I will address. https://www.signserver.org/doc/current/manual/plugins.html#Time-stamp_Signer I have questions about three of these parameters. First, the accuracy setting. I know that the ACCURACY can be only whole numbers and only one present but it doesn't seem to change the time accuracy of produced...

Hi all, I am using the latest binary release and got the default set-up working (using your example keystores and everything now). I also found this page to help with this problem and that is what I will address. https://www.signserver.org/doc/current/manual/plugins.html#Time-stamp_Signer I have questions about three of these parameters. First, the accuracy setting. I know that the ACCURACY can be only whole numbers and only one present but it doesn't seem to change the time accuracy of produced...