From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jean-Philippe Aumasson <jeanphilippe.aumasson@gmail.com>
Subject: Re: [PATCH v2 1/4] random: use computational hash for entropy extraction
Date: Mon, 7 Feb 2022 15:24:11 +0100 [thread overview]
Message-ID: <CAHmME9po1ybEsM6G7=2o73cVV5ESdrwcNO6QW+CdOSmorbQq_Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9q-hfSRegD0azEX0Z+5uNGCyS3N4VhMPqp206zP+WjZtg@mail.gmail.com>
Hey Dominik,
I just noticed that we use RDSEED in crng_reseed(). I would think we
could remove that and stick to having RDSEED used in extract entropy
as you suggested. I'm now pretty sure the older decision boiled down
to the 10 bytes vs 5 minutes thing, as discussed before. So please
feel free to send a patch doing just this.
Jason
next prev parent reply other threads:[~2022-02-07 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:53 [PATCH v2 0/4] random: use computational hash for entropy extraction, and related fixes Jason A. Donenfeld
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 [this message]
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='CAHmME9po1ybEsM6G7=2o73cVV5ESdrwcNO6QW+CdOSmorbQq_Q@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeanphilippe.aumasson@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tytso@mit.edu \
/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).