feat(tee): land Azure CVM distinct runtime.platform value (agentrust-trace 0.4)#411
Merged
Merged
Conversation
…race 0.4) Azure CVM attestation previously mapped onto the amd-sev-snp platform and was distinguished at verify time by its evidence envelope, to avoid an agentrust-trace release. With agentrust-trace 0.4 adding the distinct azure-cvm-sev-snp platform value, use it directly: a consumer keying on runtime.platform now sees that the root of trust is vTPM-rooted (paravisor model), not a guest-controlled SNP report_data. - bump agentrust-trace dependency to >=0.4 - _PROVIDER_MAP: azure-cvm-sev-snp -> azure-cvm-sev-snp (was amd-sev-snp) - verify.py: dispatch on the explicit platform; drop the envelope-sniff helper; add azure-cvm-sev-snp to _KNOWN_PLATFORMS - CHANGELOG updated 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.
Re-lands the distinct-platform switch that was intended for #407 but did not make it onto
main— the #407 merge (322f49f) kept the originalamd-sev-snpmapping. Right nowagentrust-trace 0.4.0, trace-tests (#41), and ca2a (#58) all support/expect the distinctazure-cvm-sev-snpplatform, but cMCP still emitsamd-sev-snpfor Azure and distinguishes it only by evidence shape — the inconsistency this closes.Changes
agentrust-tracedependency>=0.1→>=0.4(the release that adds the platform value)_PROVIDER_MAP:azure-cvm-sev-snp→azure-cvm-sev-snp(wasamd-sev-snp)verify.py: dispatch on the explicitazure-cvm-sev-snpplatform; drop the_is_azure_cvm_evidenceenvelope-sniff workaround; addazure-cvm-sev-snpto_KNOWN_PLATFORMSAn Azure cMCP claim now reports
runtime.platform: azure-cvm-sev-snp, so a consumer keying onruntime.platformsees the root of trust is vTPM-rooted (paravisor model), not a guest-controlled SNPreport_data. 72 attestation/verify tests pass against 0.4.0; ruff + mypy clean.🤖 Generated with Claude Code