You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add baremetal TDX/SNP and NVIDIA GPU attestation support (#21)
* feat: add baremetal TDX and SNP attestation support
Add direct TEE attestation rules for baremetal Intel TDX and AMD SEV-SNP.
These use init_data hash verification (platform-independent) rather than
Azure vTPM PCR measurements.
Make pcr-stash secret lookup conditional in RVPS policy so baremetal
deployments (which lack pcr-stash) don't fail. The init_data reference
value is always included for both Azure and baremetal platforms.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: disable TLS cert verification for PCCS in QCNL config
The PCCS service uses a self-signed certificate which causes
SGX_QL_ROOT_CA_UNTRUSTED errors during TDX quote verification.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support both Azure vTPM and baremetal init_data reference values
The init_data RVPS entry now includes four values:
- PCR8_HASH (secure + debug): SHA256(zeros || SHA256(toml)) for Azure vTPM
- RAW_HASH padded (secure + debug): SHA256(toml) zero-padded to 48 bytes for baremetal TDX/SNP
This allows a single attestation server to validate both Azure vTPM
attestation (which presents PCR-extended hashes) and baremetal TDX/SNP
attestation (which presents raw SHA-256 initdata hashes in the quote's
mr_config_id field, zero-padded to SHA-384 width).
Long-term, veritas (https://github.com/confidential-devhub/veritas)
should be integrated for comprehensive reference value generation
including firmware, kernel, and RTMR measurements.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use chained single-item append calls for ACM compatibility
ACM ConfigurationPolicy template engine rejects variadic append
(want 2 got 11). Chain individual append calls instead.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: add NVIDIA GPU attestation via NRAS remote verifier
- Add kbs.gpu.enabled value (default false) for GPU attestation support
- Configure NRAS remote verifier when GPU enabled (kbs-config-map)
- Add default_gpu.rego policy for NRAS x-nvidia-* claims
- Add GPU-aware resource policy requiring both cpu0 and gpu0 affirming
- Existing GPU rules in default_cpu.rego handle CPU-class + GPU evidence
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: ensure GPU attestation is required when GPU is enabled
Previously, when GPU attestation was enabled, the policy would still
allow access with only CPU attestation due to the first rule being
unconditionally present. This fix ensures the CPU-only rule only
applies when GPU is disabled, preventing the bypass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* chore: version bump
Signed-off-by: Chris Butler <chris.butler@redhat.com>
---------
Signed-off-by: Chris Butler <chris.butler@redhat.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments