diff options
author | Hauke Mehrtens <hauke@hauke-m.de> | 2023-04-22 15:28:01 +0200 |
---|---|---|
committer | Hauke Mehrtens <hauke@hauke-m.de> | 2023-04-29 12:35:44 +0200 |
commit | 2bab7d273e02bb463c121233d5d7e74157844305 (patch) | |
tree | 7df8162dfd16713c899e9e68061ef5be5defd890 /target/linux/uml | |
parent | 1c5cafa3ebcb6427e95f221eec3ffe27bc7a76c9 (diff) | |
download | upstream-2bab7d273e02bb463c121233d5d7e74157844305.tar.gz upstream-2bab7d273e02bb463c121233d5d7e74157844305.tar.bz2 upstream-2bab7d273e02bb463c121233d5d7e74157844305.zip |
kernel: Initialize RNG using CPU RNG and bootloader
This activates the following kernel options by default:
* CONFIG_RANDOM_TRUST_CPU
* CONFIG_RANDOM_TRUST_BOOTLOADER
With these option Linux will also use data from the CPU RNG e.g. RDRAND
and the bootloader to initialize the Linux RNG if such sources are
available.
These random bits are used in addition to the other sources, no other
sources are getting deactivated. I read that the Chacha mixer isn't
vulnerable to injected entropy, so this should not be a problem even if
these sources might inject bad random data.
The Linux kernel suggests to activate both options, Debian also
activates them. This does not increase kernel code size.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Diffstat (limited to 'target/linux/uml')
0 files changed, 0 insertions, 0 deletions