Skip to main content
This topic has been closed for replies.
Correct answer sixteenlabs

For those having issues with the openssl command not working on Windows due to the missing configuration file, before using the openssl command, enter "set OPENSSL_CONF=C:\path\openssl.cfg" to enable openssl to find your local configuration. Ensure no spaces before or after the "=" sign.

10 replies

Participant
January 19, 2013

This worked beautifully

Participating Frequently
October 20, 2012

I followed all the instructions and generated all the certificates but after i generated the P12 file, Command Prompt is asking me to Enter Export Password: What does this mean?

chris.campbell
Legend
October 25, 2012

If you're using Flash builder, then the password it's asking for is the one that you used when you generated the p12 file.

Participant
September 6, 2012

Hello,

this documentation page at the "Changing certificates" section says:

***********************************************************************************************************************************************************

In some circumstances, you must change the certificate you use to sign updates for your AIR application. Such circumstances include:

1. Renewing the original signing certificate.

2. Upgrading from a self-signed certificate to a certificate issued by a certification authority

3. Changing from a self-signed certificate that is about to expire to another

4. Changing from one commercial certificate to another, for example, when your corporate identity changes

***********************************************************************************************************************************************************

What about "Downgrading from a certificate issued by a certification authority to a self-signed certificate" please ? e.g: the opposite of the second circumstance listed in this part of the documentation.

Considering that we respect the 180 days limit after certificate's expiration date:

  • Is it possible to move from certificate issued by a trusted CA to a self-signed certificate ?

  • And then move back from the self-signed certificate to a new certificate issued by the same trusted CA as the old one ?

I ask about this because :

  • Our application's certificate issued by Thawte has expired for 30 days.

  • Thawte can't provide us a new certificate before the 180 days limit is reached.

So we consider to move from the expired Thawte certificate to a self-singed one. And then move back from the self-signed certificate to the new Thawte certificate which they will give us in the future.

Since we have a big amount of users, we'd like to be sure that this will work and everybody will be able to update the application without any troubles related to the "old expired Thawte certifcate => self-signed certificate => new Thawte certificate" migration.

Thanks for your help

chris.campbell
Legend
September 6, 2012

@khelkun - You've now got a 365 day grace period for apps built with AIR 1.5.3 or higher   Please see this doc for details:

http://help.adobe.com/en_US/air/build/WS13ACB483-1711-43c0-9049-0A7251630A7D.html

Participant
September 7, 2012

Thanks for your quick feedback!
The problem is that we have to delvier a master release of our application to our users on next week.
So we really need this "old expired Thawte certifcate => self-signed certificate => new Thawte certificate" migration.

However we tested the update of our application after moving from the old expired Thawte certificate to the self-signed certificate and it sounds to be ok.

So everything should go fine, thanks again.

sixteenlabsCorrect answer
Participant
May 25, 2012

For those having issues with the openssl command not working on Windows due to the missing configuration file, before using the openssl command, enter "set OPENSSL_CONF=C:\path\openssl.cfg" to enable openssl to find your local configuration. Ensure no spaces before or after the "=" sign.

Inspiring
June 7, 2012

I am receiving the following:

F:\dData\Downloads\openssl-0.9.8k_X64\bin>set OPENSSL_CONF=C:\path\openssl.cfg

F:\dData\Downloads\openssl-0.9.8k_X64\bin>openssl x509 -in developer_identity.ce

r -inform DER -out developer_identity.pem -outform PEM

Error opening Certificate developer_identity.cer

7856:error:02001002:system library:fopen:No such file or directory:.\crypto\bio\

bss_file.c:356:fopen('developer_identity.cer','rb')

7856:error:20074002:BIO routines:FILE_CTRL:system lib:.\crypto\bio\bss_file.c:35

8:

unable to load certificate

Inspiring
June 7, 2012

Did this just in case I was supposed to substitute for file created:

F:\dData\Downloads\openssl-0.9.8k_X64\bin>openssl x509 -in CerticateSigningReque

st.certSigningRequest.cer -inform DER -out CertificateSigningRequest.cerSigningR

equest.pem -outform PEM

Error opening Certificate CerticateSigningRequest.certSigningRequest.cer

6516:error:02001002:system library:fopen:No such file or directory:.\crypto\bio\

bss_file.c:356:fopen('CerticateSigningRequest.certSigningRequest.cer','rb')

6516:error:20074002:BIO routines:FILE_CTRL:system lib:.\crypto\bio\bss_file.c:35

8:

unable to load certificate