Code signing certificate has expired

Question

Code signing certificate has expired

cartel0x27 opened this issue 9 years ago · 4 comments

Your certificate has expired (26/02/2016).

This is probably contributing to the smartscreen errors I get every time I try and start the app.

The fix would be to renew the certificate and resign the binary I guess?

Answer 1 · 2016-03-14T21:38:45.000Z

Recent (from the last year or so) binaries are timestamped, which is supposed to stop this from happening. What smartscreen actually does inside is rather black box, though, unfortunately.

I will have a look.

Answer 2 · 2016-03-14T21:54:16.000Z

The latest download, signed 24th Jan 2016 with certificate expired on 26 Feb 2016, was signed with SHA-2 but time-stamped with SHA-1 and thus considered invalid - SmartScreen requires the signature and time-stamp both be SHA-2 if the time-stamp is 1st Jan 2016 or later.

Answer 3 · 2016-03-15T03:31:20.000Z

Found this:

http://stackoverflow.com/questions/12311203/how-to-pass-the-smart-screen-on-win8-when-install-a-signed-application

which recommends using the WACK (Windows App Certification Kit)

Answer 4 · 2016-03-16T00:24:02.000Z

I've requested an updated certificate, but obviously it's not in a CA's interest to make my life easy by actually issuing it, or their life profitable by allowing me to pay them. Sigh.