merge the old faq-abuse exitpolicies entry
Roger Dingledine

Roger Dingledine commited on 2009-06-24 07:01:31
Zeige 2 geänderte Dateien mit 11 Einfügungen und 17 Löschungen.

... ...
@@ -16,7 +16,6 @@
16 16
 <li><a href="<page faq-abuse>#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></li>
17 17
 <li><a href="<page faq-abuse>#DDoS">What about distributed denial of service attacks?</a></li>
18 18
 <li><a href="<page faq-abuse>#WhatAboutSpammers">What about spammers?</a></li>
19
-<li><a href="<page faq-abuse>#ExitPolicies">How do Tor exit policies work?</a></li>
20 19
 <li><a href="<page faq-abuse>#HowMuchAbuse">Does Tor get much abuse?</a></li>
21 20
 <li><a href="<page faq-abuse>#TypicalAbuses">So what should I expect if I run an exit relay?</a></li>
22 21
 <li><a href="<page faq-abuse>#IrcBans">Tor is banned from the IRC network I want to use.</a></li>
... ...
@@ -110,15 +109,9 @@ it only transports correctly-formed TCP connections.
110 109
 <a id="ExitPolicies"></a>
111 110
 <h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3>
112 111
 
113
-<p>Each Tor relay has an exit policy that specifies what sort of
114
-outbound connections are allowed or refused from that relay. The exit
115
-policies are propagated to the client via the directory, so clients
116
-will automatically avoid picking exit nodes that would refuse to exit
117
-to their intended destination. </p>
118
-
119
-<p>This way each relay can decide the services, hosts, and networks
120
-he wants to allow connections to, based on abuse potential and his own
121
-situation. </p>
112
+<p>
113
+<a href="<page faq>#RunARelayBut">Moved to the new FAQ page</a>
114
+</p>
122 115
 
123 116
 <a id="HowMuchAbuse"></a>
124 117
 <h3><a class="anchor" href="#HowMuchAbuse">Does Tor get much abuse?</a></h3>
... ...
@@ -298,7 +291,7 @@ services that aggregate many users behind a few IP addresses. Tor is
298 291
 not so different from AOL in this respect.</p>
299 292
 
300 293
 <p>Lastly, please remember that Tor relays have <a
301
-href="#ExitPolicies">individual exit policies</a>. Many Tor relays do
294
+href="#RunARelayBut">individual exit policies</a>. Many Tor relays do
302 295
 not allow exiting connections at all. Many of those that do allow some
303 296
 exit connections might already disallow connections to
304 297
 your service. When you go about banning nodes, you should parse the
... ...
@@ -719,8 +719,7 @@ ernation
719 719
 feature</a>.
720 720
 </li>
721 721
 <li>Each Tor relay has an <a
722
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RunARelayBut">ex
723
-it
722
+href="#RunARelayBut">exit
724 723
 policy</a> that specifies what sort of outbound connections are allowed
725 724
 or refused from that relay. If you are uncomfortable allowing people
726 725
 to exit from your relay, you can set it up to only allow connections
... ...
@@ -759,10 +758,12 @@ Great. That's exactly why we implemented exit policies.
759 758
 
760 759
 <p>
761 760
 Each Tor relay has an exit policy that specifies what sort of outbound
762
-connections he will allow from his relay, and what sort he will
763
-refuse. The exit policies are propagated to the client in the directory,
764
-so clients will avoid picking exit nodes that would refuse to exit to
765
-their intended destination.
761
+connections are allowed or refused from that relay. The exit policies are
762
+propagated to the client via the directory, so clients will automatically
763
+avoid picking exit relays that would refuse to exit to their intended
764
+destination. This way each relay can decide the services, hosts, and
765
+networks he wants to allow connections to, based on abuse potential and
766
+his own situation.
766 767
 </p>
767 768
 
768 769
 <p>
769 770