Revert tcp reset recommendation. It breaks 'connection refused' notification for exit nodes, and some newer firewalls have moved to other TCP breakage mechanisms anyways.
Mike Perry commited on 2008-03-23 20:53:37
Zeige 1 geänderte Dateien mit 1 Einfügungen und 12 Löschungen.
- docs/en/tor-doc-relay.wml 8e8024ddb..009b67671
| ... | ... |
@@ -282,18 +282,7 @@ you launch Tor. |
| 282 | 282 |
</p> |
| 283 | 283 |
|
| 284 | 284 |
<p> |
| 285 |
- |
|
| 286 |
-17. (Unix only.) You may also want to improve accessibility of your node in |
|
| 287 |
-censored locations by dropping TCP resets to its IP. Many national and |
|
| 288 |
-institutional firewalls operate by killing TCP connections that contain |
|
| 289 |
-censored keywords or byte patterns. On Linux, blocking these connection |
|
| 290 |
-resets is accomplished by running |
|
| 291 |
-'iptables -I INPUT -d your.tor.ip -p tcp --tcp-flags RST RST -j DROP'. |
|
| 292 |
- |
|
| 293 |
-</p> |
|
| 294 |
- |
|
| 295 |
-<p> |
|
| 296 |
-18. If you installed Tor via some package or installer, it probably starts |
|
| 285 |
+17. If you installed Tor via some package or installer, it probably starts |
|
| 297 | 286 |
Tor for you automatically on boot. But if you installed from source, |
| 298 | 287 |
you may find the initscripts in contrib/tor.sh or contrib/torctl useful. |
| 299 | 288 |
</p> |
| 300 | 289 |