linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	Yann Droneaud <ydroneaud@opteya.com>,
	linux-crypto@vger.kernel.org,
	Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
	labbott@redhat.com
Subject: Re: [PATCH] random: add a config option to trust the CPU's hwrng
Date: Sun, 5 Aug 2018 11:44:32 +0200	[thread overview]
Message-ID: <20180805094432.GA22948@amd> (raw)
In-Reply-To: <20180805002514.GF4461@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]

On Sat 2018-08-04 20:25:14, Theodore Y. Ts'o wrote:
> On Sat, Aug 04, 2018 at 11:52:10PM +0200, Pavel Machek wrote:
> > > However, enabling config option means that the CRNG will be
> > > initialized with potentially information available to the CPU
> > > manufacturer and/or Nation States, and this persists *after*
> > > initialization / early boot.  So to say, "we're perfectly safe after
> > > we leave initialization / early boot" is not true.
> > 
> > This should really be explained in the help text.
> > 
> > I assume that after 10 seconds of moving mouse, user is safe even when
> > rdrand is backoored?
> 
> You'll hate this answer, but "it depends".  Suppose someone is using
> an init script which generates ssh keys upon first boot if they are
> missing.  If this is the case, *and* RDRAND is backdoored, then the
> keys will be generated in such a way that they *might* be succeptible
> to being guessed by a nation state.  Moving your mouse around for 1000
> or 10,000 seconds won't help if the host's ssh keys has already been
> generated.

Yep, understood, but after moving the mouse, /dev/random &
/dev/urandom can be trusted afaict.

> Depending on your hardware, no mouse motion might be necessary at all.
> On my laptop (a Dell XPS 13 model 9370) using an dm-crypt protected
> root disk, and running a Debian testing userspace, with a 4.18-rc6
> based kernel, the "CRNG is initialized" message is printed *before*
> the root file system is mounted.

Entropy is easy to gather on any laptop. cat /dev/sda > /dev/null :-).

> On other systems, where the hardware does not issue as many
> interrupts, the mouse motion might be extremely important in order to
> get the "CRNG is initialized" message.
> 
> > (Plus, I'd say this should be kernel command line option, not config
> > option...?)
> 
> Agreed, there should be a command line option as well.  I just haven't
> gotten around to it yet, and in the meantime, having a config option
> is better than nothing.   Patches gratefully accepted...  :-)

Well, this was RFC :-). I actually don't think config option is good
idea. Command line option is enough.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-08-05  9:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  1:43 [PATCH] random: add a config option to trust the CPU's hwrng Theodore Ts'o
2018-07-18  1:51 ` Theodore Y. Ts'o
2018-07-18 15:14   ` Sandy Harris
2018-07-18 17:36     ` [PATCH] random: addu " Theodore Y. Ts'o
2018-07-18 20:22       ` Sandy Harris
2018-07-19 14:21         ` Theodore Y. Ts'o
2018-07-19 20:17       ` Yann Droneaud
2018-07-18 17:36   ` [PATCH] random: add " Ken Moffat
2018-07-19  0:19     ` Ken Moffat
2018-07-18  5:09 ` Randy Dunlap
2018-07-18  6:46 ` Jeffrey Walton
2018-07-18  7:22 ` Yann Droneaud
2018-07-18 14:26   ` Theodore Y. Ts'o
2018-07-18 15:29     ` Yann Droneaud
2018-07-18 19:17       ` Theodore Y. Ts'o
2018-08-04 21:52     ` Pavel Machek
2018-08-05  0:25       ` Theodore Y. Ts'o
2018-08-05  0:28         ` Theodore Y. Ts'o
2018-08-05  9:44         ` Pavel Machek [this message]
2018-07-20 19:09 ` Laura Abbott

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=20180805094432.GA22948@amd \
    --to=pavel@ucw.cz \
    --cc=labbott@redhat.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=ydroneaud@opteya.com \
    /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).