Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode

From	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode
Date	2017-04-14 20:20 +0200
Message-ID	<twdZ7-4pP-11@gated-at.bofh.it> (permalink)
References	<tsZzj-7hF-5@gated-at.bofh.it> <tsZzl-7hF-47@gated-at.bofh.it> <twdPr-4ma-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 14 April 2017 at 19:05, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
>> From: Kyle McMartin <kyle@redhat.com>
>>
>> Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running
>> kernel image to be modified.  This lifts the lockdown.
>>
>> Signed-off-by: Kyle McMartin <kyle@redhat.com>
>> Signed-off-by: David Howells <dhowells@redhat.com>
>> cc: x86@kernel.org
>
> Matt, Ard?
>
> Any opinions on this?
>

From an EFI point of view, there is not a lot to see here. I think
having a SysRq to lift lockdown makes sense, although I think we
should avoid 'secure boot' when referring to lockdown because they are
really two different things. As someone else pointed out, you may have
other ways of trusting your kernel, in which case you should be able
to lock it down as well.

That does bring me to another EFI related point: many of these patches
are x86 specific for no good reason. We have been working really hard
over the past couple of years to move EFI plumbing into
drivers/firmware/efi, and things are not intimately related to an
architecture should ideally be implemented there. Looking at the
diffstat of this patch, I don't see why this should be a x86 only
feature.

In general, though, I think this should be two patches, one that
introduces the functionality to restrict some SysRq keys to console
only, and one that adds the 'x' for lockdown lift.

I haven't gotten around to responding to David's general email
regarding the point of all of this. I will do so asap, but it will
need to wait until Tuesday at least.

-- 
Ard.

On 14 April 2017 at 19:05, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
>> From: Kyle McMartin <kyle@redhat.com>
>>
>> Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running
>> kernel image to be modified.  This lifts the lockdown.
>>
>> Signed-off-by: Kyle McMartin <kyle@redhat.com>
>> Signed-off-by: David Howells <dhowells@redhat.com>
>> cc: x86@kernel.org
>
> Matt, Ard?
>
> Any opinions on this?
>
> Thanks,
>
>         tglx

Thread

Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode Thomas Gleixner <tglx@linutronix.de> - 2017-04-14 20:10 +0200
  Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode Ard Biesheuvel <ard.biesheuvel@linaro.org> - 2017-04-14 20:20 +0200
    Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode David Howells <dhowells@redhat.com> - 2017-04-15 01:20 +0200
  Re: [PATCH 06/24] Add a sysrq option to exit secure boot mode Matt Fleming <matt@codeblueprint.co.uk> - 2017-04-16 22:50 +0200

csiph-web