tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 2-medium

4) 

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

11) <h2>Tor FAQ</h2>
12) <hr />

13) 

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

15) <ul>

16) <li><a href="#WhatIsTor">What is Tor?</a></li>

17) <li><a href="#Torisdifferent">How is Tor different from other proxies?</a></li>

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

29) </ul>
30) 

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

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

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

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

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

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

40) </ul>

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

47) <ul>

48) <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>

49) <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal

50) with abuse issues.</a></li>

51) <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
52) relay?</a></li>

53) <li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li>

54) </ul>

55) 
56) <p>Running a Tor hidden service:</p>
57) 

58) <p>Anonymity and Security:</p>
59) <ul>

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

61) </ul>
62) 

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

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

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

80) <hr />
81) 
82) <a id="General"></a>
83) 

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

104) and develops the Tor software.

105) </p>
106) 

107) <hr />
108) 

109) <a id="Torisdifferent"></a>
110) <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
111) <p>
112) A typical proxy provider sets up a server somewhere on the Internet and allows you to use it to relay your traffic.  This creates a simple, easy to maintain architecture.  The users all enter and leave through the same server.  The provider may charge for use of the proxy, or fund their costs through advertisements on the server.  In the simplest configuration, you don't have to install anything.  You just have to point your browser at their proxy server.  Simple proxy providers are fine solutions if you do not want protections for your privacy and anonymity online and you trust the provider from doing bad things.  Some simple proxy providers use SSL to secure your connection to them.  This may protect you against local eavesdroppers, such as those at a cafe with free wifi Internet.
113) </p>
114) <p>
115) Simple proxy providers also create a single point of failure.  The provider knows who you are and where you browse on the Internet.  They can see your traffic as it passes through their server.  In some cases, they can see your encrypted traffic as they relay it to your banking site or to ecommerce stores.  You have to trust the provider isn't doing any number of things, such as watching your traffic, injecting their own advertisements into your traffic stream, and isn't recording your personal details.
116) </p>
117) <p>
118) Tor passes your traffic through at least 3 different servers before sending it on to the destination.  Tor does not modify, or even know, what you are sending into it.  It merely relays your traffic, completely encrypted through the Tor network and has it pop out somewhere else in the world, completely intact.  The Tor client is required because we assume you trust your local computer.  The Tor client manages the encryption and the path chosen through the network.  The relays located all over the world merely pass encrypted packets between themselves.</p>
119) <p>

120) <dl>

121) <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad first of three servers can see encrypted Tor traffic coming from your computer.  It still doesn't know who you are and what you are doing over Tor.  It merely sees "This IP address is using Tor".  Tor is not illegal anywhere in the world, so using Tor by itself is fine.  You are still protected from this node figuring out who you are and where you are going on the Internet.</dd>
122) <dt>Can't the third server see my traffic?</dt><dd>Possibly.  A bad third of three servers can see the traffic you sent into Tor.  It won't know who sent this traffic.  If you're using encryption, such as visiting a bank or ecommerce website, or encrypted mail connections, etc, it will only know the destination.  It won't be able to see the data inside the traffic stream.  You are still protected from this node figuring out who you are and if using encryption, what data you're sending to the destination.</dd>

123) </dl>

124) </p>
125) 

126) <hr />
127) 

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

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

131) 
132) <p>
133) There are two pieces to "Torifying" a program: connection-level anonymity
134) and application-level anonymity. Connection-level anonymity focuses on

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

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

144) </p>
145) 
146) <p>

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

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

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

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

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

165) </p>
166) 

167) <hr />
168) 

169) <a id="WhyCalledTor"></a>
170) <h3><a class="anchor" href="#WhyCalledTor">Why is it called Tor?</a></h3>
171) 
172) <p>

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

180) </p>
181) 
182) <p>

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

184) </p>
185) 
186) <p>

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

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

192) </p>
193) 

194) <hr />
195) 

196) <a id="Backdoor"></a>
197) <h3><a class="anchor" href="#Backdoor">Is there a backdoor in Tor?</a></h3>
198) 
199) <p>

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

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

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

203) ask us, we will fight them, and (the lawyers say) probably win.
204) </p>
205) 
206) <p>
207) We think that putting a backdoor in Tor would be tremendously
208) irresponsible to our users, and a bad precedent for security software

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

