Carl,
This is the output generated :
>openssl asn1parse -in my.key - inform der
0:d=0 hl=4 l= 672 cons: SEQUENCE
4:d=1 hl=2 l= 26 cons: SEQUENCE
6:d=2 hl=2 l= 9 prim: OBJECT :pbeWithSHA1AndDES-CBC
17:d=2 hl=2 l= 13 cons: SEQUENCE
19:d=3 hl=2 l= 8 prim: OCTET STRING [HEX DUMP]:02DC52CA3207BFA6
29:d=3 hl=2 l= 1 prim: INTEGER :64
32:d=1 hl=4 l= 640 prim: OCTET STRING [HEX
DUMP]:FE5140525758C44868E28A
C21A858B2988C91548EDF811014508A5FEB8378D541CB4C3F7F89E20B062E9DEAC534F925482A31D
548748ECA15ED9FF59B9B7E5129545328E8AC2E04785DA65C43FC4FB4C8F0BE6A98AE019A10DA2C5
...
What could you said about that?
Thanks,
Sebastien
carlyo...@keycomm.co.uk a écrit :
On Tue 16/06/09 3:09 PM , carlyo...@keycomm.co.uk sent:
Is it possible that the key was not exported as PKCS#8 and was just exported to
DER just using i2d_PrivateKey >or similar?
You can use openssl asn1parse to check:
"openssl asn1parse -in my.key -inform der"
If it is PKCS#8 exported, then you should see sequence, integer, sequence, object
(RSAEnc) and a single octet >string.
If it is exported directly, then I think you get 6 or more octet strings listed.
My memory is bad - if it is exported directly, then you get a SEQUENCE followed
by 9 integers or something from the PKCS#1 ASN.1 definition of a private key.
Carl
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
