Thanks, Dr. Henson. I know those functions work because they perform search against those "standard" objects based on length and data fields, i.e., they don't care about sn or ln.
I guess I am trying to find out, that during the creation of X509_NAME_ENTRY, when ASN1_OBJECT is attached, why the sn, ln and nid are NOT assigned values. I can see theoretically, it is because it avoids duplicate those redundant entries. I am just curious where the missing links lie.. If you can point me out, I'd appreciate it since I've been sifting through the code but couldn't identify it by myself.. --- "Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote: > On Tue, Aug 30, 2005, Lincoln wrote: > > > Hi, > > Would any guru please take a look at this > following > > question? Thanks! > > Don't try to access the ASN1_OBJECT structures > directly. Use functions such as > OBJ_obj2nid() etc instead. > > Steve. > -- > Dr Stephen N. Henson. Email, S/MIME and PGP keys: > see homepage > OpenSSL project core developer and freelance > consultant. > Funding needed! Details on homepage. > Homepage: http://www.drh-consultancy.demon.co.uk > ______________________________________________________________________ > OpenSSL Project > http://www.openssl.org > User Support Mailing List > openssl-users@openssl.org > Automated List Manager > [EMAIL PROTECTED] > ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
