[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linuxbios
Subject:    [coreboot] [coreboot - Feature #423] Implement legacy and crypto agile TPM event log formats
From:       Michał Żygowski <coreboot () fe80 ! eu>
Date:       2022-10-14 13:08:04
Message-ID: redmine.journal-1177.20221014130803.700 () fe80 ! eu
[Download RAW message or body]

Issue #423 has been updated by Michał Żygowski.



Parent task set to #420



----------------------------------------

Feature #423: Implement legacy and crypto agile TPM event log formats

https://ticket.coreboot.org/issues/423#change-1177



* Author: Krystian Hebel

* Status: New

* Priority: Normal

* Target version: none

* Start date: 2022-10-12

----------------------------------------

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.







-- 

You have received this notification because you have either subscribed to it, or are \
involved in it.

To change your notification preferences, please click here: \
https://ticket.coreboot.org/my/account

_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org


[prev in list] [next in list] [prev in thread] [next in thread]