Permissions and users · Lesson 8 of 33 · 7 minutes

Sudoers review

Read a simulated sudoers drop-in without granting power.

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
Read sudoers
Run sudo cat /etc/sudoers.d/learners.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sudo cat /etc/sudoers.d/learners
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Search NOPASSWD
Run sudo grep NOPASSWD /etc/sudoers.d/learners.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sudo grep NOPASSWD /etc/sudoers.d/learners
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Confirm user
Run whoami.
Hint & worked example
Print the effective user name.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
whoami
```
Remember: An elevated command can run with a different effective identity from the normal shell.

Understand the pattern

Sudo rules are high-impact security controls.

cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.
whoami: Print the effective user name.
An elevated command can run with a different effective identity from the normal shell.

Worked example and expected result

$ sudo cat /etc/sudoers.d/learners

learner ALL=(root) NOPASSWD: /usr/bin/systemctl status *
# fake readonly training rule

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

$ sudo grep NOPASSWD /etc/sudoers.d/learners

learner ALL=(root) NOPASSWD: /usr/bin/systemctl status *

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

$ whoami

learner

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 “Sudoers review”, which interpretation is safe?No matches is exit status 1, which is different from a malformed invocation.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Public and private files 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