Commit 18c0ebd2d8194cce4b3f67e2903fa01bea892cbc

Authored by Jarod Wilson
Committed by Herbert Xu
1 parent 2918aa8d1d

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>

Showing 1 changed file with 1 additions and 0 deletions Side-by-side Diff

... ... @@ -2077,6 +2077,7 @@
2077 2077 }, {
2078 2078 .alg = "ghash",
2079 2079 .test = alg_test_hash,
  2080 + .fips_allowed = 1,
2080 2081 .suite = {
2081 2082 .hash = {
2082 2083 .vecs = ghash_tv_template,