Sandy Harris <sandyinchina@xxxxxxxxx> wrote: > The biggest problem with random(4) is that you cannot generate good > output without a good seed & just after boot, ... > > The only really good solution I know of is to find a way to provide a > chunk of randomness early in the boot process. John Denker has a good > discussion of doing this by modifying the kernel image & Ted talks of > doing it via the boot loader. ... Would it be enough to have a kernel module that does more-or-less what the current shell scripts do, but earlier in the boot process? Throw the stored data into the random(4) driver at module init time & update it periodically later. This would not help much for first boot on a new system, unless its store could be updated during install; Denker's point that you need each system provisioned differently is important. However it looks like it would be enough on other boots. It also looks like it might be easier to implement & test. In particular it is an isolated do-one-thing-well tool; the programmer only needs to worry about his or her module, not several different boot loaders or the procedures that distros have for CD images or manufacturers for device setup.
