From: Phillip Susi <psusi@cfl.rr.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: G.Ohrner@post.rwth-aachen.de, linux-kernel@vger.kernel.org
Subject: Re: Entropy Pool Contents
Date: Mon, 27 Nov 2006 13:54:59 -0500 [thread overview]
Message-ID: <456B3483.4010704@cfl.rr.com> (raw)
In-Reply-To: <456B101D.3040803@nortel.com>
Chris Friesen wrote:
> I believe the idea was that you don't want random users being able to
> artificially inflate your entropy count. So the kernel tries to make
> use of entropy entered by regular users (by stirring it into the pool)
> but it doesn't increase the entropy estimate unless root says its okay.
Why are non root users allowed write access in the first place? Can't
the pollute the entropy pool and thus actually REDUCE the amount of good
entropy? It seems to me that only root should have write access in the
first place because of this, and thus, anything root writes should
increase the entropy count since one can assume that root is supplying
good random data for the purpose of increasing the entropy count.
I was planning on just setting up a little root cron script to pull some
random data from another machine on the network to add to the local
pool, then push some random data back to the other machine to increase
its pool, but found that this doesn't work due to this restriction.
next prev parent reply other threads:[~2006-11-27 18:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 23:54 Entropy Pool Contents Gunter Ohrner
2006-11-22 23:59 ` Gunter Ohrner
2006-11-23 0:10 ` Jan Engelhardt
2006-11-23 21:40 ` Gunter Ohrner
2006-11-27 16:16 ` Phillip Susi
2006-11-27 16:19 ` Chris Friesen
2006-11-27 18:54 ` Phillip Susi [this message]
2006-11-27 19:33 ` David Wagner
2006-11-27 20:38 ` Phillip Susi
2006-11-27 20:40 ` David Wagner
2006-11-27 21:52 ` Kyle Moffett
2006-11-28 4:17 ` David Wagner
2006-11-28 5:19 ` Ben Pfaff
2006-11-28 12:13 ` Henrique de Moraes Holschuh
2006-11-28 12:58 ` David Wagner
2006-11-28 13:32 ` Eran Tromer
2006-11-28 13:15 ` Martin Mares
2006-11-28 17:22 ` Phillip Susi
2006-11-28 17:24 ` Martin Mares
2006-11-28 17:46 ` Phillip Susi
2006-11-28 17:49 ` Martin Mares
2006-11-28 18:40 ` Phillip Susi
2006-11-28 21:05 ` Martin Mares
2006-11-29 20:04 ` Phillip Susi
2006-11-28 17:42 ` Phillip Susi
2006-11-28 17:59 ` Martin Mares
2006-11-28 22:50 ` Eran Tromer
2006-11-27 22:21 ` Gunter Ohrner
2006-11-24 0:48 ` Theodore Tso
2006-11-24 1:01 ` Jeff Garzik
2006-11-23 20:54 ` Lennart Sorensen
2006-11-23 21:34 ` Gunter Ohrner
2006-11-23 21:04 ` Jeff Garzik
2006-11-23 21:43 ` Gunter Ohrner
2006-11-26 1:26 ` Folkert van Heusden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=456B3483.4010704@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=G.Ohrner@post.rwth-aachen.de \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox