RunARelayBut sucks as an anchor name
Roger Dingledine

Roger Dingledine commited on 2009-06-24 10:23:15
Zeige 3 geänderte Dateien mit 8 Einfügungen und 7 Löschungen.

... ...
@@ -95,7 +95,7 @@ If not, see number 4 below.</li>
95 95
 <li>Choose the <tt>Exit Policies</tt> tab.  If you want to allow others
96 96
 to use your relay for these services, don't change anything.  Un-check
97 97
 the services you don't want to allow people to <a href="<page
98
-faq>#RunARelayBut">reach from your relay</a>.
98
+faq>#ExitPolicies">reach from your relay</a>.
99 99
 If you want to be a non-exit relay, un-check all services.</li>
100 100
 <li>Click the <tt>Ok</tt> button.  See Step Three below for confirmation
101 101
 that the relay is working correctly.</li>
... ...
@@ -107,7 +107,7 @@ that the relay is working correctly.</li>
107 107
 <li>Edit the bottom part of <a
108 108
 href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">your
109 109
 torrc file</a>. Make sure to define ORPort and <a href="<page
110
-faq>#RunARelayBut">look at ExitPolicy</a>
110
+faq>#ExitPolicies">look at ExitPolicy</a>
111 111
 if you want to be a public relay (recommended), or just add
112 112
 <a href="<page bridges>#RunningABridge">these lines</a>
113 113
 if you want to be a <a href="<page bridges>">bridge</a>
... ...
@@ -110,7 +110,7 @@ it only transports correctly-formed TCP connections.
110 110
 <h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3>
111 111
 
112 112
 <p>
113
-<a href="<page faq>#RunARelayBut">Moved to the new FAQ page</a>
113
+<a href="<page faq>#ExitPolicies">Moved to the new FAQ page</a>
114 114
 </p>
115 115
 
116 116
 <a id="HowMuchAbuse"></a>
... ...
@@ -291,7 +291,7 @@ services that aggregate many users behind a few IP addresses. Tor is
291 291
 not so different from AOL in this respect.</p>
292 292
 
293 293
 <p>Lastly, please remember that Tor relays have <a
294
-href="#RunARelayBut">individual exit policies</a>. Many Tor relays do
294
+href="<page faq>#ExitPolicies">individual exit policies</a>. Many Tor relays do
295 295
 not allow exiting connections at all. Many of those that do allow some
296 296
 exit connections might already disallow connections to
297 297
 your service. When you go about banning nodes, you should parse the
... ...
@@ -49,7 +49,7 @@ have a virus or spyware?</a></li>
49 49
 <p>Running a Tor relay:</p>
50 50
 <ul>
51 51
 <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
52
-<li><a href="#RunARelayBut">I'd run a relay, but I don't want to deal
52
+<li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
53 53
 with abuse issues.</a></li>
54 54
 <li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li>
55 55
 </ul>
... ...
@@ -719,7 +719,7 @@ ernation
719 719
 feature</a>.
720 720
 </li>
721 721
 <li>Each Tor relay has an <a
722
-href="#RunARelayBut">exit
722
+href="#ExitPolicies">exit
723 723
 policy</a> that specifies what sort of outbound connections are allowed
724 724
 or refused from that relay. If you are uncomfortable allowing people
725 725
 to exit from your relay, you can set it up to only allow connections
... ...
@@ -749,7 +749,8 @@ low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
749 749
 <hr />
750 750
 
751 751
 <a id="RunARelayBut"></a>
752
-<h3><a class="anchor" href="#RunARelayBut">I'd run a relay, but I don't
752
+<a id="ExitPolicies"></a>
753
+<h3><a class="anchor" href="#ExitPolicies">I'd run a relay, but I don't
753 754
 want to deal with abuse issues.</a></h3>
754 755
 
755 756
 <p>
756 757