Summary

With the deprecation of SHA-1 certificates, signed installations require SHA-2 signatures to be validated on newer Windows OS.

Symptoms

With the deprecation of SHA-1 certificates, signed installations require SHA-2 signatures to be validated on newer Windows OS. On the other hand, Vista/Server 2008 and earlier OS will not validate SHA-2 signatures. Therefore, to support a signed installation that can be validated both on Vista/Server 2008 and newer OS, executables will need to be dual signed with both a SHA-1 hash and a SHA-256 hash using the SHA-256 certificate. Currently, InstallShield does not have the ability to dual sign during build.

Cause

An enhancement request for this feature has been submitted and is pending review from our Engineering team. The issue is being tracked under issue #IOJ-1749020.

Workaround

Currently, the workaround involves performing dual signing with Microsoft's signtool.exe after build. This can be integrated into the InstallShield build process by including the signtool calls as a Postbuild Event.

Additional Information

• For information regarding installers and dual signing, please refer to the Microsoft article Windows Enforcement of Authenticode Code Signing and Timestamping
• For information regarding Postbuild Events, please refer to our HelpNet article Postbuild Event Dialog Box