Re: /dev/random blocks forever on 2.2.12 and 2.2.16

Theodore Y. Ts'o (tytso@MIT.EDU)
Tue, 8 Aug 2000 13:54:08 -0400


Date: Tue, 8 Aug 2000 19:42:39 +0200
From: "Andi Kleen" <ak@suse.de>

That wouldn't happen when you were using a secure PRNG to select the
interrupts to get data from, or ? You just have to make sure that the
PRNG initial state is not seeded from the network or anything else the
attacker could guess.

Well, the question I thought that was being asked was why wasn't the
interrupts from NIC's feeding in entropy by default into the /dev/random
pool.

I'm not sure what you mean about using a secure PRNG to select the
interrupts to get data from; there's a bootstrapping issue here, and
even if you do use a PRNG to select whether or not a particular entropy
is sampled, that decision only contributes one bit of entropy into the
pool.....

- Ted

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/