Hi,
i am trying to parse a pkcs#5 encrypted pkcs#8 private
key. it is B64 encoded, with -----BEGIN ENCRYPTED
PRIVATE KEY----- as a name, but no header info, using
the following command:
openssl pkcs8 -in keyfile
i am getting an error:
Warning: broken key encoding: No Octet String in
PrivateKey
the code that is responsible for this is in
apps/pkcs8.c
if (p8inf->broken) {
BIO_printf(bio_err, "Warning: broken key encoding:
");
switch (p8inf->broken) {
case PKCS8_NO_OCTET:
BIO_printf(bio_err, "No Octet String in
PrivateKey\n");
break;
.
.
. default:
BIO_printf(bio_err, "Unknown broken type\n");
break;
}
}
namely, p8inf->broken has been set.
now, to get here, the private key HAS been
successfully decrypted in:
if (!(pkey = EVP_PKCS82PKEY(p8inf)))
(and i also parsed it by hand, and it is valid) i also
use this key in an sslplus based app. its known to be
valid.)
so, does anyone know what this NO_OCTET stuff means
and why p8inf is broken?
thanks
=====
-zeo
zeo_bartoli at yahoo
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
