List of special chatterers not supported in controller certificate private key passphrase

Aruba Employee
Q:

How to find whether private key is encrypted or non-encrypted? 

A: When the private key file is opened in a notepad, if the first and last line has "-----BEGIN ENCRYPTED PRIVATE KEY-----" and "-----END ENCRYPTED PRIVATE KEY-----" this is an encrypted private key with passphrase. Whereas for an non-encrypted private key first and last line will be "-----BEGIN RSA PRIVATE KEY-----" and "-----END RSA PRIVATE KEY-----". 

 

Q:

What is a private key passphrase

A: The passphrase is just a key/password characters used to encrypt the private key file that contains the RSA key, using a symmetric cipher (usually DES or 3DES). 

 

Q:

Can I import an encrypted private key without a passphrase? 

A: No, an encrypted private key requires exact match of passphrase to import successfully. 

 

Q:

List of supported characters in passphrase:

A: 

Charecter Name
~ Tilde
! Exclamation
@ At sign
# hash
% Percent
^ Caret
* Asterisk
_ Underscore
+ Plus
- Hyphen
= Equal sign
{ Left brace
} Right brace
[ Left bracket
] Right bracket
: Colon
, Comma
. Full stop
/ Slash


Q:

List of un-supported characters in passphrase: 



A:
Character Name
` Grave accent (backtick)
$ Dollar sign
& Ampersand
( Left parenthesis
) Right parenthesis
| Vertical bar
\ Backslash
" Double quote
; Semicolon
' Single quote
< Less than
> Greater than
? Question mark

 

Q:

What happens if an unsupported character is used in passphrase and attempted to import the certificate? 

A: If an unsupported character is used in the passphrase, below is the error message displayed while uploading the certificate. 

Q: 

How to convert an encrypted private key (with unsupported character) to un-encrypted private key file? 

A: If we import a certificate file (in PEM format with unsupported character as passphrase), upload will fail with the above mentioned error message. Hence we need to convert the encrypted private key to an unencrypted private key. Below are the steps to extract private key separately, convert and re-arrange the certificate with unencrypted key for windows machine. 

  1. Open the PEM format certificate file which has private key and the complete certificate chain in notepad. 
  2. CUT/COPY the private key part with starts from "-----BEGIN ENCRYPTED PRIVATE KEY-----" and end as "-----END ENCRYPTED PRIVATE KEY-----". 
  3. Open another notepad, PASTE the content and save the file locally with '.pem' as extension.
  4. Download OpenSSL for windows and follow the instruction to how to install. 
  5. Open command prompt and navigate to location where 'openssl.exe' file is located (default location is under C:\Openssl\bin\).
  6. Execute the below command to convert:

Command Syntax:

>openssl.exe rsa -in <Traditional PEM Key Filename> -out <Unencrypted Key Filename>

Command Sample: 

 

  1. Once the command is executed, option to enter passphrase will be promoted. Enter the passphrase (same passphrase when creating the CSR).
  2. If the convection is successful, no error will be displayed under 'writing RSA Key' 
  3. Open the unencrypted key file, copy the complete contact (Starts with 'BEGIN RSA PRIVATE KEY' and ends with 'END RSA PRIVATE KEY') and replace the private key part in the PEM formatted certificate file (Replace the content which starts from 'BEGIN ENCRYPTED PRIVATE KEY' and ends with 'BEGIN ENCRYPTED PRIVATE KEY')
  4. Save the file and attempt to import with out any passphrase. 

Q:

What is the certificate format is imported with PKCS#12. Will I get the same error? 

A: Yes, the same error message will be displayed as the private key will be in PKCS#8 within PKCS#12. 

 

Version history
Revision #:
2 of 2
Last update:
‎03-24-2017 03:44 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: