[tor-commits] r25961: {website} vidalia users can't do all that mumbo-jumbo (website/trunk/docs/en)

[Roger Dingledine <arma@xxxxxxxxxxxxxx>]

Author: arma
Date: 2012-12-25 19:25:40 +0000 (Tue, 25 Dec 2012)
New Revision: 25961

Modified:
   website/trunk/docs/en/tor-doc-relay.wml
Log:
vidalia users can't do all that mumbo-jumbo


Modified: website/trunk/docs/en/tor-doc-relay.wml
===================================================================
--- website/trunk/docs/en/tor-doc-relay.wml	2012-12-25 19:21:39 UTC (rev 25960)
+++ website/trunk/docs/en/tor-doc-relay.wml	2012-12-25 19:25:40 UTC (rev 25961)
@@ -161,23 +161,12 @@
     <h2><a class="anchor" href="#after">Step Four: Once it is working</a></h2>
     <br>
 
-    <p>
-    We recommend the following steps as well:
-    </p>
-
-    <ol>
-    <li>Read
+    <p>Read
     <a href="<wiki>doc/OperationalSecurity">about operational security</a>
     to get ideas how you can increase the security of your relay.
-    </li>
+    </p>
 
-    <li>
-    If you want to run more than one relay that's great, but please set <a
-    href="<page docs/faq>#MultipleRelays">the
-    MyFamily option</a> in all your relays' configuration files.
-    </li>
-
-    <li>
+    <p>
     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
@@ -185,24 +174,8 @@
     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.
-    </li>
+    </p>
 
-    <li>
-    If your computer isn't running a webserver, please consider
-    changing your ORPort to 443 and your DirPort to 80. Many Tor
-    users are stuck behind firewalls that only let them browse the
-    web, and this change will let them reach your Tor relay. Win32
-    relays can simply change their ORPort and DirPort directly
-    in their torrc and restart Tor. OS X or Unix relays can't bind
-    directly to these ports (since they don't run as root), so they will
-    need to set up some sort of <a
-    href="<wikifaq>#ServerForFirewalledClients">
-    port forwarding</a> so connections can reach their Tor relay. If you are
-    using ports 80 and 443 already but still want to help out, other useful
-    ports are 22, 110, and 143.
-    </li>
-    </ol>
-
     <p>
     When you change your Tor configuration, remember to verify that your
     relay still works correctly after the change.

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits