mirror of
https://github.com/torvalds/linux.git
synced 2024-11-24 21:21:41 +00:00
fcd7c26901
The two existing trusted key sources don't make use of the kernel RNG, but instead let the hardware doing the sealing/unsealing also generate the random key material. However, both users and future backends may want to place less trust into the quality of the trust source's random number generator and instead reuse the kernel entropy pool, which can be seeded from multiple entropy sources. Make this possible by adding a new trusted.rng parameter, that will force use of the kernel RNG. In its absence, it's up to the trust source to decide, which random numbers to use, maintaining the existing behavior. Suggested-by: Jarkko Sakkinen <jarkko@kernel.org> Acked-by: Sumit Garg <sumit.garg@linaro.org> Acked-by: Pankaj Gupta <pankaj.gupta@nxp.com> Reviewed-by: David Gstir <david@sigma-star.at> Reviewed-by: Pankaj Gupta <pankaj.gupta@nxp.com> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org> Tested-by: Pankaj Gupta <pankaj.gupta@nxp.com> Tested-by: Michael Walle <michael@walle.cc> # on ls1028a (non-E and E) Tested-by: John Ernberg <john.ernberg@actia.se> # iMX8QXP Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org> |
||
---|---|---|
.. | ||
asymmetric-parser.h | ||
asymmetric-subtype.h | ||
asymmetric-type.h | ||
big_key-type.h | ||
ceph-type.h | ||
dns_resolver-type.h | ||
encrypted-type.h | ||
keyring-type.h | ||
request_key_auth-type.h | ||
rxrpc-type.h | ||
system_keyring.h | ||
trusted_tee.h | ||
trusted_tpm.h | ||
trusted-type.h | ||
user-type.h |