[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180405185347.2785eb8a@alans-desktop>
Date: Thu, 5 Apr 2018 18:53:47 +0100
From: Alan Cox <gnomes@...rguk.ukuu.org.uk>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: David Howells <dhowells@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
Kees Cook <keescook@...omium.org>,
James Morris <jmorris@...ei.org>, linux-efi@...r.kernel.org,
Matthew Garrett <mjg59@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jforbes@...hat.com, linux-man@...r.kernel.org,
joeyli <jlee@...e.com>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: [GIT PULL] Kernel lockdown for secure boot
> Furthermore, there is a fundamental deviation from common security
> sense here, where things like command line parameters and other
> lockdown specific tunables are blacklisted rather than whitelisted,
I've been complaining about this from the start but it appears to be a
write only authorship process going on.
Alan
Powered by blists - more mailing lists