tor-webwml.git

1) ## translation metadata
2) # Based-On-Revision: 15123
3) # Last-Translator: djhasis(at)gmail.com
4) 
5) #include "head.wmi" TITLE="Tor: Ohjeet" CHARSET="UTF-8"
6) 
7) <div class="main-column">
8) 
9) <a id="RunningTor"></a>
10) <h2><a class="anchor" href="#RunningTor">Tor-ohjelman pyörittäminen</a></h2>
11) <ul>
12) <li><a href="<page docs/tor-doc-windows>">Tor-ohjelman asentaminen 32-bittisessä Windowssisa</a></li>
13) <li><a href="<page docs/tor-doc-osx>">Tor-ohjelman asentaminen Mac OS X:ssä</a></li>
14) <li><a href="<page docs/tor-doc-unix>">Tor-ohjelman asentaminen Linux/BSD/Unix:ssa</a></li>
15) <li><a href="<page docs/tor-doc-relay>">Tor-reitittimen määrittäminen</a></li>
16) <li><a href="<page docs/tor-hidden-service>">Tor-piilopalvelun määrittäminen</a></li>
17) </ul>
18) 
19) <a id="Support"></a>
20) <h2><a class="anchor" href="#Support">Avun saaminen</a></h2>
21) <ul>
22) <li>The <a href="https://wiki.torproject.org/wiki/TheOnionRouter/TorFAQ">Tor
23) Technical FAQ Wiki</a> should be the first place you look. The
24) <a href="https://wiki.torproject.org/wiki/TheOnionRouter/TorifyHOWTO">Guide
25) to Torifying various applications</a> is also popular. (While we
26) monitor the Wiki page to help ensure accuracy, the Tor developers are
27) not responsible for the content.)</li>
28) <li>The <a href="<page faq-abuse>">Abuse FAQ</a> is a collection of
29) common questions and issues discussed when running a Tor relay.</li>
30) <li>The <a href="<page eff/tor-legal-faq>">Tor Legal FAQ</a> is written by
31) EFF lawyers. It aims to give you an overview of some of the legal issues
32) that arise from the Tor project in the US.</li>
33) <li>The <a href="<page tor-manual>">manual</a>
34) lists all the possible entries you can put in your <a
35) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc
36) file</a>. We also provide a <a href="<page tor-manual-dev>">manual for
37) the development version of Tor</a>.</li>
38) <li>The <a href="https://wiki.torproject.org/noreply/TheOnionRouter">Tor
39) wiki</a> provides a plethora of helpful contributions from Tor
40) users. Check it out!</li>
41) <li>The Tor IRC channel (for users, relay operators, and developers)
42) is <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>.</li>
43) <li>We have a <a
44) href="https://bugs.torproject.org/tor">bugtracker</a>.
45) If you have a bug, especially a crash bug, read <a
46) href="https://wiki.torproject.org/wiki/TheOnionRouter/TorFAQ#RelayCrashing">how
47) to report a Tor bug</a> first and then tell us as much information
48) about it as you can in the bugtracker. (If your bug is
49) with Privoxy, your browser, or some other application, please don't put
50) it in our bugtracker.)</li>

51) <li>Try the or-talk mailing list <a href="#MailingLists">below</a>.</li>

