You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consider exposing the Generation of an AttestationReport #389
The crate already has the logic to derive a Generation enum from an attestation report (e.g. in the impl Encoder<()> for AttestationReport implementation).
The generation is necessary in order to e.g. encode/decode the TcbVersion. However, the generation is not exposed, so users must duplicate the generation detection logic from the crate.
Would be nice to have a field or a method on AttestationReport that clients could use to retrieve the generation of the plaform.
I agree. For attestation reports where generation detection does not work (e.g. reports retrieved from AWS EC2 instances with SEV-SNP), generation info must be specified explicitly.
Activity
hyperfinitism commentedon Apr 8, 2026
I agree. For attestation reports where generation detection does not work (e.g. reports retrieved from AWS EC2 instances with SEV-SNP), generation info must be specified explicitly.