Repository navigation
test(fuzz): nightly cargo-fuzz target on the wire decode surface (OSTIF T-13) - #86
Merged
Merged
Conversation
…IF T-13, G-001) - fuzz/ standalone workspace (excluded from root): libfuzzer-sys target wire_decode covering the framed wire reader (read_frame_opt — the ADR-0039 self-identified residual weakness), Request::decode, parse_response, every body decoder, and Object::decode. - .github/workflows/fuzz.yml: nightly schedule + workflow_dispatch, 10-minute libFuzzer run, crash reproducers uploaded on failure, SHA-pinned actions, contents:read. Never a PR gate. - The fuzz crate carries the same [patch.crates-io] glib pin as the root workspace so dependency resolution matches production. Verified: cargo check clean locally (Homebrew Rust has no rustup/ nightly, so the libFuzzer build is verified via a dispatched CI run on this branch — see PR).
…ly tag for fuzz, drop ignored toolchain inputs The dtolnay/rust-toolchain tag commits hardcode their toolchain and have no 'toolchain' input (surfaced as a warning annotation on the first sbom run, and a hard failure on the fuzz job which needed nightly but got 1.96.1). Pin the nightly tag's SHA for fuzz.yml; remove the ignored inputs from ci.yml/sbom.yml and correct comments.
…file
rust-toolchain.toml pins stable 1.96.1 and silently overrode the
installed nightly default inside the checkout ('option Z is only
accepted on the nightly compiler'). Job-level env wins over the file.
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.
Executes T-13 (G-001's fuzzing half) from the OSTIF audit (#76):
fuzz/standalone workspace with one libFuzzer target,wire_decode, covering the remote-facing decode surface:read_frame_opt(the frame-length header ADR-0039 self-identifies as the residual weak point),Request::decode,parse_response, every wire body decoder, andObject::decode.fuzz.yml: nightly scheduled 10-minute run +workflow_dispatch+ a PR-scoped trigger on the fuzz files themselves (validating this very PR). Crash reproducers upload as artifacts. SHA-pinned,contents: read, never a merge gate.[patch.crates-io]glib pin so resolution matches production.Verification:
cargo checkclean locally; the full nightly libFuzzer build + run executes on this PR via the new trigger (local machine is rustup-less Homebrew Rust, so CI is the honest verifier here). Do not merge until thecargo fuzz (wire_decode)job on this PR is green.