Uh oh!
There was an error while loading. Please reload this page.
Encrypt PKCS#8 keys when a cipher is set on the PrivateKeyInfo encoder - #453
Conversation
ac3f5e5 to
87304bcCompare87304bc to
736e81fCompare27cb2e5 to
b266849Compare6566c83 to
f821937CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
padelsbach
left a comment
There was a problem hiding this comment.
Would prefer if we had an actual command line test as shown in the PR description, but can be a follow up
aidangarske
commented
Aug 3, 2026
I agree let me add that |
a809327 to
86e10e4Compare86e10e4 to
ba4b462Comparepadelsbach
commented
Aug 4, 2026
LGTM, let's give @ColtonWilley a chance to look at this one |
openssl pkey -aes256silently wrote unencrypted private keys forEC, Ed25519, X25519, DH and ML-DSA(RSA was fine) because the encoders only encrypted when the caller explicitly asked for theEncryptedPrivateKeyInfostructure, ignoring a cipher set on the ordinaryPrivateKeyInfopath now they encrypt whenever a cipher is set plus a DH fix so generated keys don't encode an empty private value.CLI-testing the new SLH-DSA encoders using
openssl pkey -aes256emittedBEGIN PRIVATE KEYinstead ofBEGIN ENCRYPTED PRIVATE KEYAdded PKCS8 openssl scripts testing