Re: [lamps] draft-ietf-lamps-samples: PKCS12 expertise needed (including objects for comparison)

[Daniel Kahn Gillmor <[e-mail]>]

On Fri 2021-07-30 10:57:25 -0400, Russ Housley wrote:

> 40-bit RC2? Really?

hey, i just clicked the buttons, i didn't set any knobs!

afaict, it looks to me like the 40-bit RC2 in bob.laundered.p12 is
wrapping the certificates themselves, not the associated secret keys,
which i think are inside the pkcs-12-pkcs-8ShroudedKeyBag objects, which
are protected with pbeWithSHAAnd3-KeyTripleDES-CBC instead?

hm, looks like bob.laundered.p12 is also missing the cross-signed
intermediate CA cert, but that is probably due to operator error when i
was trying to figure out what to select in Thunderbird's certificate
manager to make the exported p12 object contain the right keys.

Seems to me like there's no need to encrypt any of the public objects
(certificates) in a PKCS12 file, and 40-bit RC2 doesn't seem that much
worse than cleartext.

do folks here think it's a bug that Keychain Access isn't capable of
reading bob.p12, but is capable of reading bob.laundered.p12?  or is
bob.p12 actually malformed in some way?

I confess i don't understand the definite length encoding vs. indefinite
encoding question.  are these both acceptable PKCS#12 structures?

     --dkg