SetGID, SetUID, Sticky for files vs directories
Open
Nobody has claimed this yet.
style: article/section 📝
system: cheaha 🖧
system: storage 🛢
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
| bit | dir | file |
|---|---|---|
| setgid | New subdirectories and files inherit group owner and setgid bit. | When run as an executable, spawned processes are owned by the group owner. Poses additional data security risks, please be cautious. |
| setuid | No effect on most Unix systems, including Cheaha. | When run as an exectuable, spawned processes are owned by the user owner. Poses additional data security risks, please be cautious. |
| sticky | mv and rm can only be run by root, the directory owner, or the subdirectory or file owner. |
No effect. |
More details about setuid and setgid: https://en.wikipedia.org/wiki/Setuid
More details about sticky: https://en.wikipedia.org/wiki/Sticky_bit
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 target file or documentation entry point is specified. Search the documentation for existing Unix or file-permission guidance and determine where this comparison belongs. Done means adding an accurate setgid, setuid, and sticky-bit table for files and directories, including the stated security cautions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100