fix: correct td_attributes.debug field path in baremetal TDX policy#32
Merged
butler54 merged 2 commits intoJun 1, 2026
Merged
Conversation
The attestation policy used the wrong path for debug attribute checking:
- Wrong: input["tdx"].quote.body.td_attributes.debug
- Correct: input["tdx"].td_attributes.debug
The quote.body.td_attributes contains a hex string ("0000001000000000"),
not a parsed object. The verifier parses this hex value and places the
structured object at the top level: input["tdx"].td_attributes.
This caused the configuration trust claim to always evaluate to 36
(default/unavailable) instead of 2 (approved) or 3 (no known
vulnerabilities), even when debug was disabled and xfam matched.
Affected rules:
- configuration := 2 (main rule with xfam check)
- configuration := 3 (fallback without xfam)
Aligned with upstream trustee-operator reference policy which uses
input.tdx.td_attributes.debug (not input.tdx.quote.body.td_attributes.debug).
Fixes attestation for bare metal TDX deployments where configuration
claim should pass when debug=false and xfam reference values available.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Chris Butler <chris.butler@redhat.com>
butler54
added a commit
to butler54/coco-pattern
that referenced
this pull request
Jun 1, 2026
Bump trustee chart dependency from 0.4.*/0.6.* to 0.7.* in all profiles. Also migrate values-trusted-hub from git branch reference to chart registry. Changes: - values-baremetal.yaml: 0.6.* → 0.7.* - values-baremetal-gpu.yaml: 0.6.* → 0.7.* - values-simple.yaml: 0.4.* → 0.7.* - values-trusted-hub.yaml: git branch → chart 0.7.* Trustee v0.7.0 includes the td_attributes.debug path fix that was causing configuration trust claim to evaluate to 36 (unavailable) instead of 2 (approved). This fix enables proper debug-disabled enforcement in the attestation policy. Related: validatedpatterns/trustee-chart#32 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
butler54
added a commit
to validatedpatterns/coco-pattern
that referenced
this pull request
Jun 1, 2026
Bump trustee chart dependency from 0.4.*/0.6.* to 0.7.* in all profiles. Also migrate values-trusted-hub from git branch reference to chart registry. Changes: - values-baremetal.yaml: 0.6.* → 0.7.* - values-baremetal-gpu.yaml: 0.6.* → 0.7.* - values-simple.yaml: 0.4.* → 0.7.* - values-trusted-hub.yaml: git branch → chart 0.7.* Trustee v0.7.0 includes the td_attributes.debug path fix that was causing configuration trust claim to evaluate to 36 (unavailable) instead of 2 (approved). This fix enables proper debug-disabled enforcement in the attestation policy. Related: validatedpatterns/trustee-chart#32 Co-authored-by: Claude Sonnet 4.5 <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.
Problem
The baremetal TDX attestation policy uses the wrong field path for debug attribute checking, causing configuration trust claim to always evaluate to 36 (unavailable) instead of 2 (approved) or 3 (no known vulnerabilities).
Wrong path:
Correct path:
Root Cause
The TDX quote.body.td_attributes field contains a hex string (
"0000001000000000"), not a parsed object. The verifier parses this hex value and places the structured object at the top level:input["tdx"].td_attributes.Impact
Solution
Align with upstream trustee-operator reference policy (
ear_default_attestation_policy_cpu.rego) which correctly usesinput.tdx.td_attributes.debug.Fixed in both:
Testing
Verified against cluster with:
"debug": false)Part of Wave 2 bare metal attestation hardening work.