docs: record bare-metal SEVSNPProvider hardware validation (GCP N2D) - #230
Merged
Conversation
The configfs-TSM SEVSNPProvider is now hardware-validated end to end on a non-paravisor SEV-SNP guest (GCP N2D, AMD Milan): the manifest digest lands in the guest-controlled REPORT_DATA and the report verifies against the AMD VCEK chain. Lifts the "not yet validated on non-Azure SNP hardware" caveat in the provider docstrings and CHANGELOG. Docs only; no code change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
SEVSNPProvider(configfs-TSM, for bare-metal / non-paravisor SNP guests) is now hardware-validated end to end on a real non-paravisor SEV-SNP guest — GCP N2D, AMD Milan (dmesg:AMD SEV SEV-ES SEV-SNP; guest controlsREPORT_DATA).Validated live:
extend_manifest_hash→get_attestation_report→verify_manifest_in_report(True),REPORT_DATA[:32] == sha256(manifest_pre_image)(the guest-controlled binding Azure's paravisor can't provide), andverify_attestation_chain(passed=True, signature=VERIFIED)against the VCEK fetched from the AMD KDS.Docs only — lifts the "not yet validated on non-Azure SNP hardware" caveat in the module + provider docstrings and the CHANGELOG. No code change (the provider worked as-is; the parallel cmcp fix, agentrust-io/cmcp#412, needed code because cmcp's bare-metal path used a broken ioctl).
🤖 Generated with Claude Code