211) trust our software ever again — for excellent reason!
212) </p>
213) 
214) <p>
215) But that said, there are still plenty of subtle attacks

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

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

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

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

221) should also check the <a href="<page verifying-signatures>">PGP

222) signatures</a> on the releases, to make sure nobody messed with the
223) distribution sites.

224) </p>
225) 
226) <p>
227) Also, there might be accidental bugs in Tor that could affect your

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

230) </p>
231) 

232) <hr />
233) 

234) <a id="DistributingTor"></a>
235) <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor on

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

237) 
238) <p>
239) Yes.
240) </p>
241) 
242) <p>

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

244) means we give you the rights to redistribute the Tor software, either
245) modified or unmodified, either for a fee or gratis. You don't have to
246) ask us for specific permission.
247) </p>
248) 
249) <p>
250) However, if you want to redistribute the Tor software you must follow our

251) <a href="<svnsandbox>LICENSE">LICENSE</a>.

252) Essentially this means that you need to include our LICENSE file along
253) with whatever part of the Tor software you're distributing.
254) </p>
255) 
256) <p>
257) Most people who ask us this question don't want to distribute just the
258) Tor software, though. They want to distribute the Tor bundles, which
259) typically include <a href="http://www.privoxy.org/">Privoxy</a>

260) and <a href="<page vidalia/index>">Vidalia</a>.

261) You will need to follow the licenses for those programs
262) as well. Both of them are distributed under the <a

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

264) Public License</a>. The simplest way to obey their licenses is to
265) include the source code for these programs everywhere you include
266) the bundles themselves. Look for "source" packages on the <a

267) href="<page vidalia/index>">Vidalia page</a> and the <a

268) href="http://sourceforge.net/project/showfiles.php?group_id=11118">Privoxy
269) download page</a>.
270) </p>
271) 
272) <p>

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

274) who makes it, and what properties it provides (and doesn't provide). See
275) our <a href="<page trademark-faq>">trademark FAQ</a> for details.
276) </p>
277) 
278) <p>
279) Lastly, you should realize that we release new versions of the
280) Tor software frequently, and sometimes we make backward incompatible
281) changes. So if you distribute a particular version of the Tor software, it
282) may not be supported &mdash; or even work &mdash; six months later. This
283) is a fact of life for all security software under heavy development.
284) </p>
285) 

286) <hr />
287) 

288) <a id="SupportMail"></a>
289) <h3><a class="anchor" href="#SupportMail">How can I get an answer to my
290) Tor support mail?</a></h3>
291) 
292) <p>
293) Many people send the Tor developers mail privately, or send mail to

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

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

296) they can't configure Privoxy correctly, or so on. Sometimes our
297) volunteers can answer these mails, but typically they need to spend
298) most of their time on development tasks that will benefit more people.
299) This is especially true if your question is already covered in the <a
300) href="<page documentation>">documentation</a> or on this FAQ. We don't
301) hate you; we're just busy.
302) </p>
303) 
304) <p>
305) So if we don't answer your mail, first check the <a href="<page
306) documentation>">documentation</a> page, along with this FAQ,
307) to make sure your question isn't already answered.  Then read <a
308) href="http://www.catb.org/~esr/faqs/smart-questions.html">"How to ask
309) questions the smart way"</a>. If this doesn't help you, note that we
310) have <a href="<page documentation>#Support">an IRC channel</a> where you
311) can ask your questions (but if they are still open-ended, ill-formed,
312) or not about Tor, you likely won't get much help there either). Lastly,
313) people on the <a href="<page documentation>#MailingLists">or-talk
314) mailing list</a> may be able to provide some hints for you, if
315) others have experienced your problems too. Be sure to look over <a
316) href="http://archives.seul.org/or/talk/">the archives</a> first.
317) </p>
318) 
319) <p>
320) Another strategy is to <a href="<page docs/tor-doc-relay>">run a Tor
321) relay for a while</a>, and/or <a href="<page donate>">donate money</a>
322) <a href="<page volunteer>">or time</a> to the effort. We're more likely
323) to pay attention to people who have demonstrated interest and commitment
324) to giving back to the Tor community.
325) </p>
326) 
327) <p>

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

