Digitally signed EXE files are "corrupt or invalid" in IE
Posted: Fri Sep 20, 2013 2:29 pm
A recent update to IE9 and IE10 (KB2870699) causes digitally signed EXE files to be marked as "corrupt or invalid" when downloading with Internet Explorer 9 or 10.
For more info, see: http://connect.microsoft.com/IE/feedbac ... validation
I use a code signing certificate from GoDaddy.com, so the following workaround caught my eye:
For more info, see: http://connect.microsoft.com/IE/feedbac ... validation
I use a code signing certificate from GoDaddy.com, so the following workaround caught my eye:
How can I configure Installaware to timestamp the application signature with sha256 instead of sha2?Posted by tgrand7 on 9/20/2013 at 11:36 AM
GoDaddy tech support provided a workaround that works for a GoDaddy cert. Here's what they said:
Please note that there was an issue discovered where Internet Explorer reports that the download of an application that is code signed and timestamped using SHA1 will report the error message you are receiving. You can verify the correct signature by using 'signtool verify /v /pa <application>'. This issue can be mitigated by time stamping the application signature with sha256. A SHA256 timestamp can be applied when signing the application. As an example using signtool: signtool sign -n "My CodeSigning Subject" /tr http://tsa.starfieldtech.com /td SHA256 "MyApp.exe" When verified sign 'signtool verify /v /pa MyApp.exe', a SHA2 timestamped application will show the Timestamp was issued by 'Starfield Timestamp Authority - G2'.