Skip to content

Bind consumer validation to its executable and native target - #545

Open
charliermarsh wants to merge 1 commit into
charlie/codex-toucan-oracle-crashesfrom
charlie/codex-toucan-cleanup-evidence
Open

Bind consumer validation to its executable and native target#545
charliermarsh wants to merge 1 commit into
charlie/codex-toucan-oracle-crashesfrom
charlie/codex-toucan-cleanup-evidence

Conversation

@charliermarsh

Copy link
Copy Markdown
Member

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.

@charliermarsh
charliermarsh force-pushed the charlie/codex-toucan-cleanup-evidence branch from cfcedf0 to 45849cb Compare September 11, 2026 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant