tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) 

4) #include "head.wmi" TITLE="Tor FAQ"
5) 
6) <div class="main-column">
7) 
8) <!-- PUT CONTENT AFTER THIS TAG -->
9) 

10) # Translators: you probably don't want to translate this file yet,
11) # since I'm hoping it will keep changing for a while. Thanks! -RD
12) 

13) <h2>Tor FAQ</h2>
14) <hr />

15) 

16) <p>General questions:</p>

17) <ul>

18) <li><a href="#WhatIsTor">What is Tor?</a></li>
19) <li><a href="#CompatibleApplications">What programs can I use with
20) Tor?</a></li>
21) <li><a href="#WhyCalledTor">Why is it called Tor?</a></li>
22) <li><a href="#Backdoor">Is there a backdoor in Tor?</a></li>
23) <li><a href="#DistributingTor">Can I distribute Tor on my magazine's
24) CD?</a></li>
25) <li><a href="#SupportMail">How can I get an answer to my
26) Tor support mail?</a></li>
27) <li><a href="#WhySlow">Why is Tor so slow?</a></li>
28) <li><a href="#Funding">What would The Tor Project do with more
29) funding?</a></li>

30) </ul>
31) 

32) <p>Compilation and Installation:</p>

33) <ul>
34) <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>

35) <li><a href="#PGPSigs">What are these "sig" files on the download
36) page?</a></li>

37) <li><a href="#CompileTorWindows">How do I compile Tor under Windows?</a></li>

38) <li><a href="#VirusFalsePositives">Why does my Tor executable appear to
39) have a virus or spyware?</a></li>

40) <li><a href="#LiveCD">Is there a LiveCD or other bundle that includes Tor?</li>
41) </ul>

42) 
43) <p>Running Tor:</p>
44) 
45) <p>Running a Tor client:</p>
46) 
47) <p>Running a Tor relay:</p>

48) <ul>
49) <li><a href="#WhyNotNamed">Why is my Tor relay not named?</li>
50) </ul>

51) 
52) <p>Running a Tor hidden service:</p>
53) 

54) <p>Anonymity and Security:</p>
55) <ul>

56) <li><a href="#KeyManagement">Tell me about all the keys Tor uses.</a></li>

57) </ul>
58) 

59) <p>Alternate designs that we don't do (yet):</p>
60) <ul>
61) <li><a href="#EverybodyARelay">You should make every Tor user be a
62) relay.</a></li>
63) </ul>
64) 

65) <p>Abuse</p>
66) <ul>
67) <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
68) <li><a href="#RespondISP">How do I respond to my ISP about my exit
69) relay?</a></li>
70) </ul>
71) 

72) <p>For other questions not yet on this version of the FAQ, see the <a
73) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ">wiki
74) FAQ</a> for now.</p>
75) 

76) <hr />
77) 
78) <a id="General"></a>
79) 

80) <a id="WhatIsTor"></a>
81) <h3><a class="anchor" href="#WhatIsTor">What is Tor?</a></h3>
82) 
83) <p>
84) The name "Tor" can refer to several different components.
85) </p>
86) 
87) <p>
88) The Tor software is a program you can run on your computer that helps keep
89) you safe on the Internet. Tor protects you by bouncing your communications
90) around a distributed network of relays run by volunteers all around
91) the world: it prevents somebody watching your Internet connection from
92) learning what sites you visit, and it prevents the sites you visit
93) from learning your physical location. This set of volunteer relays is
94) called the Tor network. You can read more about how Tor works on the <a
95) href="<page overview>">overview page</a>.
96) </p>
97) 
98) <p>
99) The Tor Project is a non-profit (charity) organization that maintains

100) and develops the Tor software.

101) </p>
102) 

103) <a id="CompatibleApplications"></a>

104) <h3><a class="anchor" href="#CompatibleApplications">What programs can
105) I use with Tor?</a></h3>

106) 
107) <p>
108) There are two pieces to "Torifying" a program: connection-level anonymity
109) and application-level anonymity. Connection-level anonymity focuses on

110) making sure the application's Internet connections get sent through Tor.
111) This step is normally done by configuring

