trailofbits / trailofbits/claude-code-config
"Read(~/.ssh/**)" too restrictive?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.1k
- Forks
- 161
- Avg merge
- 3d 59m
- Merged PRs (30d)
- 1
Description
I was wondering from security perspective - isn't "Read(~/.ssh/**)" too restrictive? We want to protect accidental key leakage, but with this rule we also prevent reading known_hosts.
and known_hosts is necessary if one wants to do "git push". In sandbox mode my process dies with:
The push failed due to a sandbox restriction on reading ~/.ssh/known_hosts. Let me retry without the sandbox.
What about something like this:
"Read(~/.ssh/id_*)",
"Read(~/.ssh/config)",
"Read(~/.ssh/authorized_keys)",
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the sandbox permission configuration that defines Read(~/.ssh/**) and review how the existing SSH rules are assembled. Check the behavior around ~/.ssh/known_hosts and git push in sandbox mode, then verify the resulting permission set still protects private keys while allowing the reported workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100