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 brett.cannon, dstufft, ned.deily
Date 2016-06-10.19:56:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465588599.3.0.867244099768.issue27288@psf.upfronthosting.co.za>
In-reply-to
Content
In 3.5.0 and 3.5.1 os.urandom will, where available, use the getrandom() to block rather than get insecure random from the urandom pool on Linux. In 3.5.2 this change is reverted so that os.urandom will return possibly predictable random numbers instead of blocking waiting for /dev/urandom to be intialized.

However, secrets.py is a module which is explicitly for getting cryptographically safe data for, and reverting that change means that the functions in this module are no longer cryptographically safe on Linux if they are called early enough in the boot process. Thus, secrets.py should be modified so that it no longer uses os.urandom on systems where there is a better source of randomness available-- namely getrandom() set to block on Linux.
History
Date User Action Args
2016-06-10 19:56:39dstufftsetrecipients: + dstufft, brett.cannon, ned.deily
2016-06-10 19:56:39dstufftsetmessageid: <1465588599.3.0.867244099768.issue27288@psf.upfronthosting.co.za>
2016-06-10 19:56:39dstufftlinkissue27288 messages
2016-06-10 19:56:38dstufftcreate