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 christian.heimes
Recipients christian.heimes, dstufft, martin.panter, tim.peters, vstinner
Date 2016-06-09.09:53:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465466007.33.0.309018608433.issue27272@psf.upfronthosting.co.za>
In-reply-to
Content
New plan:

* Add a new uint64 _Py_HashSecret.random_seed
* On 'import random' seed random.Random() from _Py_HashSecret.random_seed + gettimeofday().tv_sec + gettimeofday().tv_usec + id(self). That way subinterpreters get a different init state.

On systems with a good entropy source, _Py_HashSecret will be filled with cryptographically strong material. On early boot / VM scenarios the situation is a bit degraded but still properly good enough. It's better than to seed from a bad RNG or just from time.time().
History
Date User Action Args
2016-06-09 09:53:27christian.heimessetrecipients: + christian.heimes, tim.peters, vstinner, martin.panter, dstufft
2016-06-09 09:53:27christian.heimessetmessageid: <1465466007.33.0.309018608433.issue27272@psf.upfronthosting.co.za>
2016-06-09 09:53:27christian.heimeslinkissue27272 messages
2016-06-09 09:53:27christian.heimescreate