Re: Entropy Pool Contents
- From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Nov 2006 22:40:36 +0100
Jan Engelhardt wrote:
Hornburg:~# cat /proc/sys/kernel/random/entropy_availYou really must have bad luck with your entropy...
0
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.
Disk activities are "somewhat predictable", like network traffic, and
hence are not (or should not - have not checked it) contribute to the
pool.
Well, they do, block device operations do, using the function
add_blkdev_randomness, as far as I know.
Note that urandom is the device which _always_ gives you data, and
when the pool is exhausted, returns pseudorandom data.
I know, and running on deterministically computed random values only for
days in a row is no situation I'm paticularily happy about...
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...
Greetings,
Gunter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Entropy Pool Contents
- From: Phillip Susi
- Re: Entropy Pool Contents
- References:
- Entropy Pool Contents
- From: Gunter Ohrner
- Re: Entropy Pool Contents
- From: Jan Engelhardt
- Entropy Pool Contents
- Prev by Date: Re: security: introduce file caps
- Next by Date: Re: Entropy Pool Contents
- Previous by thread: Re: Entropy Pool Contents
- Next by thread: Re: Entropy Pool Contents
- Index(es):
Relevant Pages
|
