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, N
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?
smime.p7s
Description: S/MIME cryptographic signature
The code below fails sometimes( it prints "error"). I
don't understand why. I have a multi threaded
application, and all the threads may be doing the
following code simultaneously. Are the functions
d2i_X509_fp and PEM_read_X509 thread safe?
The variables - x509, fp, cert_filename are local
non-st
