vaportpm: no_std attestation surface; verify auto-detects captured input#9
Merged
Conversation
…ured input Make the attestation surface (quote + cert chain + unified JSON) no_std-capable so one payload can attest on every cloud, including from inside a UEFI bootloader. vaportpm-attest: - attest_with(tpm, nonce, fetcher) is the no_std core; the HTTP certificate fetcher is decoupled behind an injected CertFetcher trait. The std attest() (opens /dev/tpm0 + StdHttpFetcher) stays behind the http-fetch feature. - cert/a9n/nsm/roots lifted to no_std (alloc, BTreeMap, core::str). The AWS Nitro NSM document is a TPM vendor command, so it stays in the no_std `attest` surface, not std. - Features: attest (no_std surface), http-fetch (std fetcher, default), std. - Workspace deps set default-features = false at the workspace level; -attest and -verify opt back into std where each needs it. vaportpm-verify: - normalize_attestation_input auto-detects the captured form -- bare JSON, a base64 blob, or either wrapped in ===ATTESTATION=== markers with EC2/Nitro serial-console timestamps interleaved -- so a raw console capture verifies directly. New InputDecode error for malformed input. 138 workspace tests pass; clippy -D warnings clean; vaportpm-attest builds for x86_64-unknown-uefi with --no-default-features --features attest. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
HarryR
force-pushed
the
no-std-attestation
branch
from
June 26, 2026 16:00
7681d53 to
930f452
Compare
HarryR
added a commit
that referenced
this pull request
Jul 11, 2026
First git-tagged release baseline. 0.1.0 and 0.2.0 were never tagged, and 0.2.0 existed in two distinct untagged states (post-#9 on main, and this PR), so a clean 0.3.0 anchors the accumulated feature (no_std attestation surface) and internal (session split, lockboot:build harness, x509-cert test certs) changes to a single verifiable point. High-assurance consumers should pin as { git = "...", rev = "<sha>", version = "=0.3.0" }. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
HarryR
added a commit
that referenced
this pull request
Jul 11, 2026
First git-tagged release baseline. 0.1.0 and 0.2.0 were never tagged, and 0.2.0 existed in two distinct untagged states (post-#9 on main, and this PR), so a clean 0.3.0 anchors the accumulated feature (no_std attestation surface) and internal (session split, lockboot:build harness, x509-cert test certs) changes to a single verifiable point. High-assurance consumers should pin as { git = "...", rev = "<sha>", version = "=0.3.0" }. Co-Authored-By: Claude Opus 4.8 <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
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.
What
Makes the vaportpm attestation surface no_std-capable so a single payload can attest on every cloud, including from inside a UEFI bootloader (stage0's chain-loaded payload), and makes
vaportpm-verifyingest a raw cloud console capture directly.vaportpm-attest
attest_with(tpm, nonce, fetcher)is the no_std core; the HTTP certificate fetcher is decoupled behind an injectedCertFetchertrait. The stdattest()(opens/dev/tpm0+StdHttpFetcher) stays behind thehttp-fetchfeature.cert/a9n/nsm/rootslifted to no_std (alloc,BTreeMap,core::str). The AWS Nitro NSM document is reached via a TPM vendor command, so it stays in the no_stdattestsurface rather than being gated behindstd.attest(no_std surface),http-fetch(std fetcher, default on),std.default-features = falseat the workspace level;-attest/-verifyopt back into std where each needs it.vaportpm-verify
normalize_attestation_inputauto-detects the captured form — bare JSON, a base64 blob, or either wrapped in===ATTESTATION===markers with EC2/Nitro serial-console timestamps interleaved — so a raw console log verifies with no preprocessing. NewInputDecodeerror for malformed input.Validation
clippy -D warningsclean.vaportpm-attestbuilds forx86_64-unknown-uefiwith--no-default-features --features attest.attest_withproduced an attestation thatvaportpm-verifyconfirmed (provider Aws, TPM quote + NSM chain to the AWS root).🤖 Generated with Claude Code