User Tools

Site Tools


doc:appunti:linux:sa:openvpn_openssl_problem

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
doc:appunti:linux:sa:openvpn_openssl_problem [2025/04/15 12:40] – [Extracting certificates an keys from the old .p12 file] niccolodoc:appunti:linux:sa:openvpn_openssl_problem [2025/04/15 12:53] (current) – [OpenVPN problem with obsolete pkcs12 files] niccolo
Line 1: Line 1:
-====== OpenVPN problem with obsolete pkcs12 files ======+====== OpenVPN problem with obsolete PKCS12 file ======
  
 If you are migrating a configuration from an old **OpenVPN 2.5.x** to a new **2.6**, you may face a problem with the **PKCS12** file, which was created with a legacy encryption. The error message is as follow: If you are migrating a configuration from an old **OpenVPN 2.5.x** to a new **2.6**, you may face a problem with the **PKCS12** file, which was created with a legacy encryption. The error message is as follow:
Line 9: Line 9:
 </code> </code>
  
-Generally the pkcs12 file contains also the Certification Authority certificate, so that ssl can check the integrity of all the chain. If the CA cert is missing, you can encounter another error:+Generally the pkcs12 file contains also the Certification Authority certificate, so that ssl can check the integrity of the entire chain. If the CA cert is missing, you can encounter another error:
  
 <code> <code>
Line 17: Line 17:
 </code> </code>
  
-===== Extracting certificates an keys from the old .p12 file =====+====== Inspecting the PKCS12 file ====== 
 + 
 +To inspect the PKCS12 certificate and the encryption is uses: 
 + 
 +<code> 
 +openssl pkcs12 -info -in file.p12 
 +</code> 
 + 
 +the command must be run on an host supporting the SSL encryption used to create the file. 
 + 
 +A file created with a legacy encryption may be like this: 
 + 
 +<code> 
 +... 
 +MAC: sha1, Iteration 1 
 +MAC length: 20, salt length: 8 
 +PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2048 
 +... 
 +PKCS7 Data 
 +Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048 
 +... 
 +</code> 
 + 
 +indeed a newer certificate will be: 
 + 
 +<code> 
 +... 
 +MAC: sha256, Iteration 2048 
 +MAC length: 32, salt length: 8 
 +PKCS7 Encrypted data: PBES2, PBKDF2, AES-256-CBC, Iteration 2048, PRF hmacWithSHA256 
 +... 
 +PKCS7 Data 
 +Shrouded Keybag: PBES2, PBKDF2, AES-256-CBC, Iteration 2048, PRF hmacWithSHA256 
 +... 
 +</code> 
 + 
 + 
 +===== Extracting certificates and keys from the old .p12 file =====
  
 To solve the problem you can repack the .p12 file with a modern encryption. The extraction of the content must be performed on an the old host, **supporting the legacy encryption**: To solve the problem you can repack the .p12 file with a modern encryption. The extraction of the content must be performed on an the old host, **supporting the legacy encryption**:
doc/appunti/linux/sa/openvpn_openssl_problem.1744713655.txt.gz · Last modified: 2025/04/15 12:40 by niccolo