From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Kees Cook <keescook@chromium.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tcharding <me@tobin.cc>
Subject: Re: Hashed pointer issues
Date: Mon, 30 Apr 2018 17:01:04 +0000 [thread overview]
Message-ID: <CA+55aFyNqnrM=_5pMgEeL20jVKN7MgWKG52pbaR0FayO=5VuXw@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFzpJC4+tuSopeze72D2sv1urGdap8+Bj2Y9hEYitAkE4Q@mail.gmail.com>
On Mon, Apr 30, 2018 at 9:57 AM Linus Torvalds <
torvalds@linux-foundation.org> wrote:
> Although in *practice* we'd have tons of entropy on any modern development
> CPU too, since any new hardware will have the hardware random number
> generation. Some overly cautious person might not trust it, of course.
In fact, maybe that's the right policy. Avoid a boot-time parameter by just
saying
"if you have hardware random number generation, we can fill entropy
immediately"
No kernel command line needed in practice any more. That's assuming any
kernel developer will have an IvyBridge or newer.
The "I don't trust my hardware" people can still disable that with
"nordrand".
Hmm?
Linus
next prev parent reply other threads:[~2018-04-30 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:50 Hashed pointer issues Anna-Maria Gleixner
2018-04-30 16:11 ` Kees Cook
2018-04-30 16:31 ` Linus Torvalds
2018-04-30 16:41 ` Steven Rostedt
2018-04-30 16:57 ` Linus Torvalds
2018-04-30 17:01 ` Linus Torvalds [this message]
2018-04-30 17:06 ` Randy Dunlap
2018-04-30 17:12 ` Linus Torvalds
2018-05-01 7:05 ` tcharding
2018-05-03 8:41 ` Geert Uytterhoeven
2018-04-30 18:38 ` Kees Cook
2018-04-30 19:00 ` Linus Torvalds
2018-04-30 19:16 ` Kees Cook
2018-04-30 20:01 ` Linus Torvalds
2018-04-30 20:07 ` Linus Torvalds
2018-04-30 21:23 ` Tobin C. Harding
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='CA+55aFyNqnrM=_5pMgEeL20jVKN7MgWKG52pbaR0FayO=5VuXw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).