> From: owner-openssl-us...@openssl.org On Behalf Of Kyle Hamilton > Sent: Saturday, 29 May, 2010 14:24
> Don't forget to call SSL_load_error_strings() and > CRYPTO_load_error_strings() just after you initialize the library for > this to work. 1. There is no CRYPTO_load_error_strings. There is ERR_load_crypto_strings and ERR_load_SSL_strings, and SSL_load_error_strings does (exactly) both of those, which is a good idea for *all* openssl apps. But: 2. This *particular* routine (X509_verify_cert_error_string) *doesn't* use the errstring mechanism and doesn't depend on loading. It's in x509_txt.c NOT x509_err.c. Maybe it should, but that's a different question. > > On Fri, May 28, 2010 at 3:14 PM, Dave Thompson > <dthomp...@prinpay.com> wrote: > >>> From: owner-openssl-us...@openssl.org On Behalf Of Dallas Clement > >>> Sent: Wednesday, 26 May, 2010 22:03 > >> > >>> Is there a function that translates certificate verify > return codes? > >> > >> x509.h, x509/x509_txt.c > >> const char *X509_verify_cert_error_string(long n) > >> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
