Hi All, We have upgraded our OpenSSL from 9.0.8b to OpenSSL 1.0.1e. We have encountered some thread issues. From releated OpenSSL document (http://www.openssl.org/docs/crypto/threads.html), we see the following description.
/CRYPTO_THREADID and associated functions were introduced in OpenSSL 1.0.0 to replace (actually, deprecate) the previous CRYPTO_set_id_callback(), CRYPTO_get_id_callback(), and CRYPTO_thread_id() functions which assumed thread IDs to always be represented by 'unsigned long'. / We haven't change all calls to CRYPTO_set_id_callback(), CRYPTO_get_id_callback(), and CRYPTO_thread_id() in our code to CRYPTO_THREADID routines. The question I would like to ask is if we upgrade OpenSSL from 9.0.8b to OpenSSL 1.0.1e without making the above suggested change what the sebsequence is? Will this cause race conditions? And do we take any rick if we decide to change all calls to CRYPTO_set_id_callback(), CRYPTO_get_id_callback(), and CRYPTO_thread_id() in our code to CRYPTO_THREADID routines? Thanks so much, Aaron -- View this message in context: http://openssl.6102.n7.nabble.com/A-Question-about-CRYPTO-THREADID-when-upgrading-to-OpenSSL-1-0-1e-tp48125.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
