From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [RFC] Second attempt at kernel secure boot support Date: Wed, 31 Oct 2012 17:10:48 +0000 Message-ID: <20121031171048.GA17163@srcf.ucam.org> References: <1348152065-31353-1-git-send-email-mjg@redhat.com> <20121029174131.GC7580@srcf.ucam.org> <20121031155503.1aaf4c93@pyramind.ukuu.org.uk> <20121031170334.59833fb1@pyramind.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20121031170334.59833fb1@pyramind.ukuu.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Alan Cox Cc: Jiri Kosina , Josh Boyer , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org List-Id: linux-efi@vger.kernel.org On Wed, Oct 31, 2012 at 05:03:34PM +0000, Alan Cox wrote: > On Wed, 31 Oct 2012 16:55:04 +0100 (CET) > Jiri Kosina wrote: > > Prepare (as a root) a hand-crafted image, reboot, let the kernel resume > > from that artificial image. > > It's not signed. It won't reboot from that image. The kernel is signed. The kernel doesn't check the signature on the suspend image. -- Matthew Garrett | mjg59@srcf.ucam.org