File permissions too open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 412
- Forks
- 16
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
I have run into a use-case where the 3rd-party app actually checks that the file is not only root owned, but also no one but the root-user has write permissions.
Can we make the file appear as a regular file, not a symlink and the apparent permissions for envfs-provided executables either configurable, or remove the write bit for group and others?
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by tracing how envfs exposes PATH executables through its FUSE filesystem, then determine how symlink targets and apparent permissions are produced. Done means the issue's requested root-only write protection or configurability is supported and the regular-file requirement is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100