Message 267688 - Python tracker

➜

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	Colm Buckley, Lukasa, alex, christian.heimes, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date	2016年06月07日.14:59:16
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<375318ea-1783-d681-1c71-cbe6430337bb@cheimes.de>
In-reply-to	<5756DEF2.5040506@egenix.com>

Content
On 2016年06月07日 16:49, Marc-Andre Lemburg wrote: > This gives people a clear choice and doesn't cause people > to have to reconsider using the random module or wait for > Python hash randomization to initialize itself when using > Python during VM/container/system startup. > > I don't really appreciate this approach to break Python in > cloud setups just because some entropy pool is not initialized, > which only a tiny fraction of users care about. It doesn't > make Python land a better place. VM and cloud setup without a proper CPRNG source are plain broken. True fact! Secure entropy sources are a fundamental resource for all modern applications. Please start treating CPRNG like RAM, CPU or disks. You wouldn't add a workaround for broken CPU instructions to math.c or semi-functional network card to socket.c, would you?

Content

On 2016年06月07日 16:49, Marc-Andre Lemburg wrote:
> This gives people a clear choice and doesn't cause people
> to have to reconsider using the random module or wait for
> Python hash randomization to initialize itself when using
> Python during VM/container/system startup.
> 
> I don't really appreciate this approach to break Python in
> cloud setups just because some entropy pool is not initialized,
> which only a tiny fraction of users care about. It doesn't
> make Python land a better place.
VM and cloud setup without a proper CPRNG source are plain broken. True
fact!
Secure entropy sources are a fundamental resource for all modern
applications. Please start treating CPRNG like RAM, CPU or disks. You
wouldn't add a workaround for broken CPU instructions to math.c or
semi-functional network card to socket.c, would you?

History
Date	User	Action	Args
2016年06月07日 14:59:16	christian.heimes	set	recipients: + christian.heimes, lemburg, rhettinger, doko, vstinner, larry, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, dstufft, Lukasa, thomas-petazzoni, Colm Buckley
2016年06月07日 14:59:16	christian.heimes	link	issue26839 messages
2016年06月07日 14:59:16	christian.heimes	create

homepage