Eric Biggers <ebiggers@xxxxxxxxxx> wrote: > From: Eric Biggers <ebiggers@xxxxxxxxxx> > > The essiv and hmac templates refuse to use any hash algorithm that has a > ->setkey() function, which includes not just algorithms that always need > a key, but also algorithms that optionally take a key. > > Previously the only optionally-keyed hash algorithms in the crypto API > were non-cryptographic algorithms like crc32, so this didn't really > matter. But that's changed with BLAKE2 support being added. BLAKE2 > should work with essiv and hmac, just like any other cryptographic hash. > > Fix this by allowing the use of both algorithms without a ->setkey() > function and algorithms that have the OPTIONAL_KEY flag set. > > Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> > --- > crypto/essiv.c | 2 +- > crypto/hmac.c | 4 ++-- > crypto/shash.c | 3 +-- > include/crypto/internal/hash.h | 6 ++++++ > 4 files changed, 10 insertions(+), 5 deletions(-) Patch applied. Thanks. -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
