summaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorJarod Wilson <jarod@redhat.com>2011-01-29 15:14:35 +1100
committerHerbert Xu <herbert@gondor.apana.org.au>2011-01-29 15:14:35 +1100
commit18c0ebd2d8194cce4b3f67e2903fa01bea892cbc (patch)
tree4cc000697114e61cde326ce9f6e09ed6f939240f /init/Kconfig
parent2918aa8d1d4e7b4586a5a89dc8406e1d431f5129 (diff)
downloadop-kernel-dev-18c0ebd2d8194cce4b3f67e2903fa01bea892cbc.zip
op-kernel-dev-18c0ebd2d8194cce4b3f67e2903fa01bea892cbc.tar.gz
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 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud