tor-webwml.git

@@ -1,32 +1,32 @@

 ## translation metadata

 # Revision: $Revision$

-#include "head.wmi" TITLE="Server Configuration Instructions"

+#include "head.wmi" TITLE="Relay Configuration Instructions"

 <div class="center">

 <div class="main-column">

-<h1>Configuring a <a href="<page index>">Tor</a> server</h1>

+<h1>Configuring a <a href="<page index>">Tor</a> relay</h1>

 <br />

 <p>

 The Tor network relies on volunteers to donate bandwidth. The more

-people who run servers, the faster the Tor network will be. If you have

+people who run relays, the faster the Tor network will be. If you have

 at least 20 kilobytes/s each way, please help out Tor by configuring your

-Tor to be a server too. We have many features that make Tor servers easy

+Tor to be a relay too. We have many features that make Tor relays easy

 and convenient, including rate limiting for bandwidth, exit policies so

 you can limit your exposure to abuse complaints, and support for dynamic

 IP addresses.</p>

-<p>Having servers in many different places on the Internet is what

+<p>Having relays in many different places on the Internet is what

 makes Tor users secure. <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You

 may also get stronger anonymity yourself</a>,

 since remote sites can't know whether connections originated at your

 computer or were relayed from others.</p>

-<p>Setting up a Tor server is easy and convenient:

+<p>Setting up a Tor relay is easy and convenient:

 <ul>

 <li>Tor has built-in support for <a

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

@@ -36,34 +36,34 @@ but want to limit the number of bytes per day

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hibernation

 feature</a>.

 </li>

-<li>Each Tor server has an <a

+<li>Each Tor relay has an <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#RunAServerBut">exit

 policy</a> that specifies what sort of outbound connections are allowed

-or refused from that server. If you are uncomfortable allowing people

-to exit from your server, you can set it up to only allow connections

-to other Tor servers.

+or refused from that relay. If you are uncomfortable allowing people

+to exit from your relay, you can set it up to only allow connections

+to other Tor relays.

 </li>

-<li>It's fine if the server goes offline sometimes. The directories

-notice this quickly and stop advertising the server. Just try to make

-sure it's not too often, since connections using the server when it

+<li>It's fine if the relay goes offline sometimes. The directories

+notice this quickly and stop advertising the relay. Just try to make

+sure it's not too often, since connections using the relay when it

 disconnects will break.

 </li>

-<li>We can handle servers with dynamic IPs just fine &mdash; simply

+<li>We can handle relays with dynamic IPs just fine &mdash; simply

 leave the Address config option blank, and Tor will try to guess.

 </li>

-<li>If your server is behind a NAT and it doesn't know its public

+<li>If your relay is behind a NAT and it doesn't know its public

 IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

 forwarding. Forwarding TCP connections is system dependent but <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this

 FAQ entry</a> offers some examples on how to do this.

 </li>

-<li>Your server will passively estimate and advertise its recent

-bandwidth capacity, so high-bandwidth servers will attract more users than

-low-bandwidth ones. Therefore having low-bandwidth servers is useful too.

+<li>Your relay will passively estimate and advertise its recent

+bandwidth capacity, so high-bandwidth relays will attract more users than

+low-bandwidth ones. Therefore having low-bandwidth relays is useful too.

 </li>

 </ul>

-<p>You can run a Tor server on

+<p>You can run a Tor relay on

 pretty much any operating system, but see <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerOS">this

 FAQ entry</a> for advice about which ones work best and other problems

@@ -91,7 +91,7 @@ while to make sure it's actually working.</p>

 <hr />

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

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

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

 <br />

 <p>

@@ -110,20 +110,20 @@ href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#torrc">this

 FAQ entry</a> for help.)

 Make sure to define at least Nickname and ORPort. Create the DataDirectory

 if necessary, and make sure it's owned by the user that will be running

-tor. <em>If you want to run more than one server that's great, but

+tor. <em>If you want to run more than one relay that's great, but

 please set <a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#MultipleServers">the

-MyFamily option</a> in all your servers' configuration files.</em>

+MyFamily option</a> in all your relays' configuration files.</em>

 </p>

 <p>

 4. If you are using a firewall, open a hole in your firewall so

-incoming connections can reach the ports you configured in step 3 (ORPort, plus

+incoming connections can reach the ports you configured (ORPort, plus

 DirPort if you enabled it). Make sure you allow all outgoing connections,

-so your server can reach the other Tor servers.

+so your relay can reach the other Tor relays.

 </p>

 <p>

-5. Restart your server. If it <a

+5. Restart your relay. If it <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Logs">logs

 any warnings</a>, address them.

 </p>

@@ -141,7 +141,7 @@ where new development releases are announced.

 7. Have a look at the manual.

 The <a href="<page tor-manual>">manual</a> for the

 latest stable version provides a list of all the possible configuration

-options for both clients and servers.

+options for both clients and relays.

 If you are running the development version of Tor, the manual is available

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

 </p>

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

 <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

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

 try to determine whether the ports you configured are reachable from

 the outside. This may take up to 20 minutes. Look for a

 <a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Logs">log

 entry</a> like

 <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>

-If you don't see this message, it means that your server is not reachable

+If you don't see this message, it means that your relay is not reachable

 from the outside — you should re-check your firewalls, check that it's

 testing the IP and port you think it should be testing, etc.

 </p>

 <p>When it decides that it's reachable, it will upload a "server

 descriptor" to the directories. This will let clients know

-what address, ports, keys, etc your server is using. You can <a

+what address, ports, keys, etc your relay is using. You can <a

 href="http://moria.seul.org:9032/tor/status/authority">load one of

 the network statuses manually</a> and

 look through it to find the nickname you configured, to make sure it's

@@ -183,11 +183,11 @@ We recommend the following steps as well:

 <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.

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

 </p>

 <p>

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

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

 access to many popular services, but restricts 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.

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

 </p>

 <p>

-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

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

+in your DataDirectory). This is your relay'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

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

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#UpgradeServer">move

-or restore your Tor server</a> if something goes wrong.

+or restore your Tor relay</a> if something goes wrong.

 </p>

 <p>

@@ -230,32 +230,32 @@ understand what's going on.

 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

-servers can simply change their ORPort and DirPort directly

-in their torrc and restart Tor. OS X or Unix servers can't bind

+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="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">

-port forwarding</a> so connections can reach their Tor server. If you are

+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.

 </p>

 <p>

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

+14. If your Tor relay 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

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

 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">safest

 way to reach that webserver</a>, and always build a circuit that ends

-at your server. If you don't want to allow the connections, you must

+at your relay. If you don't want to allow the connections, you must

 explicitly reject them in your exit policy.

 </p>

 <p>

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

+15. (Unix only). Make a separate user to run the relay. 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

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

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

 as a 'tor' user avoids issues with identd and other services that

 detect user name. If you're the paranoid sort, feel free to <a

@@ -284,7 +284,7 @@ you may find the initscripts in contrib/tor.sh or contrib/torctl useful.

 <p>

 When you change your Tor configuration, remember to verify that your

-server still works correctly after the change. Be sure to set your

+relay still works correctly after the change. Be sure to set your

 "ContactInfo" line in the torrc so we can contact you if you need to

 upgrade or something goes wrong. If you have problems or questions, see

 the <a href="<page documentation>#Support">Support</a> section or