Message267628
I agree with Alex here.
The documentation of ``os.urandom`` states: Return a string of n random bytes suitable for cryptographic use. However the old behavior prior to using the ``getrandom()`` call and the behavior with this patch makes that documentation a lie. It's now a string of n random bytes that may or may not be suitable for cryptographic use, but we have no idea which one it is.
No where in the documentation of ``os.urandom`` does it ever promise it will not block. In fact, on systems like FreeBSD where their /dev/urandom is better than Linuxes it always blocked on start up because that's just the way their /dev/urandom works. |
|
Date |
User |
Action |
Args |
2016-06-07 11:36:17 | dstufft | set | recipients:
+ dstufft, lemburg, rhettinger, doko, vstinner, larry, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, Lukasa, thomas-petazzoni, Colm Buckley |
2016-06-07 11:36:17 | dstufft | set | messageid: <1465299377.41.0.45258059526.issue26839@psf.upfronthosting.co.za> |
2016-06-07 11:36:17 | dstufft | link | issue26839 messages |
2016-06-07 11:36:17 | dstufft | create | |
|