android_kernel_xiaomi_sm8350/crypto
David McCullough 55e9dce37d [CRYPTO] aes: Fixed array boundary violation
The AES setkey routine writes 64 bytes to the E_KEY area even though
there are only 60 bytes there.  It is in fact safe since E_KEY is
immediately follwed by D_KEY which is initialised afterwards.  However,
doing this may trigger undefined behaviour and makes Coverity unhappy.

So by combining E_KEY and D_KEY into one array we sidestep this issue
altogether.

This problem was reported by Adrian Bunk.

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2006-03-21 20:14:10 +11:00
..
aes.c [CRYPTO] aes: Fixed array boundary violation 2006-03-21 20:14:10 +11:00
anubis.c
api.c [CRYPTO] all: Use kzalloc where possible 2006-03-21 20:14:08 +11:00
arc4.c
blowfish.c
cast5.c
cast6.c
cipher.c
compress.c
crc32c.c
crypto_null.c
deflate.c [CRYPTO] all: Use kzalloc where possible 2006-03-21 20:14:08 +11:00
des.c [CRYPTO] all: Add missing cra_alignmask 2006-03-21 20:14:09 +11:00
digest.c
hmac.c
internal.h
Kconfig
khazad.c
Makefile
md4.c
md5.c
michael_mic.c
proc.c
scatterwalk.c
scatterwalk.h
serpent.c [CRYPTO] all: Add missing cra_alignmask 2006-03-21 20:14:09 +11:00
sha1.c
sha256.c
sha512.c
tcrypt.c
tcrypt.h [CRYPTO] tcrypt: Fix key alignment 2006-03-21 20:14:09 +11:00
tea.c
tgr192.c
twofish.c
wp512.c