Issue #423 has been reported by Krystian Hebel.
---------------------------------------- Feature #423: Implement legacy and crypto agile TPM event log formats https://ticket.coreboot.org/issues/423
* 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.
Issue #423 has been updated by Michał Żygowski.
Related to Feature #420: Use standard format of TPM event log added
---------------------------------------- Feature #423: Implement legacy and crypto agile TPM event log formats https://ticket.coreboot.org/issues/423#change-1167
* 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.
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.
-
Krystian Hebel -
Michał Żygowski