2-22-2016 Dev Build MSI Corrupt / Invalid

[rkavalap]

Dev build MSI's corrupt. At least IE is blocking me from download.

[mjbvz]

Thank you for reporting this. It looks like all three of the 2/22 MSIs have this problem.

I confirmed that the downloads do work as expected in Chrome, and you can also ignore the warning and manually run the downloaded MSI through edge or IE, but this should be fixed. We're looking into it.

[mousetraps]

Thanks for reporting. I suspect something recently changed with our internal code sign process... I removed the dev build temporarily because we shouldn't be asking people to ignore code sign warnings, and will look into this tomorrow.

[NoelAbrahams]

Worked fine for me in Chrome.

[mousetraps]

@NoelAbrahams that's because Chrome isn't enforcing code signing guidelines. You'll see what I mean if you run from Explorer.

In any case, I figured it out:

Effective January 1, 2016, Windows (version 7 and higher) and Windows Server will no longer trust new code that is signed with a SHA-1 code signing certificate for Mark-of-the-Web This link is external to TechNet Wiki. It will open in a new window. related scenarios (e.g. files containing a digital signature) and that has been time-stamped with a value greater than January 1, 2016. This cut-off date applies to the code-signing certificate itself.

http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx

We'll switch certificates to sign with SHA2 and upload a new build this week.

[mousetraps]

Okay, updated our signing certs and uploaded a new dev build! Please try it out and verify it's working for you.
https://github.com/Microsoft/nodejstools/releases