tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 3-low
4) 
5) #include "head.wmi" TITLE="Tor: Linux/BSD/Unix Install Instructions" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page docs/documentation>">Documentation &raquo; </a>
10)     <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix Client</a>
11)   </div> 
12)   <div id="maincol"> 

13)     <h1>Running the <a href="<page index>">Tor</a> client on Linux/BSD/Unix</h1>

14)     <br>

15)     
16)     <p>
17)     <b>Note that these are the installation instructions for running a Tor
18)     client. If you want to relay traffic for others to help the network grow
19)     (please do), read the <a
20)     href="<page docs/tor-doc-relay>">Configuring a relay</a> guide.</b>
21)     </p>
22)     

23)     <hr>

24)     <a id="installing"></a>
25)     <h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>

26)     <br>

27)     
28)     <p>
29)     The latest release of Tor can be found on the <a
30)     href="<page download/download>">download</a> page. We have packages for Debian,
31)     Red Hat, Gentoo, *BSD, etc there too. If you're
32)     using Ubuntu, don't use the default packages: use <a
33)     href="<page docs/debian>#ubuntu">our deb repository</a> instead.

34)     Similarly, CentOS / Fedora / OpenSUSE users should use <a href="<page
35)     docs/rpms>">our rpm repository</a> instead.

36)     </p>
37)     
38)     <p>If you're building from source, first install <a
39)     href="http://www.monkey.org/~provos/libevent/">libevent</a>, and
40)     make sure you have openssl and zlib (including the -devel packages if

41)     applicable). Then run:<br>
42)     <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable></tt><br>
43)     <tt>./configure &amp;&amp; make</tt><br>

44)     Now you can run tor as <tt>src/or/tor</tt>, or you can run <tt>make install</tt>
45)     (as root if necessary) to install it into /usr/local/, and then you can
46)     start it just by running <tt>tor</tt>.
47)     </p>
48)     
49)     <p>Tor comes configured as a client by default. It uses a built-in
50)     default configuration file, and most people won't need to change any of
51)     the settings. Tor is now installed.
52)     </p>
53)     

54)     <hr>

55)     <a id="using"></a>

56)     <h2><a class="anchor" href="#using">Step Two: Configure your applications to use Tor</a></h2>

57)     <br>

58)     

59)     <p>After installing Tor, you need to configure your applications to
60)     use them. The first step is to set up web browsing.</p>

61)     
62)     <p>You should use Tor with Firefox and Torbutton, for best safety.
63)     Simply install the <a

64)     href="<page torbutton/index>">Torbutton

65)     plugin</a>, restart your Firefox, and you're all set:
66)     </p>
67)     
68)     <img alt="Torbutton plugin for Firefox"

69)     src="$(IMGROOT)/screenshot-torbutton.png"

70)    >

71)     

72)     <br>

73)     
74)     <p>
75)     If you plan to run Firefox on a different computer than Tor, see the <a

76)     href="<wikifaq>#SocksListenAddress">

77)     FAQ
78)     entry for running Tor on a different computer</a>.
79)     </p>
80)     
81)     <p>To Torify other applications that support HTTP proxies, just
82)     point them at Polipo (that is, localhost port 8118). To use SOCKS
83)     directly (for instant messaging, Jabber, IRC, etc), you can point
84)     your application directly at Tor (localhost port 9050), but see <a

85)     href="<wikifaq>#SOCKSAndDNS">this

86)     FAQ entry</a> for why this may be dangerous. For applications
87)     that support neither SOCKS nor HTTP, take a look at <a

88)     href="https://code.google.com/p/torsocks/">torsocks</a> or <a

89)     href="<wiki>doc/TorifyHOWTO#socat">socat</a>.

90)     </p>
91)     
92)     <p>For information on how to Torify other applications, check out the

93)     <a href="<wiki>doc/TorifyHOWTO">Torify

94)     HOWTO</a>.
95)     </p>
96)     

97)     <hr>

98)     <a id="verify"></a>

99)     <h2><a class="anchor" href="#verify">Step Three: Make sure it's working</a></h2>

100)     <br>

101)     
102)     <p>
103)     Next, you should try using your browser with Tor and make
104)     sure that your IP address is being anonymized. Click on
105)     <a href="https://check.torproject.org/">the
106)     Tor detector</a>
107)     and see whether it thinks you're using Tor or not.
108)     #<a href="http://ipchicken.com/">this site</a>
109)     #to see what IP address it thinks you're using.
110)     (If that site is down, see <a

111)     href="<wikifaq>#IsMyConnectionPrivate">this

112)     FAQ entry</a> for more suggestions on how to test your Tor.)
113)     </p>
114)     
115)     <p>If you have a personal firewall that limits your computer's
116)     ability to connect to itself (this includes something like SELinux on
117)     Fedora Core 4), be sure to allow connections from
118)     your local applications to Polipo (local port 8118) and Tor (local port
119)     9050). If
120)     your firewall blocks outgoing connections, punch a hole so
121)     it can connect to at least TCP ports 80 and 443, and then see <a

122)     href="<wikifaq>#FirewalledClient">this

123)     FAQ entry</a>.  If your SELinux config is not allowing tor or privoxy to
124)     run correctly, create a file named booleans.local in the directory
125)     /etc/selinux/targeted.  Edit this file in your favorite text editor and
126)     insert "allow_ypbind=1".  Restart your machine for this change to take
127)     effect.
128)     </p>
129)     
130)     <p>If it's still not working, look at <a

131)     href="<page docs/faq>#DoesntWork">this

132)     FAQ entry</a> for hints.</p>
133)     

134)     <hr>

135)     <a id="server"></a>
136)     <a id="relay"></a>

137)     <h2><a class="anchor" href="#relay">Step Four: Configure it as a relay</a></h2>

138)     <br>

139)     
140)     <p>The Tor network relies on volunteers to donate bandwidth. The more
141)     people who run relays, the faster the Tor network will be. If you have
142)     at least 20 kilobytes/s each way, please help out Tor by configuring your
143)     Tor to be a relay too. We have many features that make Tor relays easy
144)     and convenient, including rate limiting for bandwidth, exit policies so
145)     you can limit your exposure to abuse complaints, and support for dynamic
146)     IP addresses.</p>
147)     
148)     <p>Having relays in many different places on the Internet is what
149)     makes Tor users secure. <a

150)     href="<wikifaq>#RelayAnonymity">You

151)     may also get stronger anonymity yourself</a>,
152)     since remote sites can't know whether connections originated at your
153)     computer or were relayed from others.</p>
154)     
155)     <p>Read more at our <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
156)     guide.</p>
157)     

158)     <hr>