fwupd/plugins/tpm
Richard Hughes c1f7ac47e8 tpm: Actually add the v1.2 device
Also, add end-to-end tests for this so it can never happen again.

Fixes https://github.com/fwupd/fwupd/issues/3972
2021-11-10 14:08:08 +00:00
..
fuzzing Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
tests/tpm0 Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-plugin-tpm.c tpm: Actually add the v1.2 device 2021-11-10 14:08:08 +00:00
fu-self-test.c tpm: Actually add the v1.2 device 2021-11-10 14:08:08 +00:00
fu-tpm-device.c Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-tpm-device.h Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-tpm-eventlog-common.c Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
fu-tpm-eventlog-common.h Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
fu-tpm-eventlog-parser.c Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
fu-tpm-eventlog-parser.h Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
fu-tpm-eventlog.c Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
fu-tpm-v1-device.c Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-tpm-v1-device.h Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-tpm-v2-device.c Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fu-tpm-v2-device.h Move the TPM handling into the TPM place 2021-11-01 14:51:27 +00:00
fwupdtpmevlog.1 Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
meson.build tpm: Actually add the v1.2 device 2021-11-10 14:08:08 +00:00
README.md Merge tpm-eventlog into the tpm plugin 2021-11-02 13:47:25 +00:00
tpm.quirk Simplify the quirk file format 2021-03-03 08:30:34 +00:00

TPM

Introduction

This allows enumerating Trusted Platform Modules, also known as "TPM" devices, although it does not allow the user to update the firmware on them.

The TPM Event Log records which events are registered for the PCR0 hash, which may help in explaining why PCR0 values are differing for some firmware.

The device exposed is not upgradable in any way and is just for debugging. The created device will be a child device of the system TPM device, which may or may not be upgradable.

GUID Generation

These devices use custom GUIDs:

  • TPM\VEN_$(manufacturer)&DEV_$(type)
  • TPM\VEN_$(manufacturer)&MOD_$(vendor-string)
  • TPM\VEN_$(manufacturer)&DEV_$(type)_VER_$(family),
  • TPM\VEN_$(manufacturer)&MOD_$(vendor-string)_VER_$(family)

...where family is either 2.0 or 1.2

Example GUIDs from a real system containing a TPM from Intel:

  Guid:                 34801700-3a50-5b05-820c-fe14580e4c2d <- TPM\VEN_INTC&DEV_0000
  Guid:                 03f304f4-223e-54f4-b2c1-c3cf3b5817c6 <- TPM\VEN_INTC&DEV_0000&VER_2.0

Vendor ID Security

The device is not upgradable and thus requires no vendor ID set.

External Interface Access

This plugin uses the tpm2-tss library to access the TPM. It requires access to /sys/class/tpm and optionally requires read only access to /sys/kernel/security/tpm0/binary_bios_measurements.