On Fri, 14 Apr, at 08:05:07PM, Thomas Gleixner wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
> > From: Kyle McMartin
> >
> > Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running
> > kernel image to be modified. This lifts the lockdown.
> >
> >
On Fri, 14 Apr, at 08:05:07PM, Thomas Gleixner wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
> > From: Kyle McMartin
> >
> > 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
Ard Biesheuvel wrote:
> That does bring me to another EFI related point: many of these patches
> are x86 specific for no good reason.
Note that the sysrq one is awkward since the key chosen *is* arch-specific.
SysRq+x can't be arbitrarily assigned to this since some
Ard Biesheuvel wrote:
> That does bring me to another EFI related point: many of these patches
> are x86 specific for no good reason.
Note that the sysrq one is awkward since the key chosen *is* arch-specific.
SysRq+x can't be arbitrarily assigned to this since some other arches have
their own
On 14 April 2017 at 19:05, Thomas Gleixner wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
>> From: Kyle McMartin
>>
>> Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running
>> kernel image to be modified. This lifts the lockdown.
>>
On 14 April 2017 at 19:05, Thomas Gleixner wrote:
> On Wed, 5 Apr 2017, David Howells wrote:
>
>> From: Kyle McMartin
>>
>> 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
>>
On Wed, 5 Apr 2017, David Howells wrote:
> From: Kyle McMartin
>
> 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
> Signed-off-by: David
On Wed, 5 Apr 2017, David Howells wrote:
> From: Kyle McMartin
>
> 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
> Signed-off-by: David Howells
> cc: x...@kernel.org
Matt,
From: Kyle McMartin
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
Signed-off-by: David Howells
cc: x...@kernel.org
---
From: Kyle McMartin
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
Signed-off-by: David Howells
cc: x...@kernel.org
---
arch/x86/Kconfig| 10 ++
From: Kyle McMartin
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
Signed-off-by: David Howells
---
arch/x86/Kconfig
From: Kyle McMartin
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
Signed-off-by: David Howells
---
arch/x86/Kconfig| 10 ++
arch/x86/kernel/setup.c |
From: Kyle McMartin
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
Signed-off-by: David Howells
---
arch/x86/Kconfig
From: Kyle McMartin
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
Signed-off-by: David Howells
---
arch/x86/Kconfig| 10 ++
arch/x86/kernel/setup.c |
14 matches
Mail list logo