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)     <h2>Note that these are the installation instructions for running a

17)     Tor client. The easiest way to do this is to simply download the <a

18)     href="<page projects/torbrowser>">Tor Browser Bundle</a> and you are

19)     done.
20)     </h2>

21)     

22)     <hr>

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

25)     <br>

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

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

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

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

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

53)     <hr>

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

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

56)     <br>

57)     

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

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

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

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

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

69)    >

70)     

71)     <br>

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

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

76)     FAQ
77)     entry for running Tor on a different computer</a>.
78)     </p>
79)     

80)     <p>To Torify other applications that support SOCKS proxies, just
81)     point them at Tor's SOCKS port (127.0.0.1 port 9050). See <a
82)     href="<wikifaq>#SOCKSAndDNS">this FAQ entry</a> for why this may be
83)     dangerous. For applications that support neither SOCKS nor HTTP, take
84)     a look at <a href="https://code.google.com/p/torsocks/">torsocks</a>
85)     or <a href="<wiki>doc/TorifyHOWTO#socat">socat</a>.

86)     </p>
87)     
88)     <p>For information on how to Torify other applications, check out the

89)     <a href="<wiki>doc/TorifyHOWTO">Torify HOWTO</a>.

90)     </p>
91)     

92)     <hr>

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

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

95)     <br>

96)     
97)     <p>
98)     Next, you should try using your browser with Tor and make

99)     sure that your IP address is being anonymized. Click on <a
100)     href="https://check.torproject.org/">the Tor detector</a>

101)     and see whether it thinks you're using Tor or not.
102)     (If that site is down, see <a

103)     href="<wikifaq>#IsMyConnectionPrivate">this FAQ entry</a> for more
104)     suggestions on how to test your Tor.)

105)     </p>
106)     

107)     <p>If you have a personal firewall that limits your computer's ability
108)     to connect to itself (this includes something like SELinux on Fedora
109)     Core 4), be sure to allow connections from your local applications to
110)     Tor (local port 9050). If your firewall blocks outgoing connections,
111)     punch a hole so it can connect to at least TCP ports 80 and 443, and
112)     then see <a href="<wikifaq>#FirewalledClient">this FAQ entry</a>.
113)     If your SELinux config is not allowing tor or privoxy to run
114)     correctly, create a file named booleans.local in the directory
115)     /etc/selinux/targeted.  Edit this file in your favorite text editor
116)     and insert "allow_ypbind=1".  Restart your machine for this change
117)     to take effect.

118)     </p>
119)     
120)     <p>If it's still not working, look at <a

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

122)     FAQ entry</a> for hints.</p>
123)     

124)     <hr>

125)     <a id="server"></a>
126)     <a id="relay"></a>

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

128)     <br>

129)     
130)     <p>The Tor network relies on volunteers to donate bandwidth. The more
131)     people who run relays, the faster the Tor network will be. If you have

132)     at least 20 KiloBytes/s each way, please help out Tor by configuring your

133)     Tor to be a relay too. We have many features that make Tor relays easy
134)     and convenient, including rate limiting for bandwidth, exit policies so
135)     you can limit your exposure to abuse complaints, and support for dynamic
136)     IP addresses.</p>
137)     
138)     <p>Having relays in many different places on the Internet is what

139)     makes Tor users secure. <a href="<wikifaq>#RelayAnonymity">You may
140)     also get stronger anonymity yourself</a>, since remote sites can't
141)     know whether connections originated at your computer or were relayed
142)     from others.</p>
143) 

144)     <p>Read more at our <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
145)     guide.</p>
146)     

147)     <hr>