tor-webwml.git

@@ -92,8 +92,8 @@ of the Unix Tor installation howto.

 while to make sure it's actually working.</p>

 <hr />

-<a id="one"></a>

-<h2><a class="anchor" href="#one">Step One: Set it up as a server</a></h2>

+<a id="setup"></a>

+<h2><a class="anchor" href="#setup">Step One: Set it up as a server</a></h2>

 <br />

 <p>

@@ -102,7 +102,8 @@ your clock with public time servers.

 </p>

 <p>

-2. Make sure name resolution works (that is, your computer can resolve addresses correctly).

+2. Make sure name resolution works (that is, your computer can resolve

+Internet addresses correctly).

 </p>

 <p>

@@ -151,13 +152,9 @@ If you are running the development version of Tor the manual is available

 <a href="<page tor-manual-cvs>">here</a>.

 </p>

-<p>

-8. Read

-<a href="http://wiki.noreply.org/noreply/TheOnionRouter/OperationalSecurity">this document</a>

-to get ideas how you can increase the security of your server.

 <hr />

-<a id="two"></a>

-<h2><a class="anchor" href="#two">Step Two: Make sure it's working</a></h2>

+<a id="check"></a>

+<h2><a class="anchor" href="#check">Step Two: Make sure it's working</a></h2>

 <br />

 <p>As soon as your server manages to connect to the network, it will

@@ -179,46 +176,22 @@ there. You may need to wait a few seconds to give enough time for it to

 make a fresh directory.</p>

 <hr />

-<a id="three"></a>

-<h2><a class="anchor" href="#three">Step Three: Register your nickname</a></h2>

+<a id="after"></a>

+<h2><a class="anchor" href="#after">Step Three: Once it's working</a></h2>

 <br />

 <p>

-Once you are convinced it's working (after a day or two maybe), you should

-register your server.

-This reserves your nickname so nobody else can take it, and lets us

-contact you if you need to upgrade or something goes wrong.

-</p>

-

-<p>

-Send mail to <a

-href="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</a> with a

-subject of '[New Server] <your server's nickname>' and

-include the following information in the message:

+We recommend the following steps as well:

 </p>

-<ul>

-<li>Your server's nickname</li>

-<li>The fingerprint for your server's key (the contents of the

-"fingerprint" file in your DataDirectory — on Windows, look in

-\<i>username</i>\Application&nbsp;Data\tor\ or \Application&nbsp;Data\tor\;

-on OS X, look in /Library/Tor/var/lib/tor/; and on Linux/BSD/Unix,

-look in /var/lib/tor or ~/.tor)

-</li>

-<li>Who you are, so we know whom to contact if a problem arises</li>

-<li>What kind of connectivity the new server will have</li>

-</ul>

-

-<hr />

-<a id="four"></a>

-<h2><a class="anchor" href="#four">Step Four: Once it's working</a></h2>

-<br />

 <p>

-We recommend the following steps as well:

+8. Read

+<a href="http://wiki.noreply.org/noreply/TheOnionRouter/OperationalSecurity">this document</a>

+to get ideas how you can increase the security of your server.

 </p>

 <p>

-6. Decide what exit policy you want. By default your server allows

+9. Decide what exit policy you want. By default your server allows

 access to many popular services, but we restrict some (such as port 25)

 due to abuse potential. You might want an exit policy that is

 less restrictive or more restrictive; edit your torrc appropriately.

@@ -230,7 +203,7 @@ sure your ISP is ok with that choice.

 </p>

 <p>

-7. Decide about rate limiting. Cable modem, DSL, and other users

+10. Decide about rate limiting. Cable modem, DSL, and other users

 who have asymmetric bandwidth (e.g. more down than up) should

 rate limit to their slower bandwidth, to avoid congestion. See the <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate

@@ -238,7 +211,7 @@ limiting FAQ entry</a> for details.

 </p>

 <p>

-8. Back up your Tor server's private key (stored in "keys/secret_id_key"

+11. Back up your Tor server's private key (stored in "keys/secret_id_key"

 in your DataDirectory). This is your server's "identity," and

 you need to keep it safe so nobody can read the traffic that goes

 through your server. This is the critical file to keep if you need to <a

@@ -247,14 +220,14 @@ or restore your Tor server</a> if something goes wrong.

 </p>

 <p>

-9. If you control the name servers for your domain, consider setting

+12. If you control the name servers for your domain, consider setting

 your hostname to 'anonymous' or 'proxy' or 'tor-proxy', so when other

 people see the address in their web logs, they will more quickly

 understand what's going on.

 </p>

 <p>

-10. If your computer isn't running a webserver, please consider

+13. 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 server. Win32

@@ -269,7 +242,7 @@ ports are 22, 110, and 143.

 </p>

 <p>

-11. If your Tor server provides other services on the same IP address

+14. If your Tor server provides other services on the same IP address

 — such as a public webserver — make sure that connections to the

 webserver are allowed from the local host too. You need to allow these

 connections because Tor clients will detect that your Tor server is the <a

@@ -280,7 +253,7 @@ explicitly reject them in your exit policy.

 </p>

 <p>

-12. (Unix only). Make a separate user to run the server. If you

+15. (Unix only). Make a separate user to run the server. If you

 installed the OS X package or the deb or the rpm, this is already

 done. Otherwise, you can do it by hand. (The Tor server doesn't need to

 be run as root, so it's good practice to not run it as root. Running

@@ -291,7 +264,7 @@ into a chroot jail</a>.)

 </p>

 <p>

-13. (Unix only.) Your operating system probably limits the number

+16. (Unix only.) Your operating system probably limits the number

 of open file descriptors per process to 1024 (or even less). If you

 plan to be running a fast exit node, this is probably not enough. On

 Linux, you should add a line like "toruser hard nofile 8192" to your

@@ -304,7 +277,7 @@ you launch Tor.

 </p>

 <p>

-14. If you installed Tor via some package or installer, it probably starts

+17. If you installed Tor via some package or installer, it probably starts

 Tor for you automatically on boot. But if you installed from source,

 you may find the initscripts in contrib/tor.sh or contrib/torctl useful.

 </p>

@@ -319,6 +292,37 @@ the change.

 <hr />

+<a id="register"></a>

+<h2><a class="anchor" href="#register">Step Four: Register your nickname</a></h2>

+<br />

+

+<p>

+Let it run a few days to make sure it's actually working and that you're

+happy with its level of resource use. Then you should register your server.

+This reserves your nickname so nobody else can take it, and lets us

+contact you if you need to upgrade or something goes wrong.

+</p>

+

+<p>

+Send mail to <a

+href="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</a> with a

+subject of '[New Server] <your server's nickname>' and

+include the following information in the message:

+</p>

+<ul>

+<li>Your server's nickname</li>

+<li>The fingerprint for your server's key (the contents of the

+"fingerprint" file in your DataDirectory — on Windows, look in

+\<i>username</i>\Application&nbsp;Data\tor\ or \Application&nbsp;Data\tor\;

+on OS X, look in /Library/Tor/var/lib/tor/; and on Linux/BSD/Unix,

+look in /var/lib/tor or ~/.tor)

+</li>

+<li>Who you are, so we know whom to contact if a problem arises</li>

+<li>What kind of connectivity the new server will have</li>

+</ul>

+

+<hr />

+

 <p>If you have suggestions for improving this document, please <a

 href="<page contact>">send them to us</a>. Thanks!</p>