329) mailing list and answer questions from others.
330) </p>
331) 

332) <hr />
333) 

334) <a id="WhySlow"></a>
335) <h3><a class="anchor" href="#WhySlow">Why is Tor so slow?</a></h3>
336) 
337) <p>
338) There are many reasons why the Tor network is currently slow.
339) </p>
340) 
341) <p>
342) Before we answer, though, you should realize that Tor is never going to
343) be blazing fast. Your traffic is bouncing through volunteers' computers
344) in various parts of the world, and some bottlenecks and network latency
345) will always be present. You shouldn't expect to see university-style
346) bandwidth through Tor.
347) </p>
348) 
349) <p>
350) But that doesn't mean that it can't be improved. The current Tor network
351) is quite small compared to the number of people trying to use it, and
352) many of these users don't understand or care that Tor can't currently
353) handle file-sharing traffic load.
354) </p>
355) 
356) <p>
357) What can you do to help?
358) </p>
359) 
360) <ul>
361) 
362) <li>
363) <a href="<page docs/tor-doc-relay>">Configure your Tor to relay traffic
364) for others</a>. Help make the Tor network large enough that we can handle
365) all the users who want privacy and security on the Internet.
366) </li>
367) 
368) <li>
369) <a href="<page gui/index>">Help us make Tor more usable</a>. We
370) especially need people to help make it easier to configure your Tor
371) as a relay. Also, we need help with clear simple documentation to
372) walk people through setting it up.
373) </li>
374) 
375) <li>
376) There are some bottlenecks in the current Tor network. Help us design
377) experiments to track down and demonstrate where the problems are, and
378) then we can focus better on fixing them.
379) </li>
380) 
381) <li>
382) There are some steps that individuals
383) can take to improve their Tor performance. <a
384) href="https://wiki.torproject.org/noreply/TheOnionRouter/FireFoxTorPerf">You
385) can configure your Firefox to handle Tor better</a>, <a
386) href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
387) Polipo with Tor</a>, or you can try <a href="<page download>">upgrading
388) to the latest version of Tor</a>.  If this works well, please help by
389) documenting what you did, and letting us know about it.
390) </li>
391) 
392) <li>
393) Tor needs some architectural changes too. One important change is to

394) start providing <a

395) href="#EverybodyARelay">better

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

398) </li>
399) 
400) <li>
401) Help do other things so we can do the hard stuff. Please take a moment
402) to figure out what your skills and interests are, and then <a href="<page
403) volunteer>">look at our volunteer page</a>.
404) </li>
405) 
406) <li>
407) Help find sponsors for Tor. Do you work at a company or government agency
408) that uses Tor or has a use for Internet privacy, e.g. to browse the
409) competition's websites discreetly, or to connect back to the home servers
410) when on the road without revealing affiliations? If your organization has
411) an interest in keeping the Tor network working, please contact them about
412) supporting Tor. Without sponsors, Tor is going to become even slower.
413) </li>
414) 
415) <li>
416) If you can't help out with any of the above, you can still help out
417) individually by <a href="<page donate>">donating a bit of money to the
418) cause</a>. It adds up!
419) </li>
420) 
421) </ul>
422) 

423) <hr />
424) 

425) <a id="Funding"></a>

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

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

521) <a id="HowUninstallTor"></a>
522) <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall Tor?</a></h3>
523) 
524) <p>
525) This depends entirely on how you installed it and which operating system you
526) have. If you installed a package, then hopefully your package has a way to

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

528) completely remove Tor, Vidalia, Torbutton for Firefox, and Privoxy on any
529) version of Windows is as follows:
530) </p>
531) 
532) <ol>
533) <li>In your taskbar, right click on Privoxy (the blue icon with a white "P")
534) and choose exit.</li>
535) <li>In your taskbar, right click on Vidalia (the green onion or the black head)
536) and choose exit.</li>
537) <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
538) Process List. If it's running, right click and choose End Process.</li>
539) <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
540) This will remove the Vidalia bundle, which includes Tor and Privoxy.</li>
541) <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
542) Click the Uninstall button.</li>

543) </ol>

544) 
545) <p>

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

549) </p>
550) 
551) <p>
552) For Mac OS X, follow the <a

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

