corridor-data
corridor-init-forwarding
corridor-init-logged
corridor-init-snat
corridor-load-config
corridor-load-ipset
corridor-load-ipset-logged
corridor-load-ipset-relays
corridor-stop-forwarding
corridor-stop-snat
corridor 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 a fail-safe 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.
Keep track of acceptable Tor relays.
corridor-data script opens a Tor control connection and subscribes to NEWCONSENSUS events (announcements listing all public relays), unless you inform it of any bridges to use instead.
corridor-data &
Set up IP traffic forwarding.
corridor-init-forwarding
Set up Source NAT with iptables.
corridor-init-snat
Log attempted leaks from selected clients. This command will block until corridor_relays gets populated!
corridor-init-logged
Sanity test for the /etc/corridor.d configuration folder.
Also internally used by corridor.
corridor-load-config
Stop actions.
Internally used by corridor.
0 Success.
non-zero Failure.
/etc/corridor.d
https://github.com/rustybird/corridor
This package is produced independently of, and carries no guarantee from, The Tor Project.
This man page has been written by Patrick Schleizer ([email protected]).
corridor has been written by rustybird ([email protected]).