tor-doc-unix.html 8.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  2. "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
  4. <head>
  5. <title>Tor Linux/BSD/Unix Install Instructions</title>
  6. <meta name="Author" content="Roger Dingledine" />
  7. <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
  8. <link rel="stylesheet" type="text/css" href="stylesheet.css" />
  9. <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" />
  10. </head>
  11. <body>
  12. <!-- TITLE BAR & NAVIGATION -->
  13. <table class="banner" border="0" cellpadding="0" cellspacing="0">
  14. <tr>
  15. <td class="banner-left"></td>
  16. <td class="banner-middle">
  17. <a href="/index.html">Home</a>
  18. | <a href="/howitworks.html">How It Works</a>
  19. | <a href="/download.html">Download</a>
  20. | <a href="/documentation.html">Docs</a>
  21. | <a href="/users.html">Users</a>
  22. | <a href="/faq.html">FAQs</a>
  23. | <a href="/volunteer.html">Volunteer</a>
  24. | <a href="/developers.html">Developers</a>
  25. | <a href="/research.html">Research</a>
  26. | <a href="/people.html">People</a>
  27. </td>
  28. <td class="banner-right"></td>
  29. </tr>
  30. </table>
  31. <!-- END TITLE BAR & NAVIGATION -->
  32. <div class="center">
  33. <div class="main-column">
  34. <h1>Running the <a href="http://tor.eff.org/">Tor</a> client on Linux/BSD/Unix</h1>
  35. <br />
  36. <p>
  37. <b>Note that these are the installation instructions for running a Tor
  38. client. If you want to relay traffic for others to help the network grow
  39. (please do), read the <a
  40. href="tor-doc-server.html">Configuring a server</a> guide.</b>
  41. </p>
  42. <hr />
  43. <a id="installing"></a>
  44. <h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
  45. <br />
  46. <p>
  47. The latest release of Tor can be found on the <a
  48. href="/download.html">download</a> page. We have packages for Debian,
  49. Red Hat, Gentoo, *BSD, etc there too.
  50. </p>
  51. <p>If you're building from source, first install <a
  52. href="http://www.monkey.org/~provos/libevent/">libevent</a>, and
  53. make sure you have openssl and zlib (including the -devel packages if
  54. applicable). Then Run <tt>tar xzf tor-0.1.0.15.tar.gz;
  55. cd tor-0.1.0.15</tt>. Then <tt>./configure &amp;&amp; make</tt>. Now you
  56. can run tor as <tt>src/or/tor</tt>, or you can run <tt>make install</tt>
  57. (as root if necessary) to install it into /usr/local/, and then you can
  58. start it just by running <tt>tor</tt>.
  59. </p>
  60. <p>Tor comes configured as a client by default. It uses a built-in
  61. default configuration file, and most people won't need to change any of
  62. the settings. Tor is now installed.
  63. </p>
  64. <hr />
  65. <a id="privoxy"></a>
  66. <h2><a class="anchor" href="#privoxy">Step Two: Install Privoxy for Web Browsing</a></h2>
  67. <br />
  68. <p>After installing Tor, you need to configure your applications to use it.
  69. </p>
  70. <p>
  71. The first step is to set up web browsing. Start by installing <a
  72. href="http://www.privoxy.org/">Privoxy</a>: click on 'recent releases'
  73. and pick your favorite package or install from source. Privoxy is a
  74. filtering web proxy that integrates well with Tor.
  75. </p>
  76. <p>You need to configure Privoxy to use Tor.
  77. Open Privoxy's "config" file (look in /etc/privoxy/ or /usr/local/etc/)
  78. and add the line <br>
  79. <tt>forward-socks4a / localhost:9050 .</tt><br>
  80. to the top of the config file. Don't forget to add the dot at the end.
  81. </p>
  82. <p>Privoxy keeps a log file of everything passed through it. In
  83. order to stop this you will need to comment out two lines by inserting a
  84. # before the line. The two lines are:<br>
  85. <tt>logfile logfile</tt><br>
  86. and the line <br>
  87. <tt>jarfile jarfile</tt><br>
  88. </p>
  89. <p>You'll need to restart Privoxy for the changes to take effect.</p>
  90. <hr />
  91. <a id="using"></a>
  92. <h2><a class="anchor" href="#using">Step Three: Configure your applications to use Tor</a></h2>
  93. <br />
  94. <p>After installing Tor and Privoxy, you need to configure your
  95. applications to use them. The first step is to set up web browsing.</p>
  96. <p>If you're using Firefox (we recommend it), check out our <a
  97. href="tor-switchproxy.html">Tor SwitchProxy howto</a> to set up
  98. a plugin that makes it easy to switch between using Tor and using a
  99. direct connection.</p>
  100. <p>Otherwise, you need to manually configure your browser to HTTP proxy
  101. at localhost port 8118.
  102. (That's where Privoxy listens.)
  103. In Mozilla, this is in Edit|Preferences|Advanced|Proxies.
  104. In Opera 7.5x it's Tools|Preferences|Network|Proxy servers.
  105. You should click the "use the same proxy server for all protocols"
  106. button; but see <a
  107. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">this
  108. note</a> about Tor and ftp proxies.
  109. <p>Using privoxy is <strong>necessary</strong> because <a
  110. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">browsers
  111. leak your DNS requests when they use a SOCKS proxy directly</a>, which
  112. is bad for your anonymity. Privoxy also removes certain dangerous
  113. headers from your web requests, and blocks obnoxious ad sites like
  114. Doubleclick.</p>
  115. <p>To Torify other applications that support HTTP proxies, just
  116. point them at Privoxy (that is, localhost port 8118). To use SOCKS
  117. directly (for instant messaging, Jabber, IRC, etc), you can point
  118. your application directly at Tor (localhost port 9050), but see <a
  119. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
  120. FAQ entry</a> for why this may be dangerous. For applications
  121. that support neither SOCKS nor HTTP, take a look at <a
  122. href="http://tsocks.sourceforge.net/">tsocks</a> or <a
  123. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
  124. </p>
  125. <p>For information on how to Torify other applications, check out the
  126. <a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify
  127. HOWTO</a>.
  128. </p>
  129. <hr />
  130. <a id="verify"></a>
  131. <h2><a class="anchor" href="#verify">Step Four: Make sure it's working</a></h2>
  132. <br />
  133. <p>
  134. Next, you should try using your browser with Tor and make
  135. sure that your IP address is being anonymized. Click on the <a
  136. href="http://serifos.eecs.harvard.edu/cgi-bin/ipaddr.pl?tor=1">Tor
  137. detector</a> and see whether it thinks you're using Tor or not.
  138. (If that site is down, see <a
  139. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
  140. FAQ entry</a> for more suggestions on how to test your Tor.)
  141. </p>
  142. <p>If you have a personal firewall that limits your computer's
  143. ability to connect to itself (this includes something like SELinux on
  144. Fedora Core 4), be sure to allow connections from
  145. your local applications to Privoxy (local port 8118) and Tor (local port
  146. 9050). If
  147. your firewall blocks outgoing connections, punch a hole so
  148. it can connect to at least TCP ports 80 and 443, and then see <a
  149. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
  150. FAQ entry</a>. If your SELinux config is not allowing tor or privoxy to
  151. run correctly, create a file named booleans.local in the directory
  152. /etc/selinux/targeted. Edit this file in your favorite text editor and
  153. insert "allow_ypbind=1". Restart your machine for this change to take
  154. effect.
  155. </p>
  156. <p>If it's still not working, look at <a
  157. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
  158. FAQ entry</a> for hints.</p>
  159. <hr />
  160. <a id="server"></a>
  161. <h2><a class="anchor" href="#server">Step Five: Configure it as a server</a></h2>
  162. <br />
  163. <p>The Tor network relies on volunteers to donate bandwidth. The more
  164. people who run servers, the faster the Tor network will be. If you have
  165. at least 20 kilobytes/s each way, please help out Tor by configuring your
  166. Tor to be a server too. We have many features that make Tor servers easy
  167. and convenient, including rate limiting for bandwidth, exit policies so
  168. you can limit your exposure to abuse complaints, and support for dynamic
  169. IP addresses.</p>
  170. <p>Having servers in many different places on the Internet is what
  171. makes Tor users secure. <a
  172. href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You
  173. may also get stronger anonymity yourself</a>,
  174. since remote sites can't know whether connections originated at your
  175. computer or were relayed from others.</p>
  176. <p>Read more at our <a href="tor-doc-server.html">Configuring a server</a>
  177. guide.</p>
  178. <hr />
  179. <p>If you have suggestions for improving this document, please post
  180. them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
  181. website category. Thanks!</p>
  182. </div><!-- #main -->
  183. </div>
  184. <div class="bottom" id="bottom">
  185. <i><a href="mailto:tor-webmaster@freehaven.net"
  186. class="smalllink">Webmaster</a></i> - $Id$
  187. </div>
  188. </body>
  189. </html>