6 ms·
There are two types of certificate on Windows: OV and EV. OV is easier to get and the key protection requirements are less strict, but your new identity starts
by mike_hearn 4y ago
There are two types of certificate on Windows: OV and EV. OV is easier to get and the key protection requirements are less strict, but your new identity starts out with no reputation. Browsers will warn you that the program is rarely downloaded until you pick up some reputation from users not reporting it as malware.
EV certs don't have that problem. Even for a new company or individual who has never distributed software to Windows before, user won't see any warnings. EV certs have a more thorough ID verification procedure, and keys have to be protected in hardware so you can't accidentally push them somewhere. Most CAs will physically mail you a USB dongle that you can use for signing.
Nonetheless, the unknown binary warnings will go away even if you use an OV cert as long as your early users are forgiving.
- nikanj 4y agoOur company has had EV-signed binaries flagged as malware by products from Symantec, F-Secure and Avast. Probably others too, those three I can remember off the top of my head.
- mike_hearn 4y agoYes it's just a signal to AV engines, not a whitelist. Windows Defender is quite respectful of it. Something that can increase the risk of FPs is mixed signing. Like, not signing every DLL and EXE in the program with the same certificate, not signing the installers/packages, only signing the installers/packages and not the contents, etc.