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 | 55e9dce37ddf3ab358ba1d1e9eef4ee4bd8174a6 (patch) | |
| tree | e850e9052d4db68905cb6c444e269ed7c719301e /fs/xattr_acl.c | |
| parent | 06b42aa94b65806b4f8c5fc893ef97a2f491fb32 (diff) | |
[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 'fs/xattr_acl.c')
0 files changed, 0 insertions, 0 deletions