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 pitrou
Recipients barry, benjamin.peterson, christian.heimes, georg.brandl, neologix, pitrou, python-dev, sbt, vstinner
Date 2013-08-21.13:23:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Do you have a proposal for a better way to fix the issue? I don't
> think that we can hope for a fix from OpenSSL.

Instead of reseeding in the child, you can perturb the state in the parent
after fork. As far as I understand, only the "child" callback in
pthread_atfork() needs to be async-signal-safe:

"It is suggested that programs that use fork() call an exec function
very soon afterwards in the child process, thus resetting all states.
In the meantime, only a short list of async-signal-safe library
routines are promised to be available."
Date User Action Args
2013-08-21 13:23:43pitrousetrecipients: + pitrou, barry, georg.brandl, vstinner, christian.heimes, benjamin.peterson, neologix, python-dev, sbt
2013-08-21 13:23:43pitroulinkissue18747 messages
2013-08-21 13:23:42pitroucreate