Hacker News Reader

Comment by mnkypete | Hacker News Reader

This alert would not show if you used SHA256 instead of SHA1, which was deprecated: https://www.globalsign.com/en/blog/microsoft-announces-updat...

EV certs immediately gain trust: https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-sma...

View on HN

They aren't sufficient to get rid of the slanderous message on their own - even with an EV. You need to have a bit of volume first. Makes interacting with your first few customers lots of fun.

That's not true though. We have very little volume installs and since the EV, there has has not been one of these messages..

I've had differing experiences. Note that if you've been distributing before you got the cert part of that rep will carry over as its also a function of the exe signature.

I would check if something in the signing process is going wrong, refer to this (very long) SO thread: https://security.stackexchange.com/questions/109629/deprecat...

We actually switched certificates (from StartCom to Globalsign) and the signing was wrong at first, so the message kept showing. When we fixed it, it went away immediately, even though certificate and author name changed...

Here's the article:https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-sma...

"Programs signed by an EV code signing certificate can immediately establish reputation with SmartScreen reputation services even if no prior reputation exists for that file or publisher."

>This alert would not show if you used SHA256 instead of SHA1, which was deprecated

apparently sha2 signing wasn't working for him

https://news.ycombinator.com/item?id=17200491

>I would have signed with SHA-2, which for inexplicable reason is not default despite deprecation, but my signtool crashed when I enabled it.

Another 6 months!

Reply on news.ycombinator.com