ProHacking is a working notebook. Everything published here comes out of a lab I own, and it is written the way I would want to read it six months later.
Why this exists
Most security writing falls into two piles: marketing that explains nothing, or a wall of commands with no reasoning. The useful part is almost always the middle: why a particular approach was chosen, what was tried first, and what the output actually meant.
Ground rules
- Everything is tested in isolated lab environments or on systems I am authorised to test.
- No live targets, no third-party systems, no client data.
- Write-ups favour understanding over copy-paste. Commands come with reasoning.
- Corrections are welcome. If something here is wrong, I would rather know.
The setup
The lab runs on a single hypervisor with segmented VLANs, a firewall at the edge, and snapshots taken before every run, so a broken box is a two-minute rollback rather than a rebuild.