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-x86_64-asm.S	[CRYPTO] Add x86_64 asm AES	2005-07-06 13:55:00 -07:00
aes.c	[CRYPTO] aes: Fixed array boundary violation	2006-03-21 20:14:10 +11:00
Makefile	[CRYPTO] Add x86_64 asm AES	2005-07-06 13:55:00 -07:00