[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180804215209.GA3201@localhost>
Date: Sat, 4 Aug 2018 23:52:10 +0200
From: Pavel Machek <pavel@....cz>
To: "Theodore Y. Ts'o" <tytso@....edu>,
Yann Droneaud <ydroneaud@...eya.com>,
linux-crypto@...r.kernel.org,
Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
labbott@...hat.com
Subject: Re: [PATCH] random: add a config option to trust the CPU's hwrng
Hi!
On Wed 2018-07-18 10:26:25, Theodore Y. Ts'o wrote:
> On Wed, Jul 18, 2018 at 09:22:13AM +0200, Yann Droneaud wrote:
> >
> > The text message should explain this is only relevant during
> > initialization / early boot.
> >
> > The config option name should state this.
>
> There are other workarounds for hangs that happen after initialization
> / early boot, yes. They are of varying levels of quality / safely,
> but that's neither here nor there.
>
> 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?
(Plus, I'd say this should be kernel command line optiom, not config
option...?)
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists