From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [RFC] Second attempt at kernel secure boot support Date: Wed, 31 Oct 2012 17:39:19 +0000 Message-ID: <20121031173919.4fc63ddd@pyramind.ukuu.org.uk> 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> <20121031171048.GA17163@srcf.ucam.org> <20121031172121.14cc1215@pyramind.ukuu.org.uk> <20121031171743.GA17652@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20121031171743.GA17652@srcf.ucam.org> Sender: linux-security-module-owner@vger.kernel.org To: Matthew Garrett 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, 31 Oct 2012 17:17:43 +0000 Matthew Garrett wrote: > On Wed, Oct 31, 2012 at 05:21:21PM +0000, Alan Cox wrote: > > On Wed, 31 Oct 2012 17:10:48 +0000 > > Matthew Garrett wrote: > > > The kernel is signed. The kernel doesn't check the signature on the > > > suspend image. > > > > Which doesn't matter. How are you going to create the tampered image in > > the first place ? > > By booting a signed kernel, not turning on swap and writing directly to > the swap partition. Ok so the actual problem is that you are signing kernels that allow the user to skip the S4 resume check ?