linux-kernel - Re: Revisiting EFI boot stub config file support

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]

Date:	Tue, 01 Jan 2013 09:24:04 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Shea Levy <shea@...alevy.com>
CC:	linux-efi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Revisiting EFI boot stub config file support

On 01/01/2013 07:55 AM, Shea Levy wrote:
> Hi all,
> 
> In March last year, I submitted a patch to enable the EFI boot stub to
> read its config arguments from a file on the ESP, both to help with
> booting from livecds and to avoid having to use efibootmgr every time
> you change your boottime arguments. I ended up dropping the submission
> because I ended up coming to the conclusion that tools like rEFInd and
> gummiboot were better suited to the task of boot managing than the
> kernel itself.
> 
> Since then, however, I've received enough emails asking about the status
> of the patch that I think there is room for a simpler entrant into the
> field of linux EFI boot management. This could be in-kernel, as per my
> original patch, or a very simple out-of-kernel (but maybe distributed
> in-tree?) efi image that simply reads linux.conf and boots linux with
> those parameters. My personal bias is still toward handling this
> functionality outside of the kernel itself, but before I started the
> work I thought I'd ask here if anyone thought I should instead bring my
> old patch up-to-date.
> 

I am willing to accept this (but I am not the first-line maintainer,
Matt is) in the kernel EFI stub as long as there are no hard-coded
filenames involved, no automatic behavior, and no "scanning".  Those are
showstoppers, as is adding to the boot time for nonusers.

	-hpa


--
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/