There is one issue I'm facing. I have a verified certificate with which I have produced a native installer for Windows. The problem is when I download this installer file from my web server, it gives me a prompt with Publisher: UNKNOWN. Can anyone please let me know where I'm wrong? Please see the attached image
To help you guys more, when I tried to sign the native installer through command line, it gave me the following error:
Certificate in cert_2.p12 could not be used to sign setup.msi
I also looked into the certificate. It's not expired but then why It can't be used?
Please help me.
Is the certificate being used from a Certification Authority recognised by Adobe? You can self sign an AIR app for use with the installer which will ensure that the AIR archive is not tampered with before install, but a self sign cert will always be an Unknown Publisher to Adobe.
You need to use a Cert from a 3rd party authority that Adobe trusts such as Verisign to be a recogised publisher during install, these are commercial certs that Adobe will verify during install/upgrade of AIR app and display your publisher details registered against this cert when purchased.
The Comodo Cert is a social web trust mechanism used as a sort of 'recommendation of trust' for users / customers of an ecommerce web presence.
The cert you would need would have to come from one of the organisations in Adobe Approved Trust List (AATL)
aa) If your app is going out to thousands++ of users in the public domain, who expect future releases you should investigate obtaining a cert from one of the AATL members.
bb) If your app is internal to an organisation, you could make yourself a trusted authority, have a look at http://biosocket.com/tag/trusted-certificate-authority
I can't vouch for bb) as all my development is on Mac OS X and Linux
Hope this helps
I haven't seen this situation. One thing you can try is using the signtool.exe to sign an Windows app. with your cert to see if it works.
Or ask the certificate vendor if the certificate is good for code signing a Windows app.
We have a Thawte certificate. It seemed like ADT was signing it correctly but when the app was installed on Windows it was displaying Publisher: Unknown. Signtool fixed it after we packaged it.
hope that helps...let me know if you need more details. We build the exe in Hudson.
" It seemed like ADT was signing it correctly " - Could you see the native installer is signed after ADT packaging command is run?
"when the app was installed on Windows it was displaying Publisher: Unknown." - After the native installer installation, you look at the installed app.'s digital signature?
Europe, Middle East and Africa