We are in the middle of upgrading our installer project from 16.3 to 19.4.
For our product, we build the installer on a CI server, and according to company policy this server has extremely limited access to the internet.
With 16.4 this meant we had to whitelist a timestamping service for this server so that we could build and sign the installer.
Now when we build the installer with 19.4 on the CI server, we notice a significant slowdown when the installer appears to doing signing related activity. When we build the installer on a development environment with full internet access, this slowdown does not occur.
From the release notes it's clear that since 17.1, AdvancedInstaller will check the validity of the signing certificate used for signing. This actually caused an error for us earlier, which we fixed by installing the certificate chain on the CI server.
While analyzing this issue from a development environment, we still notice 6 requests to servers that are related to the signing certificate at the point where it slows down on the CI server.
Our best guess (in the absence of more detailed logging) is that AdvancedInstaller, while trying to verify the validity of the certificate, is still performing those 6 requests mentioned above, resulting in timeouts and causing the slowdown.These requests however do not appear to be crucial to verifying the singing certificate, because the build does sign and succeed eventually.
So at this point we have multiple questions that could hopefully help us resolve this:
Can verification of the signing certificate be disabled?
If not, what else (beyond installing the certificates on the server) could we do to avoid requests to external servers?
And finally, is there any way to get more detailed logging regarding this when building an installer project?
FOLLOW US
Get the latest news in Application Packaging