Hello,
Since I'm doing a lot of work that has to do with security, I have many X509 certificates installed in my local certificate store, including several expired code signing certifcates.
I have a package that uses a certificates that has several expired version (same name, different keys, hash and expirations) installed as well.
Unfortunately, Advanced installer seems unable to pick the right certificate: even though the UI only lists the valid certificate in the dropdown, the actual process clearly uses the name and not the hash for identifying the certificate because it always picks the wrong one and the signature fails. I need to keep these certificates even though they are technically invalid so deleting them isn't a solution.
As a workaround, I'm using signtools to sign and timestamp the MSI but that forces added complication to the whole build process.
FOLLOW US
Get the latest news in Application Packaging