On Mon, 25 Sep 2000, Michael Str�der wrote:
> Jean-Marc Desperrier wrote:
> >
> > No official central regitry, yes, but at least there is this
> > non-official one :
> > http://www.alvestrand.no/objectid/
>
> Thank you. I already knew that one.
>
> > It's quite complete, while sure not comprehensive.
>
> The problem is that not the vendors itself add their entries but
> normal users enter what they believe is the name and ASN.1 syntax.
>
> Example: Can someone give me the complete ASN.1 syntax of
> entrustVersInfo (OID 1.2.840.113533.7.65.0)? E.g. alvestrand.no
> says:
>
> entrustVersInfo EXTENSION ::= {
> SYNTAX EntrustVersInfoSyntax
> IDENTIFIED BY { id-nsn-ext 0}
> }
>
> EntrustVersInfoSyntax ::= OCTET STRING
>
> But according to the ASN.1 parser I'm using it seems to be a
> SEQUENCE of a string containing the version (e.g. "V4.0") and a BIT
> STRING containing some flags.
>
> See output of Peter Gutmann's dumpasn1:
>
> : SEQUENCE {
> 564 06 9: OBJECT IDENTIFIER
> : entrustVersInfo (1 2 840 113533 7 65 0)
> 575 04 12: OCTET STRING, encapsulates {
> 577 30 10: SEQUENCE {
> 579 1B 4: GeneralString 'V4.0'
> 585 03 2: BIT STRING 4 unused bits
> : '1001'B
> : }
> : }
> : }
> : }
> : }
> : }
Well.... alvestrand.no is right on this one.... You can see it in your
dump... The SEQUENCE is encapsulated in an OCTET STRING...
What you would like is the internal format of this OCTET STRING... Just
ask Entrust...
How could you force anyone to describe the internal format of every
structure they use? Don't even think of it...
--
Erwann ABALEA
System and Development Engineer - Certplus SA
[EMAIL PROTECTED]
- RSA PGP Key ID: 0x2D0EABD5 -
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