52) <li>As a last resort, look through <a href="<page contact>">the Tor
53) contact page</a>.</li>
54) </ul>
55) 
56) <a id="MailingLists"></a>
57) <h2><a class="anchor" href="#MailingLists">Postituslistatietoja</a></h2>
58) <ul>
59) <li>The <a href="http://archives.seul.org/or/announce/">or-announce
60) mailing list</a> is a low volume list for announcements of new releases
61) and critical security updates. Everybody should be on this list.
62) There is also an
63) <a href="http://rss.gmane.org/gmane.network.onion-routing.announce">RSS
64) feed</a> of or-announce at <a href="http://gmane.org">gmane.org</a>.</li>
65) <li>The <a href="http://archives.seul.org/or/talk/">or-talk list</a>
66) is where a lot of discussion happens, and is where we send notifications
67) of prerelease versions and release candidates.</li>
68) <li>The <a href="http://archives.seul.org/or/dev/">or-dev list</a>
69) is for posting by developers only, and is very low traffic.</li>
70) <li>A list for <a href="http://archives.seul.org/or/cvs/">svn commits</a>
71) may be interesting for developers.</li>
72) </ul>
73) 
74) <a id="UpToSpeed"></a>
75) <h2><a class="anchor" href="#UpToSpeed">Getting up to speed on Tor's past,
76) present, and future</a></h2>
77) 
78) <ol>
79) <li>
80) First, read the <a href="<page overview>">overview page</a> to get a
81) basic idea of how Tor works, what it's for, and who uses it.
82) </li>
83) 
84) <li>
85) <a href="<page download>">Install the Tor bundle</a> and try it out.
86) Make sure you've got Firefox installed first, and be sure to read the
87) <a href="<page download>#Warning">list of warnings</a> about ways you
88) can screw up your anonymity.
89) </li>
90) 
91) <li>
92) Download and watch Roger's overview talk from What The Hack (<a
93) href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">video</a>,
94) <a href="http://freehaven.net/~arma/wth1.pdf">slides</a>, <a
95) href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">abstract</a>).
96) This talk was given in July 2005, back when we were funded by EFF and back
97) when the network was quite small, but it still provides good background
98) on how Tor works and what it's for.
99) </li>
100) 
101) <li>
102) Our <a
103) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ">FAQ</a>
104) covers all sorts of topics, including questions about setting up a client
105) or relay, concerns about anonymity attacks, why we didn't build Tor in
106) other ways, and discussion of Tor users and abuse.
107) </li>
108) 
109) <li>
110) <a href="https://blog.torproject.org/">Tor has a blog now</a>.
111) We try to keep it updated every week or two with the latest news.
112) </li>
113) 
114) <li>
115) Look through our <a href="#DesignDoc">Design
116) Documents</a>. Notice that we have RFC-style specs to tell you exactly
117) how Tor is built.
118) </li>
119) 
120) <li>
121) There's a skeletal <a

122) href="<svnprojects>design-paper/roadmap-future.pdf">list of items

123) we'd like to tackle in the future</a>. Alas, many of those items need
124) to be fleshed out more before they'll make sense to people who aren't
125) Tor developers, but you can still get a general sense of what issues
126) need to be resolved next.
127) </li>
128) 
129) <li>
130) Download and watch Nick's "Technical changes since 2004" talk from
131) Defcon in July 2007 (<a
132) href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">video</a>, <a
133) href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">slides</a>),
134) Roger's "blocking-resistance
135) and circumvention" talk from 23C3 in December 2006 (<a
136) href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
137) <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
138) <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,

139) <a href="<svnprojects>design-paper/blocking.html">design paper</a>),

140) and Roger's "Current events in 2007" talk from 24C3 in December
141) 2007 (<a
142) href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
143) <a href="http://freehaven.net/~arma/slides-24c3.pdf">slides</a>,
144) <a href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">abstract</a>).
145) We also have the What The Hack tutorial on hidden services (<a
146) href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">video</a>,
147) <a href="http://freehaven.net/~arma/wth3.pdf">slides</a>).
148) </li>
149) 
150) <li>
151) Learn about the <a

152) href="<gitblob>doc/spec/proposals/001-process.txt">Tor

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

154) href="<gittree>doc/spec/proposals">existing proposals</a>.

155) </li>
156) 
157) <li>

158) Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a

159) timeline for external promises &mdash; things <a href="<page sponsors>">our
160) sponsors</a> have paid to see done. It also lists many other tasks
161) and topics we'd like to tackle next.
162) </li>
163) 
164) <li>
165) Once you're up to speed, things will continue to change surprisingly fast.
166) The <a href="#MailingLists">or-dev mailing list</a> is where the complex
167) discussion happens, and the <a href="#Support">#tor IRC channel</a>
168) is where the less complex discussion happens.
169) </li>
170) 
171) </ol>
172) 
173) <a id="DesignDoc"></a>
174) <h2><a class="anchor" href="#DesignDoc">Suunnitteludokumentteja</a></h2>
175) <ul>
176) <li>The <b>design document</b> (published at Usenix Security 2004)
177) gives our justifications and security analysis for the Tor design:

