manifoldco / manifoldco/torus-cli
User vs system configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Running torus system wide for machine usage is quite different than for a single user, as seen in #59
We need to enforce a different permission model.
For a user, everything should be accessible by that user *and only that user*. For a machine, the machine's token should be accessible only by root/the init process.
Logs should be viewable by system admins, and the torus socket/pid file should be accessible by some semi-trusted set of processes (ie a group).
This is mostly supported now, but configuring it is not ideal.
This issue will cover the changes we can make to make configuring torus as a system daemon for machine use nice and easy.
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 by reading issue #59 and the existing system-wide configuration, since the issue says most permission support already exists but is not easy to configure. Done means a system-daemon setup clearly enforces the stated token, log, socket, and pid-file access boundaries and is straightforward to configure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- devops, operating-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100