Yes, I have set up the call-backs exactly as in
crypto\threads\mttest.c
The problem seems to be going away when the replace
the
fseek with fclose and fopen the file again. Does this
sound weird? (considering that all threads may be
executing this code simultaneously).
if(!(x509=d2i_X509_fp(fp, NULL))) {
fseek(fp, 0,SEEK_SET);
x509 = PEM_read_X509( fp, NULL, NULL, NULL );
}
--- Joseph Bruni <[EMAIL PROTECTED]> wrote:
> Did you set up your mutex call-backs needed by the
> library? See the
> man page for CRYPTO_set_locking_callback, et al for
> details.
>
> -joe
>
>
> On May 6, 2005, at 8:56 AM, Calista wrote:
>
> > Are the functions
> > d2i_X509_fp and PEM_read_X509 thread safe?
>
>
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
