[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 04 Apr 2018 00:46:00 +0000
From: Matthew Garrett <mjg59@...gle.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: luto@...nel.org, David Howells <dhowells@...hat.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, jmorris@...ei.org,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jforbes@...hat.com, linux-man@...r.kernel.org, jlee@...e.com,
LSM List <linux-security-module@...r.kernel.org>,
linux-api@...r.kernel.org, Kees Cook <keescook@...omium.org>,
linux-efi <linux-efi@...r.kernel.org>
Subject: Re: [GIT PULL] Kernel lockdown for secure boot
On Tue, Apr 3, 2018 at 5:33 PM Linus Torvalds
<torvalds@...ux-foundation.org>
wrote:
> In contrast, the generic distros can't enable it anyway if it breaks
> random hardware. And it wouldn't be about secure boot or not, but
> about the random hardware choice.
The generic distros have been shipping this policy for the past 5 years.
Powered by blists - more mailing lists