112) the program to use your Tor client as a "socks" proxy, but there are
113) other ways to do it too. For application-level anonymity, you need to
114) make sure that the information the application sends out doesn't hurt
115) your privacy. (Even if the connections are being routed through Tor, you
116) still don't want to include sensitive information like your name.) This
117) second step needs to be done on a program-by-program basis, which is
118) why we don't yet recommend very many programs for safe use with Tor.

119) </p>
120) 
121) <p>

122) Most of our work so far has focused on the Firefox web browser. The
123) bundles on the <a href="<page download>">download page</a> automatically
124) install the <a href="<page torbutton/index>">Torbutton Firefox
125) extension</a> if you have Firefox installed. As of version 1.2.0,
126) Torbutton now takes care of a lot of the connection-level and
127) application-level worries.

128) </p>
129) 
130) <p>

131) There are plenty of other programs you can use with Tor,
132) but we haven't researched the application-level anonymity
133) issues on them well enough to be able to recommend a safe
134) configuration. Our wiki has a list of instructions for <a

135) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torifying

136) specific applications</a>. There's also a <a
137) href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">list
138) of applications that help you direct your traffic through Tor</a>.
139) Please add to these lists and help us keep them accurate!

140) </p>
141) 
142) <a id="WhyCalledTor"></a>
143) <h3><a class="anchor" href="#WhyCalledTor">Why is it called Tor?</a></h3>
144) 
145) <p>

146) Because Tor is the onion routing network. When we were starting the
147) new next-generation design and implementation of onion routing in
148) 2001-2002, we would tell people we were working on onion routing,
149) and they would say "Neat. Which one?" Even if onion routing has
150) become a standard household term, Tor was born out of the actual <a
151) href="http://www.onion-router.net/">onion routing project</a> run by
152) the Naval Research Lab.

153) </p>
154) 
155) <p>

156) (It's also got a fine translation from German and Turkish.)

157) </p>
158) 
159) <p>

160) Note: even though it originally came from an acronym, Tor is not spelled

161) "TOR". Only the first letter is capitalized. In fact, we can usually
162) spot people who haven't read any of our website (and have instead learned
163) everything they know about Tor from news articles) by the fact that they
164) spell it wrong.

165) </p>
166) 
167) <a id="Backdoor"></a>
168) <h3><a class="anchor" href="#Backdoor">Is there a backdoor in Tor?</a></h3>
169) 
170) <p>

171) There is absolutely no backdoor in Tor. Nobody has asked us to put one

172) in, and we know some smart lawyers who say that it's unlikely that anybody

173) will try to make us add one in our jurisdiction (U.S.). If they do

174) ask us, we will fight them, and (the lawyers say) probably win.
175) </p>
176) 
177) <p>
178) We think that putting a backdoor in Tor would be tremendously
179) irresponsible to our users, and a bad precedent for security software

180) in general. If we ever put a deliberate backdoor in our security
181) software, it would ruin our professional reputations. Nobody would

182) trust our software ever again — for excellent reason!
183) </p>
184) 
185) <p>
186) But that said, there are still plenty of subtle attacks

187) people might try. Somebody might impersonate us, or break into our
188) computers, or something like that. Tor is open source, and you should

189) always check the source (or at least the diffs since the last release)

190) for suspicious things. If we (or the distributors) don't give you

191) source, that's a sure sign something funny might be going on. You

192) should also check the <a
193) href="https://wiki.torproject.org/noreply/TheOnionRouter/VerifyingSignatures">PGP
194) signatures</a> on the releases, to make sure nobody messed with the
195) distribution sites.

196) </p>
197) 
198) <p>
199) Also, there might be accidental bugs in Tor that could affect your

200) anonymity. We periodically find and fix anonymity-related bugs, so make
201) sure you keep your Tor versions up-to-date.

202) </p>
203) 
204) <a id="DistributingTor"></a>
205) <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor on

206) my magazine's CD?</a></h3>

207) 
208) <p>
209) Yes.
210) </p>
211) 
212) <p>

213) The Tor software is <a href="https://www.fsf.org/">free software</a>. This

214) means we give you the rights to redistribute the Tor software, either
215) modified or unmodified, either for a fee or gratis. You don't have to
216) ask us for specific permission.
217) </p>
218) 
219) <p>
220) However, if you want to redistribute the Tor software you must follow our

