nextcloud / nextcloud/notify_push
Socket default permissions are insecure
Open
A pull request for this has already been merged.
- #665 by @wilkis3 — merged
documentation
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
The default permissions for the socket file are:
~/:ls -l /run/nextcloud/notify_push
srw-rw-rw- 1 nextcloud users 0 Sep 8 07:29 /run/nextcloud/notify_push=
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 locating the code that creates /run/nextcloud/notify_push and determine the intended restrictive permissions for the socket. Reproduce or inspect the generated socket mode, then add a regression test if the repository’s test structure supports it; done means the socket’s default permissions match the agreed secure behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100