[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130221203843.GD23427@redhat.com>
Date: Thu, 21 Feb 2013 15:38:43 -0500
From: Vivek Goyal <vgoyal@...hat.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Jones <pjones@...hat.com>,
David Howells <dhowells@...hat.com>,
Josh Boyer <jwboyer@...hat.com>,
Kees Cook <keescook@...omium.org>, keyrings@...ux-nfs.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Load keys from signed PE binaries
On Thu, Feb 21, 2013 at 08:32:54PM +0000, Matthew Garrett wrote:
> On Thu, Feb 21, 2013 at 03:31:19PM -0500, Vivek Goyal wrote:
> > On Thu, Feb 21, 2013 at 10:56:44AM -0800, Linus Torvalds wrote:
> >
> > [..]
> > > So no. The PE file thing makes no sense what-so-ever. What you mention
> > > we can already do, and we already do it *better*.
> >
> > IIUC, PE/COFF signature verification bits can be useful for verifying
> > the signature of PE/COFF signed bzImage. This verification will be
> > required before kexec decides to load the kernel.
>
> Only if the kexec validation's being done in kernel. We'd need agreement
> on that before it's a justification.
Even if /sbin/kexec does bzImage validation I think it will require
kernel's help. (This is assuming that only /sbin/kexec is signed and we
can't trust user space crypto libraries).
Thanks
Vivek
--
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