Mailing List Archive

[PATCH v5 5/5] efi: Do not use command line if unified config is included
If a unified Xen image is used, then the bundled configuration,
Xen command line, dom0 kernel, and ramdisk are prefered over
any files listed in the config file or provided on the command line.

Unlike the shim based verification, the PE signature on a unified image
covers all of the Xen+config+kernel+initrd modules linked into the
unified image. This also ensures that, on properly configured UEFI Secure Boot
platforms, the entire runtime will be measured into the TPM for unsealing
secrets or remote attestation.

Signed-off-by: Trammell Hudson <hudson@trmm.net>
---
xen/common/efi/boot.c | 43 ++++++++++++++++++++++++++++++++++++++-----
1 file changed, 38 insertions(+), 5 deletions(-)

diff --git a/xen/common/efi/boot.c b/xen/common/efi/boot.c
index c14e836640..6dc3f5ac94 100644
--- a/xen/common/efi/boot.c
+++ b/xen/common/efi/boot.c
@@ -952,6 +952,35 @@ static void __init setup_efi_pci(void)
efi_bs->FreePool(handles);
}

+/*
+ * Logic should remain sync'ed with linux/arch/x86/xen/efi.c
+ * Secure Boot is enabled iff 'SecureBoot' is set and the system is
+ * not in Setup Mode.
+ */
+static bool __init efi_secure_boot(void)
+{
+ static __initdata EFI_GUID global_guid = EFI_GLOBAL_VARIABLE;
+ uint8_t secboot, setupmode;
+ UINTN secboot_size = sizeof(secboot);
+ UINTN setupmode_size = sizeof(setupmode);
+ EFI_STATUS rc;
+
+ rc = efi_rs->GetVariable(L"SecureBoot", &global_guid,
+ NULL, &secboot_size, &secboot);
+ if ( rc != EFI_SUCCESS )
+ return false;
+
+ rc = efi_rs->GetVariable(L"SetupMode", &global_guid,
+ NULL, &setupmode_size, &setupmode);
+ if ( rc != EFI_SUCCESS )
+ return false;
+
+ if ( secboot > 1 || setupmode > 1 )
+ blexit(L"Invalid SecureBoot/SetupMode variables");
+
+ return secboot == 1 && setupmode == 0;
+}
+
static void __init efi_variables(void)
{
EFI_STATUS status;
@@ -1128,15 +1157,15 @@ efi_start(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)
static EFI_GUID __initdata shim_lock_guid = SHIM_LOCK_PROTOCOL_GUID;
EFI_LOADED_IMAGE *loaded_image;
EFI_STATUS status;
- unsigned int i, argc;
- CHAR16 **argv, *file_name, *cfg_file_name = NULL, *options = NULL;
+ unsigned int i, argc = 0;
+ CHAR16 **argv = NULL, *file_name, *cfg_file_name = NULL, *options = NULL;
UINTN gop_mode = ~0;
EFI_SHIM_LOCK_PROTOCOL *shim_lock;
EFI_GRAPHICS_OUTPUT_PROTOCOL *gop = NULL;
union string section = { NULL }, name;
bool base_video = false;
const char *option_str;
- bool use_cfg_file;
+ bool use_cfg_file, secure;

__set_bit(EFI_BOOT, &efi_flags);
__set_bit(EFI_LOADER, &efi_flags);
@@ -1155,8 +1184,10 @@ efi_start(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)
PrintErrMesg(L"No Loaded Image Protocol", status);

efi_arch_load_addr_check(loaded_image);
+ secure = efi_secure_boot();

- if ( use_cfg_file )
+ if ( use_cfg_file &&
+ !read_section(loaded_image, ".config", &cfg, NULL))
{
UINTN offset = 0;

@@ -1214,6 +1245,8 @@ efi_start(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)

PrintStr(L"Xen " __stringify(XEN_VERSION) "." __stringify(XEN_SUBVERSION)
XEN_EXTRAVERSION " (c/s " XEN_CHANGESET ") EFI loader\r\n");
+ if ( secure )
+ PrintStr(L"UEFI Secure Boot enabled\r\n");

efi_arch_relocate_image(0);

@@ -1233,7 +1266,7 @@ efi_start(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)
/* Get the file system interface. */
dir_handle = get_parent_handle(loaded_image, &file_name);

- if ( read_section(loaded_image, ".config", &cfg, NULL) )
+ if ( cfg.ptr )
PrintStr(L"Using unified config file\r\n");
else if ( !cfg_file_name )
{
--
2.25.1
Re: [PATCH v5 5/5] efi: Do not use command line if unified config is included [ In reply to ]
On 17.09.2020 17:40, Trammell Hudson wrote:
> @@ -1155,8 +1184,10 @@ efi_start(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)
> PrintErrMesg(L"No Loaded Image Protocol", status);
>
> efi_arch_load_addr_check(loaded_image);
> + secure = efi_secure_boot();
>
> - if ( use_cfg_file )
> + if ( use_cfg_file &&
> + !read_section(loaded_image, ".config", &cfg, NULL))
> {
> UINTN offset = 0;

I continue to think that it's wrong to ignore the command line
altogether. And this isn't just for the Dom0 kernel part when
there's no .kernel section, but also because there may be
firmware workarounds that the user needs to be able to make use
of in order for the binary to work on certain hardware.

Jan