That is great to know because I did not know if while loading the certiicate it parses the fields and hashes or just loads it.
But any way, if I call the X509_cmp() it will do the X509_check_purpose() and I would like to avoid that by just getting the public key part and doing memcmp on it with the one already in my cache. Thanks, Joe On 1/26/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: > On Thu, Jan 26, 2006, Joe Gluck wrote: > > > That is good to know, and I assumed it will hash only once, but I want > > to skip that one time as well, and have the verification done only > > once on the certificate, and then while my application may run for a > > year, I just want to compare the public key with memcpy even without > > that one time hash, (unless that hash also is done automaticly when > > loading the cert into the X509 before calling the compare function. > > > > It isn't currently always calculated when a certifcate is loaded into an X509 > structure but you can call X509_check_purpose(cert, -1, 0) once after it has > been loaded to calculate it. > > 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 > 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]
