Message267932
| Author | ncoghlan |
|---|---|
| Recipients | Lukasa, alex, christian.heimes, dstufft, lemburg, ncoghlan, vstinner |
| Date | 2016-06-08.23:46:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1465429609.74.0.0532338312882.issue27250@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
One request I'd make in these discussions is that we avoid using the term "block" - it makes people think of the /dev/random behaviour (i.e. blocking intermittently and unhelpfully), rather than the usually-desired "wait for sufficient entropy on system startup" behaviour.
I'd also request that we keep in mind that any Linux user always remains free to write the 3-line utility function:
def read_urandom(num_bytes):
with open('/dev/urandom', 'rb') as urandom:
return urandom.read(num_bytes)
If they want to get precisely the Linux /dev/urandom semantics, and not a Python level abstraction that provides the same kinds of assurances offered by other *nix platforms. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-06-08 23:46:49 | ncoghlan | set | recipients: + ncoghlan, lemburg, vstinner, christian.heimes, alex, dstufft, Lukasa |
| 2016-06-08 23:46:49 | ncoghlan | set | messageid: <1465429609.74.0.0532338312882.issue27250@psf.upfronthosting.co.za> |
| 2016-06-08 23:46:49 | ncoghlan | link | issue27250 messages |
| 2016-06-08 23:46:49 | ncoghlan | create | |