Option to require that the configs have secure permissions
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
Some configs will have sensitive tokens or secrets in them. In those cases I'd like to be able to either warn or enforce that config files have proper permissions, like 0600 on unix.
For prior art, see SSH, which refuses to load keys if they have improper permissions.
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
The issue names no files, tests, or entry points. Start by locating where config files are loaded and where public loading options are defined; review how Unix permissions can be inspected, then define how warning and enforcement should be exposed and tested for secure and insecure permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100