From: Herbert Xu <herbert@gondor.apana.org.au>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Jarod Wilson <jarod@redhat.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] add infrastructure for ansi_cprng self-tests
Date: Mon, 4 May 2009 19:48:03 +0800 [thread overview]
Message-ID: <20090504114803.GA5445@gondor.apana.org.au> (raw)
In-Reply-To: <20090429105501.GE7227@hmsreliant.think-freely.org>
On Wed, Apr 29, 2009 at 06:55:01AM -0400, Neil Horman wrote:
> On Tue, Apr 28, 2009 at 09:28:13PM -0400, Jarod Wilson wrote:
> > Add some necessary infrastructure to make it possible to run
> > self-tests for ansi_cprng. The bits are likely very specific
> > to the ANSI X9.31 CPRNG in AES mode, and thus perhaps should
> > be named more specifically if/when we grow additional CPRNG
> > support...
> >
> > Successfully tested against the cryptodev-2.6 tree and a
> > Red Hat Enterprise Linux 5.x kernel with the follow-on
> > patch that adds the actual test vectors.
> >
> > Signed-off-by: Jarod Wilson <jarod@redhat.com>
> >
> Thanks Jarod!
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Both patches applied. Thanks!
In future this should be moved to user-space where we can perform
more complicated tests such as entropy testing.
Of course we need to finish the user-space API first :)
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2009-05-04 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 1:27 [PATCH 0/2] crypto: ansi_cprng self-test infra and vectors Jarod Wilson
2009-04-29 1:28 ` [PATCH 1/2] add infrastructure for ansi_cprng self-tests Jarod Wilson
2009-04-29 10:55 ` Neil Horman
2009-05-04 11:48 ` Herbert Xu [this message]
2009-04-29 1:32 ` [PATCH 2/2] add ansi_cprng test vectors Jarod Wilson
2009-04-29 10:56 ` Neil Horman
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=20090504114803.GA5445@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=jarod@redhat.com \
--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
all inboxes | Powered by JetHome®