Charles-François Natali added the comment: > Christian Heimes added the comment: > > I have taken care of Antoine's and Victor's reviews. The fix has landed in > Python 2.7, 3.3 and 3.4. What about 2.6, 3.1 and 3.2? After all it's a > security fix (although I don't consider its severity as high).
There's still the #if 0 in the patch you committed. And basically, because PySSL_RAND_atfork_child() is not async-signal safe, the interpreter is now subject to random deadlocks/crash in multi-threaded processes. I personally don't consider this a security fix... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18747> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
