多线程环境下使用openssl

openssl 官网说了：

OpenSSL can safely be used in multi-threaded applications provided that at least two callback functions are set, locking_function and threadid_func.

还有 这里说了，Openssl 是安全的，前提是必须注册两个回调函数。其中根据 Openssl 的版本不同，会有不同 版本的 threadid 回调函数。

1. Is OpenSSL thread-safe?

Yes (with limitations: an SSL connection may not concurrently be used by multiple threads). On Windows and many Unix systems, OpenSSL automatically uses the multi-threaded versions of the standard libraries. If your platform is not one of these, consult the INSTALL file.

Multi-threaded applications must provide two callback functions to OpenSSL by calling CRYPTO_set_locking_callback() and CRYPTO_set_id_callback(), for all versions of OpenSSL up to and including 0.9.8[abc...]. As of version 1.0.0, CRYPTO_set_id_callback() and associated APIs are deprecated by CRYPTO_THREADID_set_callback() and friends. This is described in the threads(3) manpage.

这里有几个例子程序，主要是在使用openssl之前，做一些初始化和设置callback函数，以及退出时的范初始化动作：

1. http://www.cs.odu.edu/~cs772/sourcecode/NSwO/compiled/common.c
2. http://ardoino.com/pub/crypto-security/sslc.c
3. http://curl.haxx.se/libcurl/c/opensslthreadlock.html
4. http://curl.haxx.se/libcurl/c/threaded-ssl.html

这里有老外推荐的3本书的链接：

Chapter 10 of the book The Definitive Guide to Linux Network Programming includes a section Thread-safe Programming with OpenSSL (on pages 255-259). This section details how OpenSSL and the pthreads library work. Specially, it tells how to setup the callback functions both in static allocation (where the number of threads are known a priori) and dynamic allocation (where threads are created and destroyed on the fly). Another good source is Section 4.1 of the book