diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2017-12-23 21:45:46 +0300 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2018-01-05 10:43:05 +0300 |
| commit | 0b5a7f71b4c557b15ec54a1b49023bc1b21044cc (patch) | |
| tree | e88daaaf068485ef8dea37c5e3040eb4a6b593f5 /fs/ecryptfs/main.c | |
| parent | 333b1928566f92ab3d9a108d570d93400c07db6d (diff) | |
| download | linux-0b5a7f71b4c557b15ec54a1b49023bc1b21044cc.tar.xz | |
crypto: crypto4xx - perform aead icv check in the driver
The ccm-aes-ppc4xx now fails one of testmgr's expected
failure test cases as such:
|decryption failed on test 10 for ccm-aes-ppc4xx:
|ret was 0, |expected -EBADMSG
It doesn't look like the hardware sets the authentication failure
flag. The original vendor source from which this was ported does
not have any special code or notes about why this would happen or
if there are any WAs.
Hence, this patch converts the aead_done callback handler to
perform the icv check in the driver. And this fixes the false
negative and the ccm-aes-ppc4xx passes the selftests once again.
|name : ccm(aes)
|driver : ccm-aes-ppc4xx
|module : crypto4xx
|priority : 300
|refcnt : 1
|selftest : passed
|internal : no
|type : aead
|async : yes
|blocksize : 1
|ivsize : 16
|maxauthsize : 16
|geniv : <none>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'fs/ecryptfs/main.c')
0 files changed, 0 insertions, 0 deletions