| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <50915975.8030503@shealevy.com> Date: Wed, 31 Oct 2012 13:01:41 -0400 From: Shea Levy <shea@...alevy.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> CC: Jiri Kosina <jkosina@...e.cz>, Josh Boyer <jwboyer@...il.com>, Matthew Garrett <mjg@...hat.com>, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, linux-efi@...r.kernel.org Subject: Re: [RFC] Second attempt at kernel secure boot support On 10/31/2012 01:03 PM, Alan Cox wrote: > On Wed, 31 Oct 2012 16:55:04 +0100 (CET) > Jiri Kosina <jkosina@...e.cz> wrote: > >> On Wed, 31 Oct 2012, Alan Cox wrote: >> >>> All this depends on your threat model. If I have physical access to >>> suspend/resume your machine then you already lost. If I don't have >>> physical access then I can't boot my unsigned OS to patch your S4 image >>> so it doesn't matter. >> 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. So then to hibernate the kernel must have a signing key? > Alan > -- > To unsubscribe from this list: send the line "unsubscribe linux-efi" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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