Hi,

I was code signing a binary and as I dual sign my binaries I noticed that the SHA1 signature was no longer working.

Took me about an hour to figure out what was wrong as signtool just flat out gave me a simple error it could no longer sign for SHA1.

Turns out that it was the time server (d'oh)
Not sure if it is a time server outage or that verisign figured that we no longer have to codesign for SHA1.

Either way...

Using another time server fixes the issue.

Maybe it saves somebody else some time....

FYI, I am now using
http://timestamp.globalsign.com/scripts/timstamp.dll

whereas the time server that had issues is:
http://timestamp.verisign.com/scripts/timstamp.dll

cheers!
--
Wil