| 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: <20130319185003.GA13301@srcf.ucam.org> Date: Tue, 19 Mar 2013 18:50:03 +0000 From: Matthew Garrett <mjg59@...f.ucam.org> To: James Bottomley <James.Bottomley@...senPartnership.com> Cc: linux-efi@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] x86/efi: pull NV+BS variables out before we exit boot services On Tue, Mar 19, 2013 at 06:40:56PM +0000, James Bottomley wrote: > On Tue, 2013-03-19 at 18:28 +0000, Matthew Garrett wrote: > > It requires the key to survive the system being entirely powered down, > > which means it needs to be BS+NV. It shouldn't be possible for userspace > > to access this key. > > It requires the *public* key to survive power down, certainly. The > private key can be thrown away once the hibernate image is signed. I > think the scheme can be constructed so the private key is never in NV > storage ... that also makes it more secure against tampering. Well, that somewhat complicates implementation - we'd be encrypting the entire contents of memory except for the key that we're using to encrypt memory. Keeping the public key away from userspace avoids having to care about that. -- Matthew Garrett | mjg59@...f.ucam.org -- 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