[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACdnJusC7pvGhaRZBHAQqxc8MLHBeFUdZAddUO5DG2kFZMktMA@mail.gmail.com>
Date: Thu, 05 Apr 2018 00:22:02 +0000
From: Matthew Garrett <mjg59@...gle.com>
To: jmorris@...ei.org
Cc: David Howells <dhowells@...hat.com>, luto@...nel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Theodore Ts'o" <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
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: An actual suggestion (Re: [GIT PULL] Kernel lockdown for secure boot)
On Wed, Apr 4, 2018 at 4:25 PM James Morris <jmorris@...ei.org> wrote:
> It's surely reasonable to allow an already secure-booted system to be
> debugged without needing to be rebooted.
alt-sysrq-x from a physical console will do that.
Powered by blists - more mailing lists