[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190815151224.GB18727@mit.edu>
Date: Thu, 15 Aug 2019 11:12:24 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Pavel Machek <pavel@....cz>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@....com>,
nhorman@...driver.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Chen Yu <yu.c.chen@...el.com>, Jonathan Corbet <corbet@....net>
Subject: Re: Non-random RDRAND Re: [PATCH] x86/CPU/AMD: Clear RDRAND CPUID
bit on AMD family 15h/16h
On Thu, Aug 15, 2019 at 01:24:35AM +0200, Pavel Machek wrote:
> Burn it with fire!
>
> I mean... people were afraid RDRAND would be backdoored, and you now
> confirm ... it indeed _is_ backdoored? /., here's news for you!
To be fair to AMD, I wouldn't call it a backdoor. Hanlon's razor is
applicable here:
"Never attribute to malice that which can be adequately
explained by neglect."
(Sometimes other words are used instead of neglect, but i'm trying to
be nice.)
- Ted
P.S. Also applicable:
https://www.youtube.com/watch?v=XZxzJGgox_E
Powered by blists - more mailing lists