Skip to content

Commit

Permalink
Revert "Mention old tor daemon crash on starting corridor-data"
Browse files Browse the repository at this point in the history
This reverts commit 02d08e5.
  • Loading branch information
rustybird committed Nov 28, 2024
1 parent 02d08e5 commit dc36d44
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,6 @@ You can think of it as a fail-safe for your vanilla Tor Browser or Tails, for yo

- You **probably should not use corridor in combination with other iptables-based firewalls** (like ufw): They can easily clobber some or all of corridor's rules. At the very least, start corridor-init-forwarding and corridor-init-snat *after* your other firewall, e.g. using systemd orderings.

- If your [tor daemon crashes on starting corridor-data](https://github.com/rustybird/corridor/issues/51), update to tor 0.4.8.x or later.

## Installation

*You may also be interested in Patrick Schleizer's [corridor Debian package](https://github.com/adrelanos/corridor), or the [corridor page in the Whonix wiki](https://www.whonix.org/wiki/Corridor)*
Expand Down

0 comments on commit dc36d44

Please sign in to comment.