If openssl pkcs12 fails with an error containing unsupported and Algorithm (RC2-40-CBC : 0), check the encryption used by the PFX archive. OpenSSL 3 supplies RC2 through its legacy provider.
Inspect the old PFX without exporting credentials
For an archive you’re authorized to inspect, load the legacy provider for this command:
openssl pkcs12 -legacy -in old.pfx -info -noout
Enter the archive password at the prompt. -info reports the archive structure and encryption algorithms. -noout suppresses certificate and key output.
If you see Mac verify error: invalid password?, check the password and try a fresh export from the source system. Keep integrity verification enabled.
Re-export with modern encryption
If the consuming application supports modern PKCS#12 encryption, re-export the identity into a fresh archive using OpenSSL 3 defaults. For a bundle with one identity, extract the leaf certificate, any intermediates you need to retain, and an encrypted PEM copy of the private key. Work in a private directory and keep the original archive for rollback.
After re-exporting, check that the new archive opens with the default provider:
openssl pkcs12 -in modern.p12 -info -noout
Compare the leaf’s SHA-256 fingerprint with the original, confirm the expected intermediates are present, and test the new archive in the application that will use it. Repacking changes the archive encryption. The certificates and their signatures stay the same.
The full PKIScope walkthrough includes the extraction, re-export, and fingerprint comparison commands.
AI was used to draft this post. The RC2 failure and re-export workflow were tested with OpenSSL 3.5.7.
Top comments (2)
-legacy 只加在检查命令上这个细节很关键,很多人会顺手把它写进日常脚本,结果一直拖着 RC2 不迁移。补充一个小点:重新导出后除了比对叶子证书 SHA-256 指纹,也值得顺手确认新档案的 MAC 算法和加密算法确实是 AES-256 而不是又落回 RC2,不然换了个壳问题还在。
Good point. Matching the leaf fingerprints confirms the certificate survived the migration. Checking the new archive’s algorithms confirms the encryption changed.
I’d run
openssl pkcs12 -in modern.p12 -info -nooutwithout-legacyand check forMAC: sha256andAES-256-CBCon both thePKCS7 Encrypted dataandShrouded Keybaglines. SHA-256 is the MAC digest, while AES-256-CBC encrypts the certificates and private key.Thanks for calling out that extra verification step.