fwupd/plugins/uefi-dbx
2022-06-14 14:36:52 -05:00
..
fuzzing uefi-dbx: Add a plugin that analyses the UEFI dbx variable 2020-05-07 16:59:36 +01:00
dbxtool.1 trivial: fix man page sections 2022-01-04 14:17:43 -06:00
fu-dbxtool.c Split out the GByte helpers to a new source file 2022-06-14 14:36:52 -05:00
fu-efi-image.c Split out the memory helpers to a new source file 2022-06-14 14:36:52 -05:00
fu-efi-image.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-plugin-uefi-dbx.c Add FuProgress to ->startup() and ->coldplug() 2022-06-04 20:21:50 +01:00
fu-self-test.c Split out the GByte helpers to a new source file 2022-06-14 14:36:52 -05:00
fu-uefi-dbx-common.c Remove the 'common' prefix from the volume creation methods 2022-06-14 14:36:52 -05:00
fu-uefi-dbx-common.h Be smarter and include less header files per source file 2022-06-14 14:36:52 -05:00
fu-uefi-dbx-device.c Remove the recently added fu_progress_add_step_full() 2022-06-03 13:47:11 -05:00
fu-uefi-dbx-device.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
meson.build uefi-dbx: No not allow the DBX update for specific motherboards 2022-03-07 22:12:06 +00:00
README.md trivial: update markdown for pre-commit style 2021-07-18 14:42:47 -05:00
uefi-dbx.quirk uefi-dbx: No not allow the DBX update for specific motherboards 2022-03-07 22:12:06 +00:00

UEFI dbx

Introduction

Updating the UEFI revocation database prevents starting EFI binaries with known security issues, and is typically no longer done from a firmware update due to the risk of the machine being "bricked" if the bootloader is not updated first.

This plugin also checks if the UEFI dbx contains all the most recent revoked checksums. The result will be stored in an security attribute for HSI.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in EFI_SIGNATURE_LIST format.

See https://www.uefi.org/sites/default/files/resources/UEFI%20Spec%202_6.pdf for details.

This plugin supports the following protocol ID:

  • org.uefi.dbx

GUID Generation

These devices use the GUID constructed of the uppercase SHA256 of the X509 certificates found in the system KEK and optionally the EFI architecture. e.g.

  • UEFI\CRT_{sha256}
  • UEFI\CRT_{sha256}&ARCH_{arch}

...where arch is typically one of IA32, X64, ARM or AA64

Update Behavior

The firmware is deployed when the machine is in normal runtime mode, but it is only activated when the system is restarted.

Vendor ID Security

The vendor ID is hardcoded to UEFI:Microsoft for all devices.

External Interface Access

This plugin requires:

  • read/write access to /sys/firmware/efi/efivars