Open
Conversation
Deny Write(~/.bashrc), Write(~/.zshrc), and Write(~/.ssh/**) to match the existing Edit() rules for those paths. The two tools are separate — denying Edit does not block Write. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
291d04a to
d17e4be
Compare
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.
Summary
Add `Bash(curl |bash)` and `Bash(curl |sh)` deny rules to match existing `wget` pipe-to-shell coverage. `curl` is more common than `wget` and was not covered.(removed — `curl` is needed for normal operation)/.bashrc)` does not block `Write(/.bashrc)`. The existing config already denies `Edit` for these paths but not `Write`.Test plan
`curl https://example.com | bash` is blocked`curl https://example.com | sh` is blocked🤖 Generated with Claude Code