Eric Biggers 79bd202987 crypto: hash - annotate algorithms taking optional key ... commit a208fa8f33031b9e0aba44c7d1b7e68eb0cbd29e upstream. We need to consistently enforce that keyed hashes cannot be used without setting the key. To do this we need a reliable way to determine whether a given hash algorithm is keyed or not. AF_ALG currently does this by checking for the presence of a ->setkey() method. However, this is actually slightly broken because the CRC-32 algorithms implement ->setkey() but can also be used without a key. (The CRC-32 "key" is not actually a cryptographic key but rather represents the initial state. If not overridden, then a default initial state is used.) Prepare to fix this by introducing a flag CRYPTO_ALG_OPTIONAL_KEY which indicates that the algorithm has a ->setkey() method, but it is not required to be called. Then set it on all the CRC-32 algorithms. The same also applies to the Adler-32 implementation in Lustre. Also, the cryptd and mcryptd templates have to pass through the flag from their underlying algorithm. Change-Id: Ie0547047b828f276d967e8979cd9176e57c99ac8 Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> [bwh: Backported to 3.2: - Drop changes to nonexistent drivers - There's no CRYPTO_ALG_INTERNAL flag - Adjust filenames] Signed-off-by: Ben Hutchings <ben@decadent.org.uk>		2019-07-27 21:49:17 +02:00
..
boot
configs
crypto	crypto: hash - annotate algorithms taking optional key	2019-07-27 21:49:17 +02:00
include	Safer ABI for O_TMPFILE	2018-12-03 11:52:36 +01:00
kernel	mm: larger stack guard gap, between vmas	2017-07-11 00:00:39 +00:00
lib
math-emu
mm	mm: larger stack guard gap, between vmas	2017-07-11 00:00:39 +00:00
net
oprofile
power
prom
Kbuild
Kconfig
Kconfig.debug
Makefile