Messages in this thread | | | From | Thomas Fossati <> | Date | Wed, 27 Sep 2023 10:43:41 +0200 | Subject | Re: [PATCH v4 2/6] configfs-tsm: Introduce a shared ABI for attestation reports |
| |
Caveat: newbie here (just subscribed the linux-coco list) trying to bridge the abstract language of IETF RATS with an actual implementation of the architecture.
> +struct tsm_report { > + struct tsm_desc desc; > + size_t outblob_len; > + u8 *outblob; > + size_t certs_len; > + u8 *certs; > +};
Could you clarify the semantics of @certs?
Are these what the IETF calls platform "endorsements" [1], [2]? Or could a DICE report (which is a cert chain) fall into this bucket too?
If the former, maybe @endorsement_certs (or similar) would minimise ambiguity.
[1] https://www.rfc-editor.org/rfc/rfc9334.html#name-endorsements [2] https://www.ietf.org/archive/id/draft-dthaler-rats-endorsements-02.html
| |