I have a question as to whether what I want to do is possible. The code signing certificates are held by certain individuals in our group and are not available to every person who may need to make installers. We have the binaries (those which are installed by the installer) signed first by the code signers, then the installer is made, and then the final resulting installer is also signed by the certificate holder.
The problem is that the uninstaller which is generated by advanced installer is not signed unless the person making the installer has the certificate, which we don't do. We could provide the certificates to everyone who makes installers but this would require a significant change in how we do things and would violate in my opinion best practices in terms of maintaining security of code signing certificates. There really should be no more than 2 people with access to these certificates, imho. Otherwise if someone leaves the organization, or whatever, there's a reason to revoke the certs, etc.
Is there a way to have someone else, other than the person making the installers, sign the uninstaller that is generated? Ie can you run advanced installer and have it output an uninstaller, then have someone else sign that, then include that signed uninstaller in a final generated installer package?
Hope the question is clear. Thanks,
FOLLOW US
Get the latest news in Application Packaging