hint towards TorExitGuidelines a bit more
Moritz Bartl

Moritz Bartl commited on 2013-01-19 13:54:25
Zeige 1 geänderte Dateien mit 4 Einfügungen und 10 Löschungen.

... ...
@@ -50,11 +50,11 @@
50 50
 
51 51
     <p>
52 52
     2. Edit the bottom part of <a href="<page
53
-    docs/faq>#torrc">/etc/tor/torrc</a>. Define an ORPort. Note
53
+    docs/faq>#torrc">/etc/tor/torrc</a>. Define an ORPort. <b>Note
54 54
     that public relays default to being <a href="<page
55
-    docs/faq>#ExitPolicies">exit relays</a> &mdash; either change your
55
+    docs/faq>#ExitPolicies">exit relays</a></b> &mdash; either change your
56 56
     ExitPolicy line or read our <a
57
-href="https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines">guidelines
57
+href="<wiki>/doc/TorExitGuidelines">guidelines
58 58
     for exit relay operators</a>. Be sure to set your ContactInfo line
59 59
     so we can contact you if you need to upgrade or something goes wrong.
60 60
     </p>
... ...
@@ -130,13 +130,7 @@ href="https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines">guide
130 130
     </p>
131 131
 
132 132
     <p>
133
-    9. If you control the name servers for your domain, consider setting your
134
-    reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
135
-    other people see the address in their web logs, they will more quickly
136
-    understand what's going on. Adding the <a
137
-    href="<gitblob>contrib/tor-exit-notice.html">Tor
138
-    exit notice</a> on a vhost for this name can go a long way to deterring abuse
139
-    complaints to you and your ISP if you are running an exit node.
133
+    9. If you run an exit relay (great!), don't miss out on our <a href="<wiki>doc/TorExitGuidelines">Exit Guidelines</a>.
140 134
     </p>
141 135
 
142 136
     <p>
143 137