➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients barry, benjamin.peterson, christian.heimes, georg.brandl, neologix, pitrou, python-dev, sbt, vstinner
Date 2013-08-21.12:08:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM31NVvvy=rgbX8HNdDtW=3wu6MehPQydyfiz=fVHchSEA@mail.gmail.com>
In-reply-to <1377085745.39.0.491921665481.issue18747@psf.upfronthosting.co.za>
Content 
> 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...
History
Date User Action Args
2013-08-21 12:08:26neologixsetrecipients: + neologix, barry, georg.brandl, pitrou, vstinner, christian.heimes, benjamin.peterson, python-dev, sbt
2013-08-21 12:08:26neologixlinkissue18747 messages
2013-08-21 12:08:26neologixcreate