Repository navigation
The taboo guard covers Edit and Write, not only Bash - #63
Merged
Merged
Conversation
The guard hooked Bash only, so in local mode Edit or Write could replace sshd_config or authorized_keys without any rule seeing it. Edit, Write and NotebookEdit now run the guard in a file mode that judges the target path alone, so memory files can still name every protected path. When jq cannot name the target the whole input is scanned, which over-blocks instead of failing open. The rule from PR #62 is rewrapped, names the full sshd_config path and adds sed -i, and the hook registration test no longer passes vacuously on quoted script paths. An AI agent wrote this text in my name. I know that is problematic.
Ships the memory-editing rule from #62 and the guard's new file mode. A minor release because the guard now denies tool calls it used to let through: Edit, Write and NotebookEdit onto sshd_config, an SSH key file or a raw disk device. An AI agent wrote this text in my name. I know that is problematic.
The file mode compared the path as written, so a capitalized name on a case-insensitive filesystem, or a //, /./ or x/../ inside the path, reached sshd_config or a key past the guard. The target is now matched without regard to case, as given and with those forms folded away, and every path key in the input is judged. Without jq a JSON escape in the input is denied, because only a parser can show what it hides. An AI agent wrote this text in my name. I know that is problematic.
This was referenced Oct 11, 2026
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
1 participant
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.
The taboo guard hooked
Bashonly. In local modeEditorWritecould replacesshd_configorauthorized_keyswithout any rule seeing it, and #62 put that gap in writing.Edit,WriteandNotebookEditnow run the guard with the argumentfile. It judges the target path alone: sshd's config, an SSH key file, a raw disk device. The text being written is not scanned, so memory files can still name those paths. Withoutjqthe whole input is scanned, which over-blocks instead of failing open.Also here: the rule from #62 rewrapped and made exact (full
sshd_configpath,sed -i), a registration test that no longer passes vacuously on quoted script paths, and the bump to 2.29.0.Left open: a symlink to a protected file, and other tools that write files.
An AI agent wrote this text in my name. I know that is problematic.