Bind consumer validation to its executable and native target - #545
Open
charliermarsh wants to merge 1 commit into
Open
Bind consumer validation to its executable and native target#545charliermarsh wants to merge 1 commit into
charliermarsh wants to merge 1 commit into
Conversation
charliermarsh
force-pushed
the
charlie/codex-toucan-cleanup-evidence
branch
from
September 11, 2026 03:15
cfcedf0 to
45849cb
Compare
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.
The standalone TLS audit verified a caller-supplied uv binary and hash without matching them to Cargo's executable. We require those bytes to match the selected artifact before runtime checks. Frozen copies remain supported, and the Cargo executable must remain readable.
SQLite's requested target previously affected binding generation and reporting while its probes and consumer ran on the host. We reject a target that differs from the Rust host before resolving dependencies or building. Regression tests cover executable substitution and target mismatches; the actual cross-target invocation stops before Cargo. The Python suite passes. A full TLS consumer replay was not rerun because the cached Cargo executable is no longer present.
Follows #542.