221) <a href="<svnsandbox>license">LICENSE</a>.

222) Essentially this means that you need to include our LICENSE file along
223) with whatever part of the Tor software you're distributing.
224) </p>
225) 
226) <p>
227) Most people who ask us this question don't want to distribute just the
228) Tor software, though. They want to distribute the Tor bundles, which
229) typically include <a href="http://www.privoxy.org/">Privoxy</a>
230) and <a href="http://www.vidalia-project.net/">Vidalia</a>.
231) You will need to follow the licenses for those programs
232) as well. Both of them are distributed under the <a

233) href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General

234) Public License</a>. The simplest way to obey their licenses is to
235) include the source code for these programs everywhere you include
236) the bundles themselves. Look for "source" packages on the <a
237) href="http://www.vidalia-project.net/download.php">Vidalia
238) download page</a> and the <a
239) href="http://sourceforge.net/project/showfiles.php?group_id=11118">Privoxy
240) download page</a>.
241) </p>
242) 
243) <p>

244) Also, you should make sure not to confuse your readers about what Tor is,

245) who makes it, and what properties it provides (and doesn't provide). See
246) our <a href="<page trademark-faq>">trademark FAQ</a> for details.
247) </p>
248) 
249) <p>
250) Lastly, you should realize that we release new versions of the
251) Tor software frequently, and sometimes we make backward incompatible
252) changes. So if you distribute a particular version of the Tor software, it
253) may not be supported &mdash; or even work &mdash; six months later. This
254) is a fact of life for all security software under heavy development.
255) </p>
256) 
257) <a id="SupportMail"></a>
258) <h3><a class="anchor" href="#SupportMail">How can I get an answer to my
259) Tor support mail?</a></h3>
260) 
261) <p>
262) Many people send the Tor developers mail privately, or send mail to

263) our internal <a href="<page contact>">lists</a>, with questions about their

264) specific setup — they can't get their firewall working right,

265) they can't configure Privoxy correctly, or so on. Sometimes our
266) volunteers can answer these mails, but typically they need to spend
267) most of their time on development tasks that will benefit more people.
268) This is especially true if your question is already covered in the <a
269) href="<page documentation>">documentation</a> or on this FAQ. We don't
270) hate you; we're just busy.
271) </p>
272) 
273) <p>
274) So if we don't answer your mail, first check the <a href="<page
275) documentation>">documentation</a> page, along with this FAQ,
276) to make sure your question isn't already answered.  Then read <a
277) href="http://www.catb.org/~esr/faqs/smart-questions.html">"How to ask
278) questions the smart way"</a>. If this doesn't help you, note that we
279) have <a href="<page documentation>#Support">an IRC channel</a> where you
280) can ask your questions (but if they are still open-ended, ill-formed,
281) or not about Tor, you likely won't get much help there either). Lastly,
282) people on the <a href="<page documentation>#MailingLists">or-talk
283) mailing list</a> may be able to provide some hints for you, if
284) others have experienced your problems too. Be sure to look over <a
285) href="http://archives.seul.org/or/talk/">the archives</a> first.
286) </p>
287) 
288) <p>
289) Another strategy is to <a href="<page docs/tor-doc-relay>">run a Tor
290) relay for a while</a>, and/or <a href="<page donate>">donate money</a>
291) <a href="<page volunteer>">or time</a> to the effort. We're more likely
292) to pay attention to people who have demonstrated interest and commitment
293) to giving back to the Tor community.
294) </p>
295) 
296) <p>

297) If you find your answer, please stick around on the IRC channel or the

