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 dstufft
Recipients Colm Buckley, Lukasa, alex, christian.heimes, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date 2016-06-07.13:43:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The net effect is that *all* invocations of Python will block at startup if the system RNG is blocking. The only reason this is being called out as Linux-specific is that the behavior has been noticed in Linux.

The fix is Linux specific, because all other modern OSs don't allow you to read randomness from /dev/urandom until the bool is initialized. So the problem that this ticket has exists on all platforms *by design* because every modern platform but Linux has a good implementation of /dev/urandom with regards to the behavior prior to the pool being fully initialized. IOW this patch on OpenBSD (where this syscall also exists) will cause us to try getrandom(), fail because it would have to block, then open up /dev/urandom and then.. block again because OpenBSD made reasonable choices and doesn't allow people to read bad random off it's random device.
Date User Action Args
2016-06-07 13:43:55dstufftsetrecipients: + dstufft, lemburg, rhettinger, doko, vstinner, larry, christian.heimes, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, Lukasa, thomas-petazzoni, Colm Buckley
2016-06-07 13:43:55dstufftsetmessageid: <>
2016-06-07 13:43:55dstufftlinkissue26839 messages
2016-06-07 13:43:55dstufftcreate