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 Colm Buckley
Recipients Colm Buckley, doko, larry, lemburg, martin.panter, matejcik, ned.deily, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date 2016-06-06.20:45:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@larry -

Thank you for joining in. I'm uploading a third version of the patch (against clean 3.5.1 source, with correct whitespace and a less confusing comment) which implements the following:

* / : looks for linux/random.h and sets HAVE_LINUX_RANDOM_H if present.

* random.c : calls getrandom() with the GRND_NONBLOCK flag; if that fails, fall back to reading /dev/urandom which will have insufficient entropy but will at least return some data.

I feel that there is no consistent way to signal to higher-level applications that the random data has sub-standard entropy; but that this at least preserves the expected semantics, and doesn't block on startup in the event of an uninitialized entropy pool.
Date User Action Args
2016-06-06 20:45:55Colm Buckleysetrecipients: + Colm Buckley, lemburg, rhettinger, doko, vstinner, larry, matejcik, ned.deily, skrah, martin.panter, ztane, thomas-petazzoni
2016-06-06 20:45:55Colm Buckleysetmessageid: <>
2016-06-06 20:45:55Colm Buckleylinkissue26839 messages
2016-06-06 20:45:55Colm Buckleycreate