Really - front page? Read the comments. The bug was filed based on a packaged image for EC2. As stated there: rng-tools is not a required package for Arch.

Really - front page? Read the comments. The bug was filed based on a packaged image for EC2. As stated there: rng-tools is not a required package for Arch. edit: I understand the concern of RNGD_OPTS, but still think that if you're installing rng-tools you should likely know what you're doing with it. As stated by rng-tools: "... Using the standard open()and read() system calls, you can read random data from the hardware RNG device. This data is NOT CHECKED by any fitness tests, and could potentially be bogus (if the hardware is faulty or has been tampered with). Data is only output if the hardware "has-data" flag is set, but nevertheless a security-conscious person would run fitness tests on the data before assuming it is truly random." ...so, in all reality the flag should be unset forcing the user to select a hardware, or other RNG device. /dev/random is likely a very bad idea as a default. So is any simplified facility that caches data from places like random.org and provides it as a continuous stream of large pools of entropy? It'd be nice if a data source such as that could be used as a simplistic way to bootstrap the entropy pool on a new system.