Patrick wrote:
>
> Update and correction:
> rsadsi OBJECT IDENTIFIER ::= {iso(1) member-body(2) us(840) rsadsi(113549)}
> *does* translate to "1.2.840.113549"
> Moreover the complete OID from RSA PK12 doc is: 1.2.840.113549.1.12.1.3
> But still, why do I get a different using NSS' secoid.c?
>
> -- P
>
> "Patrick" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > I'm trying to figure what the numbers (decimal format) would be for the
> > object with tag SEC_OID_PKCS12_V2_PBE_WITH_SHA1_AND_3KEY_TRIPLE_DES_CBC
> >
> > Looking at NSS' secoid.c code, I compute:
> > 42.134.72.134.247.13.1.12.1.3
> >
> > However looking at RSA labs PKCS#12 document, I compute:
> > 1.2.840.113549.1.12.0.1.1.3
> >
The NSS stuff looks like the contents octets of the ASN1 OBJECT
IDENTIFIER. Check out the laymans guide to ASN1 on RSAs site for info on
the encoding rules.
OpenSSL also stores the content octets internally in this form in
obj_dat.h . If you take the entry for that OID you get:
0x2A,0x86,0x48,0x86,0xF7,0x0D,0x01,0x0C,0x01,0x03
which may look familiar :-)
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Gemplus: http://www.gemplus.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
