On 08/07/2016 09:33 AM, Donald Stufft wrote:
On Aug 7, 2016, at 12:28 PM, Ethan Furman wrote:
Guido, not trying to change your mind, just trying to understand.
At this point we have concrete examples of the harm caused by blocking on os.urandom -- do we have any actual use-cases where it is hurtful to raise instead?
The problem we had that started this thread was SipHash initialization calling a blocking urandom by a script called by systemd prior to the point where systemd would attempt to reseed urandom from previous boots and prior to the point that systemd parallelizes the boot process.
So if we work around the problem in SipHash, the issue goes away? And does that work-around mean SipHash may not be robust for that instance of Python, but any Python process running that early should be short-lived anyway, so any security issues become vanishingly rare? -- ~Ethan~ _______________________________________________ Security-SIG mailing list [email protected] https://mail.python.org/mailman/listinfo/security-sig