298) mailing list and answer questions from others.
299) </p>
300) 
301) <a id="WhySlow"></a>
302) <h3><a class="anchor" href="#WhySlow">Why is Tor so slow?</a></h3>
303) 
304) <p>
305) There are many reasons why the Tor network is currently slow.
306) </p>
307) 
308) <p>
309) Before we answer, though, you should realize that Tor is never going to
310) be blazing fast. Your traffic is bouncing through volunteers' computers
311) in various parts of the world, and some bottlenecks and network latency
312) will always be present. You shouldn't expect to see university-style
313) bandwidth through Tor.
314) </p>
315) 
316) <p>
317) But that doesn't mean that it can't be improved. The current Tor network
318) is quite small compared to the number of people trying to use it, and
319) many of these users don't understand or care that Tor can't currently
320) handle file-sharing traffic load.
321) </p>
322) 
323) <p>
324) What can you do to help?
325) </p>
326) 
327) <ul>
328) 
329) <li>
330) <a href="<page docs/tor-doc-relay>">Configure your Tor to relay traffic
331) for others</a>. Help make the Tor network large enough that we can handle
332) all the users who want privacy and security on the Internet.
333) </li>
334) 
335) <li>
336) <a href="<page gui/index>">Help us make Tor more usable</a>. We
337) especially need people to help make it easier to configure your Tor
338) as a relay. Also, we need help with clear simple documentation to
339) walk people through setting it up.
340) </li>
341) 
342) <li>
343) There are some bottlenecks in the current Tor network. Help us design
344) experiments to track down and demonstrate where the problems are, and
345) then we can focus better on fixing them.
346) </li>
347) 
348) <li>
349) There are some steps that individuals
350) can take to improve their Tor performance. <a
351) href="https://wiki.torproject.org/noreply/TheOnionRouter/FireFoxTorPerf">You
352) can configure your Firefox to handle Tor better</a>, <a
353) href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
354) Polipo with Tor</a>, or you can try <a href="<page download>">upgrading
355) to the latest version of Tor</a>.  If this works well, please help by
356) documenting what you did, and letting us know about it.
357) </li>
358) 
359) <li>
360) Tor needs some architectural changes too. One important change is to

361) start providing <a

362) href="#EverybodyARelay">better

363) service to people who relay traffic</a>. We're working on this, and
364) we'll finish faster if we get to spend more time on it.

365) </li>
366) 
367) <li>
368) Help do other things so we can do the hard stuff. Please take a moment
369) to figure out what your skills and interests are, and then <a href="<page
370) volunteer>">look at our volunteer page</a>.
371) </li>
372) 
373) <li>
374) Help find sponsors for Tor. Do you work at a company or government agency
375) that uses Tor or has a use for Internet privacy, e.g. to browse the
376) competition's websites discreetly, or to connect back to the home servers
377) when on the road without revealing affiliations? If your organization has
378) an interest in keeping the Tor network working, please contact them about
379) supporting Tor. Without sponsors, Tor is going to become even slower.
380) </li>
381) 
382) <li>
383) If you can't help out with any of the above, you can still help out
384) individually by <a href="<page donate>">donating a bit of money to the
385) cause</a>. It adds up!
386) </li>
387) 
388) </ul>
389) 
390) <a id="Funding"></a>

391) <h3><a class="anchor" href="#Funding">What would The Tor Project do with

