I think i found the answer to this. The responsibility is lied within the application. The app should setup its own list of locks, possibly above and beyond the CRYPTO_NUM_LOCKS. And then provide appropriate routines to pass to the following: CRYPTO_set_locking_callback CRYPTO_set_dynlock_create_callback CRYPTO_set_dynlock_lock_callback CRYPTO_set_dynlock_destroy_callback
The desired lock type is passed in the struct CRYPTO_dynlock_value * parameter to the cusom dynlock_lock_callback. On 10-08-09 09:18 AM, Jeff Saremi wrote: > In my engine, i'd like to use a new lock for a set of operations. This > lock is not CRYPTO_LOCK_ENGINE or any other defined ones. > Is there any way in OpenSSL to define a say user lock (type) and then > use CRYPTO_Lock function on it? > What would happen to CRYPTO_NUM_LOCKS? would that increase by way of > defining and adding this lock? > > thanks > jeff > > > > This email contains Morega Systems Inc. Privileged and Confidential > information. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org This email contains Morega Systems Inc. Privileged and Confidential information. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org