Repository navigation
feat(attestation): export the compiled-in Azure vTPM root CAs - #114
Merged
Merged
Conversation
A verdict on Azure evidence rests on two root CAs compiled into this crate. Everything else it rests on is either in the evidence or fetched and handed back in EndorsementSnapshot, but the roots never leave the crate. Export them as `azure::AZURE_ROOT_CA_PEMS`, (asset file stem, PEM text) pairs in anchor order, so a caller can archive them alongside the evidence and collateral (flashbots#93) and recheck a verification deterministically later without depending on the exact version of this crate that ran it. The anchor list is now built from the same slice, so the two cannot drift. A slice rather than an array, so adding a root does not change the type.
7 tasks
samlaf
added a commit
to SeismicSystems/enclave
that referenced
this pull request
Nov 2, 2026
attestation moves from SeismicSystems/attested-tls@9b6f991 to SeismicSystems/attested-tls@dea9bf8: - The stack is rebuilt on flashbots/attested-tls main (flashbots/attested-tls@dba4485), which merged our Azure root CA export (flashbots/attested-tls#114), so the fork no longer carries it. AZURE_ROOT_CA_PEMS is now a slice rather than a fixed-size array; this crate only iterates it. - The Azure platform metadata fallback (SeismicSystems/attested-tls@7d0aab5) is gone. In its place attested-tls takes attest from SeismicSystems/attest@6d40d05, which reports 0 RAM on Azure instead of reading SMBIOS: stock amd64 Azure kernels don't build dmi-sysfs (https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2172766), which is what this repo's TDX CI runner hit once the fallback was dropped. Upstream: Easy-TEE/attest#29. The old pin stays reachable via the seismic-archive/2026-11-02 tag.
samlaf
added a commit
to SeismicSystems/enclave
that referenced
this pull request
Nov 2, 2026
…llback (#301) TLDR is 2 main changes: 1. SeismicSystems/attested-tls@7d0aab5 was dropped because no longer needed since SeismicSystems/seismic-images#95 2. attested-tls now points to our fork of attest for Easy-TEE/attest@6d40d05 ## LLM Summary attestation moves from SeismicSystems/attested-tls@9b6f991 to SeismicSystems/attested-tls@dea9bf8: - The stack is rebuilt on flashbots/attested-tls main (flashbots/attested-tls@dba4485), which merged our Azure root CA export (flashbots/attested-tls#114), so the fork no longer carries it. AZURE_ROOT_CA_PEMS is now a slice rather than a fixed-size array; this crate only iterates it. - The Azure platform metadata fallback (SeismicSystems/attested-tls@7d0aab5) is gone. In its place attested-tls takes attest from SeismicSystems/attest@6d40d05, which reports 0 RAM on Azure instead of reading SMBIOS: stock amd64 Azure kernels don't build dmi-sysfs (https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2172766), which is what this repo's TDX CI runner hit once the fallback was dropped. Upstream: Easy-TEE/attest#29. The old pin stays reachable via the seismic-archive/2026-11-02 tag.
samlaf
added a commit
to SeismicSystems/seismic-images
that referenced
this pull request
Nov 2, 2026
merging this as a rebase merge, so see individual commit msgs for more details. ## Summary Bumps enclave so the attester reports `ram_bytes` as 0 on Azure instead of reading SMBIOS, and returns SMBIOS access to the GCE-only setup script, since GCP is now the only cloud whose attester reads it. Two commits; merge with rebase to keep them separate. ### 1. `revert(seismic)`: hand SMBIOS access back to `setup-gcp-quote-access` Reverts #95. That PR moved the type-17 SMBIOS entries' `chgrp`/`chmod` from `setup-gcp-quote-access` into `/etc/tmpfiles.d/seismic-smbios.conf` so the Azure attester could read them too. After the bump below, nothing on Azure reads them, so they go back to the GCE-only script and stay root `0400` on Azure. ### 2. `chore(seismic)`: bump enclave to report 0 RAM on Azure - enclave SeismicSystems/enclave@5b88c16 → SeismicSystems/enclave@d6cd97b (SeismicSystems/enclave#301). That PR only changes enclave's `Cargo.toml`/`Cargo.lock`: - attested-tls moves to its patch stack rebuilt on flashbots main (SeismicSystems/attested-tls@dea9bf8), which now includes our Azure root CA export upstream (flashbots/attested-tls#114). - attested-tls takes attest from SeismicSystems/attest@6d40d05 (upstream: Easy-TEE/attest#29): on Azure, `ram_bytes` is 0 and SMBIOS is never read. Azure verification checks vTPM PCRs and never uses the value, and stock amd64 Azure kernels don'(https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2172766), which broke enclave's TDX CI once attested-tls's old `MemTotal` fallback was dropped. - `seismic_reth` and `summit` stay: the range touches neither custodian-ipc nor the harvest key format. - `docs/azure-measurements.md`: "`ram_bytes` on Azure" rn read on Azure". - `setup-gcp-quote-access`: the gate comment says why only GCE gets the hand-over.
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
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.
A verdict on Azure evidence rests on two root CAs compiled into this crate. Everything else it rests on is either in the evidence or fetched and handed back in EndorsementSnapshot, but the roots never leave the crate.
Export them as
azure::AZURE_ROOT_CA_PEMS, (asset file stem, PEM text) pairs in anchor order, so a caller can archive them alongside the evidence and collateral (#93) and recheck a verification deterministically later without depending on the exact version of this crate that ran it.The anchor list is now built from the same slice, so the two cannot drift. A slice rather than an array, so adding a root does not change the type.