A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Unix permissions answer two different questions: who owns an object, and what actions the owner, group, and everyone else may perform. For regular files, read, write, and execute map to reading content, changing content, and executing the file. For directories, execute means traversal. That distinction is where many permission audits go wrong.
A mode such as `-rwxr-x---` describes a regular file followed by three permission triplets. Ownership is separate metadata, visible through `stat` or `ls -l`. Special bits change the rules further: setgid on a directory influences inherited group ownership, and the sticky bit constrains deletion inside shared directories. Security reviews should inspect both the mode and the parent-directory path to understand actual exposure.
Shows symbolic permissions, owner, group, numeric mode, and path for a sensitive system file. The useful habit here is to treat the command output as evidence about one system fact, not as a magical diagnosis.
The command output shown here is a training fixture description. On a live system, verify the actual output rather than assuming it matches the example.
A file may look private while its parent directory is world-traversable. Conversely, denying directory execute can block access even when the file itself is readable. Never interpret a single `ls -l` line in isolation when reviewing access paths.
Prints the shell process’s current creation mask, which affects default permissions for newly created files and directories. Read the result in context: the same command can be correct yet insufficient if a permission boundary, alternate configuration, or different backend changes what it reports.
A practitioner’s checkpoint: compare the observed behavior with the assumption your script is about to make. If the assumption is broader than the evidence, narrow the rule. If the evidence is incomplete, report the uncertainty instead of converting it into a confident finding.
Permission interpretation should remain tied to the object type; directory traversal and file read access are different checks.
Lab discipline: stay inside the declared course environment, prefer read-only checks for learning exercises, and preserve the original output of security tools before transforming it.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.