zhu qun-ying wrote:
>
> I am actually quite new to the Crypto world, just about 2 months. While reading
> Peter Gutmann's article on breaking PKCS#12 formatted file, I am wondering is
> the implementation of OpenSSL's PKCS#12 routines subject to the same attack.
> What's the most secure format could be used under OpenSSL to protect private
> key, compatibility with others is not a concern here. While the cryptlib using
> PKCS#15 to store the private key, is OpenSSL have some plan on it?
>
I supplied some of the info for that article and I wrote PKCS#12 for
OpenSSL so I'd say yes OpenSSL PKCS#12 implementation is reasonably
secure with the usual precautions, i.e. not picking obvious or guessable
passwords.
OpenSSLs implementation uses high mac and encryption iteration counts
and strong encryption of private keys.
Wrt PKCS#15. Its an evil thing to implement in OpenSSL ASN1 and its very
new.
If its use became more widespread (e.g. Netscape, IE) for this purpose
then maybe at some point in the future support could be added. But well
after the ASN1 gets revised.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
