Frank Balluffi wrote:
>
> Steve,
>
> If the decoder possesses meta data, it would be nice for the decoder to
> report the location and cause of errors. For example, if the third
> extension in a certificate contained the illegal object identifier value
> 1.99999.3.4, the decoder could report the equivalent of something like:
>
> "Bad object identifier value in first element of SEQUENCE in third element
> of SEQUENCE OF in tenth element of SEQUENCE in first element of SEQUENCE."
> [I think I got that right.]
>
> If the meta data included the ASN.1 text, the decoder could even describe
> the location in ASN.1.
>
One of the options is to include field names in the structures. If it
had a problem with an extension OID it might indicate a problem with,
say, field "object" in first element of "extensions" in field
"cert_info" in structure "X509".
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
