Skip to content

Commit 30eddab

Browse files
hyperpolymathclaude
andcommitted
ci: mark deliberate secret-shaped test fixtures for rust-secrets
standards' `rust-secrets` job becomes blocking outside `./src` on 2026-08-21. The lines tagged here are genuine matches on genuine secret-shaped literals — they are test data, not credentials — so they take the explicit per-line pragma rather than a pattern loophole that would weaken the gate for every repo. fuzz/fuzz_targets/fuzz_hmac.rs holds a fixed HMAC key for the fuzz harness; the file already says it is 'not the secret itself'. Verified: `rust-secrets` (extracted from standards' shipping YAML) exits 0 on this tree with RUST_TODAY=2026-09-01, i.e. after the cutoff. Scope: this commit touches ONLY Rust sources. The secret-scanner re-pin is deliberately NOT bundled — this repo is one of the 22 the sweep flagged, where gitleaks findings survive the estate baseline, and switching it to the real gate needs its own triage. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 1b8cd38 commit 30eddab

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

fuzz/fuzz_targets/fuzz_hmac.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ use hmac::{Hmac, Mac};
1414
use sha2::Sha256;
1515

1616
// Fixed secret — we're testing the parsing/comparison path, not the secret itself
17-
const SECRET: &[u8] = b"fuzz-test-secret-key-not-real";
17+
const SECRET: &[u8] = b"fuzz-test-secret-key-not-real"; // scanner-allow: rust-secrets
1818

1919
fuzz_target!(|data: &[u8]| {
2020
// Split data: first 32 bytes treated as a "claimed signature", rest as body

0 commit comments

Comments
 (0)