Project

General

Profile

Actions

Feature #423

open

Feature #420: Use standard format of TPM event log

Implement legacy and crypto agile TPM event log formats

Added by Krystian Hebel almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
10/12/2022
Due date:
% Done:

0%

Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:

Description

Legacy format is simple, it always uses SHA1 and its entries can be described by a C structure, with one field of variable length at the end.

Crypto agile format is slightly more complicated. There can be more than one digest in entry, and their sizes depend on algorithm. There is code for marshaling of required structures in security/tpm/tss/tcg-2.0, but it assumes TPM endianness (BE), while entries in event log are always LE.

Headers for both formats have vendorInfo field, which can be used to hold additional data, not described by specification. An example of such may be offset to next entry to be added, which saves code from walking through all entries (possibly with different sizes) for each new entry.

Actions

Also available in: Atom PDF