Sean Soria <bugs.pyt...@seansoria.com> added the comment:

Because Python is not cleaning up after itself. I don't see how a 
multi-threaded app could work around this issue. The only solution I can think 
of at the app level is to reset those callbacks once python exits, but a 
different thread could call an SSL function at any point and cause the crash 
between the time that _ssl.so is unloaded and the app resets the callbacks.

One solution for Python would be to call CRYPTO_get_id_callback and 
CRYPTO_get_locking_callback and check that they're NULL before setting them. 
However, it's also stated in the documentation that id_callback doesn't need to 
be set for all platforms, so a NULL value could still be safe there. I haven't 
looked at the callbacks python is setting up, so I can't be sure this solution 
would work.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue7672>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to