OpenSSL P12 Certificates

OpenSSL 3.0 moved several deprecated or insecure algorithms into an internal library module called legacy provider. It is not loaded by default, so apps (or their language runtimes) that use OpenSSL for cryptographic operations cannot use such algorithms when loading certificates, creating message digests ...

 

For security reasons, it is strongly recommended to retire the use of these legacy algorithms.

 

If your application utilizes client certificates stored in a file encrypted with a legacy cipher such as RC2-40-CBC, it is possible to "modernize" the certificate file by re-encrypting it using the openssl program.

 

For example, if you have a client.p12 (or client.pfx) certificate file on your local computer:

 

$ openssl pkcs12 -legacy -in client.p12 -nodes -out cert-decrypted.tmp
(enter passphrases if prompted)


$ openssl pkcs12 -in cert-decrypted.tmp -export -out client-new.p12
(enter passphrases if prompted)


$ rm cert-decrypted.tmp

 

The exported client-new.p12 certificate file now contains the same keys, but encrypted using AES-256-CBC.

 

Check below the configuration for sgcWebSockets and sgcIndy packages:

 

sgcWebSockets

 

 

sgcIndy