554) </p>
555) 
556) <p>
557) If you installed by source, I'm afraid there is no easy uninstall method. But
558) on the bright side, by default it only installs into /usr/local/ and it should
559) be pretty easy to notice things there.
560) </p>
561) 
562) <hr />
563) 

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

567) 
568) <p>
569) These are PGP signatures, so you can verify that the file you've downloaded is
570) exactly the one that we intended you to get.
571) </p>
572) 
573) <p>
574) Please read the <a

575) href="<page verifying-signatures>">verifying signatures</a> page for details.

576) </p>
577) 
578) <hr />
579) 
580) <a id="CompileTorWindows"></a>
581) <h3><a class="anchor" href="#CompileTorWindows">How do I compile Tor under
582) Windows?</a></h3>
583) 
584) <p>
585) Try following the steps at <a

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

587) </p>
588) 

589) <p>
590) (Note that you don't need to compile Tor yourself in order to use
591) it. Most people just use the packages available on the <a href="<page
592) download>">download page</a>.)
593) </p>
594) 

595) <hr />
596) 

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

600) 
601) <p>
602) Sometimes, overzealous Windows virus and spyware detectors trigger on some
603) parts of the Tor Windows binary. Our best guess is that these are false

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

605) guessing game anyway. You should contact your vendor and explain that you have
606) a program that seems to be triggering false positives. Or pick a better vendor.
607) </p>
608) 
609) <p>

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

613) </p>
614) 
615) <hr />
616) 
617) <a id="LiveCD"></a>
618) <h3><a class="anchor" href="#LiveCD">Is there a LiveCD or other bundle that
619) includes Tor?</a></h3>
620) 
621) <p>
622) There isn't any official LiveCD at this point. We're still trying to find good
623) solutions and trying to understand the security and anonymity implications of
624) the various options. In the mean time, feel free to check out the list below
625) and use your best judgement:
626) </p>
627) 
628) <p>

629) LiveCDs:

630) </p>
631) 
632) <ol>
633) <li><a href="http://incognito.anonymityanywhere.com/">Incognito LiveCD/USB</a>
634) is a CD you can boot that has several Internet applications (Firefox, IRC,
635) Mail, etc) pre-configured to use Tor. For most computers everything is
636) automatically configured and you're ready to go. You can even copy the CD to a
637) USB drive. Includes TorK.</li>

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

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

646) </ol>
647) 
648) <p>
649) Windows bundles:
650) </p>
651) 
652) <ol>

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

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

664) </ol>
665) 
666) <p>
667) Not currently maintained as far as we know:
668) </p>
669) 
670) <ol>

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

674) <li>ELE is a Linux LiveCD which is focused on privacy related
675) software. It includes Tor and you can download it at
676) <a
677) href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
678) <li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
679) Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
680) non-Tor traffic from accidentally leaving your computer. More information at
681) <a

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

683) <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
684) than Linux for maximum security. It was designed to be anonymous and secure
685) from the ground up, and thus has some features and limitations not found in
686) other LiveCDs (Tor related or otherwise). You can obtain more information and
687) download Anonym.OS from <a
688) href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
689) <li>Phantomix is a LiveCD for anonymous surfing and chatting based on the most
690) recent KNOPPIX release. It comes preconfigured with tor and privoxy. You can
691) get it from the <a href="http://phantomix.ytternhagen.de/">Phantomix
692) Website</a>.</li>
693) </ol>
694) 

695) <p>
696) Please contact us if you know any others.
697) </p>
698) 

699) <hr />
700) 

701) <a id="RelayFlexible"></a>
702) <h3><a class="anchor" href="#RelayFlexible">How stable does my relay
703) need to be?</a></h3>
704) 
705) <p>
706) We aim to make setting up a Tor relay easy and convenient:
707) </p>
708) 
709) <ul>
710) <li>Tor has built-in support for <a
711) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">
712) rate
713) limiting</a>. Further, if you have a fast link
714) but want to limit the number of bytes per day
715) (or week or month) that you donate, check out the <a
716) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hib
717) ernation
718) feature</a>.
719) </li>
720) <li>Each Tor relay has an <a

721) href="#ExitPolicies">exit

