I've been playing with a set of tools (efitools, actually) to add
variable editing directly into flash files. Testing them, I discovered
that they don't work on Ovmf. Not because the tools have a problem but
because Ovmf ignores its flash variable area. This is a patch to fix
that (and remove a bit of unnecessary init code). It seems logical that
even the EmuVariable package should be able to use the existing variable
area in the flash file and it now allows me to pre-deposit secure boot
variables to create an ab-initio locked down image.
James Bottomley (1):
OvmfPkg: Initialize variables from Flash Image instead of creating
them anew
OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c | 169 +++++--------------------------
OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.inf | 1 +
2 files changed, 25 insertions(+), 145 deletions(-)
James
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
