Portable FARR - File Altered? Problem with Cert?

[rustymonkey]

Hi,

I just tried updating to FARR Portable 2.223.01 (on Win 8 ), but when I attempt to run the .exe, I get a windows error:

Windows smartscreen prevented an unrecognized app from starting. Running this app might put your PC at risk.
Publisher: Unknown Publisher
App: FindAndRunRobot.exe

Upon examining the certificate associated with the .exe it seems that Windows considers that "One of the countersignatures is not valid. The file may have been altered". See images re. the cert below.

[attach]

[Ath]

The file is not altered, but it's signed with a code-signing certificate that uses SHA1 hashing algorithm that is deprecated by (a.o.) Microsoft and Google.
Microsoft wrote down their policy this way: http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx
Google has been publishing their intent in this article: http://googleonlinesecurity.blogspot.nl/2014/09/gradually-sunsetting-sha-1.html

On the InstallSite blog an article in this direction is also written:

...
It only seems to affect setups that are being digitally signed.

The problem is caused by Windows Update KB3004394 which updates the way Windows checks for revoked root certificates.
...

Full article: http://blogs.msmvps.com/installsite/blog/2015/02/23/windows-update-breaks-installshield-command-line-build/
Newer versions of InstallShield just fail to digitally sign the executable, but the Portable build and Inno Setup installer that are used for SC signing doesn't seem to fail, but it's your OS that fails to accept the Certificate chain-in the file.

I guess mouser needs to update his code-signing certificates to SHA2 (aka sha256) versions (my employer also has to, but we're already due for this update in a couple of months).

[mouser]

oy that sucks, it's bound to confuse people and cause problems.
Thanks for the links Ath, looks like i have to change the hashing algorithm and/or generate new code signing certificates.  I'll try to do so this week.