Messages in this thread | | | Date | Mon, 9 Sep 2002 14:57:34 -0500 | From | Oliver Xymoron <> | Subject | Re: [PATCH] (0/4) Entropy accounting fixes |
| |
On Mon, Sep 09, 2002 at 02:54:51PM -0400, Kent Borg wrote: > Most of this thread is about on-going sources of entropy, but what > about initial state? Yes, distributions such as Red Hat save the pool > when shutting down and restore it on booting. But what about initial > initial state? What about those poor headless servers that get built > by Kickstart? What about the individual blades in a server? What > about poor embedded routers that are really impoverished: Nothing but > a CPU, timers, ethernet hardware, and ROM. And DRAM! > > Why not use the power-on state of DRAM as a source of initial pool > entropy?
There's actually not a lot there, and what is there is not random, but rather a rapidly fading "ghost" of what was there last. And for most folks, this gets wiped by POST or the kernel long before the RNG gets its hands on it.
Nonetheless, there's no reason not to take whatever state we get when we allocate our pool. Amusingly, the current code needlessly zeroes out its pool before using it - twice! I've already fixed this in my patches.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |