Christian Heimes added the comment: Am 21.08.2013 14:08, schrieb Charles-François Natali: > 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...
Which part of the function is not async-signal safe? It doesn't interact with any file descriptors nor does it use any syscalls except for getpid() and time(). Python's _ssl module doesn't re-initialize its locks on fork. That's an outstanding issue that is not related to the change. ---------- _______________________________________ 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
