Skip to content

Conversation

@jraman567
Copy link
Collaborator

This PR implements the SEVSNP scheme for Veraison.

Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in middle of review, just started today

@yogeshbdeshpande
Copy link
Collaborator

As we are adding new scheme, please refer to https://github.com/veraison/services/blob/main/README.md

  • Insert Sev-snp support in the suitable place for the text pertaining to Provisioning
  • Insert Sev-snp support in the suitable place for the text pertaining to Verification

Also remember to check the suitable places in docs repo and the Veraison book, to check where this comment is applicable.

Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some further comments.

@yogeshbdeshpande
Copy link
Collaborator

  • Also, I feel somewhere in the documentation of the Scheme, we should refer to the documentation on the Evidence Profile and also preferably the Reference Value Profile document, we have used to build this scheme!

Copy link
Contributor

@thomas-fossati thomas-fossati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this is great.

I have left a few comments inline.

Add amd-kds and nvidia coserv plugins to the spec file

Signed-off-by: Jagannathan Raman <[email protected]>
@jraman567 jraman567 changed the base branch from upstream/installation+rpm to main November 18, 2025 15:37
define SEV-SNP scheme for Veraison.

Signed-off-by: Jagannathan Raman <[email protected]>
store the trust anchors and reference values in the CoMID's
"Attest Key Triple" and "Reference Value Triple" formats.

Signed-off-by: Jagannathan Raman <[email protected]>
accept CoRIM endorsements, reference values & trust anchors,
and save them in the database.

Signed-off-by: Jagannathan Raman <[email protected]>
@jraman567
Copy link
Collaborator Author

As we are adding new scheme, please refer to https://github.com/veraison/services/blob/main/README.md

  • Insert Sev-snp support in the suitable place for the text pertaining to Provisioning
  • Insert Sev-snp support in the suitable place for the text pertaining to Verification

Also remember to check the suitable places in docs repo and the Veraison book, to check where this comment is applicable.

Done

@jraman567
Copy link
Collaborator Author

  • Also, I feel somewhere in the documentation of the Scheme, we should refer to the documentation on the Evidence Profile and also preferably the Reference Value Profile document, we have used to build this scheme!

OK, I'll add this to the scheme's README.

implement parts of the store handler that synthesize
keys from trust anchors and reference values.

Signed-off-by: Jagannathan Raman <[email protected]>
Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, subjecting to checking whether two minor comments have been incorporated or not..?

@jraman567
Copy link
Collaborator Author

Approved, subjecting to checking whether two minor comments have been incorporated or not..?

Thank you so much, @yogeshbdeshpande!

The lint error is because we're not using the return value of errors.New(). I'll update it quickly.

@yogeshbdeshpande
Copy link
Collaborator

me know about the unresolved, so I can address them and close out this PR. Thank you so much! :)

Yes, we can resolve the same and move quickly, this PR has been waiting for some time now.
I believe most of the comments you have already addressed!

@thomas-fossati
Copy link
Contributor

Hi @yogeshbdeshpande and @thomas-fossati , I've addressed most of your comments. The ones I needed more clarification aren't resolved.

Please let me know about the unresolved, so I can address them and close out this PR. Thank you so much! :)

I have a couple of comments that should probably be acted upon. They are both very simple.

@jraman567
Copy link
Collaborator Author

Hi @yogeshbdeshpande and @thomas-fossati , I've addressed most of your comments. The ones I needed more clarification aren't resolved.
Please let me know about the unresolved, so I can address them and close out this PR. Thank you so much! :)

I have a couple of comments that should probably be acted upon. They are both very simple.

I'm working on your comments, @thomas-fossati . Will update the PR shortly. Thank you!

Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Implement an evidence handler to extract claims from the evidence token
and store them in an internal representation format ( CoRIM for SEV-SNP).

Signed-off-by: Jagannathan Raman <[email protected]>
Update the store handler to get Trust Anchor and Reference Value
keys from evidence.

Add helper routines to parse the TSM report's auxblob to extract
AMD keys.

Signed-off-by: Jagannathan Raman <[email protected]>
Implement the ValidateEvidenceIntegrity routine of the EvidenceHandler interface.

Ensure the root key in auxblob matches the ARK in provisioned trust anchors.
Confirm the integrity of the certificate chain in the auxblob and the
validity of the signature in the evidence.

Signed-off-by: Jagannathan Raman <[email protected]>
Implement the AppraiseEvidence routine in the EvidenceHandler interface
to confirm the claims match with the evidence.

Signed-off-by: Jagannathan Raman <[email protected]>
Add unit tests for endorsement, evidence and storage handlers

Signed-off-by: Jagannathan Raman <[email protected]>
jraman567 and others added 7 commits November 25, 2025 12:12
Add README document for SEVSNP scheme

Signed-off-by: Jagannathan Raman <[email protected]>
Allow SEVSNP scheme to accept evidence in CMW collection format

Signed-off-by: Jagannathan Raman <[email protected]>
REPORTED_TCB is a bitfield of versions. Extract individual versions
for comparison. REPORTED_TCB in evidence should be greater than or
equal to the reference value.

Signed-off-by: Jagannathan Raman <[email protected]>
Some claims in the SEV-SNP profile aren't relevant for
verification, so skipping them

Signed-off-by: Jagannathan Raman <[email protected]>
The nonce in the evidence must match the session nonce that veraison
generated

Signed-off-by: Jagannathan Raman <[email protected]>
Add TSM report evidence in JSON & CBOR formats for testing

Signed-off-by: Jagannathan Raman <[email protected]>
Add global variables to log errors in the compareTcb function

Signed-off-by: Yogesh Deshpande <[email protected]>
Signed-off-by: Jagannathan Raman <[email protected]>
Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for incorporating my comments!
LGTM!

@yogeshbdeshpande
Copy link
Collaborator

@thomas-fossati : Please give a final look and provide your approval...

Copy link
Contributor

@thomas-fossati thomas-fossati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the execellent contribution!

@thomas-fossati thomas-fossati merged commit f1ccf18 into veraison:main Nov 26, 2025
5 checks passed
@jraman567
Copy link
Collaborator Author

Thank you so much for reviewing, @yogeshbdeshpande and @thomas-fossati !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants