tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 2-medium
4) 
5) #include "head.wmi" TITLE="Tor: Documentation" 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</a>
10)   </div>
11)   <div id="maincol"> 
12)     <a id="RunningTor"></a>
13)     <h1><a class="anchor" href="#RunningTor">Running Tor</a></h1>
14)     <ul>
15)     <li><a href="<page docs/tor-doc-windows>">Installing Tor
16)     on Win32</a></li>
17)     <li><a href="<page docs/tor-doc-osx>">Installing Tor on
18)     Mac OS X</a></li>
19)     <li><a href="<page docs/tor-doc-unix>">Installing Tor on
20)     Linux/BSD/Unix</a></li>

21)     <li><a href="<page torbutton/index>">Installing

22)     Torbutton for Tor</a></li>
23)     <li><a href="<page docs/tor-doc-relay>">Configuring a
24)     Tor relay</a></li>
25)     <li><a href="<page docs/tor-hidden-service>">Configuring
26)     a Tor hidden service</a></li>
27)     </ul>
28)     
29)     <a id="Support"></a>
30)     <a id="UpToSpeed"></a>
31)     <h1><a class="anchor" href="#UpToSpeed">Getting up to speed on Tor's past,
32)     present, and future</a></h1>
33)     
34)     <ol>
35)     <li>
36)     First, read the <a href="<page about/overview>">overview page</a> to get a
37)     basic idea of how Tor works, what it's for, and who uses it.
38)     </li>
39)     
40)     <li>
41)     <a href="<page download/download>">Install the Tor bundle</a> and try it out.
42)     Make sure you've got Firefox installed first, and be sure to read the
43)     <a href="<page download/download>#Warning">list of warnings</a> about ways you
44)     can screw up your anonymity.
45)     </li>
46)     
47)     <li>
48)     Our <a

49)     href="<page docs/faq>">FAQ</a>

50)     covers all sorts of topics, including questions about setting up a client
51)     or relay, concerns about anonymity attacks, why we didn't build Tor in
52)     other ways, etc.
53)     There's a separate <a href="<page docs/faq-abuse>">Abuse FAQ</a> to answer
54)     common questions from or for relay operators.
55)     The <a href="<page eff/tor-legal-faq>">Tor Legal FAQ</a> is written by
56)     EFF lawyers, and aims to give you an overview of some of the legal issues

57)     that arise from The Tor Project in the US.

58)     </li>
59)     

60)     <li>The <a href="<page docs/tor-manual-dev>">manual</a>

61)     lists all the possible entries you can put in your <a

62)     href="<page docs/faq>#torrc">torrc

63)     file</a>. We also provide a <a href="<page docs/tor-manual-dev>">manual for
64)     the development version of Tor</a>.</li>
65)     
66)     <li>If you have questions, we have an IRC channel (for users, relay
67)     operators, and developers)
68)     at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If
69)     you have a bug, especially a crash bug, read <a

70)     href="<wikifaq>#MyTorkeepscrashing.">how

71)     to report a Tor bug</a> first and then tell us as much information
72)     about it as you can in
73)     <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
74)     (If your bug is

75)     with your browser or some other application, please don't put

76)     it in our bugtracker.) The

77)     <a href="#MailingLists">tor-talk mailing list</a> can also be useful.

78)     </li>
79)     
80)     <li>

81)     <a href="<blog>">Tor has a blog</a>.

