Message267612
| Author |
vstinner |
| Recipients |
Colm Buckley, doko, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane |
| Date |
2016年06月07日.10:01:15 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1465293676.33.0.584066409322.issue26839@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Colm Buckley: "I feel that there is no consistent way to signal to higher-level applications that the random data has sub-standard entropy; but that this at least preserves the expected semantics, and doesn't block on startup in the event of an uninitialized entropy pool."
I chose to document the behaviour of os.urandom().
Stefan Krah (msg267539): "If admins wish, they can also integrate such checks into the system startup sequence (e.g. runlevel 3 is only reached if randomness is actually available)."
Maybe need something like time.get_clock_info(), sys.float_info and sys.thread_info for os.urandom(): a string describing the implementation of os.urandom(). It would allow the developer to decide what to do when getrandom() is not used.
Reminder: getrandom() feature is specific to Linux. I understand that all other operating systems don't warn if the urandom entropy pool is not initialized yet! |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年06月07日 10:01:16 | vstinner | set | recipients:
+ vstinner, lemburg, rhettinger, doko, larry, matejcik, ned.deily, skrah, python-dev, martin.panter, ztane, thomas-petazzoni, Colm Buckley |
| 2016年06月07日 10:01:16 | vstinner | set | messageid: <1465293676.33.0.584066409322.issue26839@psf.upfronthosting.co.za> |
| 2016年06月07日 10:01:16 | vstinner | link | issue26839 messages |
| 2016年06月07日 10:01:15 | vstinner | create |
|