Skip to content
Tor traffic whitelisting gateway - Debian focussed fork of
Shell Makefile
Branch: master
Clone or download
Pull request Compare This branch is even with adrelanos:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Tor traffic whitelisting gateway

There are several transparently torifying gateways. They suffer from the same problems:

  • It's tricky to isolate circuits and issue NEWNYM signals, especially if multiple client computers are involved.
  • Any garbage software can pump identifiers into "anonymous" circuits, and get itself exploited by malicious exit nodes.
  • Trust is centralized to the gateway, which is bad enough when used by one person, and just inappropriate when shared with strangers.

corridor takes a different approach. It allows only connections to Tor relays to pass through (no clearnet leaks!), but client computers are themselves responsible for torifying their own traffic. In other words, it is a filtering gateway, not a proxying gateway.

You can think of it as defense in depth for your vanilla Tor Browser or Tails, for your beautiful scary experimental Qubes proxying schemes, etc. Or invite the hood to use your WiFi without getting into trouble.

How to install corridor using apt-get

1. Download Whonix's Signing Key.


Users can check Whonix Signing Key for better security.

2. Add Whonix's signing key.

sudo apt-key --keyring /etc/apt/trusted.gpg.d/whonix.gpg add ~/patrick.asc

3. Add Whonix's APT repository.

echo "deb buster main contrib non-free" | sudo tee /etc/apt/sources.list.d/whonix.list

4. Update your package lists.

sudo apt-get update

5. Install corridor.

sudo apt-get install corridor

How to Build deb Package

Replace apparmor-profile-torbrowser with the actual name of this package with corridor and see instructions.



corridor requires donations to stay alive!

You can’t perform that action at this time.