82)     We try to keep it updated every week or two with the latest news.
83)     </li>
84)     
85)     <li>
86)     Download and watch Roger's overview talk from What The Hack (<a
87)     href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">video</a>,
88)     <a href="http://freehaven.net/~arma/wth1.pdf">slides</a>, <a
89)     href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">abstract</a>).
90)     This talk was given in July 2005, back when we were funded by EFF and back
91)     when the network was quite small, but it still provides good background
92)     on how Tor works and what it's for.
93)     </li>
94)     
95)     <li>
96)     Look through our <a href="#DesignDoc">Design
97)     Documents</a>. Notice that we have RFC-style specs to tell you exactly
98)     how Tor is built.
99)     </li>
100)     
101)     <li>
102)     There's a skeletal <a
103)     href="https://svn.torproject.org/svn/projects/roadmaps/2008-12-19-roadmap-full.pdf">list
104)     of items we'd like to tackle in the future</a>. Alas, many of those
105)     items need to be fleshed out more before they'll make sense to people
106)     who aren't Tor developers, but you can still get a general sense of
107)     what issues need to be resolved next.
108)     </li>
109)     
110)     <li>
111)     Download and watch Nick's "Technical changes since 2004" talk from
112)     Defcon in July 2007 (<a
113)     href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">video</a>, <a
114)     href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">slides</a>),
115)     Roger's "blocking-resistance
116)     and circumvention" talk from 23C3 in December 2006 (<a
117)     href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
118)     <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
119)     <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
120)     <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">design paper</a>),
121)     and Roger's "Current events in 2007" talk from 24C3 in December
122)     2007 (<a
123)     href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
124)     <a href="http://freehaven.net/~arma/slides-24c3.pdf">slides</a>,
125)     <a href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">abstract</a>).
126)     </li>
127)     
128)     <li>
129)     See Mike's "Securing the Tor network" talk from Defcon in July 2007
130)     (<a href="http://freehaven.net/~arma/Defcon15-Mike_Perry-Securing_the_Tor_Network.mp4">video</a>,
131)      <a href="http://freehaven.net/~arma/SecuringTheTorNetwork.pdf">slides</a>).
132)     It describes common ways to attack networks like Tor and how we try
133)     to defend against them, and it introduces the <a
134)     href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>
135)     script collection.
136)     </li>
137)     
138)     <li>
139)     Learn about the <a

140)     href="<specblob>proposals/001-process.txt">Tor

141)     proposal process for changing our design</a>, and look over the <a

142)     href="<spectree>proposals">existing proposals</a>.

143)     </li>
144)     
145)     <li>
146)     Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
147)     timeline for external promises &mdash; things <a href="<page about/sponsors>">our
148)     sponsors</a> have paid to see done. It also lists many other tasks
149)     and topics we'd like to tackle next.
150)     </li>
151)     
152)     <li>
153)     Once you're up to speed, things will continue to change surprisingly fast.

154)     The <a href="#MailingLists">tor-dev mailing list</a> is where the complex

155)     discussion happens, and the #tor IRC channel
156)     is where the less complex discussion happens.
157)     </li>
158)     
159)     </ol>
160)     
161)     <a id="MailingLists"></a>
162)     <h1><a class="anchor" href="#MailingLists">Mailing List Information</a></h1>
163)     <ul>

164)     <li>The <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce/">tor-announce

165)     mailing list</a> is a low volume list for announcements of new releases
166)     and critical security updates. Everybody should be on this list.
167)     There is also an
168)     <a href="http://rss.gmane.org/gmane.network.onion-routing.announce">RSS

169)     feed</a> of tor-announce at <a href="http://gmane.org">gmane.org</a>.</li>
170)     <li>The <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk/">tor-talk list</a>

171)     is where a lot of discussion happens, and is where we send notifications
172)     of prerelease versions and release candidates.</li>

173)     <li>The <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays/">tor-relays list</a>

174)     is where discussions about running, configuring, and handling your tor
175)     relay happen.  If you currently run a relay, or are thinking about doing
176)     so, this is the list for you.</li>

177)     <li>The <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">tor-dev list</a>

178)     is for posting by developers only, and is very low traffic.</li>
179)     <li>A list for <a href="http://archives.seul.org/tor/mirrors/">mirror
180)     operators</a> for new website mirrors, and supporting <a href="<page
181)     getinvolved/mirrors>">current website mirrors</a>.</li>

182)     <li>A list for <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits/">svn and git

183)     commits</a> may be interesting for developers.</li>

184)     <li>An automated list for <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs/">bug

