--- title: 90s Hacker Lab Workflow date: 2026-06-26 status: Manual tags: hacker, journal, workflow summary: Hacker Work Flow --- # 90s Hacker Lab Workflow ## Linux, Privacy, Code, and Defensive Security Practice This workflow is built from handwritten operator notes and reshaped into a lawful, educational path for learning Linux, privacy tooling, command-line discipline, and defensive security research. The core rule is simple: > A hacker is a programmer, coder, builder, and systems thinker — not just someone who runs tools. This path is for personal labs, owned devices, CTFs, test networks, and authorized environments only. --- ## Phase 0 — Ground Rules Before touching tools, define the legal boundary. Use only: * Your own devices * Your own lab network * Local virtual machines * CTF platforms * Authorized security-training environments * Documented client or employer-approved systems Do not use: * Unknown Wi-Fi * Third-party networks * Public targets * Real companies * Real user accounts * Any workflow involving theft, exfiltration, destruction, or hiding activity The goal is skill, not damage. --- ## Phase 1 — Hardware and Boot Media Suggested lab hardware: * Windows laptop or desktop * Linux laptop or desktop * Spare USB drives * ARM device, Raspberry Pi, or small-form-factor node * Mobile test device * External storage for backups * Dedicated lab router if available Bootable media tools: * Rufus * Win32 Disk Imager * Ventoy * Balena Etcher Recommended first images: * Ubuntu Desktop * Arch Linux * Kali Linux, for authorized security labs only * BlackArch, for advanced authorized research * Tails OS, for privacy study * Kodachi Linux, for privacy-oriented live-session study --- ## Phase 2 — First Linux Install Start with a clean Linux install. Recommended beginner flow: 1. Download Ubuntu Desktop. 2. Verify the ISO hash. 3. Write the ISO to USB using Rufus, Ventoy, or Win32 Disk Imager. 4. Boot the spare machine from USB. 5. Install Ubuntu on a non-critical device. 6. Confirm networking works. 7. Update the system. 8. Install baseline tools. Baseline tools: ```bash sudo apt update sudo apt upgrade sudo apt install vim nano curl wget git net-tools dnsutils whois traceroute ``` Optional interface direction: * Desktop environment for beginners * i3 window manager for lightweight Linux practice * CLI-only for advanced terminal discipline --- ## Phase 3 — Arch Linux Track Arch Linux teaches the system from the ground up. Core Arch tools and concepts: * `fdisk` * `cfdisk` * `gdisk` * `parted` * `gparted` * `mkfs` * `mkswap` * `mount` * `umount` * `pacman` * `mkinitcpio` * `systemd` * `networkd` * `dhcpcd` * `netctl` * `ip a` Learning objectives: * Partition a disk * Format filesystems * Mount filesystems * Install a base system * Configure networking * Install a bootloader * Understand `/etc/fstab` * Understand users, groups, and permissions This phase should be performed only on a spare lab machine or virtual machine. --- ## Phase 4 — Linux Command-Line Foundations Core identity and system commands: ```bash who -a whoami which bash busybox ip a ping grep awk sed ln ``` Command meanings: | Command | Purpose | | --------- | ----------------------------------------- | | `who -a` | Shows logged-in users and session details | | `whoami` | Shows the current user | | `which` | Locates the path of an executable | | `busybox` | Provides compact Unix utilities | | `ln` | Creates links and symlinks | | `sed` | Edits text streams | | `awk` | Processes structured text | | `grep` | Searches text | | `ping` | Tests reachability | | `ip a` | Shows network interfaces and addresses | --- ## Phase 5 — Permissions, Ownership, and Red Zones Linux permissions are foundational. Permission values: | Value | Permission | | ----- | ------------- | | `4` | Read | | `2` | Write | | `1` | Execute | | `0` | No permission | Examples: | Mode | Meaning | | ----- | ----------------------------------------------- | | `777` | Read, write, execute for everyone | | `755` | Owner can write; everyone can read and execute | | `655` | Owner read/write; group and others read/execute | Permission structure: ```text owner / group / everyone ``` Example permission string: ```text rwx r-x r-x ``` Ownership command: ```bash sudo chown user:group file ``` Sudo notes: ```bash sudo su - ``` Vim notes: ```vim :set number ``` Saving a protected file from Vim: ```vim :w !sudo tee % ``` Production warning: > Root is the red zone. Use sudo deliberately. Do not work as root unless there is a clear reason. --- ## Phase 6 — Network and Privacy Basics Study networking through lawful, defensive use. Topics: * IPv4 status * IPv6 status * NAT IP * DNS * DNSCrypt * DNS leak testing * VPN basics * OpenVPN * Proton VPN or similar providers * Tor * I2P * Tails OS * Kodachi Linux Learning objectives: * Understand public versus private IP addresses * Understand NAT * Understand DNS resolution * Understand DNS leaks * Understand VPN routing * Understand Tor as a privacy network * Understand I2P as an overlay network * Understand the limits of anonymity tools Safe rule: > Privacy tools are for privacy, journalism, research, and personal security. They are not a license to target systems you do not own. --- ## Phase 7 — Defensive Security Research Security tooling should be learned inside labs. Approved environments: * Local VMs * Home lab * Hack The Box * TryHackMe * OverTheWire * VulnHub * CTF events * Employer-approved test environments Tools and systems: * Kali Linux * BlackArch Linux * Arch Linux * Ubuntu * BusyBox * Vim * Bash * PowerShell Security framework: Use the Cyber Kill Chain as a defensive model: 1. Reconnaissance awareness 2. Delivery detection 3. Exploitation prevention 4. Installation prevention 5. Command-and-control detection 6. Objective identification 7. Containment and response 8. Documentation and lessons learned Blue-team translation: | Offensive Concept | Defensive Site-Safe Translation | | ----------------- | ------------------------------------------------ | | Recon | Asset inventory and exposure review | | Weaponization | Threat modeling | | Exploit | Vulnerability validation in lab only | | Install | Persistence detection | | C2 | Egress monitoring | | Exfiltration | Data-loss prevention | | Cleanup | Evidence preservation and incident documentation | --- ## Phase 8 — Logging and Accountability Logs are not the enemy. Logs are the record. Study: ```bash /var/log/syslog /var/log/auth.log /var/log/lastlog /etc/passwd /etc/sudoers crontab -e ``` Defensive objectives: * Review login history * Review sudo usage * Review failed authentication * Review cron entries * Review new users * Review privilege changes * Preserve logs during incidents * Document what changed and why Site principle: > A professional does not erase logs. A professional understands logs. --- ## Phase 9 — Windows Administration Track Windows systems require their own study path. Topics: * PowerShell * `.NET` * WMI * DCOM * Event Viewer * Windows Defender * RDP * Azure Virtual Desktop * Active Directory basics * Endpoint detection and response PowerShell is required for serious Windows administration. Windows learning objectives: * Query system information * Read event logs * Understand services * Understand remote administration * Understand endpoint policy * Understand identity and access controls --- ## Phase 10 — Code Discipline A hacker should know how to code. Study languages: * Bash * Python * C * Rust * Assembly fundamentals * JavaScript * PowerShell Long-term question: > Have I learned C, Assembly, and Rust yet? Recommended path: 1. Bash for automation 2. Python for scripting 3. C for systems thinking 4. Rust for memory-safe systems work 5. Assembly for low-level understanding 6. PowerShell for Windows administration --- ## Phase 11 — Shell and Syntax Notes Bash basics: ```bash #!/bin/bash ``` Shell comparison: | Shell | Notes | | ---------- | ------------------------------------------- | | `bash` | Bourne Again Shell | | `sh` | Traditional shell | | `zsh` | Extended interactive shell | | PowerShell | Windows and cross-platform automation shell | Comparison operators: | Operator | Meaning | | -------- | ------------------ | | `-lt` | Less than | | `-gt` | Greater than | | `-eq` | Equal to | | `-ne` | Not equal | | `-le` | Less than or equal | Logical operators: | Operator | Meaning | | -------- | ----------- | | `&&` | Logical AND | | `||` | Logical OR | | `!` | Logical NOT | Naming styles: | Style | Example | | ---------- | ------------- | | camelCase | `properName` | | snake_case | `proper_name` | | PascalCase | `ProperName` | --- ## Phase 12 — Documentation and Site Output Every lab session should produce documentation. Recommended format: ```text Date: System: Goal: Tools Used: Commands Practiced: What Worked: What Failed: Security Lesson: Next Step: ``` Example: ```text Date: 2026 System: Ubuntu Desktop Lab Goal: Learn Linux permissions Tools Used: chmod, chown, sudo, vim Commands Practiced: chmod 755, chown user:group, :set number What Worked: Permission math became clearer What Failed: Needed more practice with group ownership Security Lesson: Root access must be controlled Next Step: Build Arch VM and document each install stage ``` --- ## Out-of-Scope Material The handwritten notes contained some concepts that are not appropriate for a public workflow. These have been intentionally converted into lawful, defensive equivalents. Excluded or reframed: * Targeting real organizations * Exfiltration * Botnet activity * Anti-forensics * Log deletion * Unauthorized Wi-Fi use * Unauthorized persistence * Destructive device handling * Any workflow involving third-party systems without permission The public version keeps the value: * Linux mastery * Privacy literacy * Defensive security * Systems thinking * Coding discipline * Ethical boundaries --- ## Closing Principle Hacker does not mean criminal. Hacker means builder. Programmer. Coder. Operator. Researcher. Systems thinker. The work is not the mask. The work is the discipline. Code on.