🖥️ Whonix Guide
Advanced privacy with Whonix's dual VM architecture for darknet access.
VM Setup
Whonix's core idea is splitting "connects to the internet" and "runs your applications" into two separate virtual machines that can only talk to each other through one controlled channel — which is a meaningfully different security model from Tails' single-OS approach, not just a more complicated version of the same thing. Start by installing VirtualBox from virtualbox.org, then download both the Gateway and Workstation OVA images from whonix.org and actually verify their GPG signatures before importing — these two images are the entire trust base for everything you do afterward, so a tampered image defeats the isolation model before it even starts. Import both via File → Import Appliance, giving the Gateway at least 512MB RAM and the Workstation 2GB for comfortable use, and leave the default network configuration exactly as shipped — it's preconfigured specifically so the Workstation physically cannot reach the internet except through the Gateway, and "optimizing" it is the most common way people accidentally undo that guarantee.
Gateway
The Gateway is the VM that actually touches the internet and handles every Tor connection — nothing else in the system does. Start it first and wait for the Tor icon in its system tray to turn green before doing anything else; starting the Workstation early just means it sits there with no route out until the Gateway finishes connecting. What makes this architecture stronger than a single-machine Tor setup is that the Gateway acts as a transparent proxy: it forces every packet from the Workstation through Tor at the network level, regardless of what any individual application inside the Workstation thinks it's doing. A misconfigured or even fully compromised application inside the Workstation still can't leak your real IP, because it has no network path that bypasses the Gateway to leak it through in the first place.
Workstation
The Workstation is the isolated desktop where Tor Browser and everything else you actually run lives, and it has no route to the internet except through the Gateway — not a policy choice you could accidentally disable, but a property of the virtual network topology itself. Boot it only after the Gateway shows a live Tor connection, then run the built-in Whonix Check utility, which confirms both that Tor is working correctly and that your system clock is synchronized — clock drift matters more here than it sounds, since some anonymity-relevant checks and time-based protocols behave oddly on a system clock that's noticeably off. Keep every market-related activity inside this VM specifically, never in the host OS or a different VM, since mixing environments is exactly how people accidentally leave a trace in the one place they meant to keep clean.
⚠️ Important Warnings
- ✅ Verify the Gateway and Workstation GPG signatures before import — they're the entire trust base for the isolation model
- 🔧 Never modify the default network configuration between the two VMs
- 🕐 Run Whonix Check after boot to confirm Tor connectivity and clock sync
- 🧭 Keep all market activity inside the Workstation VM only — never the host OS or a different VM