722) policy</a> that specifies what sort of outbound connections are allowed
723) or refused from that relay. If you are uncomfortable allowing people
724) to exit from your relay, you can set it up to only allow connections
725) to other Tor relays.
726) </li>
727) <li>It's fine if the relay goes offline sometimes. The directories
728) notice this quickly and stop advertising the relay. Just try to make
729) sure it's not too often, since connections using the relay when it
730) disconnects will break.
731) </li>
732) <li>We can handle relays with dynamic IPs just fine &mdash; simply
733) leave the Address config option blank, and Tor will try to guess.
734) </li>
735) <li>If your relay is behind a NAT and it doesn't know its public
736) IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
737) forwarding. Forwarding TCP connections is system dependent but <a
738) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewal
739) ledClients">this
740) FAQ entry</a> offers some examples on how to do this.
741) </li>
742) <li>Your relay will passively estimate and advertise its recent
743) bandwidth capacity, so high-bandwidth relays will attract more users than
744) low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
745) </li>
746) </ul>
747) 
748) <hr />
749) 

750) <a id="RunARelayBut"></a>

751) <a id="ExitPolicies"></a>
752) <h3><a class="anchor" href="#ExitPolicies">I'd run a relay, but I don't

753) want to deal with abuse issues.</a></h3>
754) 
755) <p>
756) Great. That's exactly why we implemented exit policies.
757) </p>
758) 
759) <p>

760) Each Tor relay has an exit policy that specifies what sort of
761) outbound connections are allowed or refused from that relay. The exit

762) policies are propagated to Tor clients via the directory, so clients

763) will automatically avoid picking exit relays that would refuse to
764) exit to their intended destination. This way each relay can decide
765) the services, hosts, and networks he wants to allow connections to,
766) based on abuse potential and his own situation. Read the FAQ entry on
767) <a href="<page faq-abuse>#TypicalAbuses">issues you might encounter
768) if you use the default exit policy</a>, and then read Mike Perry's <a
769) href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">tips
770) for running an exit node with minimal harassment</a>.
771) </p>
772) 
773) <p>
774) The default exit policy allows access to
775) many popular services (e.g. web browsing), but <a
776) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
777) some due to abuse potential (e.g. mail) and some since
778) the Tor network can't handle the load (e.g. default
779) file-sharing ports). You can change your exit policy
780) using Vidalia's "Sharing" tab, or by manually editing your <a
781) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>
782) file. If you want to avoid most if not all abuse potential, set it to

783) "reject *:*" (or un-check all the boxes in Vidalia). This setting means
784) that your relay will be used for relaying traffic inside the Tor network,
785) but not for connections to external websites or other services.

786) </p>
787) 
788) <p>

789) If you do allow any exit connections, make sure name resolution works
790) (that is, your computer can resolve Internet addresses correctly).

791) If there are any resources that your computer can't reach (for example,
792) you are behind a restrictive firewall or content filter), please
793) explicitly reject them in your exit policy — otherwise Tor users
794) will be impacted too.

795) </p>
796) 
797) <hr />
798) 

799) <a id="RelayOrBridge"></a>
800) <h3><a class="anchor" href="#RelayOrBridge">Should I be a normal relay
801) or bridge relay?</a></h3>
802) 
803) <p><a href="<page bridges>">Bridge relays</a> (or "bridges" for short)

804) are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't listed
805) in the main Tor directory. That means

806) that even an ISP or government trying to filter connections to the Tor
807) network probably won't be able to block all the bridges.
808) </p>
809) 
810) <p>Being a normal relay vs being a bridge relay is almost the same
811) configuration: it's just a matter of whether your relay is listed
812) publically or not.
813) </p>
814) 
815) <p>Right now, there are roughly zero places in the world that filter
816) connections to the Tor network. So getting a lot of bridges running
817) right now is mostly a backup measure, a) in case the Tor network does
818) get blocked somewhere, and b) for people who want an extra layer of
819) security because they're worried somebody will recognize that it's a

820) public Tor relay IP address they're contacting.

821) </p>
822) 
823) <p>So should you run a normal relay or bridge relay? If you have
824) lots of bandwidth, you should definitely run a normal relay &mdash;
825) bridge relays see very little use these days. If you're willing to <a
826) href="#ExitPolicies">be an exit</a>, you should definitely run a normal
827) relay, since we need more exits. If you can't be an exit and only have
828) a little bit of bandwidth, then flip a coin. Thanks for volunteering!
829) </p>
830) 
831) <hr />
832) 

