linux-kernel - Re: Proposal: EFI boot stub configuration file

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] [day] [month] [year] [list]

Message-ID: <4F63B250.1010200@shealevy.com>
Date:	Fri, 16 Mar 2012 17:36:16 -0400
From:	Shea Levy <shea@...alevy.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	linux-kernel@...r.kernel.org, matt.fleming@...el.com
Subject: Re: Proposal: EFI boot stub configuration file

On 3/16/12 5:28 PM, H. Peter Anvin wrote:
> A file in UCS-2 seems messed up. 

Yeah, it seemed like a good way to let the code be dumb but upon 
reflection it'd just be a confusing inefficiency.

> Otherwise, seems like a reasonable idea, with a major caveat... since 
> the whole point of this is to do something when it isn't possible to 
> set NVRAM variables, it would make most sense to me if the 
> configuration file could be founin a specific location relative to the 
> kernel image itself.

OK. I'll try both approaches to see if the code complexity is greatly 
increased in the relative path case.

Cheers,
Shea
--
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/