public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH] crypto: add optional continuous repetition test to entropy store based rngs
Date: Fri, 12 Jun 2009 11:31:11 -0500	[thread overview]
Message-ID: <1244824271.4496.151.camel@calx> (raw)
In-Reply-To: <20090612142644.GA15644@gondor.apana.org.au>

On Sat, 2009-06-13 at 00:26 +1000, Herbert Xu wrote:
> On Fri, Jun 12, 2009 at 10:23:08AM -0400, Neil Horman wrote:
> >
> > > Ok, that seems like a reasonable idea.  new patch below
> > > Change Notes:
> > > 
> > > 1) Moved fips_enabled flag into its own header, included in all the appropriate
> > > places
> > > 
> > > 2) removed flags field from entropy store, keying continuous test on the
> > > non-null status of the last_data pointer
> > > 
> > > 
> > > FIPS-140 requires that all random number generators implement continuous self
> > > tests in which each extracted block of data is compared against the last block
> > > for repetition.  The ansi_cprng implements such a test, but it would be nice if
> > > the hw rng's did the same thing.  Obviously its not something thats always
> > > needed, but it seems like it would be a nice feature to have on occasion. I've
> > > written the below patch which allows individual entropy stores to be flagged as
> > > desiring a continuous test to be run on them as is extracted.  By default this
> > > option is off, but is enabled in the event that fips mode is selected during
> > > bootup.
> > > 
> > > Neil
> > > 
> > > Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> > > 
> > Ping, I don't see that this got picked up in the crypto tree.  Are there
> > subsequent objections?
> 
> Matt, are you OK with me picking this up or do you want to pick it
> up?

Acked-by: Matt Mackall <mpm@selenic.com>

You can pick it up. Speaking of, do you care if I route other RNG bits
through your crypto tree? I usually just bounce patches to Andrew.

-- 
http://selenic.com : development and support for Mercurial and Linux



  reply	other threads:[~2009-06-12 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 19:50 [PATCH] crypto: add optional continuous repetition test to entropy store based rngs Neil Horman
2009-06-04 20:14 ` Matt Mackall
2009-06-05  0:04   ` Neil Horman
2009-06-05  0:30     ` Herbert Xu
2009-06-05  1:48       ` Neil Horman
2009-06-12 14:23         ` Neil Horman
2009-06-12 14:26           ` Herbert Xu
2009-06-12 16:31             ` Matt Mackall [this message]
2009-06-12 23:09               ` Herbert Xu
2009-06-18 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=1244824271.4496.151.camel@calx \
    --to=mpm@selenic.com \
    --cc=davem@davemloft.net \
    --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