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.14:18:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465309115.08.0.157352239694.issue26839@psf.upfronthosting.co.za>
In-reply-to
Content
> I just don't understand why you are apparently not willing to even consider compromises.

I have one thing that I hold immutable here, That os.urandom should use the best interfaces provided by the OS to ensure that it always returns cryptographically random data.

I don't care if SipHash is allowed to use lesser data.
I don't care if os.urandom raises an exception or if it blocks if enough entropy isn't available.
I don't care if people are given an option that will let them maybe get bad data (but will only work on Linux or older *nixes).

All I care about is that the default behavior of os.urandom gets data that is generated using the best practices for that system, because that's what people have been told to use for years and years.
History
Date User Action Args
2016-06-07 14:18:35dstufftsetrecipients: + 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 14:18:35dstufftsetmessageid: <1465309115.08.0.157352239694.issue26839@psf.upfronthosting.co.za>
2016-06-07 14:18:35dstufftlinkissue26839 messages
2016-06-07 14:18:34dstufftcreate