Reworded the faq's no filters explanation.
Matt Pagan

Matt Pagan commited on 2014-08-22 13:52:13
Zeige 1 geänderte Dateien mit 12 Einfügungen und 9 Löschungen.

... ...
@@ -2327,21 +2327,24 @@ too.
2327 2327
 
2328 2328
     <a id="OutgoingFirewall"></a>
2329 2329
     <h3><a class="anchor" href="#OutgoingFirewall">How should I configure
2330
-    my outgoing filters?</a></h3>
2330
+    the outgoing filters on my relay?</a></h3>
2331 2331
 
2332 2332
     <p>
2333
-    Tor design assumes that any relay can reach every other relays. So
2334
-    all <em>outgoing</em> connections must be allowed.
2333
+    All <em>outgoing</em> connections must be allowed, so that each relay can 
2334
+    communicate with every other relay.
2335 2335
     </p>
2336 2336
     <p>
2337
-    Tor is promoting free network access without interference.
2338
-    Exit nodes must not attempt to filter any traffic coming from the
2339
-    Tor network. Selecting outgoing traffic is likely to forfeit the
2340
-    protections usually given to <em>common carriers</em> in many
2341
-    jurisdictions.
2337
+    In many jurisdictions, Tor relay operators are legally protected by the 
2338
+    same <em>common carrier</em> regulations that prevent internet service 
2339
+    providers from being held liable for third-party content that passes 
2340
+    through their network. Exit relays that filter some traffic would 
2341
+    likely forfeit those protections. 
2342 2342
     </p>
2343 2343
     <p>
2344
-    Exit nodes which filter traffic will get the <a
2344
+    Tor promotes free network access without interference. 
2345
+    Exit relays must not filter the traffic 
2346
+    that passes through them to the internet. 
2347
+    Exit relays found to be filtering traffic will get the <a 
2345 2348
     href="#WhatIsTheBadExitFlag">BadExit</a> flag once detected.
2346 2349
     </p>
2347 2350
 
2348 2351