Lab 02 — Permissions, ACLs, and Special Bits
Target: rhcsa-node1 or rhcsa-node2 · Time: 25 minutes · Reboot required: no
Scenario
A team-shared directory needs precise access controls. Standard Unix perms aren't enough — you need ACLs for the exceptions.
Tasks (assumes lab01 is complete: alice, bob, deploy, engineering group)
- Create `/srv/projects` owned by `root:engineering`, mode `2770` (setgid).
- Create `/srv/projects/active` and `/srv/projects/archive` with the same ownership and mode.
- Set default ACL on `/srv/projects` so new files inherit group rwx for `engineering`.
- Grant user `deploy` read-only access to `/srv/projects/archive` via ACL — `deploy` is not in `engineering`.
- Create user **carol** (UID 1502), add to `engineering`. Set an ACL denying `carol` write access on `/srv/projects/active` even though she's in the group.
- Create file `/srv/projects/active/shared.txt` (any content). Verify ACL inheritance worked.
- Set the sticky bit on `/tmp/dropbox` (create the directory first, root-owned, mode 1777).
- On `/usr/local/bin/teamtool` (create as an empty file owned by root, mode 4755), the setuid bit must be set.
Grading
~/labs/lab02-permissions-acls/grader.sh