From: Phillip Susi <psusi@cfl.rr.com>
To: G.Ohrner@post.rwth-aachen.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Entropy Pool Contents
Date: Mon, 27 Nov 2006 11:16:19 -0500 [thread overview]
Message-ID: <456B0F53.90209@cfl.rr.com> (raw)
In-Reply-To: <ek54hf$icj$2@sea.gmane.org>
Gunter Ohrner wrote:
> IMHO something really fishy's going on there. If I explicitely write data
> into the pool, it shouldd not stay at "zero", from wwhat I understood about
> how /dev/*random work.
>
<snip>
> I'm mainly wondering why writing stuff to /dev/*random does not change the
> entropy from zero to at least any low non-zero value...
>
I ran into this the other day myself and when I investigated the kernel
code, I found that writes to /dev/random do accept the data into the
entropy pool, but do NOT update the entropy estimate. In order to do
that, you have to use a root only ioctl to add the data and update the
estimate. I am not sure why this is, or if there is a tool already
written somewhere to use this ioctl, maybe someone else can comment?
next prev parent reply other threads:[~2006-11-27 16:15 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 [this message]
2006-11-27 16:19 ` Chris Friesen
2006-11-27 18:54 ` Phillip Susi
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=456B0F53.90209@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=G.Ohrner@post.rwth-aachen.de \
--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