04step · module overview

You finished Lab 01. Here's what stuck.

A quick recap of the moves you just used in the terminal — worth keeping handy. The next lab takes the same idea of snapping small tools together and points it at a recording of network traffic.

Module complete · linux-terminal-basics

You watched the intro, walked through the simulation, and pulled the flag out of a real practice machine. The terminal is no longer a scary blank screen — it's a question you now know how to answer.

XP earned+100xp

DifficultyEasy

Time spent~22min

TrackCode

≡ Recap · the five moves keep close

01 The terminal is a question. Every Linux session starts the same way — a blinking cursor waiting for you to type. You type a command, press Enter, and read the answer. There's no "submit" button.
02 Hidden files start with a dot. ls skips them; ls -la shows them all. Your home folder is full of them — files like .bashrc, .ssh/, .cache/ — and challenge flags love to hide there too.
03 find searches every folder. When you don't know where a file lives, find / -name "*flag*" 2>/dev/null checks every folder for a matching name. The 2>/dev/null bit just hides the "you're not allowed in there" messages so the real results stand out.
04 grep finds the words. grep -r 'pattern' /path reads inside every file under /path and prints any line that contains the word you asked for. Most beginner labs come down to one find plus one grep.
05 cat is your final move. Once you know where the file is, cat prints out what's inside it. Add | (which passes one command's output into the next) and > (which saves output into a file), and the terminal becomes a tiny assembly line — each tool does one job well, and you snap them together on the fly.

Next module

Lab 02 · Networking & Packet Analysis

Open a saved recording of network traffic (a .pcap file) and work out the attacker's address and the doorway they used to sneak back in. Same snap-tools-together mindset — different tools.

start · lab 02 →