That's a useful tip, perhaps, but if the underlying calls are embedded in a third-party libraries, such as handled by cURL etc, the end user has no choice as to when they're being initialized.
Of course since multiple third-party libraries could be involved (which have no knowledge of each other), it's only possible to fix this issue in OpenSSL itself. -----Original Message----- From: Stephen Henson via RT [mailto:[email protected]] Sent: Tuesday, July 07, 2009 3:57 PM To: John Wilkinson Cc: [email protected] Subject: [openssl.org #1743] crasher due to lack of threadsafety on names_lh > [[email protected] - Tue Jul 07 22:39:32 2009]: > > Any ETA on when this will make it into the upstream? > You aren't really supposed to call SSL_library_init(), OpenSSL_add_all_algorithms() et al from multiple threads simultaneously. It should be called before starting threads. If multiple threads tried the same with shutdown they could wipe out the algorithm table for other threads. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