392) more funding?</a></h3>
393) 
394) <p>
395) We have about 1500 relays right now, pushing over 150 MB/s average
396) traffic. We have several hundred thousand active users. But the Tor
397) network is not yet self-sustaining.
398) </p>
399) 
400) <p>
401) There are six main development/maintenance pushes that need attention:
402) </p>
403) 
404) <ul>
405) 
406) <li>
407) Scalability: We need to keep scaling and decentralizing the Tor
408) architecture so it can handle thousands of relays and millions of
409) users. The upcoming stable release is a major improvement, but there's
410) lots more to be done next in terms of keeping Tor fast and stable.
411) </li>
412) 
413) <li>
414) User support: With this many users, a lot of people are asking questions
415) all the time, offering to help out with things, and so on. We need good
416) clean docs, and we need to spend some effort coordinating volunteers.
417) </li>
418) 
419) <li>
420) Relay support: the Tor network is run by volunteers, but they still need
421) attention with prompt bug fixes, explanations when things go wrong,
422) reminders to upgrade, and so on. The network itself is a commons, and
423) somebody needs to spend some energy making sure the relay operators stay
424) happy. We also need to work on <a href="#RelayOS">stability</a> on some
425) platforms &mdash; e.g., Tor relays have problems on Win XP currently.
426) </li>
427) 
428) <li>
429) Usability: Beyond documentation, we also need to work on usability of the
430) software itself. This includes installers, clean GUIs, easy configuration
431) to interface with other applications, and generally automating all of
432) the difficult and confusing steps inside Tor. We've got a start on this
433) with the <a href="<page gui/index>">GUI Contest</a>, but much more work
434) remains &mdash; usability for privacy software has never been easy.
435) </li>
436) 
437) <li>
438) Incentives: We need to work on ways to encourage people to configure
439) their Tors as relays and exit nodes rather than just clients.
440) <a href="#EverybodyARelay">We need to make it easy to become a relay,
441) and we need to give people incentives to do it.</a>
442) </li>
443) 
444) <li>
445) Research: The anonymous communications field is full
446) of surprises and gotchas. In our copious free time, we
447) also help run top anonymity and privacy conferences like <a
448) href="http://petsymposium.org/">PETS</a>. We've identified a set of
449) critical <a href="<page volunteer>#Research">Tor research questions</a>
450) that will help us figure out how to make Tor secure against the variety of
451) attacks out there. Of course, there are more research questions waiting
452) behind these.
453) </li>
454) 
455) </ul>
456) 
457) <p>
458) We're continuing to move forward on all of these, but at this rate
459) <a href="#WhySlow">the Tor network is growing faster than the developers
460) can keep up</a>.
461) Now would be an excellent time to add a few more developers to the effort
462) so we can continue to grow the network.
463) </p>
464) 
465) <p>
466) We are also excited about tackling related problems, such as
467) censorship-resistance.
468) </p>
469) 
470) <p>
471) We are proud to have <a href="<page sponsors>">sponsorship and support</a>
472) from the Omidyar Network, the International Broadcasting Bureau, Bell
473) Security Solutions, the Electronic Frontier Foundation, several government
474) agencies and research groups, and hundreds of private contributors.
475) </p>
476) 
477) <p>
478) However, this support is not enough to keep Tor abreast of changes in the
479) Internet privacy landscape. Please <a href="<page donate>">donate</a>
480) to the project, or <a href="<page contact>">contact</a> our executive
481) director for information on making grants or major donations.
482) </p>
483) 
484) <hr />
485) 

486) <a id="HowUninstallTor"></a>
487) <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall Tor?</a></h3>
488) 
489) <p>
490) This depends entirely on how you installed it and which operating system you
491) have. If you installed a package, then hopefully your package has a way to

492) uninstall itself. The Windows packages include uninstallers. The proper way to

493) completely remove Tor, Vidalia, Torbutton for Firefox, and Privoxy on any
494) version of Windows is as follows:
495) </p>
496) 
497) <ol>
498) <li>In your taskbar, right click on Privoxy (the blue icon with a white "P")
499) and choose exit.</li>
500) <li>In your taskbar, right click on Vidalia (the green onion or the black head)
501) and choose exit.</li>
502) <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
503) Process List. If it's running, right click and choose End Process.</li>
504) <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
505) This will remove the Vidalia bundle, which includes Tor and Privoxy.</li>
506) <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
507) Click the Uninstall button.</li>

508) </ol>

509) 
510) <p>

511) If you do not follow these steps (for example by trying to uninstall
512) Vidalia, Tor, and Privoxy while they are still running), you will need to
513) reboot and manually remove the directory "Program Files\Vidalia Bundle".

514) </p>
515) 
516) <p>
517) For Mac OS X, follow the <a

518) href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.

519) </p>
520) 
521) <p>
522) If you installed by source, I'm afraid there is no easy uninstall method. But
523) on the bright side, by default it only installs into /usr/local/ and it should
524) be pretty easy to notice things there.
525) </p>
526) 
527) <hr />
528) 

529) <a id="PGPSigs"></a>
530) <h3><a class="anchor" href="#PGPSigs">What are these "sig" files on the
531) download page?</a></h3>

