| From: |
| Matthew Garrett <mjg59-AT-google.com> |
| To: |
| Linus Torvalds <torvalds-AT-linux-foundation.org> |
| Subject: |
| Re: [GIT PULL] Kernel lockdown for secure boot |
| Date: |
| Wed, 04 Apr 2018 00:46:00 +0000 |
| Message-ID: |
| <CACdnJuti5Riqoi1sesqPALYHq9LT87o4MFj-0Y5BZqqzJ5579g@mail.gmail.com> |
| Cc: |
| luto-AT-kernel.org, David Howells <dhowells-AT-redhat.com>, Ard Biesheuvel <ard.biesheuvel-AT-linaro.org>, jmorris-AT-namei.org, Alan Cox <gnomes-AT-lxorguk.ukuu.org.uk>, Greg Kroah-Hartman <gregkh-AT-linuxfoundation.org>, Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>, jforbes-AT-redhat.com, linux-man-AT-vger.kernel.org, jlee-AT-suse.com, LSM List <linux-security-module-AT-vger.kernel.org>, linux-api-AT-vger.kernel.org, Kees Cook <keescook-AT-chromium.org>, linux-efi <linux-efi-AT-vger.kernel.org> |
On Tue, Apr 3, 2018 at 5:33 PM Linus Torvalds
<torvalds@linux-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.
