linux-yocto/fs/verity
Eric Biggers a19bcde499 Revert "fsverity: relax build time dependency on CRYPTO_SHA256"
This reverts commit e3a606f2c5 because it
allows people to create broken configurations that enable FS_VERITY but
not SHA-256 support.

The commit did allow people to disable the generic SHA-256
implementation when it's not needed.  But that at best allowed saving a
bit of code.  In the real world people are unlikely to intentionally and
correctly make such a tweak anyway, as they tend to just be confused by
what all the different crypto kconfig options mean.

Of course we really need the crypto API to enable the correct
implementations automatically, but that's for a later fix.

Acked-by: Ard Biesheuvel <ardb@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Link: https://lore.kernel.org/r/20250217185105.26751-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
2025-02-17 11:34:15 -08:00
..
enable.c
fsverity_private.h
hash_algs.c
init.c treewide: const qualify ctl_tables where applicable 2025-01-28 13:48:37 +01:00
Kconfig Revert "fsverity: relax build time dependency on CRYPTO_SHA256" 2025-02-17 11:34:15 -08:00
Makefile
measure.c bpf: treewide: Align kfunc signatures to prog point-of-view 2024-06-12 11:01:31 -07:00
open.c
read_metadata.c
signature.c fsverity: expose verified fsverity built-in signatures to LSMs 2024-08-20 14:03:18 -04:00
verify.c