diff options
| author | Jarod Wilson <jarod@redhat.com> | 2011-01-29 05:14:35 +0100 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2011-01-29 05:14:35 +0100 |
| commit | 18c0ebd2d8194cce4b3f67e2903fa01bea892cbc (patch) | |
| tree | 4cc000697114e61cde326ce9f6e09ed6f939240f /drivers/memstick | |
| parent | crypto: testmgr - mark xts(aes) as fips_allowed (diff) | |
| download | linux-18c0ebd2d8194cce4b3f67e2903fa01bea892cbc.tar.xz linux-18c0ebd2d8194cce4b3f67e2903fa01bea892cbc.zip | |
crypto: testmgr - mark ghash as fips_allowed
A self-test failure in fips mode means a panic. Well, gcm(aes)
self-tests currently fail in fips mode, as gcm is dependent on ghash,
which semi-recently got self-test vectors added, but wasn't marked as a
fips_allowed algorithm. Because of gcm's dependence on what is now seen
as a non-fips_allowed algorithm, its self-tests refuse to run.
Previously, ghash got a pass in fips mode, due to the lack of any test
vectors at all, and thus gcm self-tests were able to run. After this
patch, a 'modprobe tcrypt mode=35' no longer panics in fips mode, and
successful self-test of gcm(aes) is reported.
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions