[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1311221449120.22082@pobox.suse.cz>
Date: Fri, 22 Nov 2013 14:50:43 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kexec@...ts.infradead.org, "H. Peter Anvin" <hpa@...or.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: [PATCH 0/6] kexec: A new system call to allow in kernel
loading
On Fri, 22 Nov 2013, Vivek Goyal wrote:
> > OTOH, does this feature make any sense whatsover on architectures that
> > don't support secure boot anyway?
>
> I guess if signed modules makes sense, then being able to kexec signed
> kernel images should make sense too, in general.
Well, that's really a grey zone, I'd say.
In a non-secureboot environment, if you are root, you are able to issue
reboot into a completely different, self-made kernel anyway, independent
on whether signed modules are used or not.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists