I'm using signtool.exe on Windows to code sign with a SHA256 signature.
The only example I see (from Symantec) shows using:
http://timestamp.geotrust.com/tsa
..as the time server.
E.g.: signtool.exe sign /a /s MY /n "Common name" /as /fd sha256 /tr http://timestamp.geotrust.com/tsa /v "<file to be signed>"
But I'm wondering if there are other publicly supported RFC 3161 timestamp servers that will also work.
I'm asking because we had previously built redundancy into our code signing process when using SHA1 by having a few different servers (and multiple retry attempts + delays). This helped resolve very occasional but annoying build failures.
I want to do the same when code signing with SHA256.