I am using VS 2015 CE and the "Microsoft Visual Studio 2015 Installer Projects" on Windows 7 SP1. When I build my MSI file, the build process automatically adds a Code Signing Certificate to the resulting MSI file. Up until today, that certificate was valid, and when you would download that MSI off a web server, there was no warning. Today, IE began displaying a warning message, "The signature of this program is corrupt or invalid." When I look at the Cert. in the properties of the MSI file, it says, "This digital signature is not valid." Even files I uploaded last week and which worked fine are now displaying the message.
I have been researching this all day, and still have some holes in my understanding of the process. For example:
1) Where is the VS Installer getting the code signing certificate to apply to the MSI? I assume it would be in my Certificate Store, but can't find it. I never generated one, as far as I know, unless it was done as part of installation? I am not doing any SignTool calls, and I can't see anything in the vdproj file that talks about certificates (there is a tag that says "SignOutput" = "11:FALSE"). This process is happening, and has been happening automatically since I began using the installer.
2) How can I get VS Installer to apply a cert that works? I found a lot of varying reasons why it would fail, like because it was SHA1, but I looked at a recent MSI download from MS, and it is also uses SHA1, and it has no error. I would prefer to continue using a cert that is applied automatically, as opposed to buying one and applying it with signtool.