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 pitrou
Recipients Arfrever, PaulMcMillan, alex, barry, benjamin.peterson, christian.heimes, dmalcolm, georg.brandl, gvanrossum, pitrou, terry.reedy, vstinner
Date 2012-01-04.02:14:54
SpamBayes Score 3.3559377e-07
Marked as misclassified No
Message-id <1325643295.39.0.0632700309253.issue13703@psf.upfronthosting.co.za>
In-reply-to
Content
For the record, here is what "man urandom" says about random seed size:

“[...] no cryptographic primitive available today can hope to promise 
more than 256  bits of  security,  so  if  any  program  reads more than 
256 bits (32 bytes) from the kernel random pool per invocation, or per 
reasonable  reseed  interval (not less than one minute), that should be
taken as a sign that its cryptography  is  not  skilfully  implemented.”

In that light, reading a 64 bytes seed from /dev/urandom is already a lot, and 4096 bytes is simply insane.
History
Date User Action Args
2012-01-04 02:14:55pitrousetrecipients: + pitrou, gvanrossum, barry, georg.brandl, terry.reedy, vstinner, christian.heimes, benjamin.peterson, Arfrever, alex, dmalcolm, PaulMcMillan
2012-01-04 02:14:55pitrousetmessageid: <1325643295.39.0.0632700309253.issue13703@psf.upfronthosting.co.za>
2012-01-04 02:14:54pitroulinkissue13703 messages
2012-01-04 02:14:54pitroucreate