Deny Read/Grep access to secret-shaped files - #3
Merged
Conversation
Adds the same permissions.deny block already in the fleet-dispatch workspace root, so a session opened directly in this repo also blocks Read/Grep on .env*, *.pem, *.key, *credentials*, *secret*, id_rsa, id_ed25519 -- previously only sessions started at the MyThingsLab workspace root inherited this protection.
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.
Adds a
.claude/settings.jsonwith the samepermissions.denyblock used in the fleet-dispatch workspace root, so sessions opened directly in this repo (not just at the MyThingsLab workspace root) blockRead/Grepon.env*,*.pem,*.key,*credentials*,*secret*,id_rsa,id_ed25519.Part of a fleet-wide backfill closing a gap found while testing the deny patterns: repo-scoped Claude Code sessions didn't inherit the parent workspace's protection.