➜

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 Gabriel Corona
Recipients Arfrever, BreamoreBoy, Gabriel Corona, Jeffrey.Walton, barry, benjamin.peterson, christian.heimes, georg.brandl, larry, neologix, pitrou, python-dev, sbt, vajrasky, vstinner
Date 2019-01-04.20:39:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1546634377.87.0.452922534853.issue18747@roundup.psfhosted.org>
In-reply-to
Content 
Now that the default PRNG of the 'random' package is automatically reseeded at fork, wouldn't it make sense to reseed the OpenSSL seed as well?

(At the same time the OpenSSL wiki states [1] that "The situation has changed greatly, starting with OpenSSL 1.1.1 which completely rewrote RNG. The concerns [of fork unsafety] do not really apply any more".)

[1] https://wiki.openssl.org/index.php/Random_fork-safety
History
Date User Action Args
2019-01-04 20:39:39Gabriel Coronasetrecipients: + Gabriel Corona, barry, georg.brandl, pitrou, vstinner, larry, christian.heimes, benjamin.peterson, Arfrever, neologix, BreamoreBoy, python-dev, sbt, vajrasky, Jeffrey.Walton
2019-01-04 20:39:37Gabriel Coronasetmessageid: <1546634377.87.0.452922534853.issue18747@roundup.psfhosted.org>
2019-01-04 20:39:37Gabriel Coronalinkissue18747 messages
2019-01-04 20:39:37Gabriel Coronacreate