Thawte's code signing certificates use an intermediate certificate that might not be installed on the user's system. When it is not installed on the user's system the installer gets an "Unknown Publisher".
signtool.exe has the ability to include an intermediate certificate when signing a file using the "additional certificate" switch /ac and the "Unknown Publisher" goes away.
Because I don't know of a way to get AI to sign using signtool with the /ac switch I use a post-build process in Visual Studio to sign the installer. This works perfectly as long as I don't need the installer bootstrapped (i.e. install using the msi). However, now I need the installer bootstrapped because I need to use the HTML features of the Enterprise version so that I can get clickable links in the License Agreement (which requires bootstrapping to work). I can't use the VS post-build signing with the exe because the bootstrapper throws an error when the exe is signed differently than the msi. I can only sign the final output; I can't create the msi in AI, then sign the msi in VS, then create the bootstrapper in AI, and then sign the exe in VS.
So a couple of questions:
Is there a way to get the HTML pages to work without bootstrapping?
Is there a way to get AI to use signtool with the /ac switch?
Is there a way to extract the manifest that AI would use to create the bootstrapper and then use VS to create the bootstrapper using that manifest?
Is there anything that I'm missing that might meet my needs?
FOLLOW US
Get the latest news in Application Packaging