> > >> Do you provide mutexes to the library? For multi-threaded applications,
> > >> the following calls are required in initialization:
> > >>
> > >> CRYPTO_set_id_callback(id_callback);
> > >> CRYPTO_set_locking_callback(locking_callback);
I have a question that seem obvious to me but is not dealt with in the
code. If you have an application that loads OpenSSL as a dynamic
or shared library, how is the application supposed to know how many
locks to create?
The application can't use CRYPTO_NUM_LOCKS as the method for
determining the value since this number can change with each release
of OpenSSL. It seems to me that a function is needed to provide
this number to the application.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]