From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Matthew Garrett <mjg59@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Justin Forbes <jforbes@redhat.com>,
linux-man <linux-man@vger.kernel.org>, joeyli <jlee@suse.com>,
LSM List <linux-security-module@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-efi <linux-efi@vger.kernel.org>
Subject: Re: An actual suggestion (Re: [GIT PULL] Kernel lockdown for secure boot)
Date: Thu, 5 Apr 2018 09:25:19 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1804050918330.21060@namei.org> (raw)
In-Reply-To: <1119.1522858644@warthog.procyon.org.uk>
On Wed, 4 Apr 2018, David Howells wrote:
> > 6. There's a way to *decrease* the lockdown level below the configured
> > value. (This ability itself may be gated by a config option.)
> > Choices include a UEFI protected variable,
>
> By turning secure boot off, maybe?
It's surely reasonable to allow an already secure-booted system to be
debugged without needing to be rebooted.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-04-04 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 14:49 An actual suggestion (Re: [GIT PULL] Kernel lockdown for secure boot) Andy Lutomirski
2018-04-04 16:17 ` David Howells
2018-04-04 16:23 ` Jann Horn
2018-04-04 16:36 ` Andy Lutomirski
2018-04-04 22:19 ` David Howells
2018-04-05 1:48 ` joeyli
2018-04-04 23:25 ` James Morris [this message]
2018-04-05 0:22 ` Matthew Garrett
2018-04-05 2:16 ` joeyli
2018-04-05 14:01 ` Mimi Zohar
2018-04-05 16:11 ` jlee
2018-04-05 1:45 ` joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.21.1804050918330.21060@namei.org \
--to=jmorris@namei.org \
--cc=ard.biesheuvel@linaro.org \
--cc=dhowells@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jforbes@redhat.com \
--cc=jlee@suse.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mjg59@google.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).