From: "Stephan Müller" <smueller@chronox.de>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Cc: Vladis Dronov <vdronov@redhat.com>,
Marcelo Cerri <marcelo.cerri@canonical.com>
Subject: [PATCH v3 0/2] crypto: jitter - SHA-3 conditioner and test interface
Date: Fri, 21 Apr 2023 08:07:39 +0200 [thread overview]
Message-ID: <2687238.mvXUDI8C0e@positron.chronox.de> (raw)
In-Reply-To: <4825604.31r3eYUQgx@positron.chronox.de>
The patch set replaces the LFSR conditioning function of the Jitter RNG
with SHA-3 256. This change requires also a new test interface to
analyze the raw unconditioned noise data.
Albeit the test interface can be used directly with dd, a small helper
tool is provided at [1] which can be used to perform the collection
of raw entropy. The analysis of the data can be done with your favorite
tool. Or you may use the helper in [2] which uses the NIST SP800-90B
tool for entropy rate measurement.
[1] https://github.com/smuellerDD/jitterentropy-library/tree/master/tests/raw-entropy/recording_runtime_kernelspace
[2] https://github.com/smuellerDD/jitterentropy-library/tree/master/tests/raw-entropy/validation-runtime-kernel
Changes v3:
- fix jent_kcapi_init: error code for jent_entropy_collector_alloc now
properly cleans up the state
- fix jent_kcapi_init: initialize lock at the beginning as it is used in
error code path function jent_kcapi_cleanup
- editorial change: update description in MODULE_PARM_DESC in patch 0002
Changes v2:
- fix use-after-free by switching shash_desc_zero and crypto_free_shash
in jent_mod_init reported by kernel-test-robot
Stephan Mueller (2):
crypto: jitter - replace LFSR with SHA3-256
crypto: jitter - add interface for gathering of raw entropy
crypto/Kconfig | 21 +++
crypto/Makefile | 1 +
crypto/jitterentropy-kcapi.c | 190 ++++++++++++++++++---
crypto/jitterentropy-testing.c | 294 +++++++++++++++++++++++++++++++++
crypto/jitterentropy.c | 145 ++++++----------
crypto/jitterentropy.h | 20 ++-
6 files changed, 551 insertions(+), 120 deletions(-)
create mode 100644 crypto/jitterentropy-testing.c
--
2.40.0
next prev parent reply other threads:[~2023-04-21 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 11:52 [PATCH 0/2] crypto: jitter - SHA-3 conditioner and test interface Stephan Müller
2023-04-07 11:53 ` [PATCH 1/2] crypto: jitter - replace LFSR with SHA3-256 Stephan Müller
2023-04-10 0:44 ` kernel test robot
2023-04-07 11:56 ` [PATCH 2/2] crypto: jitter - add interface for gathering of raw entropy Stephan Müller
2023-04-10 20:53 ` [PATCH v2 0/2] crypto: jitter - SHA-3 conditioner and test interface Stephan Müller
2023-04-10 20:55 ` [PATCH v2 1/2] crypto: jitter - replace LFSR with SHA3-256 Stephan Müller
2023-04-20 9:55 ` Herbert Xu
2023-04-20 11:05 ` Stephan Mueller
2023-04-10 20:55 ` [PATCH v2 2/2] crypto: jitter - add interface for gathering of raw entropy Stephan Müller
2023-04-21 6:07 ` Stephan Müller [this message]
2023-04-21 6:08 ` [PATCH v3 1/2] crypto: jitter - replace LFSR with SHA3-256 Stephan Müller
2023-04-21 6:08 ` [PATCH v3 2/2] crypto: jitter - add interface for gathering of raw entropy Stephan Müller
2023-05-12 10:58 ` [PATCH v3 0/2] crypto: jitter - SHA-3 conditioner and test interface 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=2687238.mvXUDI8C0e@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=vdronov@redhat.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.