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
The library currently uses the CurrentTCB values of a report when querying the AMD KDS for the VCEK certificate, as opposed to the AMD SEV-SNP ABI spec, which says:
The firmware maintains a TCB_VERSION called the ReportedTcb. ReportedTcb is used to derive
the VCEK that signs the attestation report.
When ReportedTCB != CurrentTCB, this results in a signature verification error when checking the report's signature with the VCEK certificate's public key here:
The library currently uses the
CurrentTCB
values of a report when querying the AMD KDS for the VCEK certificate, as opposed to the AMD SEV-SNP ABI spec, which says:go-sev-guest/verify/verify.go
Line 618 in d8660ce
When
ReportedTCB != CurrentTCB
, this results in a signature verification error when checking the report's signature with the VCEK certificate's public key here:go-sev-guest/verify/verify.go
Lines 463 to 464 in d8660ce
The text was updated successfully, but these errors were encountered: