fwupd/plugins/uefi-pk
Richard Hughes 1981c63d58 Remove FuFirmwareImage and just use FuFirmware instead
This allows us to 'nest' firmware formats, and removes a ton of duplication.

The aim here is to deprecate FuFirmwareImage -- it's almost always acting
as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow
custom types. If I'm struggling to work out what should be a FuFirmware and
what should be a FuFirmwareImage then a plugin author has no hope.

For simple payloads we were adding bytes into an image and then the image into
a firmware. This gets really messy when most plugins are treating the FuFirmware
*as* the binary firmware file.

The GBytes saved in the FuFirmware would be considered the payload with the
aim of not using FuFirmwareImage in the single-image case.
2021-03-09 21:14:12 +00:00
..
fu-plugin-uefi-pk.c Remove FuFirmwareImage and just use FuFirmware instead 2021-03-09 21:14:12 +00:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md Check the AMI test key if not installed for HSI-1 2021-01-05 17:09:02 +00:00

UEFI PK Support

Introduction

The platform key (PK) specifies the machine owner, typically the OEM that created the laptop or desktop.

Several device manufacturers decide to ship the default "AMI Test PK" platform key instead of a Device Manufacturer specific one. This will cause an HSI-1 failure.

External interface access

This plugin requires:

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