NOISSUE - Add vTPM AK hash to SEV-SNP report#543
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #543 +/- ##
==========================================
+ Coverage 66.90% 69.30% +2.39%
==========================================
Files 76 76
Lines 6884 5554 -1330
==========================================
- Hits 4606 3849 -757
+ Misses 1936 1363 -573
Partials 342 342 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
SammyOina
approved these changes
Nov 3, 2025
dborovcanin
approved these changes
Nov 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a small update. The PR adds the hash of the attestation key (AK) of the vTPM to the SEV-SNP report. The idea is to further strengthen the cryptographic bond between the vTPM and the SEV-SNP.
What does this do?
The OR adds the AK of the vTPM to the
REPORT_DATAfields of the SEV-SNP attestation report.Which issue(s) does this PR fix/relate to?
No issue.
Have you included tests for your changes?
Did you document any new/modified feature?
Notes