Check out my first novel, midnight's simulacra!
OpenSSL: Difference between revisions
From dankwiki
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
==See also== | ==See also== | ||
[http://www.mail-archive.com/openssl-users@openssl.org/msg52117.html "Clarification questions on OpenSSL thread-safe support"], openssl-users mailing list 2008-03-10 | *[http://www.mail-archive.com/openssl-users@openssl.org/msg52117.html "Clarification questions on OpenSSL thread-safe support"], openssl-users mailing list 2008-03-10 | ||
[http://www.mail-archive.com/openssl-users@openssl.org/msg46161.html "When to use CRYPTO_set_locking_callback() and CRYPTO_set_id_callback()?"], openssl-users mailing list 2006-08-17 | *[http://www.mail-archive.com/openssl-users@openssl.org/msg46161.html "When to use CRYPTO_set_locking_callback() and CRYPTO_set_id_callback()?"], openssl-users mailing list 2006-08-17 | ||
Revision as of 08:19, 5 August 2009
Threads
- The threads(3ssl) man page is pretty good.
- Unless you're using OpenSSL 0.9.9, the CRYPTO_set_id_callback(3ssl) is pretty much broken on pthreads implementations which don't return an integer value from pthread_self(3). This is true for the FreeBSD native implementations (the LinuxThreads emulation package should work, but is broken in other, more grave, ways). On OpenSSL 0.9.9, CRYPTO_set_idptr_callback(3ssl) can be used for implementations which return a pointer or an aggregate.
See also
- "Clarification questions on OpenSSL thread-safe support", openssl-users mailing list 2008-03-10
- "When to use CRYPTO_set_locking_callback() and CRYPTO_set_id_callback()?", openssl-users mailing list 2006-08-17
