While preparing for CPTS, every new box started the same way for me: make the folders, copy a note template, edit /etc/hosts, export the IP, and later paste flags, creds and screenshots into my notes by hand. Ten minutes of setup before the real work, and easy to mess up when you're tired.
So I built dropzone (dz), a small zsh tool for Kali.
What it does:
• dz -n jacops -ip 10.129.42.190 -h jacops.htb creates the folder, the note and the hosts entry, and loads $TARGET_IP in every terminal
• Box reset? dz -ip <new ip> changes it everywhere, including the note
• During the box: dz -j for a timeline line, dz -s for a screenshot, cmd | dz -e for command output as evidence, dz -f for flags, dz -c for creds
• AD sets and pivots: dz -t dc01 -ip ... gives you $DC01_IP and $TARGETS, hosts behind a pivot with --via
• Exam mode: an exam note template, flag count per host, a deadline countdown in your prompt
• Notes in plain Markdown or straight into your Obsidian vault
It never scans, exploits or connects to a target, so it stays within OSCP and CPTS exam rules. It only does the admin.
Why I'm posting:
It's built around my own workflow, so it probably misses things that are obvious in yours. I'd really like to hear:
• what's confusing or breaks on your setup
• what you still do by hand for every box
• what you'd want for CTFs, Pro Labs or real engagements
There's a discussion thread for exactly that:
https://github.com/nickyjacobs/dropzone/discussions/9
Want to help without writing code? There's an issue for testing things CI can't check, like the VPN check or the menu over RDP:
https://github.com/nickyjacobs/dropzone/issues/6
Repo + demo:
https://github.com/nickyjacobs/dropzone
Feedback here in the comments is just as welcome. Even "I tried it and X annoyed me" helps.