On Tue, Jun 16, 2009, Sbastien PIAU wrote: > 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? >
If that is the real key then you just posted it to a public mailing list. Fortunately the output is truncated and the first bit is just the public key components. It is encrypted but with a weak key. It is PKCS#8 encrypted private key format. You should be able to access it with: openssl pkcs8 -inform DER -in my.key you will need the password. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
