Permissions and users · Lesson 27 of 33 · 8 minutes

Group write risk

Spot group ownership before changing modes.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Set lab group
Run chgrp www-data lab.
Hint & worked example
Change the file group within the permissions of the acting user.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chgrp www-data lab
```
Remember: A group name alone does not grant access unless membership and mode bits agree.
2
Set lab mode
Run chmod 750 lab.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 750 lab
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
3
Inspect lab mode
Run stat lab.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat lab
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

chgrp: Change the file group within the permissions of the acting user.
A group name alone does not grant access unless membership and mode bits agree.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ chgrp www-data lab

group www-data set on /home/learner/lab

Exit status: 0. The command completed successfully in the training fixture.

$ chmod 750 lab

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ stat lab

Path: /home/learner/lab
Type: dir
Mode: drwxr-x---
Owner: learner
Group: www-data
Size: 0 items

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Group write risk”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Do not use 777 as a blanket fix. Grant the smallest access needed.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the chmod workflow from “Group write risk” to another server, what should you do?Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Least privilege audit Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual