Skip to content

docs: README states the exec inline-code denylist surface and its residuals - #47

Merged
VarunGore36 merged 1 commit into
mainfrom
docs/policy-exec-denylist-readme
Nov 9, 2026
Merged

VarunGore36 merged 1 commit into
mainfrom
docs/policy-exec-denylist-readme

Conversation

@VarunGore36

Copy link
Copy Markdown
Owner

Summary

Part 13 of 18 in the exec-denylist fix series — documentation.

The README policy section now states the denylist's full surface:

  • Catches: shell inline/script/startup-file forms anywhere in argv; interpreter inline-code spellings (incl. bundled clusters), the -x extraction flag, python -m; the awk family outright; env -S/--split-string.
  • Residuals, stated honestly: GNU sed's e command, interpreter script files (python3 script.py — allowed by design), and self-executing tools (find -exec, xargs, git hooks). These belong behind exec.allowlist.

Docs-only.

Test plan

  • cargo test --workspace: 51 suites, 0 failed (unchanged)

…iduals

The policy section now enumerates what the denylist catches (shell
inline/script/startup-file forms wherever they appear in argv,
interpreter inline-code spellings incl. -x and python -m, the awk
family, env split-string) and — honestly — what it cannot see: GNU
sed's e command, interpreter script files (allowed by design), and
tools that exec on their own (find -exec, xargs, git hooks). Those
belong behind exec.allowlist.
@VarunGore36
VarunGore36 merged commit 5d58340 into main Nov 9, 2026
5 checks passed
@VarunGore36
VarunGore36 deleted the docs/policy-exec-denylist-readme branch November 9, 2026 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant