From ece04fa8099175daefb0432919efdd622424c943 Mon Sep 17 00:00:00 2001 From: bchanot Date: Sun, 25 Oct 2026 02:41:46 +0100 Subject: [PATCH] chore(memory): bash deny evasion probe, rtk rewrite bypass measured --- .../2026-10-25-bash-deny-probe/README.md | 43 +++++++++++++++++ .../2026-10-25-bash-deny-probe/results.tsv | 46 +++++++++++++++++++ .../plans/2026-10-25-bash-deny-probe/run.sh | 21 +++++++++ 3 files changed, 110 insertions(+) create mode 100644 .claude/tasks/plans/2026-10-25-bash-deny-probe/README.md create mode 100644 .claude/tasks/plans/2026-10-25-bash-deny-probe/results.tsv create mode 100755 .claude/tasks/plans/2026-10-25-bash-deny-probe/run.sh diff --git a/.claude/tasks/plans/2026-10-25-bash-deny-probe/README.md b/.claude/tasks/plans/2026-10-25-bash-deny-probe/README.md new file mode 100644 index 0000000..4c25762 --- /dev/null +++ b/.claude/tasks/plans/2026-10-25-bash-deny-probe/README.md @@ -0,0 +1,43 @@ +# Bash deny-rule evasion probe (2026-10-25) + +Question: do `permissions.deny` Bash rules survive shell wrappers, or must every +rule be duplicated for `bash -c`, `cd &&`, heredocs…? Method: `claude -p --model +haiku --tools Bash`, one harmless analogue rule `Bash(echo SECRET*)`, every +variant sent verbatim, the tool_result read for "has been denied"; each run +repeated without the rule to separate DENY-RULE from ASK. `run.sh