linux-kernel - Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen

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:	Wed, 23 Oct 2013 19:01:55 +0200
From:	Vladimir 'φ-coder/phcoder' Serbinenko 
	<phcoder@...il.com>
To:	The development of GNU GRUB <grub-devel@....org>
CC:	Jan Beulich <jbeulich@...e.com>, ian.campbell@...rix.com,
	konrad.wilk@...cle.com, keir@....org, david.woodhouse@...el.com,
	stefano.stabellini@...citrix.com, daniel.kiper@...cle.com,
	linux-kernel@...r.kernel.org, mjg59@...f.ucam.org,
	xen-devel@...ts.xen.org, ross.philipson@...rix.com,
	boris.ostrovsky@...cle.com, richard.l.maliszewski@...el.com
Subject: Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen

> GrUB - which iiuc stays in memory
> after transferring control - could export its file system support to its
> descendants).

Xen shouldn't need to load any file after multiboot2 entry point. The
needed files would already be in memory with pointers to them passed.
If you insist on being able to load directly from EFI, then IMO the best
way is to have a PE executable with one of sections containing Xen and
code which would load remaining files to memory and call common entry point.

Download attachment "signature.asc" of type "application/pgp-signature" (292 bytes)