Re: Security considerations of "openssl pkcs12 -export -legacy"
Viktor Dukhovni <[email protected]>
| Newsgroups | gmane.comp.encryption.openssl.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, May 20, 2025 at 08:45:22PM +0000, Wall, Stephen wrote:
> What are the ramifications of using the “-legacy” options to “pkcs12
> -export” from a security perspective? I’ve been told by another
> engineer that older versions of Android (10, 11) are not able to parse
> the format that OpenSSL 3 defaults to, and am considering implementing
> an option to allow users to export PKCS12 files using the older
> format, but I’m concerned with how bad of a security risk that is. It
> doesn’t seem like Sweet32 is really applicable, as that requires large
> amounts of data to exercise. Is there a real vulnerability here that
> could compromise users private keys?
[ Off the cuff response, not deeply analysed. ]
If the passphrase has sufficient entropy to not require much PBKDF2
hardening against brute-force attacks, then in legacy mode you get
roughly 112-bit security via 3DES-CBC which should be sufficient to
protect typical private keys.
--
Viktor.
--
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/aC1QvMljbNhOkhW6%40chardros.imrryr.org.