I've used DC-based naming (RFC 2377?) for a while now, and can't really remember running in to any particular problems.
I generate the certificates using the OpenSSL command line apps using a configuration like this: [ OJ_req_distinguished_name ] 0.domainComponent = TLD component (eg. com, net, org) 0.domainComponent_default = example 1.domainComponent = Second level domain component 1.domainComponent_default = acme 2.domainComponent = Third level domain component 2.domainComponent_default = www ... Having them in obj_mac.h should mean they are recognized by default, shouldn't it? I'm not sure exactly what a_strnid.c does, but it looks like a collection of convenience functions. I'm sure DC could be added, as long as some kind soul could point out what its upper bound and string type are. Bear Giles wrote: > > Oops. The information *is* in <obj_mac.h>, even if it's unused. > > But again, shouldn't this be in crypto/asn1/a_strnid.c (and elsewhere) > so it's recognized by default? > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
