Author ssoria
Recipients janssen, loewis, ssoria
Date 2010-01-10.23:37:20
SpamBayes Score 1.1449e-10
Marked as misclassified No
Message-id <>
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 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.
Date User Action Args
2010-01-10 23:37:22ssoriasetrecipients: + ssoria, loewis, janssen
2010-01-10 23:37:22ssoriasetmessageid: <>
2010-01-10 23:37:20ssorialinkissue7672 messages
2010-01-10 23:37:20ssoriacreate