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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zjyombla.fsf@mid.deneb.enyo.de>
Date:	Thu, 28 Feb 2013 21:23:45 +0100
From:	Florian Weimer <fw@...eb.enyo.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Chris Friesen <chris.friesen@...band.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	David Howells <dhowells@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Josh Boyer <jwboyer@...hat.com>,
	Peter Jones <pjones@...hat.com>,
	Vivek Goyal <vgoyal@...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

* Matthew Garrett:

> On Thu, Feb 28, 2013 at 08:41:13PM +0100, Florian Weimer wrote:
>> * Matthew Garrett:
>> 
>> >> Would it be possible to have a signed bootloader that allows booting
>> >> Win8 from within the secure environment, or it could exit the secure
>> >> environment and run unsigned grub?
>> >
>> > What would stop the unsigned grub from installing a firmware hook that 
>> > lies about whether or not Secure Boot is enabled, and then booting 
>> > Windows?
>> 
>> Windows would not have access to the product key because it is stored
>> in a variable without EFI_VARIABLE_RUNTIME_ACCESS, so WGA and other
>> checks will fail, and the user will notice.
>
> grub's running before ExitBootServices(), because otherwise it has no 
> way to actually read anything off disk. Or draw to the screen.

Sorry, if Linux can read from the disk after ExitBootServices(), so
can a boot loader.  Actually, we could boot Linux directly, with an
initrd which contains a boot selector, and use kexec if the chosen
kernel doesn't match the initial one.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