From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-hardening@lists.openwall.com
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH RFC 0/3] get_random_bytes seed blocking
Date: Sat, 3 Jun 2017 04:32:01 +0200 [thread overview]
Message-ID: <20170603023204.30933-1-Jason@zx2c4.com> (raw)
In-Reply-To: <CAHmME9oLHP85ENr5aZgKsTSrxiUWoQ_pfv7C6XYxmcoxPfq3Ew@mail.gmail.com>
Per the other thread on this mailing list, here's an initial
stab at what we discussed -- adding a blocking API for the RNG,
and adding a default-on dmesg Kconfig value for when things go
wrong.
Let me know what you think of this general implementation strategy,
and if you like it, I'll move forward with polish and with integrating
it into a fix for a few currently buggy get_random_bytes use cases.
Jason A. Donenfeld (3):
random: add synchronous API for the urandom pool
random: add get_random_{bytes,u32,u64,int,long}_wait family
random: warn when kernel uses unseeded randomness
drivers/char/random.c | 49 +++++++++++++++++++++++++++++++++++++++++++++----
include/linux/random.h | 31 +++++++++++++++++++++++++++++++
lib/Kconfig.debug | 15 +++++++++++++++
3 files changed, 91 insertions(+), 4 deletions(-)
--
2.13.0
next prev parent reply other threads:[~2017-06-03 2:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 14:59 get_random_bytes returns bad randomness before seeding is complete Jason A. Donenfeld
2017-06-02 15:53 ` Jason A. Donenfeld
2017-06-02 16:48 ` Jason A. Donenfeld
2017-06-02 17:41 ` [kernel-hardening] " Daniel Micay
2017-06-02 17:46 ` Jason A. Donenfeld
2017-06-02 18:58 ` Kees Cook
2017-06-02 17:26 ` Theodore Ts'o
2017-06-02 17:44 ` Jason A. Donenfeld
2017-06-02 19:07 ` Theodore Ts'o
2017-06-02 23:58 ` Jason A. Donenfeld
2017-06-03 0:20 ` [kernel-hardening] " Sandy Harris
2017-06-03 2:32 ` Jason A. Donenfeld [this message]
2017-06-03 2:32 ` [PATCH RFC 1/3] random: add synchronous API for the urandom pool Jason A. Donenfeld
2017-06-03 2:32 ` [PATCH RFC 2/3] random: add get_random_{bytes,u32,u64,int,long}_wait family Jason A. Donenfeld
2017-06-03 2:32 ` [PATCH RFC 3/3] random: warn when kernel uses unseeded randomness Jason A. Donenfeld
2017-06-03 5:04 ` get_random_bytes returns bad randomness before seeding is complete Theodore Ts'o
2017-06-03 12:30 ` Jason A. Donenfeld
2017-06-03 21:45 ` Sandy Harris
2017-06-03 22:54 ` Jeffrey Walton
2017-06-03 23:55 ` [kernel-hardening] " Daniel Micay
2017-06-04 5:55 ` Stephan Müller
2017-06-04 5:48 ` Stephan Müller
2017-06-04 5:54 ` Jeffrey Walton
2017-06-04 6:23 ` Stephan Müller
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=20170603023204.30933-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®