[issue18747] Re-seed OpenSSL's PRNG after fork
STINNER Victor
report at bugs.python.org
Thu Aug 15 19:44:04 CEST 2013
STINNER Victor added the comment:
This issue was already discussed in the atfork issue:
http://bugs.python.org/issue16500#msg179838
See also:
http://www.openwall.com/lists/oss-security/2013/04/12/3
"I believe it is wrong to fix this in PostgreSQL. Rather, this is a
bug in the OpenSSL fork protection code. It should either install a
fork hook, or reseed the PRNG from /dev/urandom if a PID change is
detected."
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18747>
_______________________________________
More information about the Python-bugs-list
mailing list