zabkat support forum

Correct -- I'm the person that answered the Stack Overflow question and was pointing out the same thing to you.

I realize that, but that timestamp server's certificate is SHA1. /td specifies the digest algorithm used by the server but doesn't determine the certificate of the server itself (read the linked article again -- the same question applies to http://timestamp.comodoca.com/rfc3161).

The timestamp cert for your SHA256 cert will still be SHA1 when using that time stamp server. We won't know until Jan. 1 if that's a problem, but see here for a solution:

https://stackoverflow.com/questions/306 ... de-signing