Hi,

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.

Cheers

Mark

Hi,

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)

http://www.adobe.com/security/approved-trust-list.html

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

Cheers

Mark

Hi, we're seeing the same error. Just curious if changing the extension from .p12 to .pfx worked for you? Doesn't seem to be working for us...thnx in advance. Seth

K. We got it working by signing the exe with Signtool (the wizard is easy) and using the pfx file to sign it.

Hi Ted,

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.

Seth