hint towards TorExitGuidelines a bit more

This commit is contained in:
Moritz Bartl 2013-01-19 12:54:25 +00:00
parent 2eb94c2363
commit 41933ead42

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