From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
Jann Horn <jannh@google.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Guenter Roeck <linux@roeck-us.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Theodore Ts'o <tytso@mit.edu>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] random: allow writes to /dev/urandom to influence fast init
Date: Thu, 24 Mar 2022 18:26:56 +0000 [thread overview]
Message-ID: <Yjy38Nl2wYf0L1eY@gmail.com> (raw)
In-Reply-To: <CAHmME9ovJpdcuuZhNKrOTUc8XvKDDdC+axhAmOD9iESnRR7JqA@mail.gmail.com>
On Wed, Mar 23, 2022 at 09:18:16PM -0600, Jason A. Donenfeld wrote:
> In light of that conclusion, I'm going to work with every userspace
> downstream I can find to help them fix their file-based seeding, if it
> has bugs. I've started talking with the buildroot folks, and then I'll
> speak with the OpenRC people (being a Gentoo dev, that should be easy
> going). Systemd does the right thing already.
>
> I wrote a little utility for potential inclusion in
> busybox/util-linux/whatever when it matures beyond its current age of
> being half hour old:
> - https://git.zx2c4.com/seedrng/about/
> - https://git.zx2c4.com/seedrng/tree/seedrng.c
> So I'll see what the buildroot people think of this and take it from there.
>
The example in random(4) needs to be fixed too, right?
https://man7.org/linux/man-pages/man4/random.4.html
- Eric
next prev parent reply other threads:[~2022-03-24 18:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 19:14 [PATCH] random: allow writes to /dev/urandom to influence fast init Jason A. Donenfeld
2022-03-22 20:42 ` Linus Torvalds
2022-03-22 23:54 ` Jason A. Donenfeld
2022-03-23 2:15 ` David Laight
2022-03-23 2:50 ` Jason A. Donenfeld
2022-03-23 8:43 ` Rasmus Villemoes
2022-03-24 14:12 ` Jason A. Donenfeld
2022-03-23 11:45 ` David Laight
2022-03-23 3:35 ` Theodore Ts'o
2022-03-23 4:00 ` Jason A. Donenfeld
2022-03-23 12:31 ` Theodore Ts'o
2022-05-23 17:59 ` Pavel Machek
2022-03-23 4:30 ` Alex Xu (Hello71)
2022-03-23 4:47 ` Jason A. Donenfeld
2022-03-23 14:01 ` David Laight
2022-03-23 19:53 ` Jason A. Donenfeld
2022-03-24 18:01 ` Eric Biggers
2022-03-24 3:18 ` Jason A. Donenfeld
2022-03-24 16:28 ` Alex Xu (Hello71)
2022-03-24 17:20 ` Jason A. Donenfeld
2022-03-24 19:03 ` Alex Xu (Hello71)
2022-03-24 18:26 ` Eric Biggers [this message]
2022-03-24 18:31 ` Jason A. Donenfeld
2022-06-19 16:44 ` Pavel Machek
2022-03-24 19:53 ` Eric Biggers
2022-03-24 20:25 ` Jason A. Donenfeld
2022-06-19 16:56 ` Pavel Machek
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=Yjy38Nl2wYf0L1eY@gmail.com \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=alex_y_xu@yahoo.ca \
--cc=jannh@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.org \
--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).