From: Jarod Wilson <jarod@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH] crypto: print self-test pass notices in fips mode
Date: Wed, 29 Apr 2009 09:21:53 -0400 [thread overview]
Message-ID: <200904290921.54483.jarod@redhat.com> (raw)
In-Reply-To: <20090429131817.GB17254@gondor.apana.org.au>
On Wednesday 29 April 2009 09:18:17 Herbert Xu wrote:
> On Tue, Apr 28, 2009 at 09:21:35PM -0400, Jarod Wilson wrote:
> >
> > diff --git a/crypto/testmgr.c b/crypto/testmgr.c
> > index 39ffa69..d0cc85c 100644
> > --- a/crypto/testmgr.c
> > +++ b/crypto/testmgr.c
> > @@ -2149,6 +2149,10 @@ notest:
> > test_done:
> > if (fips_enabled && rc)
> > panic("%s: %s alg self test failed in fips mode!\n", driver, alg);
> > + /* fips mode requires we print out self-test success notices */
> > + if (fips_enabled && !rc && strncmp(alg, "ctr(aes", 7))
> > + printk(KERN_INFO "alg: self-tests for %s (%s) passed\n",
> > + driver, alg);
>
> What is this strncmp crap for?
To avoid claiming we successfully self-tested ctr(aes) when its
not actually directly testable. Was intended to go sort of hand
in hand with the other patch to suppress 'no self test' messages
for ctr(aes) when in fips mode. Of course, since at this point,
we've run ecb(aes), and that's what's suggested as the way to
test ctr(aes)[*], perhaps we don't need to
suppress it.
[*] well, along with the sign-off from the lab that the counter
code is acceptable
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-04-29 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 1:21 [PATCH] crypto: print self-test pass notices in fips mode Jarod Wilson
2009-04-29 10:52 ` Neil Horman
2009-04-29 13:18 ` Herbert Xu
2009-04-29 13:21 ` Jarod Wilson [this message]
2009-04-29 13:24 ` Jarod Wilson
2009-04-30 21:25 ` [PATCH v2] " Jarod Wilson
2009-05-04 11:51 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904290921.54483.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).