Eric Biggers a208fa8f33 crypto: hash - annotate algorithms taking optional key ... 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. Cc: stable@vger.kernel.org Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>		2018-01-12 23:03:35 +11:00
..
aes_asm.S
aes_glue.c
camellia_asm.S
camellia_glue.c
crc32c_asm.S
crc32c_glue.c	crypto: hash - annotate algorithms taking optional key	2018-01-12 23:03:35 +11:00
crop_devid.c
des_asm.S
des_glue.c
Makefile
md5_asm.S
md5_glue.c
opcodes.h
sha1_asm.S
sha1_glue.c
sha256_asm.S
sha256_glue.c
sha512_asm.S
sha512_glue.c