[Feature Request] Implement an execution path flag for hardening
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 379
- Forks
- 103
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Description
Currently, the CLI doesn't restrict what can run from $PATH, so if an attacker has write access to a user directory in their $PATH, they can create a malicious file that runs with a temporal command.
Consider adding something like git's --exec-path flag to protect against this.
Contributor guide
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 at the CLI entry points and compare the requested behavior with Git's --exec-path flag. Define which commands and PATH-based execution cases the hardening flag should cover, then verify that enabling it prevents execution from writable PATH directories without breaking intended command execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100