summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2019-03-31 13:04:21 -0700
committerHerbert Xu <herbert@gondor.apana.org.au>2019-04-08 14:42:55 +0800
commitf6e9af87661530e60d9faf1d96675e8f22127aa8 (patch)
tree0d273a53ba49e083e33abc022172b6653e743b36 /tools
parentc31a871985cac1a594a7e61e7ab808c0f81845ee (diff)
downloadlinux-stable-f6e9af87661530e60d9faf1d96675e8f22127aa8.tar.gz
linux-stable-f6e9af87661530e60d9faf1d96675e8f22127aa8.tar.bz2
linux-stable-f6e9af87661530e60d9faf1d96675e8f22127aa8.zip
crypto: arm64/cbcmac - handle empty messages in same way as template
My patches to make testmgr fuzz algorithms against their generic implementation detected that the arm64 implementations of "cbcmac(aes)" handle empty messages differently from the cbcmac template. Namely, the arm64 implementations return the encrypted initial value, but the cbcmac template returns the initial value directly. This isn't actually a meaningful case because any user of cbcmac needs to prepend the message length, as CCM does; otherwise it's insecure. However, we should keep the behavior consistent; at the very least this makes testing easier. Do it the easy way, which is to change the arm64 implementations to have the same behavior as the cbcmac template. For what it's worth, ghash does things essentially the same way: it returns its initial value when given an empty message, even though in practice ghash is never passed an empty message. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions