From: "Stephan Müller" <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v2 0/2] crypto: Jitter RNG SP800-90B compliance
Date: Fri, 17 Apr 2020 21:32:53 +0200 [thread overview]
Message-ID: <9339058.MEWKF1lRGI@positron.chronox.de> (raw)
Hi,
This patch set adds SP800-90B compliance to the Jitter RNG. The
SP800-90B patch is tested for more than half a year in user space
with the Jitter RNG version 2.2.0.
The full SP800-90B assessment of the Jitter RNG is provided at [1].
In addition, the DRBG implementation is updated to always be
reseeded from the Jitter RNG. To ensure the DRBG is reseeded within
an appropriate amount of time, the reseed threshold is lowered.
Changes v2:
* Instead of free/alloc of the Jitter RNG instance in case of a health
test error, re-initialize the RNG instance by performing the
power-up test and after a success, clear the health test status and
error.
[1] http://www.chronox.de/jent/doc/CPU-Jitter-NPTRNG.pdf
Stephan Mueller (2):
crypto: Jitter RNG SP800-90B compliance
crypto: DRBG always seeded with SP800-90B compliant noise source
crypto/drbg.c | 26 ++-
crypto/jitterentropy-kcapi.c | 27 +++
crypto/jitterentropy.c | 417 ++++++++++++++++++++++++++---------
include/crypto/drbg.h | 6 +-
4 files changed, 363 insertions(+), 113 deletions(-)
--
2.25.2
next reply other threads:[~2020-04-17 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 19:32 Stephan Müller [this message]
2020-04-17 19:33 ` [PATCH v2 1/2] crypto: Jitter RNG SP800-90B compliance Stephan Müller
2020-04-17 19:34 ` [PATCH v2 2/2] crypto: DRBG always seeded with SP800-90B compliant noise source Stephan Müller
2020-04-24 7:47 ` [PATCH v2 0/2] crypto: Jitter RNG SP800-90B compliance 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=9339058.MEWKF1lRGI@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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).