Repository navigation
Conversation
- It described the superseded attestation format as current; teep refuses it. - It described a teep workaround that was removed with the move to the current format. - It said nvswitch_binding fails closed and blocks requests; it is allowed to fail. - Its Teep Status gave tee_reportdata_binding and cpu_gpu_chain as Pass; both fail, allowed. - It linked tinfoilsh/confidential-cvmimage, which does not resolve; the repository is tinfoilsh/cvmimage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Its Tinfoil V3 section gave the superseded REPORTDATA formula and said cpu_gpu_chain passes; teep does not read device evidence, so it fails. - It said both that no provider binds CPU to GPU and that Tinfoil passes; it now gives one statement. - It named a DefaultEnforced set that does not exist; enforcement comes from the allow_fail lists. - It said the Proof of Cloud JWT signature is verified when a key is configured; only the claims are checked. - It gave one Skip/Fail rule for both registry factors; the gateway factor skips, and is n/a for SEV-SNP. - It called the registry deployed without saying that no model passed it on 2026-11-14. - It listed spurious nvidia_nonce_client_bound failures on nearcloud; that factor passes there. - It credited Option 1 with closing the splicing gap; that is Option 2. - Its report.go line anchor and its provider lists were out of date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It gave measured_model_weights as Pass for Tinfoil; tinfoil_v3_cloud has no backend quote, so it fails, allowed. - Its tables left out Phala Cloud, NanoGPT and the two Tinfoil providers. - It called RTMR0-2 and the Sigstore digests verified; they are checked and allowed to fail by default. - Its diagram put MRCONFIGID under the RTMR3 event log; it is a quote field of its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It presented tinfoil_v3_direct as the remedy; that provider has been disabled since 2026-11-12. - It said direct mode validates GPU and NVSwitch evidence; teep reads CPU evidence only and refuses an enclave that serves device evidence. - It gave a meaning for measured_model_weights=Pass on the cloud route; the cloud route cannot produce Pass. - It named only measured_model_weights; it now names the gateway_tee_* router factors and the backend factors that fail, allowed. - It did not say that the cloud router report is SEV-SNP. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Its recommended policy, if followed, blocks every NEAR and Venice dstack request: a configured list replaces the default, and its MRTD is not the one served. - Its policy snippets were YAML; the configuration is TOML. - Its Teep Status said the allowlists apply when configured and named no factor; teep ships default lists, and allow_fail decides what blocks. - Its MRSEAM table lacked TDX modules 1.5.24 and 2.0.18, and its MRTD and RTMR sections gave values not seen on 2026-11-14. - It said every report shows the register values; the text report does not, the JSON report and --update-config do. - It did not say that --update-config writes only observed values, which replace the defaults. - It said sigstore_code_verified replaces the Tinfoil register allowlists; MRSEAM, MRTD and RTMR0 are still checked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It said Venice ACI/1 carries no GPU evidence; 4 of 6 models carried it on 2026-11-14. - It listed Proof of Cloud registration as enforced; gateway_cpu_id_registry is allowed to fail. - It said a response with another keyset digest is relayed; it fails before relay. - It linked aci_specification.md, which is not in the repository. - Its Phala Cloud session statements were from 2026-11-03; on 2026-11-14 9 of 23 models failed aci_session_verified. - It did not name the enforced aci_session_verified and aci_receipt_verified for Phala Cloud. - It listed the Phala Cloud TLS key binding as pending; it is done and enforced. - It grouped Phala Cloud with the all_attestations form; only NanoGPT uses it. - It called the gateway image a dev channel; on 2026-11-14 it was dstack-0.5.12. - It did not say that 2 of 7 NanoGPT ACI/1 models carried no GPU evidence and were blocked. - It said twelve tee_* factors; there are eleven, plus intel_pcs_collateral. - It said all model-tier supply-chain factors fail; only compose_binding and component_recognition do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It limited the launcher-manifest gap to the two DeepSeek models; on 2026-11-14 all 24 NEAR model composes pinned the manifest and failed the Rekor lookup. - It said the exception also covers GLM models that did not need it; the GLM composes need it too. - Its Teep Status named only the NEAR providers; Venice allows the same failure and its 5 dstack reports show it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It said a new model of another kind fails the factor and is reported; e2ee_usable is enforced, so the report blocks. - It said there is no route for openai/privacy-filter and that NearCloud has no audio route; both NEAR providers now route audio and the privacy endpoints, and refuse them while E2EE is on. - It said the models pass every other check; they fail allowed checks, and no other enforced check fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It said the evidence response echoes no nonce; attested_body states it, under a signature teep cannot verify. - It said the supply-chain factors return Skip with old detail strings; they are N/A, with current strings, and three more factors are N/A. - It gave the pinned sek8s versions as 1.3.1, 1.4.0 and 1.4.1; the RTMR rows are for 1.3.0, 1.4.0 and 1.4.1, with MRTD also for 1.3.1. - It said GPU evidence is verifiable via NVIDIA EAT tokens; Chutes sends SPDM evidence. - It left out that NanoGPT's relay of Chutes evidence also checks attested_body, and that this check does not show freshness. - Its Teep Status did not record that tee_boot_config failed on 8 of 11 Chutes models on 2026-11-14. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Its Teep Status gave the "not probed" details for all four models; a blocked report does not get them. - It dated the kev-4b 404 to 2026-11-14 without saying it came from a run before teep skipped the probe. - It said teep sends these models only chat completions; Phala Cloud also has an embeddings route, refused while E2EE is on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Its instance counts, body sizes and failed instance ids were from 2026-11-12 only; it now also gives the 2026-11-14 values. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- It described gateway_tee_hardware_config as RTMR[0] only; for an SEV-SNP gateway it checks the guest policy and firmware minimums. - It said gateway_tee_tcb_not_revoked checks that the TCB SVN is not revoked; it is the same threshold check as gateway_tee_tcb_current and does not read the AMD CRL. - It did not say that gateway_compose_binding, gateway_cpu_id_registry and gateway_event_log_integrity do not apply to an SEV-SNP gateway. - It gave the TDX wording for gateway_tee_debug_disabled only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Its Tinfoil REPORTDATA cell gave the superseded formula; it now gives the current derivation. - Its NanoGPT row left out the Chutes evidence format that NanoGPT relays, and gave no REPORTDATA binding for the dstack format. - Its Venice row left out the ACI/1 format, and did not say that ACI/1 E2EE ends at the gateway. - Its gateway_tee_hardware_config and gateway_tee_tcb_not_revoked rows did not describe the SEV-SNP checks. Co-Authored-By: Claude Opus 5.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
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
Several attestation gap documents and two README sections describe behavior that teep no longer has, or results that the provider data of 2026-11-14 contradicts. Examples:
cpu_gpu_chainandmeasured_model_weightsas Pass. Both fail, allowed, on everytinfoil_v3_cloudmodel.tinfoil_cloud_integrity.mdpresentstinfoil_v3_directas the remedy; that provider has been disabled since 2026-11-12.dstack_integrity.md, if followed, blocks every NEAR and Venice dstack request: a configured list replaces the default list, and its MRTD is not the one served.aci_gateway.mdlists Proof of Cloud registration as enforced, says a response with another keyset digest is relayed, and links a file that is not in the repository.near_image_provenance.mdlimits the launcher-manifest gap to two DeepSeek models; every captured NEAR model shows it.Change
One commit per document, with the smallest correction for each finding. Each commit message lists what was wrong.
docs/attestation_gaps/tinfoil_nvswitch_json.mddocs/attestation_gaps/gpu_cpu_binding.mddocs/attestation_gaps/model_weights.mddocs/attestation_gaps/tinfoil_cloud_integrity.md: its Teep Status now names the factors it affects.docs/attestation_gaps/dstack_integrity.mddocs/attestation_gaps/aci_gateway.mddocs/attestation_gaps/near_image_provenance.mddocs/attestation_gaps/near_model_endpoints.mddocs/attestation_gaps/sek8s_integrity.mddocs/attestation_gaps/phalacloud_model_endpoints.mddocs/attestation_gaps/nanogpt_chutes_evidence.mdREADME.md: the Tier 4 gateway factor rowsREADME_ADVANCED.md: the Provider Comparison and two gateway factor rowsEach corrected statement is checked against the code at the base commit and against
teep verifyreports and attestation responses captured on 2026-11-14. Observations are dated. A statement that could not be verified is removed or marked as not verified. The documents keep the sections of the gap template.No code changes.
Effect
The documents state what teep verifies and enforces today, and the provider results observed on 2026-11-14.
To verify
The first command lists only the thirteen documents. For any corrected claim, compare it with the code it names, for example the default
allow_faillists ininternal/attestation/report.goand the Tinfoil format ininternal/provider/tinfoil/attestation.go.Checklist
make checkpasses.make integrationandmake reportspass.