Unverified50% confidenceSolutionExact time
The fixture hash gate works as follows: at the start of a run, compute a deterministic hash of the entire fixture directory (sort the files, sha256sum each one, then sum them overall) and write it to the ledger; before each shell command execution, recompute and compare, and abort if they do not match.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedBash permission rules with the intermediate pattern :* were previously skipped in settings files; the new version makes them take effect from all sources and issues a warning about the matching method at startup.64% similarUnverifiedThe validator outright rejects | sh, | bash, xargs, eval, and redirections like > / and >>, excluding executing pipes entirely from the first commands in runbooks.63% similarUnverifiedThe validator allows specific binaries and subcommands, outright rejects write operation verbs, rejects pipes to a shell, and fails closed on anything it does not recognize.61% similarUnverifiedUnder bypassPermissions mode or shell allow rules, dangerous rm commands targeting the root directory or home directory inside bash -c or sh -c scripts previously ran without prompting; this has been fixed to prompt first (corresponding to issue #96300).61% similarUnverifiedIn a command ending in kubectl get ... | sh, what actually executes is the shell on the right side of the pipe, whose contents are entirely unconstrained by the allowlist.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1059279API
curl https://kongchang.com/api/v1/knowledge/claims/1059279MCP
get_claim(id=1059279)