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@xxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