532) 
533) <p>
534) These are PGP signatures, so you can verify that the file you've downloaded is
535) exactly the one that we intended you to get.
536) </p>
537) 
538) <p>
539) Please read the <a
540) href="https://wiki.torproject.org/noreply/TheOnionRouter/VerifyingSignatures">verifying
541) signatures</a> page for details.
542) </p>
543) 
544) <hr />
545) 
546) <a id="CompileTorWindows"></a>
547) <h3><a class="anchor" href="#CompileTorWindows">How do I compile Tor under
548) Windows?</a></h3>
549) 
550) <p>
551) Try following the steps at <a

552) href="<svnsandbox>doc/tor-win32-mingw-creation.txt"><svnsandbox>doc/tor-win32-mingw-creation.txt</a>.

553) </p>
554) 

555) <p>
556) (Note that you don't need to compile Tor yourself in order to use
557) it. Most people just use the packages available on the <a href="<page
558) download>">download page</a>.)
559) </p>
560) 

561) <hr />
562) 

563) <a id="VirusFalsePositives"></a>
564) <h3><a class="anchor" href="#VirusFalsePositives">Why does my Tor
565) executable appear to have a virus or spyware?</a></h3>

566) 
567) <p>
568) Sometimes, overzealous Windows virus and spyware detectors trigger on some
569) parts of the Tor Windows binary. Our best guess is that these are false

570) positives — after all, the anti-virus and anti-spyware business is just a

571) guessing game anyway. You should contact your vendor and explain that you have
572) a program that seems to be triggering false positives. Or pick a better vendor.
573) </p>
574) 
575) <p>

576) In the meantime, we encourage you to not just take our word for
577) it. Our job is to provide the source; if you're concerned, please do <a
578) href="#CompileTorWindows">recompile it yourself</a>.

579) </p>
580) 
581) <hr />
582) 
583) <a id="LiveCD"></a>
584) <h3><a class="anchor" href="#LiveCD">Is there a LiveCD or other bundle that
585) includes Tor?</a></h3>
586) 
587) <p>
588) There isn't any official LiveCD at this point. We're still trying to find good
589) solutions and trying to understand the security and anonymity implications of
590) the various options. In the mean time, feel free to check out the list below
591) and use your best judgement:
592) </p>
593) 
594) <p>

595) LiveCDs:

596) </p>
597) 
598) <ol>
599) <li><a href="http://incognito.anonymityanywhere.com/">Incognito LiveCD/USB</a>
600) is a CD you can boot that has several Internet applications (Firefox, IRC,
601) Mail, etc) pre-configured to use Tor. For most computers everything is
602) automatically configured and you're ready to go. You can even copy the CD to a
603) USB drive. Includes TorK.</li>

604) <li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
605) is Knoppix-based with an emphasis on user-friendliness. You can work
606) anonymously or non-anonymously while TorK tries to keep you informed of the
607) consequences of your activity. The TorK LiveCD is experimental, so the aim is
608) to provide regular releases through 2007 and beyond.</li>

609) <li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> is a
610) debian based live-system including tor, firefox and torbutton which can save
611) bookmarks and other settings or data on an encrypted usb-key</li>

612) </ol>
613) 
614) <p>
615) Windows bundles:
616) </p>
617) 
618) <ol>

619) <li><a href="<page torbrowser/index>">Tor Browser Bundle</a>

620) for Windows comes with a pre-configured web browser and is self contained
621) so you can run it from a USB stick.</li>
622) <li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> is a successor
623) to JanusVM. It needs testing from you!</li>
624) <li><a href="http://janusvm.com/">JanusVM</a> is a Linux kernel and software
625) running in VMWare that sits between your Windows computer and the Internet,
626) making sure that your Internet traffic is scrubbed and anonymized.</li>
627) <li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>,
628) previously known as Torpark, is a Firefox+Tor package for Win32 that can
629) installed on a USB key. It needs a host Win32 operating system.</li>

630) </ol>
631) 
632) <p>
633) Not currently maintained as far as we know:
634) </p>
635) 
636) <ol>

637) <li>Polippix / Privatlivets Fred is a Danish Knoppix-based LiveCD with Tor
638) and utilities to encrypt IP-telephony. <a href="http://polippix.org/">Info and
639) download</a>.</li>

640) <li>ELE is a Linux LiveCD which is focused on privacy related
641) software. It includes Tor and you can download it at
642) <a
643) href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
644) <li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
645) Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
646) non-Tor traffic from accidentally leaving your computer. More information at
647) <a

