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 martin.panter
Recipients christian.heimes, dstufft, martin.panter, vstinner
Date 2016-06-09.02:49:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465440543.29.0.581467319212.issue27272@psf.upfronthosting.co.za>
In-reply-to
Content
If the seed is to be based on time.time(), why not use something based on hash(time.time()) to avoid the 1/256 s resolution?

If there is a practical way to get pseudo-random data from the platform, it would be better to use that, rather than cooking up our own entropy from time.time(), PID, etc. But I guess that depends on the future of os.urandom() and friends.

In the meantime, limiting to os.urandom(256) seems reasonable, though I’m not a random number or cryptography expert.
History
Date User Action Args
2016-06-09 02:49:03martin.pantersetrecipients: + martin.panter, vstinner, christian.heimes, dstufft
2016-06-09 02:49:03martin.pantersetmessageid: <1465440543.29.0.581467319212.issue27272@psf.upfronthosting.co.za>
2016-06-09 02:49:03martin.panterlinkissue27272 messages
2016-06-09 02:49:02martin.pantercreate