From: Jarod Wilson <jarod@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Neil Horman <nhorman@tuxdriver.com>,
linux-crypto@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH 0/3] enhance RNG api with flags to allow for different operational modes
Date: Thu, 17 Sep 2009 08:28:08 -0400 [thread overview]
Message-ID: <4AB22B58.5050105@redhat.com> (raw)
In-Reply-To: <20090917033729.GA13826@gondor.apana.org.au>
On 09/16/2009 11:37 PM, Herbert Xu wrote:
> On Wed, Sep 16, 2009 at 12:04:56PM -0400, Neil Horman wrote:
>>
>> So the question is, how do I make this RNG fips compliant without
>> breaking some subset of users out there that rely on the predictability of the
>> CPRNG? The solution I've come up with is a dynamic flag. This patch series
>
> What user apart from the test vector relies on the predictability?
As far as I know, only the internal self-tests and fips testing rely on
the predictability without the first value consumed internally. However,
in theory, being able to disable the continuity check could also be of
benefit to some throughput-intensive operation, particularly on an
embedded system.
The monte carlo self-tests could obviously compensate for the internally
consumed value without altering the end result, but the single-iteration
tests could not. We're using self-test vectors that were published by
NIST right now, so I'd rather avoid having to alter them.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-09-17 12:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 16:04 [PATCH 0/3] enhance RNG api with flags to allow for different operational modes Neil Horman
2009-09-16 16:11 ` [PATCH 1/3] add RNG api calls to set common flags Neil Horman
2009-09-16 20:56 ` Jarod Wilson
2009-09-16 16:13 ` [PATCH 2/3] augment the testmgr code to set TEST_MODE flag on all rng instances Neil Horman
2009-09-16 20:57 ` Jarod Wilson
2009-09-16 16:25 ` [PATCH 3/3] augment CPRNG to correctly implement continuous test for FIPS, and support TEST_MODE flags Neil Horman
2009-09-16 20:57 ` Jarod Wilson
2009-09-16 20:56 ` [PATCH 0/3] enhance RNG api with flags to allow for different operational modes Jarod Wilson
2009-09-17 3:37 ` Herbert Xu
2009-09-17 12:28 ` Jarod Wilson [this message]
2009-09-17 12:43 ` Neil Horman
2009-09-17 15:39 ` Herbert Xu
2009-09-17 17:08 ` Neil Horman
2009-09-17 20:16 ` Herbert Xu
2009-09-17 20:18 ` Jarod Wilson
2009-09-17 20:23 ` Herbert Xu
2009-09-18 18:32 ` [PATCH 0/1] enhance RNG api with flags to allow for different operational modes (v2) Neil Horman
2009-09-18 18:34 ` [PATCH 1/1] add fips(ansi_cprng) (v2) Neil Horman
2009-09-19 1:12 ` Jarod Wilson
2009-10-19 2:56 ` 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=4AB22B58.5050105@redhat.com \
--to=jarod@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.