I'm working on a project that is using X509 certs for custom uses. As a
part of this, I've experimented with teaching openssl about new OIDs, and
about new X509 extensions. I've found out some stuff I'd like to share.
First, the comment in crypto/conf/README about the oid module ("A set of
builtin modules (currently only an ASN1 non functional test module) can
be added by calling OPENSSL_load_builtin_modules().") is wrong. If your
init section (init_section in the example) contains:
oid_section = new_oids
You do get the oids in [new_oids]. And they seem to work rather well. The
only thing that would be nice is if there were a way to have both short
and long names. ;-)
Second, I have written a simple module, like the ASN.1 oid module, that
will load extension aliases. It's a config file interface for
X509V3_EXT_add_alias(), and takes a section with entries as:
name_needing_extension_method = extension_name_to_alias
or:
wasabi_extension = nsBaseUrl
to give the "wasabi_extension" OID the same extension method as nsBaseUrl.
How would I go about feeding this back to the OpenSSL project? It'd really
help us as then we just tell our customers to get binaries for version
XXX, and hand them a config file fragment.
Take care,
Bill
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]