648) href="https://wiki.torproject.org/noreply/VirtualPrivacyMachine">https://wiki.torproject.org/noreply/VirtualPrivacyMachine</a>.</li>

649) <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
650) than Linux for maximum security. It was designed to be anonymous and secure
651) from the ground up, and thus has some features and limitations not found in
652) other LiveCDs (Tor related or otherwise). You can obtain more information and
653) download Anonym.OS from <a
654) href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
655) <li>Phantomix is a LiveCD for anonymous surfing and chatting based on the most
656) recent KNOPPIX release. It comes preconfigured with tor and privoxy. You can
657) get it from the <a href="http://phantomix.ytternhagen.de/">Phantomix
658) Website</a>.</li>
659) </ol>
660) 

661) <p>
662) Please contact us if you know any others.
663) </p>
664) 

665) <hr />
666) 

667) <a id="WhyNotNamed"></a>
668) <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3>
669) 
670) <p>
671) We currently use these metrics to determine if your relay should be named:<br />
672) </p>
673) <ul>
674) <li>The name is not currently mapped to a different key. Existing mappings
675) are removed after 6 months of inactivity from a relay.</li>
676) <li>The relay must have been around for at least two weeks.</li>
677) <li>No other router may have wanted the same name in the past month.</li>
678) </ul>
679) 
680) <hr />
681) 

682) <a id="KeyManagement"></a>

683) <h3><a class="anchor" href="#KeyManagement">Tell me about all the keys
684) Tor uses.</a></h3>

685) 
686) <p>

687) Tor uses a variety of different keys, with three goals in mind: 1)

688) encryption to ensure privacy of data within the Tor network, 2)
689) authentication so clients know they're
690) talking to the relays they meant to talk to, and 3) signatures to make
691) sure all clients know the same set of relays.

692) </p>
693) 
694) <p>
695) <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
696) so observers can't look inside to see which circuit a given cell is
697) intended for. Further, the Tor client establishes an ephemeral encryption
698) key with each relay in the circuit, so only the exit relay can read
699) the cells. Both sides discard the circuit key when the circuit ends,
700) so logging traffic and then breaking into the relay to discover the key
701) won't work.
702) </p>
703) 
704) <p>
705) <b>Authentication</b>:
706) Every Tor relay has a public decryption key called the "onion key".
707) When the Tor client establishes circuits, at each step it <a
708) href="<svnsandbox>doc/design-paper/tor-design.html#subsec:circuits">demands
709) that the Tor relay prove knowledge of its onion key</a>. That way

710) the first node in the path can't just spoof the rest of the path.

711) Each relay rotates its onion key once a week.

712) </p>
713) 
714) <p>

715) <b>Coordination</b>:

716) How do clients know what the relays are, and how do they know that they

717) have the right keys for them? Each relay has a long-term public signing
718) key called the "identity key". Each directory authority additionally has a

719) "directory signing key". The directory authorities <a
720) href="<svnsandbox>doc/spec/dir-spec.txt">provide a signed list</a>

721) of all the known relays, and in that list are a set of certificates from
722) each relay (self-signed by their identity key) specifying their keys,
723) locations, exit policies, and so on. So unless the adversary can control
724) a threshold of the directory authorities, he can't trick the Tor client
725) into using other Tor relays.

726) </p>
727) 
728) <p>

729) How do clients know what the directory authorities are? The Tor software
730) comes with a built-in list of location and public key for each directory
731) authority. So the only way to trick users into using a fake Tor network

732) is to give them a specially modified version of the software.
733) </p>

734) 

735) <p>
736) How do users know they've got the right software? When we distribute
737) the source code or a package, we digitally sign it with <a

738) href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a

739) href="https://wiki.torproject.org/noreply/TheOnionRouter/VerifyingSignatures">instructions
740) on how to check Tor's signatures</a>.
741) </p>

742) 

743) <p>

744) In order to be certain that it's really signed by us, you need to have
745) met us in person and gotten a copy of our GPG key fingerprint, or you
746) need to know somebody who has. If you're concerned about an attack on
747) this level, we recommend you get involved with the security community
748) and start meeting people.

