I understand that I need to provide locking callbacks with CRYPTO_set_locking_callback() and CRYPTO_set_id_callback(), in the case where more than one thread will be concurrently accessing OpenSSL library. However, is this necessary if my code will do its own serializing of access to OpenSSL, such that no more than one thread will ever be accessing OpenSSL at the same time? (Different threads will be used, but not necessarily concurrently. And the OpenSSL data structures will be shared between threads.) I'm assuming that this is correct, since it makes sense, but I'd just like to confirm it before I go do something wrong.
Thanks. Chuck Wells ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
