Re: [RFC 0/3] extend kexec_file_load system call
From: Vivek Goyal <vgoyal@redhat.com>
Date: 2016-07-15 13:03:47
Also in:
kexec, linux-arm-kernel, lkml
From: Vivek Goyal <vgoyal@redhat.com>
Date: 2016-07-15 13:03:47
Also in:
kexec, linux-arm-kernel, lkml
On Fri, Jul 15, 2016 at 09:49:25AM +0100, Russell King - ARM Linux wrote:
On Wed, Jul 13, 2016 at 03:13:42PM +0200, Arnd Bergmann wrote:quoted
On Wednesday, July 13, 2016 10:41:28 AM CEST Mark Rutland wrote:quoted
The big question is whether this is a realistic case on a secure boot system.What does x86 do here? I assume changes to the command line are also limited.They aren't. You can specify /anything/ even with a fully-signed kernel and initrd, which was one of the things I pointed out in my previous set of responses.
Yes, kernel command line is not signed. For that matter even initird is not signed. Just kernel is signed and its signatures are verified. Idea is an unsigned code should not be able to execute in kernel space. Vivek