Practical cybersecurity guides, labs & compliance
Kioptrix Labs 
Build an Obsidian service card with the command, observed result, hypothesis and evidence link kept distinct. Use the retrieval review to check attachment links after moving or exporting notes and retain provenance and handling context.
Diagnose a Kioptrix VM with no identified IP through host compatibility, named-network membership and MAC-linked address evidence. Review DHCP and guest-NIC questions separately, preserving the old settings before any documented reversible change.
Review the historical Samba CVE-2003-0201 advisory separately from the service running in your Kioptrix image. Use the applicability record to retain build, backport and architecture uncertainty before any expressly authorized test.
Use an enumeration timebox to review evidence and choose whether to continue, park or revisit a lead. Preserve the next discriminating question and stop condition, and keep study timing separate from actual exam rules.
Review a Kioptrix practice screenshot through target identity, source evidence and report context. Use the practice-proof record to check what the image establishes and compare exam submissions with the current official proof requirements.
Diagnose terminal problems by separating the local terminal, transport, remote shell and PTY behavior. Use the working note to test echo, signals and terminal size separately while preserving a recovery route.
Review suspected Bash or Zsh history exposure without copying or replaying secrets. Use the response card to record access context, owner-led credential containment and the limits of history settings or deletion.
Review current identity, complete sudo policy, SUID ownership and kernel prerequisites in a Kioptrix lab without treating a clue as proof.
Describe a Kioptrix command-injection lead with the baseline request, controlled variation and attributed effect. Use the working note to separate observed behavior, execution claims, remaining alternatives and remediation that was actually retested.
Distinguish the local smbclient version, negotiated SMB dialect and remote Samba build. Use the evidence table to label each clue, handle disagreement and report an unknown version without inferring a client failure.