749) </p>

750) 

751) <hr />
752) 

753) <a id="EverybodyARelay"></a>
754) <h3><a class="anchor" href="#EverybodyARelay">You should make every Tor
755) user be a relay.</a></h3>
756) 
757) <p>
758) Requiring every Tor user to be a relay would help with scaling the

759) network to handle all our users, and <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor

760) relay may help your anonymity</a>. However, many Tor users cannot be good
761) relays &mdash; for example, some Tor clients operate from behind restrictive
762) firewalls, connect via modem, or otherwise aren't in a position where they
763) can relay traffic. Providing service to these clients is a critical

764) part of providing effective anonymity for everyone, since many Tor users
765) are subject to these or similar constraints and including these clients
766) increases the size of the anonymity set.
767) </p>
768) 
769) <p>
770) That said, we do want to encourage Tor users to run relays, so what we
771) really want to do is simplify the process of setting up and maintaining

772) a relay. We've made a lot of progress with easy configuration in the past
773) few years: Vidalia has an easy relay configuration interface, and supports
774) uPnP too. Tor is good at automatically detecting whether it's reachable and
775) how much bandwidth it can offer.

776) </p>
777) 
778) <p>
779) There are five steps we need to address before we can do this though:
780) </p>
781) 
782) <p>

783) First, we need to make Tor stable as a relay on all common
784) operating systems. The main remaining platform is Windows,
785) and we plan to finally address that in 2009. See Section 4.1 of <a
786) href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">our
787) development roadmap</a>.

788) </p>
789) 
790) <p>

791) Second, we still need to get better at automatically estimating
792) the right amount of bandwidth to allow. See item #7 on the
793) <a href="<page volunteer>#Research">research section of the
794) volunteer page</a>: "Tor doesn't work very well when relays
795) have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
796) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
797) to UDP transport</a> is the simplest answer here &mdash; which alas is
798) not a very simple answer at all.

799) </p>
800) 
801) <p>

802) Third, we need to work on scalability, both of the network (how to
803) stop requiring that all Tor relays be able to connect to all Tor
804) relays) and of the directory (how to stop requiring that all Tor
805) users know about all Tor relays). Changes like this can have large
806) impact on potential and actual anonymity. See Section 5 of the <a
807) href="<svnsandbox>doc/design-paper/challenges.pdf">Challenges</a> paper
808) for details. Again, UDP transport would help here.

809) </p>
810) 
811) <p>

812) Fourth, we need to better understand the risks from
813) letting the attacker send traffic through your relay while
814) you're also initiating your own anonymized traffic. <a
815) href="http://freehaven.net/anonbib/#back01">Three</a> <a
816) href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
817) <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
818) describe ways to identify the relays in a circuit by running traffic
819) through candidate relays and looking for dips in the traffic while the
820) circuit is active. These clogging attacks are not that scary in the Tor
821) context so long as relays are never clients too. But if we're trying to
822) encourage more clients to turn on relay functionality too (whether as
823) <a href="<page bridges>">bridge relays</a> or as normal relays), then
824) we need to understand this threat better and learn how to mitigate it.

825) </p>
826) 
827) <p>
828) Fifth, we might need some sort of incentive scheme to encourage people
829) to relay traffic for others, and/or to become exit nodes. Here are our

830) <a href="https://blog.torproject.org/blog/two-incentive-designs-tor">current
831) thoughts on Tor incentives</a>.

832) </p>
833) 
834) <p>
835) Please help on all of these!
836) </p>
837) 
838) <hr />
839) 

840) <a id="Criminals"></a>
841) <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals to do bad
842) things?</a></h3>
843) 
844) <p>
845) For the answer to this question and others, please see our new <a

846) href="<page faq-abuse>">Tor Abuse FAQ</a>.

847) </p>
848) 
849) <hr />
850) 
851) <a id="RespondISP"></a>
852) <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP about my
853) exit relay?</a></h3>
854) 
855) <p>
856) A collection of templates for successfully responding to ISPs is <a
857) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorAbuseTemplates">collected
858) here</a>.
859) </p>
860) 

861) <hr />

862) 

863)   </div><!-- #main -->

864) 
865) #include <foot.wmi>