diff options
| author | David McCullough <david_mccullough@au.securecomputing.com> | 2006-03-15 21:08:51 +1100 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2006-03-21 20:14:10 +1100 |
| commit | b4c49c5e6eb2d8f7cb095b5eed430158d9f095ea (patch) | |
| tree | 08c32b8a4dcdd2ba4de824400cdf468289f9010d /crypto/tgr192.c | |
| parent | 66679dbab12e84fabe2c54890b5c8112f553a77e (diff) | |
| download | linux-crypto-b4c49c5e6eb2d8f7cb095b5eed430158d9f095ea.tar.gz linux-crypto-b4c49c5e6eb2d8f7cb095b5eed430158d9f095ea.zip | |
[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>
Diffstat (limited to 'crypto/tgr192.c')
0 files changed, 0 insertions, 0 deletions