34679ec7a0
The khwrngd thread is started when a hwrng device of sufficient quality is registered. The virtio-rng device is backed by the hypervisor, and we trust the hypervisor to provide real entropy. A malicious or badly-implemented hypervisor is a scenario that's irrelevant -- such a setup is bound to cause all sorts of badness, and a compromised hwrng is the least of the user's worries. Given this, we might as well assume that the quality of randomness we receive is perfectly trustworthy. Hence, we use 100% for the factor, indicating maximum confidence in the source. Signed-off-by: Amit Shah <amit.shah@redhat.com> Reviewed-by: H. Peter Anvin <hpa@linux.intel.com> Reviewed-by: Amos Kong <akong@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
amd-rng.c | ||
atmel-rng.c | ||
bcm63xx-rng.c | ||
bcm2835-rng.c | ||
core.c | ||
exynos-rng.c | ||
geode-rng.c | ||
intel-rng.c | ||
ixp4xx-rng.c | ||
msm-rng.c | ||
mxc-rnga.c | ||
n2-asm.S | ||
n2-drv.c | ||
n2rng.h | ||
nomadik-rng.c | ||
octeon-rng.c | ||
omap-rng.c | ||
omap3-rom-rng.c | ||
pasemi-rng.c | ||
powernv-rng.c | ||
ppc4xx-rng.c | ||
pseries-rng.c | ||
timeriomem-rng.c | ||
tpm-rng.c | ||
tx4939-rng.c | ||
via-rng.c | ||
virtio-rng.c |