sha1signtoolsha2verisign

Using SignTool.exe to sign using SHA256 after Microsoft dropped support for SHA-1


Since MS dropped SHA-1 support we now need to sign with SHA-2.

I sign all dlls, exe and msi. I changed my signtool.exe call to this:

signtool.exe /f "PathToPFX.pfx" /fd SHA256 /p "password" /d "product" /du "www.site.com" /tr "http://timestamp.geotrust.com/tsa"

I dont need dual signing because we dont support < vista. Im using the sign tool in the Windows 8.1 SDK

The sign tool gives no errors when i call it, and when i look at the certs they look to be updated correctly:

enter image description here

But i still get the corrupt msi error when downloading through IE.

Im guessing my cert needs renewing but im unsure how i can check if my pfx cert is using SHA1 or not. The cert was provided by VeriSign - Semantec are now support for this.


Solution

  • I talked to Semantec customer support and need to get the certificate re issued.

    https://knowledge.symantec.com/support/ssl-certificates-support/index.html

    Chat link at the top right. The new cert will be emailed to the technical contact on your companies account.

    After the reissue, i was able to solve the issue