185)     reports from trac</a> may be interesting for users and developers.</li>
186)     </ul>
187)     
188)     <a id="DesignDoc"></a>
189)     <h1><a class="anchor" href="#DesignDoc">Design Documents</a></h1>
190)     <ul>
191)     <li>The <b>design document</b> (published at Usenix Security 2004)
192)     gives our justifications and security analysis for the Tor design:
193)     <a href="https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf">PDF</a> and
194)     <a href="https://svn.torproject.org/svn/projects/design-paper/tor-design.html">HTML</a>
195)     versions available.</li>
196)     <li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
197)     (still in draft form) details more recent experiences and directions:
198)     <a href="https://svn.torproject.org/svn/projects/design-paper/challenges.pdf">PDF
199)     draft</a>.</li>
200)     <li>Our paper at WEIS 2006 &mdash; <b>Anonymity Loves Company:
201)     Usability and the Network Effect</b> &mdash; explains why usability in
202)     anonymity systems matters for their security: <a
203)     href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
204)     <li>Our preliminary design to make it harder for large firewalls to
205)     prevent access to the Tor network is described in
206)     <b>design of a blocking-resistant anonymity system</b>:
207)     <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.pdf">PDF draft</a> and
208)     <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">HTML draft</a>.
209)     Want to <a href="<page getinvolved/volunteer>#Coding">help us build it</a>?</li>
210)     <li>The <b>specifications</b> aim to give
211)     developers enough information to build a compatible version of Tor:
212)     <ul>

213)     <li><a href="<specblob>tor-spec.txt">Main Tor specification</a></li>
214)     <li><a href="<specblob>dir-spec.txt">Tor

215)     version 3 directory server specification</a> (and older <a

216)     href="<specblob>dir-spec-v1.txt">version 1</a> and <a
217)     href="<specblob>dir-spec-v2.txt">version 2</a> directory

218)     specifications)</li>

219)     <li><a href="<specblob>control-spec.txt">Tor control protocol

220)     specification</a></li>

221)     <li><a href="<specblob>rend-spec.txt">Tor rendezvous

222)     specification</a></li>

223)     <li><a href="<specblob>path-spec.txt">Tor path selection

224)     specification</a></li>

225)     <li><a href="<specblob>address-spec.txt">Special hostnames in

226)     Tor</a></li>

227)     <li><a href="<specblob>socks-extensions.txt">Tor's SOCKS support

228)     and extensions</a></li>

229)     <li><a href="<specblob>version-spec.txt">How Tor version numbers

230)     work</a></li>

231)     <li><a href="<spectree>proposals">In-progress drafts of

232)     new specifications and proposed changes</a></li>
233)     </ul></li>
234)     
235)     </ul>
236)     
237)     <a id="NeatLinks"></a>
238)     <h1><a class="anchor" href="#NeatLinks">Neat Links</a></h1>
239)     <ul>

240)     <li>The <a href="<wiki>">Tor

241)     wiki</a> provides a plethora of helpful contributions from Tor
242)     users. Check it out!</li>
243)     <li><a

244)     href="<wiki>TheOnionRouter/SupportPrograms">A

245)     list of supporting programs you might want to use in association with
246)     Tor</a>.</li>
247)     <li><a href="https://check.torproject.org/">The
248)     Tor detector</a> or <a href="http://torcheck.xenobite.eu/">the other
249)     Tor detector</a> try to guess if you're using Tor or not.</li>
250)     <li>Check out one of the Tor status pages, such as <a
251)     href="http://torstatus.blutmagie.de/">blutmagie's</a>, or <a
252)     href="http://trunk.torstatus.kgprog.com/index.php">kgprog's</a>, or
253)     Xenobite's <a href="https://torstat.xenobite.eu/">Tor node status</a> page.
254)     Remember that these lists may not be as accurate as what your Tor
255)     client uses, because your client fetches its own directory information and
256)     examines it locally.</li>
257)     <li>Read <a
258)     href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">these
259)     papers</a> (especially the ones in boxes) to get up to speed on the field
260)     of anonymous communication systems.</li>
261)     </ul>
262)     
263)     <a id="Developers"></a>
264)     <h1><a class="anchor" href="#Developers">For Developers</a></h1>
265)       Browse the Tor <b>source repository</b>:
266)       <ul>
267)         <li><a href="<gitrepo>">Browse the repository's source tree directly</a></li>
268)         <li>Git and SVN access:
269)           <ul>
270)             <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>

271)             <li>The development branch is <kbd>master</kbd>.  The active maintenance branches are <kbd>maint-0.2.1</kbd> and <kbd>maint-0.2.2</kbd>.</li>