[Feat]: Bind to unix socket with permissions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 80.6k
- Forks
- 6.6k
- Avg merge
- 15h 12m
- Merged PRs (30d)
- 305
Description
Problem
While it's actually easy to bind Netdata to multiple IP:PORT with permissions (streaming, dashoard... etc), it's actualy not possible to bind to unix socket with permission.
Description
Entering unix socket with permissions in the bind to config does not handle permissions :
With this example :
[web]
bind to = unix:/run/netdata/netdata.sock=dashboard
it create of a socket file /run/netdata/netdata.sock=dashboard with full permissions instead of creating a socket file in /run/netdata/netdata.sock with dashboard only permission.
It would be useful to be able to bind it to unix sockets with permissions too, like :
[web]
bind to = unix:/run/netdata/netdata.sock=dashboard unix:/run/netdata/api.sock=management|netdata.conf
Importance
nice to have
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 with the [web] bind to configuration and trace how unix: socket paths are parsed and created. Reproduce the example with socket permissions, then verify that the path excludes the permission suffix, the socket receives the requested dashboard or management permissions, and multiple unix sockets work.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100