> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Levitte - VMS
> Whacker
> Sent: den 25 september 2000 23:14
> To: [EMAIL PROTECTED]
> Subject: Objects and a configuration file
>
> [...]
>
> I'm definitely willing to redesign the contents of objects.txt, and am
> currently looking for ideas. I'm pondering regular LDAP schema
> entries as shown in RFC2256, or something similar to Peter Gutmanns
> config file for dumpasn1, or maybe something different. There's also
> the format used by some OpenSSL utilities which is very simple (OID
> followed by a "shortname" optionally followed by a "longname").
>
> Comments?
Disclaimer: knowing next to nothing about the upcoming ASN.1 engine
changes, there's probably much more to it than meets my eye at the moment.
Anyway:
Would it not be 'a good thing' to eventually be able to use the actual
X.500 (520, RFC 2560, PKCS#1 etc., etc.) ASN.1 modules themselves, thus
alleviating the need for a 'proprietary' set of configuration data to be
kept current?
Granted, it would require that OpenSSL were made a full-fledged ASN.1
compiler.
As for the issue currently at hand however, the string representations
that is, I guess we'd need some kind of BNF encoding/parsing lib as well,
seeing as that's the mechanism employed in RFC 2256. :-/
Just a thought,
//oscar
smime.p7s
