Repository navigation
Capture v0.9 release controls in isolated execution roots - #275
Merged
Merged
Conversation
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
1 participant
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 v0.9 release matrix has a common-population runner, but its non-report controls still need isolated output capture and pinned supplementary probes. Two historical Java probes share an output path, and the shipped OpenTaint product requires its full distribution rather than the analyzer JAR alone.
Register all 33 controls with exact commands, script identities, explicit environments and captured scratch. Prepare a separate checkout for each control, share the analyzer reservation gate with the matrix, retain terminal attempt receipts and raw output, and stop before reusing an existing control root. Preserve the two warm and three overhead measurement repeats inside each harness command.
Add versioned Python-modeling and OpenTaint-product probes without changing historical scripts or evidence. The restored OpenTaint 0.4.6 archive and exact 329-file inventory match their historical hashes. Record the merged Rust harness build provenance and budget all control checkouts, raising the prospective launch floor to 124 GiB.
Execution remains disabled until the control harness is merged, exact identities and resource reservation are bound, and the final executable plan is reviewed. This PR does not claim a matrix run, qualified control outcomes, freeze, or publication.
Validation: 78 focused tests across 14 scripts passed, including immutable capture verification, failure/timeout retention, missing-output rejection, exact-root isolation, authorization denial, runtime drift, and nested-process interruption cleanup. The planning checker confirms 84 matrix groups and 33 controls with execution disabled. Exact held Python/CodeQL tools and packs were verified read-only. No Rust source changed in this PR.