Linux Permissions
ACCESS CONTROL
MISSION BRIEF
A controlled Linux target contains a restricted practice file. The objective is to work through the access path, understand the permission context, reach the intended file, and preserve visible evidence of successful content retrieval.
01 • THE SCENARIO
The access-control checkpoint. You are working inside a deliberately controlled TryHackMe environment. The Linux host exposes a practice directory containing a file whose content is part of the lab evidence. The exercise reinforces how filesystem permissions govern what a user can read, modify, or execute.
OPERATING CONTEXT
The source task directs the learner to connect to the TryHackMe target via SSH, locate /home/student/practice/restricted_file.txt, understand Linux permissions, and capture evidence with the flag visible.
Environment Snapshot
02 • PRACTICAL WORKFLOW
Use the following sequence as a clean lab record. It is intentionally structured as an operational workflow rather than a question-and-answer sheet.
EVIDENCE STANDARD
Get Sourabh Jala’s stories in your inbox
Join Medium for free to get updates from this writer.
A professional lab submission should make the execution context, target artifact, successful retrieval, and final flag easy to verify from a single readable evidence frame.
03 • TERMINAL EVIDENCE
The original task submission contains a terminal screenshot showing the practice directory and successful reading of restricted_file.txt. The completed worksheet surfaces the same evidence and the recorded flag.
OBSERVED LAB RESULT
The terminal evidence shows the learner moving into the practice directory and reading restricted_file.txt. The source document records the resulting flag as shown below.
flag{you_understood_permission}
SUCCESS • FILE CONTENT RETRIEVED
What the Evidence Demonstrates
The target file is located beneath the student’s practice directory.
The lab workflow reaches the intended file rather than an unrelated resource.
The terminal output provides direct evidence of successful content retrieval.
The visible flag establishes completion of the practical objective.
04 • COMPLETION RECORD
CORE CONCEPT
Linux permissions form an access-control layer around filesystem objects. Effective access depends on the relationship between the requesting user, the file’s ownership/group context, and the permission bits assigned to those classes.
Operational Takeaways
Submission-Ready Record
Task: Linux Permissions
Target artifact: /home/student/practice/restricted_file.txt
Outcome: File content successfully retrieved; flag visible in evidence.
Evidence source: Original terminal screenshot supplied with the task.
