mirror of
https://git.yoctoproject.org/poky
synced 2026-04-18 03:32:13 +02:00
9217de77b9
Feeding the output of /dev/urandom into /dev/random is pretty much insane and not something we should encourage. I can't really imagine a scenario where this would be a sensible idea since /dev/urandom if effectively derived from /dev/random. This changes the tool to default to /dev/hwrng which makes much more sense, feeding hardware entropy into the random pool. In the QEMU case, this will feed entropy from the host into the guests which is also what we want. Yes, this change will cause rngd not to start if /dev/hwrng isn't present, but it isn't needed if that isn't so I don't see this as a bad thing. (https://wiki.archlinux.org/index.php/Rng-tools has a section in red which agrees with the above, "this is a really bad idea, since you are simple filling the kernel entropy pool with entropy coming from the kernel itself!") (From OE-Core rev: d177516d846ec4bed483d7e9d80775bb341c869e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f1dc9ac46710814c27cae2d22e79c84a9522993a) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
QEMU Emulation Targets ====================== To simplify development, the build system supports building images to work with the QEMU emulator in system emulation mode. Several architectures are currently supported in 32 and 64 bit variants: * ARM (qemuarm + qemuarm64) * x86 (qemux86 + qemux86-64) * PowerPC (qemuppc only) * MIPS (qemumips + qemumips64) Use of the QEMU images is covered in the Yocto Project Reference Manual. The appropriate MACHINE variable value corresponding to the target is given in brackets.