833) <a id="WhyNotNamed"></a>
834) <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3>
835) 
836) <p>
837) We currently use these metrics to determine if your relay should be named:<br />
838) </p>
839) <ul>
840) <li>The name is not currently mapped to a different key. Existing mappings
841) are removed after 6 months of inactivity from a relay.</li>
842) <li>The relay must have been around for at least two weeks.</li>
843) <li>No other router may have wanted the same name in the past month.</li>
844) </ul>
845) 
846) <hr />
847) 

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

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

851) 
852) <p>

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

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

858) </p>
859) 
860) <p>
861) <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
862) so observers can't look inside to see which circuit a given cell is
863) intended for. Further, the Tor client establishes an ephemeral encryption
864) key with each relay in the circuit, so only the exit relay can read
865) the cells. Both sides discard the circuit key when the circuit ends,
866) so logging traffic and then breaking into the relay to discover the key
867) won't work.
868) </p>
869) 
870) <p>
871) <b>Authentication</b>:
872) Every Tor relay has a public decryption key called the "onion key".
873) When the Tor client establishes circuits, at each step it <a
874) href="<svnsandbox>doc/design-paper/tor-design.html#subsec:circuits">demands
875) that the Tor relay prove knowledge of its onion key</a>. That way

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

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

878) </p>
879) 
880) <p>

881) <b>Coordination</b>:

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

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

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

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

892) </p>
893) 
894) <p>

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

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

900) 

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

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

905) href="<page verifying-signatures>">instructions

906) on how to check Tor's signatures</a>.
907) </p>

908) 

909) <p>

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

915) </p>

916) 

917) <hr />
918) 

919) <a id="EverybodyARelay"></a>
920) <h3><a class="anchor" href="#EverybodyARelay">You should make every Tor
921) user be a relay.</a></h3>
922) 
923) <p>
924) Requiring every Tor user to be a relay would help with scaling the

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

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

930) part of providing effective anonymity for everyone, since many Tor users
931) are subject to these or similar constraints and including these clients
932) increases the size of the anonymity set.
933) </p>
934) 
935) <p>
936) That said, we do want to encourage Tor users to run relays, so what we
937) really want to do is simplify the process of setting up and maintaining

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

942) </p>
943) 
944) <p>
945) There are five steps we need to address before we can do this though:
946) </p>
947) 
948) <p>

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

954) </p>
955) 
956) <p>

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

965) </p>
966) 
967) <p>

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

975) </p>
976) 
977) <p>

978) Fourth, we need to better understand the risks from
979) letting the attacker send traffic through your relay while
980) you're also initiating your own anonymized traffic. <a
981) href="http://freehaven.net/anonbib/#back01">Three</a> <a
982) href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
983) <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
984) describe ways to identify the relays in a circuit by running traffic
985) through candidate relays and looking for dips in the traffic while the
986) circuit is active. These clogging attacks are not that scary in the Tor
987) context so long as relays are never clients too. But if we're trying to
988) encourage more clients to turn on relay functionality too (whether as
989) <a href="<page bridges>">bridge relays</a> or as normal relays), then
990) we need to understand this threat better and learn how to mitigate it.

991) </p>
992) 
993) <p>
994) Fifth, we might need some sort of incentive scheme to encourage people
995) to relay traffic for others, and/or to become exit nodes. Here are our

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

998) </p>
999) 
1000) <p>
1001) Please help on all of these!
1002) </p>
1003) 
1004) <hr />
1005) 

1006) <a id="Criminals"></a>
1007) <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals to do bad
1008) things?</a></h3>
1009) 
1010) <p>

1011) For the answer to this question and others, please see our <a

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

1013) </p>
1014) 
1015) <hr />
1016) 
1017) <a id="RespondISP"></a>
1018) <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP about my
1019) exit relay?</a></h3>
1020) 
1021) <p>
1022) A collection of templates for successfully responding to ISPs is <a
1023) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorAbuseTemplates">collected
1024) here</a>.
1025) </p>
1026) 

1027) <hr />

1028) 

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

1030) 
1031) #include <foot.wmi>