From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH v2 0/4] random: use computational hash for entropy extraction, and related fixes
Date: Fri, 4 Feb 2022 14:53:21 +0100 [thread overview]
Message-ID: <20220204135325.8327-1-Jason@zx2c4.com> (raw)
The bulk of the motivation for this and description of crypto
vulnerabilities is in the first patch of this series. The following two
patches then fix up entropy accounting for the new model. The last patch
fixes a minor code safety issue.
This v2 improves some documentation comments and unifies these patches
into one patchset.
Jason A. Donenfeld (4):
random: use computational hash for entropy extraction
random: simplify entropy debiting
random: use linear min-entropy accumulation crediting
random: make credit_entropy_bits() always safe
drivers/char/random.c | 490 ++++++----------------------------
include/trace/events/random.h | 30 +--
2 files changed, 87 insertions(+), 433 deletions(-)
--
2.35.0
next reply other threads:[~2022-02-04 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:53 Jason A. Donenfeld [this message]
2022-02-04 13:53 ` [PATCH v2 1/4] random: use computational hash for entropy extraction Jason A. Donenfeld
2022-02-05 8:23 ` Dominik Brodowski
2022-02-05 11:42 ` Jason A. Donenfeld
2022-02-05 11:43 ` Jason A. Donenfeld
2022-02-07 14:24 ` Jason A. Donenfeld
2022-02-04 13:53 ` [PATCH v2 2/4] random: simplify entropy debiting Jason A. Donenfeld
2022-02-05 7:18 ` Dominik Brodowski
2022-02-04 13:53 ` [PATCH v2 3/4] random: use linear min-entropy accumulation crediting Jason A. Donenfeld
2022-02-05 7:00 ` Eric Biggers
2022-02-05 12:54 ` Jason A. Donenfeld
2022-02-04 13:53 ` [PATCH v2 4/4] random: make credit_entropy_bits() always safe Jason A. Donenfeld
2022-02-05 7:21 ` Dominik Brodowski
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=20220204135325.8327-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®