178) <a href="<svnprojects>design-paper/tor-design.pdf">PDF</a> and
179) <a href="<svnprojects>design-paper/tor-design.html">HTML</a>

180) versions available.</li>
181) <li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
182) (still in draft form) details more recent experiences and directions:

183) <a href="<svnprojects>design-paper/challenges.pdf">PDF

184) draft</a>.</li>
185) <li>Our paper at WEIS 2006 &mdash; <b>Anonymity Loves Company:
186) Usability and the Network Effect</b> &mdash; explains why usability in
187) anonymity systems matters for their security: <a
188) href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
189) <li>Our preliminary design to make it harder for large firewalls to
190) prevent access to the Tor network is described in
191) <b>design of a blocking-resistant anonymity system</b>:

192) <a href="<svnprojects>design-paper/blocking.pdf">PDF draft</a> and
193) <a href="<svnprojects>design-paper/blocking.html">HTML draft</a>.

194) Want to <a href="<page volunteer>#Coding">help us build it</a>?</li>
195) <li>The <b>specifications</b> aim to give
196) developers enough information to build a compatible version of Tor:
197) <ul>

198) <li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor

199) specification</a></li>

200) <li><a href="<gitblob>doc/spec/dir-spec.txt">Tor

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

202) href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
203) href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory

204) specifications)</li>

205) <li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol

206) specification</a></li>

207) <li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous

208) specification</a></li>

209) <li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection

210) specification</a></li>

211) <li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in

212) Tor</a></li>

213) <li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support

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

215) <li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers

216) work</a></li>

217) <li><a href="<gittree>doc/spec/proposals">In-progress drafts of

218) new specifications and proposed changes</a></li>
219) </ul></li>
220) 
221) </ul>
222) 
223) <a id="NeatLinks"></a>
224) <h2><a class="anchor" href="#NeatLinks">Siistit linkit</a></h2>
225) <ul>
226) <li>The <a href="https://wiki.torproject.org/noreply/TheOnionRouter">Tor
227) wiki</a> provides a plethora of helpful contributions from Tor
228) users. Check it out!</li>
229) <li><a
230) href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">A
231) list of supporting programs you might want to use in association with
232) Tor</a>.</li>
233) <li><a href="http://check.torproject.org/">The
234) Tor detector</a> or <a href="http://torcheck.xenobite.eu/">the other
235) Tor detector</a> try to guess if you're using Tor or not.</li>
236) <li>Check out the
237) <a href="http://torstatus.kgprog.com/">Tor Status</a> page, the other
238) <a href="http://torstatus.blutmagie.de/">Tor Status</a> page, or
239) Xenobite's <a href="https://torstat.xenobite.eu/">Tor node status</a> page.
240) Remember that these lists may not be as accurate as what your Tor
241) client uses, because your client fetches all the authoritative directories
242) and combines them locally.</li>
243) <li>Read <a
244) href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">these
245) papers</a> (especially the ones in boxes) to get up to speed on the field
246) of anonymous communication systems.</li>
247) </ul>
248) 
249) <a id="Developers"></a>
250) <h2><a class="anchor" href="#Developers">Kehittäjille</a></h2>
251)   Browse the Tor <b>source repository</b>: (which may not necessarily work or even compile)
252)   <ul>

253)     <li><a href="<gittree>">Regularly updated SVN sandbox</a></li>

254)     <li><a href="https://svn.torproject.org/svn/tor/trunk">Browse the repository's source tree directly</a></li>
255)     <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/tor/?root=Tor">ViewCVS</a></li>
256)     <li>anonymous <a href="http://subversion.tigris.org/">subversion</a> access:
257)       <ul>
258)         <li>Make a new empty directory and cd into it.</li>
259)         <li><kbd>svn checkout https://tor-svn.freehaven.net/svn/tor/trunk tor</kbd></li>
260)         <li><kbd>svn checkout https://tor-svn.freehaven.net/svn/website/trunk website</kbd></li>
261)         <li>To check out the maintenance branch, use<br /><kbd>svn checkout https://tor-svn.freehaven.net/svn/tor/branches/tor-0_1_2-patches</kbd></li>

262)       </ul><br />