tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 2-medium
4) 
5) #include "head.wmi" TITLE="Tor Project: FAQ" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page docs/documentation>">Documentation &raquo; </a>
10)     <a href="<page docs/faq>">FAQ</a>
11)   </div>
12)   <div id="maincol">
13)     <!-- PUT CONTENT AFTER THIS TAG -->
14)     <h1>Tor FAQ</h1>

15)     <hr>

16) 

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

32)     <li><a href="#Metrics">How many people use Tor? How many relays or
33)     exit nodes are there?</a></li>

34)     </ul>

35) 

36)     <p>Compilation and Installation:</p>
37)     <ul>
38)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
39)     <li><a href="#PGPSigs">What are these "sig" files on the download
40)     page?</a></li>
41)     <li><a href="#CompileTorWindows">How do I compile Tor under Windows?</a></li>
42)     <li><a href="#VirusFalsePositives">Why does my Tor executable appear to
43)     have a virus or spyware?</a></li>
44)     <li><a href="#LiveCD">Is there a LiveCD or other bundle that includes Tor?</a></li>
45)     </ul>

46) 

47)     <p>Running Tor:</p>

48) 

49)     <p>Running a Tor client:</p>
50)     <ul>

51)     <li><a href="#DoesntWork">I installed Tor and Polipo but it's not
52)     working.</a></li>
53)     <li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at
54)     start.</a></li>
55)     <li><a href="#ChooseEntryExit">Can I control which nodes (or country)
56)     are used for entry/exit?</a></li>
57)     <li><a href="#GoogleCaptcha">Google makes me solve a Captcha or tells
58)     me I have spyware installed.</a></li>
59)     <li><a href="#GmailWarning">Gmail warns me that my account may have
60)     been compromised.</a></li>

61)     <li><a href="#FirewallPorts">My firewall only allows a few outgoing
62)     ports.</a></li>

63)     </ul>

64) 

65)     <p>Running a Tor relay:</p>
66)     <ul>
67)     <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
68)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
69)     with abuse issues.</a></li>
70)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
71)     relay?</a></li>

72)     <li><a href="#ManyRelays">I want to run more than one relay.</a></li>

73)     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?</a></li>
74)     <li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li>
75)     </ul>

76) 

77)     <p>Running a Tor hidden service:</p>

78) 

79)     <p>Anonymity and Security:</p>
80)     <ul>
81)     <li><a href="#KeyManagement">Tell me about all the keys Tor uses.</a></li>
82)     </ul>

83) 

84)     <p>Alternate designs that we don't do (yet):</p>
85)     <ul>
86)     <li><a href="#EverybodyARelay">You should make every Tor user be a
87)     relay.</a></li>
88)     </ul>

89) 

90)     <p>Abuse</p>
91)     <ul>
92)     <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
93)     <li><a href="#RespondISP">How do I respond to my ISP about my exit
94)     relay?</a></li>
95)     </ul>

96) 

97)     <p>For other questions not yet on this version of the FAQ, see the <a

98)     href="<wikifaq>">wiki FAQ</a> for now.</p>

99) 

100)     <hr>

101) 

102)     <a id="General"></a>

103) 

104)     <a id="WhatIsTor"></a>
105)     <h3><a class="anchor" href="#WhatIsTor">What is Tor?</a></h3>

106) 

107)     <p>
108)     The name "Tor" can refer to several different components.
109)     </p>

110) 

111)     <p>
112)     The Tor software is a program you can run on your computer that helps keep
113)     you safe on the Internet. Tor protects you by bouncing your communications
114)     around a distributed network of relays run by volunteers all around
115)     the world: it prevents somebody watching your Internet connection from
116)     learning what sites you visit, and it prevents the sites you visit
117)     from learning your physical location. This set of volunteer relays is
118)     called the Tor network. You can read more about how Tor works on the <a
119)     href="<page about/overview>">overview page</a>.
120)     </p>

121) 

122)     <p>
123)     The Tor Project is a non-profit (charity) organization that maintains
124)     and develops the Tor software.
125)     </p>

126) 

127)     <hr>

128) 

129)     <a id="Torisdifferent"></a>
130)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
131)     <p>

132)     A typical proxy provider sets up a server somewhere on the Internet and
133) allows you to use it to relay your traffic.  This creates a simple, easy to
134) maintain architecture.  The users all enter and leave through the same server.
135) The provider may charge for use of the proxy, or fund their costs through
136) advertisements on the server.  In the simplest configuration, you don't have to
137) install anything.  You just have to point your browser at their proxy server.
138) Simple proxy providers are fine solutions if you do not want protections for
139) your privacy and anonymity online and you trust the provider from doing bad
140) things.  Some simple proxy providers use SSL to secure your connection to them.
141) This may protect you against local eavesdroppers, such as those at a cafe with
142) free wifi Internet.
143)     </p>
144)     <p>
145)     Simple proxy providers also create a single point of failure.  The provider
146) knows who you are and where you browse on the Internet.  They can see your
147) traffic as it passes through their server.  In some cases, they can see your
148) encrypted traffic as they relay it to your banking site or to ecommerce stores.
149) You have to trust the provider isn't doing any number of things, such as
150) watching your traffic, injecting their own advertisements into your traffic
151) stream, and isn't recording your personal details.
152)     </p>
153)     <p>
154)     Tor passes your traffic through at least 3 different servers before sending
155) it on to the destination.  Tor does not modify, or even know, what you are
156) sending into it.  It merely relays your traffic, completely encrypted through
157) the Tor network and has it pop out somewhere else in the world, completely
158) intact.  The Tor client is required because we assume you trust your local
159) computer.  The Tor client manages the encryption and the path chosen through
160) the network.  The relays located all over the world merely pass encrypted
161) packets between themselves.</p>

162)     <p>
163)     <dl>

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

177)     </dl>
178)     </p>

179) 

180)     <hr>

181) 

182)     <a id="CompatibleApplications"></a>
183)     <h3><a class="anchor" href="#CompatibleApplications">What programs can
184)     I use with Tor?</a></h3>

185) 

186)     <p>
187)     There are two pieces to "Torifying" a program: connection-level anonymity
188)     and application-level anonymity. Connection-level anonymity focuses on
189)     making sure the application's Internet connections get sent through Tor.
190)     This step is normally done by configuring
191)     the program to use your Tor client as a "socks" proxy, but there are
192)     other ways to do it too. For application-level anonymity, you need to
193)     make sure that the information the application sends out doesn't hurt
194)     your privacy. (Even if the connections are being routed through Tor, you
195)     still don't want to include sensitive information like your name.) This
196)     second step needs to be done on a program-by-program basis, which is
197)     why we don't yet recommend very many programs for safe use with Tor.
198)     </p>

199) 

200)     <p>
201)     Most of our work so far has focused on the Firefox web browser. The
202)     bundles on the <a href="<page download/download>">download page</a> automatically

203)     install the <a href="<page torbutton/index>">Torbutton Firefox

204)     extension</a> if you have Firefox installed. As of version 1.2.0,
205)     Torbutton now takes care of a lot of the connection-level and
206)     application-level worries.
207)     </p>

208) 

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

214)     href="<wiki>TheOnionRouter/TorifyHOWTO">Torifying

215)     specific applications</a>. There's also a <a

216)     href="<wiki>TheOnionRouter/SupportPrograms">list

217)     of applications that help you direct your traffic through Tor</a>.
218)     Please add to these lists and help us keep them accurate!
219)     </p>

220) 

221)     <hr>

222) 

223)     <a id="WhyCalledTor"></a>
224)     <h3><a class="anchor" href="#WhyCalledTor">Why is it called Tor?</a></h3>

225) 

226)     <p>
227)     Because Tor is the onion routing network. When we were starting the
228)     new next-generation design and implementation of onion routing in
229)     2001-2002, we would tell people we were working on onion routing,
230)     and they would say "Neat. Which one?" Even if onion routing has
231)     become a standard household term, Tor was born out of the actual <a
232)     href="http://www.onion-router.net/">onion routing project</a> run by
233)     the Naval Research Lab.
234)     </p>

235) 

236)     <p>
237)     (It's also got a fine translation from German and Turkish.)
238)     </p>

239) 

240)     <p>
241)     Note: even though it originally came from an acronym, Tor is not spelled
242)     "TOR". Only the first letter is capitalized. In fact, we can usually
243)     spot people who haven't read any of our website (and have instead learned
244)     everything they know about Tor from news articles) by the fact that they
245)     spell it wrong.
246)     </p>

247) 

248)     <hr>

249) 

250)     <a id="Backdoor"></a>
251)     <h3><a class="anchor" href="#Backdoor">Is there a backdoor in Tor?</a></h3>

252) 

253)     <p>
254)     There is absolutely no backdoor in Tor. Nobody has asked us to put one
255)     in, and we know some smart lawyers who say that it's unlikely that anybody
256)     will try to make us add one in our jurisdiction (U.S.). If they do
257)     ask us, we will fight them, and (the lawyers say) probably win.
258)     </p>

259) 

260)     <p>
261)     We think that putting a backdoor in Tor would be tremendously
262)     irresponsible to our users, and a bad precedent for security software
263)     in general. If we ever put a deliberate backdoor in our security
264)     software, it would ruin our professional reputations. Nobody would
265)     trust our software ever again &mdash; for excellent reason!
266)     </p>

267) 

268)     <p>
269)     But that said, there are still plenty of subtle attacks
270)     people might try. Somebody might impersonate us, or break into our
271)     computers, or something like that. Tor is open source, and you should
272)     always check the source (or at least the diffs since the last release)
273)     for suspicious things. If we (or the distributors) don't give you
274)     source, that's a sure sign something funny might be going on. You
275)     should also check the <a href="<page docs/verifying-signatures>">PGP
276)     signatures</a> on the releases, to make sure nobody messed with the
277)     distribution sites.
278)     </p>

279) 

280)     <p>
281)     Also, there might be accidental bugs in Tor that could affect your
282)     anonymity. We periodically find and fix anonymity-related bugs, so make
283)     sure you keep your Tor versions up-to-date.
284)     </p>

285) 

286)     <hr>

287) 

288)     <a id="DistributingTor"></a>
289)     <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor on
290)     my magazine's CD?</a></h3>

291) 

292)     <p>
293)     Yes.
294)     </p>

295) 

296)     <p>
297)     The Tor software is <a href="https://www.fsf.org/">free software</a>. This
298)     means we give you the rights to redistribute the Tor software, either
299)     modified or unmodified, either for a fee or gratis. You don't have to
300)     ask us for specific permission.
301)     </p>

302) 

303)     <p>
304)     However, if you want to redistribute the Tor software you must follow our
305)     <a href="<gitblob>LICENSE">LICENSE</a>.
306)     Essentially this means that you need to include our LICENSE file along
307)     with whatever part of the Tor software you're distributing.
308)     </p>

309) 

310)     <p>
311)     Most people who ask us this question don't want to distribute just the
312)     Tor software, though. They want to distribute the Tor bundles, which
313)     typically include <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
314)     and <a href="<page projects/vidalia>">Vidalia</a>.
315)     You will need to follow the licenses for those programs
316)     as well. Both of them are distributed under the <a
317)     href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General
318)     Public License</a>. The simplest way to obey their licenses is to
319)     include the source code for these programs everywhere you include
320)     the bundles themselves. Look for "source" packages on the <a
321)     href="<page projects/vidalia>">Vidalia page</a> and the <a
322)     href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo
323)     download page</a>.
324)     </p>

325) 

326)     <p>
327)     Also, you should make sure not to confuse your readers about what Tor is,
328)     who makes it, and what properties it provides (and doesn't provide). See
329)     our <a href="<page docs/trademark-faq>">trademark FAQ</a> for details.
330)     </p>

331) 

332)     <p>
333)     Lastly, you should realize that we release new versions of the
334)     Tor software frequently, and sometimes we make backward incompatible
335)     changes. So if you distribute a particular version of the Tor software, it
336)     may not be supported &mdash; or even work &mdash; six months later. This
337)     is a fact of life for all security software under heavy development.
338)     </p>

339) 

340)     <hr>

341) 

342)     <a id="SupportMail"></a>
343)     <h3><a class="anchor" href="#SupportMail">How can I get an answer to my
344)     Tor support mail?</a></h3>

345) 

346)     <p>There is no official support for Tor. Your best bet is to try the following:</p>

347)     <ol>
348)     <li>Read through this <a href="<page docs/faq>">FAQ</a>.</li>
349)     <li>Read through the <a href="<page docs/documentation>">documentation</a>.</li>
350)     <li>Read through the <a
351)     href="http://archives.seul.org/or/talk">OR-TALK Archives</a> and
352)     see if your question is already answered.</li>
353)     <li>Join our <a href="irc://irc.oftc.net#tor">irc channel</a> and
354)     state the issue and wait for help.</li>
355)     <li>Send an email to tor-assistants at torproject.org. These are
356)     volunteers who may be able to help you but you may not get a response
357)     for days.</li>
358)     </ol>

359) 

360)     <p>If you find your answer, please stick around on the IRC channel or the
361)     mailing list and answer questions from others.</p>

362) 

363)     <hr>

364) 

365)     <a id="WhySlow"></a>
366)     <h3><a class="anchor" href="#WhySlow">Why is Tor so slow?</a></h3>

367) 

368)     <p>
369)     There are many reasons why the Tor network is currently slow.
370)     </p>

371) 

372)     <p>
373)     Before we answer, though, you should realize that Tor is never going to
374)     be blazing fast. Your traffic is bouncing through volunteers' computers
375)     in various parts of the world, and some bottlenecks and network latency
376)     will always be present. You shouldn't expect to see university-style
377)     bandwidth through Tor.
378)     </p>

379) 

380)     <p>
381)     But that doesn't mean that it can't be improved. The current Tor network
382)     is quite small compared to the number of people trying to use it, and
383)     many of these users don't understand or care that Tor can't currently
384)     handle file-sharing traffic load.
385)     </p>

386) 

387)     <p>
388)     For the much more in-depth answer, see <a

389)     href="<blog>why-tor-is-slow">Roger's blog

390)     post on the topic</a>, which includes both a detailed PDF and a video
391)     to go with it.
392)     </p>

393) 

394)     <p>
395)     What can you do to help?
396)     </p>

397) 

398)     <ul>

399) 

400)     <li>
401)     <a href="<page docs/tor-doc-relay>">Configure your Tor to relay traffic
402)     for others</a>. Help make the Tor network large enough that we can handle
403)     all the users who want privacy and security on the Internet.
404)     </li>

405) 

406)     <li>

407)     <a href="<page projects/vidalia>">Help us make Tor more usable</a>. We

408)     especially need people to help make it easier to configure your Tor
409)     as a relay. Also, we need help with clear simple documentation to
410)     walk people through setting it up.
411)     </li>

412) 

413)     <li>
414)     There are some bottlenecks in the current Tor network. Help us design
415)     experiments to track down and demonstrate where the problems are, and
416)     then we can focus better on fixing them.
417)     </li>

418) 

419)     <li>
420)     There are some steps that individuals
421)     can take to improve their Tor performance. <a

422)     href="<wiki>TheOnionRouter/FireFoxTorPerf">You

423)     can configure your Firefox to handle Tor better</a>, <a
424)     href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
425)     Polipo with Tor</a>, or you can try <a href="<page download/download>">upgrading
426)     to the latest version of Tor</a>.  If this works well, please help by
427)     documenting what you did, and letting us know about it.
428)     </li>

429) 

430)     <li>
431)     Tor needs some architectural changes too. One important change is to
432)     start providing <a href="#EverybodyARelay">better service to people who
433)     relay traffic</a>. We're working on this, and we'll finish faster if we
434)     get to spend more time on it.
435)     </li>

436) 

437)     <li>
438)     Help do other things so we can do the hard stuff. Please take a moment
439)     to figure out what your skills and interests are, and then <a href="<page
440)     getinvolved/volunteer>">look at our volunteer page</a>.
441)     </li>

442) 

443)     <li>
444)     Help find sponsors for Tor. Do you work at a company or government agency
445)     that uses Tor or has a use for Internet privacy, e.g. to browse the
446)     competition's websites discreetly, or to connect back to the home servers
447)     when on the road without revealing affiliations? If your organization has
448)     an interest in keeping the Tor network working, please contact them about
449)     supporting Tor. Without sponsors, Tor is going to become even slower.
450)     </li>

451) 

452)     <li>
453)     If you can't help out with any of the above, you can still help out
454)     individually by <a href="<page donate/donate>">donating a bit of money to the
455)     cause</a>. It adds up!
456)     </li>

457) 

458)     </ul>

459) 

460)     <hr>

461) 

462)     <a id="Funding"></a>
463)     <h3><a class="anchor" href="#Funding">What would The Tor Project do with
464)     more funding?</a></h3>

465) 

466)     <p>
467)     We have about 1800 relays right now, pushing over 150 MB/s average
468)     traffic. We have several hundred thousand active users. But the Tor
469)     network is not yet self-sustaining.
470)     </p>

471) 

472)     <p>
473)     There are six main development/maintenance pushes that need attention:
474)     </p>

475) 

476)     <ul>

477) 

478)     <li>
479)     Scalability: We need to keep scaling and decentralizing the Tor
480)     architecture so it can handle thousands of relays and millions of
481)     users. The upcoming stable release is a major improvement, but there's
482)     lots more to be done next in terms of keeping Tor fast and stable.
483)     </li>

484) 

485)     <li>
486)     User support: With this many users, a lot of people are asking questions
487)     all the time, offering to help out with things, and so on. We need good
488)     clean docs, and we need to spend some effort coordinating volunteers.
489)     </li>

490) 

491)     <li>
492)     Relay support: the Tor network is run by volunteers, but they still need
493)     attention with prompt bug fixes, explanations when things go wrong,
494)     reminders to upgrade, and so on. The network itself is a commons, and
495)     somebody needs to spend some energy making sure the relay operators stay
496)     happy. We also need to work on <a href="#RelayOS">stability</a> on some
497)     platforms &mdash; e.g., Tor relays have problems on Win XP currently.
498)     </li>

499) 

500)     <li>
501)     Usability: Beyond documentation, we also need to work on usability of the
502)     software itself. This includes installers, clean GUIs, easy configuration
503)     to interface with other applications, and generally automating all of
504)     the difficult and confusing steps inside Tor. We've got a start on this

505)     with the <a href="<page projects/vidalia>">Vidalia GUI</a>, but much more work

506)     remains — usability for privacy software has never been easy.
507)     </li>

508) 

509)     <li>
510)     Incentives: We need to work on ways to encourage people to configure
511)     their Tors as relays and exit nodes rather than just clients.
512)     <a href="#EverybodyARelay">We need to make it easy to become a relay,
513)     and we need to give people incentives to do it.</a>
514)     </li>

515) 

516)     <li>
517)     Research: The anonymous communications field is full
518)     of surprises and gotchas. In our copious free time, we
519)     also help run top anonymity and privacy conferences like <a
520)     href="http://petsymposium.org/">PETS</a>. We've identified a set of
521)     critical <a href="<page getinvolved/volunteer>#Research">Tor research questions</a>
522)     that will help us figure out how to make Tor secure against the variety of
523)     attacks out there. Of course, there are more research questions waiting
524)     behind these.
525)     </li>

526) 

527)     </ul>

528) 

529)     <p>
530)     We're continuing to move forward on all of these, but at this rate
531)     <a href="#WhySlow">the Tor network is growing faster than the developers
532)     can keep up</a>.
533)     Now would be an excellent time to add a few more developers to the effort
534)     so we can continue to grow the network.
535)     </p>

536) 

537)     <p>
538)     We are also excited about tackling related problems, such as
539)     censorship-resistance.
540)     </p>

541) 

542)     <p>
543)     We are proud to have <a href="<page about/sponsors>">sponsorship and support</a>
544)     from the Omidyar Network, the International Broadcasting Bureau, Bell
545)     Security Solutions, the Electronic Frontier Foundation, several government
546)     agencies and research groups, and hundreds of private contributors.
547)     </p>

548) 

549)     <p>
550)     However, this support is not enough to keep Tor abreast of changes in the
551)     Internet privacy landscape. Please <a href="<page donate/donate>">donate</a>
552)     to the project, or <a href="<page about/contact>">contact</a> our executive
553)     director for information on making grants or major donations.
554)     </p>

555) 

556)     <a id="Metrics"></a>

557)     <h3><a class="anchor" href="#Metrics">How many people use Tor?
558)     How many relays or exit nodes are there?</a></h3>

559) 

560)     <p>All this and more about measuring Tor can be found at the <a

561)     href="https://metrics.torproject.org/">Tor Metrics Portal</a>.</p>

562)     <hr>

563) 

564)     <a id="HowUninstallTor"></a>

565)     <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall
566)     Tor?</a></h3>
567) 

568)     <p>
569)     This depends entirely on how you installed it and which operating system you
570)     have. If you installed a package, then hopefully your package has a way to
571)     uninstall itself. The Windows packages include uninstallers. The proper way to
572)     completely remove Tor, Vidalia, Torbutton for Firefox, and Polipo on any
573)     version of Windows is as follows:
574)     </p>

575) 

576)     <ol>
577)     <li>In your taskbar, right click on Vidalia (the green onion or the black head)
578)     and choose exit.</li>
579)     <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
580)     Process List. If it's running, right click and choose End Process.</li>
581)     <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
582)     This will remove the Vidalia bundle, which includes Tor and Polipo.</li>
583)     <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
584)     Click the Uninstall button.</li>
585)     </ol>

586) 

587)     <p>
588)     If you do not follow these steps (for example by trying to uninstall
589)     Vidalia, Tor, and Polipo while they are still running), you will need to
590)     reboot and manually remove the directory "Program Files\Vidalia Bundle".
591)     </p>

592) 

593)     <p>
594)     For Mac OS X, follow the <a
595)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
596)     </p>

597) 

598)     <p>
599)     If you installed by source, I'm afraid there is no easy uninstall method. But
600)     on the bright side, by default it only installs into /usr/local/ and it should
601)     be pretty easy to notice things there.
602)     </p>

603) 

604)     <hr>

605) 

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

609) 

610)     <p>
611)     These are PGP signatures, so you can verify that the file you've downloaded is
612)     exactly the one that we intended you to get.
613)     </p>

614) 

615)     <p>
616)     Please read the <a
617)     href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
618)     </p>

619) 

620)     <hr>

621) 

622)     <a id="CompileTorWindows"></a>
623)     <h3><a class="anchor" href="#CompileTorWindows">How do I compile Tor under
624)     Windows?</a></h3>

625) 

626)     <p>
627)     Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
628)     tor-win32-mingw-creation.txt</a>.
629)     </p>

630) 

631)     <p>
632)     (Note that you don't need to compile Tor yourself in order to use
633)     it. Most people just use the packages available on the <a href="<page
634)     download/download>">download page</a>.)
635)     </p>

636) 

637)     <hr>

638) 

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

642) 

643)     <p>
644)     Sometimes, overzealous Windows virus and spyware detectors trigger on some
645)     parts of the Tor Windows binary. Our best guess is that these are false
646)     positives &mdash; after all, the anti-virus and anti-spyware business is just a
647)     guessing game anyway. You should contact your vendor and explain that you have
648)     a program that seems to be triggering false positives. Or pick a better vendor.
649)     </p>

650) 

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

656) 

657)     <hr>

658) 

659)     <a id="LiveCD"></a>
660)     <h3><a class="anchor" href="#LiveCD">Is there a LiveCD or other bundle that
661)     includes Tor?</a></h3>

662) 

663)     <p>
664)     There isn't any official LiveCD at this point. We're still trying to find good
665)     solutions and trying to understand the security and anonymity implications of
666)     the various options. In the mean time, feel free to check out the list below
667)     and use your best judgement:
668)     </p>

669) 

670)     <p>
671)     LiveCDs:
672)     </p>

673) 

674)     <ol>
675)     <li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
676)     System</a> is a Live System aimed at preserving your privacy and
677)     anonymity:
678)     <ul>
679)     <li> All outgoing connections to the Internet are forced to go through
680)     the Tor network.</li>
681)     <li> No trace is left on local storage devices unless explicitely asked.</li>
682)     <li> It includes Firefox, Tor, Torbutton, Vidalia graphical Tor
683)     controller, Pidgin Instant Messaging client, and lots of other
684)     software.</li>
685)     <li> It's based upon Debian gnu/linux and comes with the GNOME desktop
686)     environment.</li>
687)     </ul>
688)     <li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
689)     is Knoppix-based with an emphasis on user-friendliness. You can work
690)     anonymously or non-anonymously while TorK tries to keep you informed of the
691)     consequences of your activity. The TorK LiveCD is experimental, so the aim is
692)     to provide regular releases through 2007 and beyond.</li>
693)     <li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> is a
694)     debian based live-system including tor, firefox and torbutton which can save
695)     bookmarks and other settings or data on an encrypted usb-key</li>
696)     </li>
697)     </ol>

698) 

699)     <p>
700)     Windows bundles:
701)     </p>

702) 

703)     <ol>
704)     <li><a href="<page projects/torbrowser>">Tor Browser Bundle</a>
705)     for Windows comes with a pre-configured web browser and is self contained
706)     so you can run it from a USB stick.</li>
707)     <li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> is a successor
708)     to JanusVM. It needs testing from you!</li>
709)     <li><a href="http://janusvm.com/">JanusVM</a> is a Linux kernel and software
710)     running in VMWare that sits between your Windows computer and the Internet,
711)     making sure that your Internet traffic is scrubbed and anonymized.</li>
712)     <li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>,
713)     previously known as Torpark, is a Firefox+Tor package for Win32 that can
714)     installed on a USB key. It needs a host Win32 operating system.</li>
715)     </ol>

716) 

717)     <p>
718)     Not currently maintained as far as we know:
719)     </p>

720) 

721)     <ol>
722)     <li>Polippix / Privatlivets Fred is a Danish Knoppix-based LiveCD with Tor
723)     and utilities to encrypt IP-telephony. <a href="http://polippix.org/">Info and
724)     download</a>.</li>
725)     <li>ELE is a Linux LiveCD which is focused on privacy related
726)     software. It includes Tor and you can download it at
727)     <a
728)     href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
729)     <li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
730)     Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
731)     non-Tor traffic from accidentally leaving your computer. More information at

732)     <a href="<wiki>VirtualPrivacyMachine"><wiki>VirtualPrivacyMachine</a>.</li>

733)     <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
734)     than Linux for maximum security. It was designed to be anonymous and secure
735)     from the ground up, and thus has some features and limitations not found in
736)     other LiveCDs (Tor related or otherwise). You can obtain more information and
737)     download Anonym.OS from <a href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
738)     <li>Phantomix is a LiveCD for anonymous surfing and chatting based on the most
739)     recent KNOPPIX release. It comes preconfigured with Privoxy, Tor and Polipo. You can
740)     get it from the <a href="http://phantomix.ytternhagen.de/">Phantomix
741)     Website</a>.</li>
742)     </ol>

743) 

744)     <p>
745)     Please contact us if you know any others.
746)     </p>

747) 
748) <hr>
749) 
750) <a id="DoesntWork"></a>
751) <h3><a class="anchor" href="#DoesntWork">I installed Tor and Polipo but
752) it's not working.</a></h3>
753) 
754) <p>
755) Once you've installed the Tor bundle, there are two questions to ask:
756) first, is your Tor able to establish a circuit? Second, is your
757) Firefox correctly configured to send its traffic through Tor?
758) </p>
759) 
760) <p>If Tor can establish a circuit, the onion icon in
761) Vidalia will turn green. You can also check in the Vidalia
762) Control Panel to make sure it says "Connected to the Tor
763) network!" under Status. For those not using Vidalia, check your <a

764) href="<wikifaq>#HowdoIsetuploggingorseeTorslogs">Tor logs</a> for

765) a line saying that Tor "has successfully opened a circuit. Looks like
766) client functionality is working."
767) </p>
768) 
769) <p>
770) If Tor can't establish a circuit, here are some hints:
771) </p>
772) 
773) <ol>
774) <li>Are you sure Tor is running? If you're using Vidalia, you may have
775) to click on the onion and select "Start" to launch Tor.</li>
776) <li>Check your system clock. If it's more than a few hours off, Tor will
777) refuse to build circuits. For XP users, synchronize your clock under
778) the clock -&gt; Internet time tab. In addition, correct the day and date
779) under the 'Date &amp; Time' Tab.</li>
780) <li>Is your Internet connection <a

781) href="#FirewallPorts">firewalled by port</a>,

782) or do you normally need to use a <a

783) href="<wikifaq>#MyInternetconnectionrequiresanHTTPorSOCKSproxy.">proxy</a>?

784) </li>
785) <li>Are you running programs like Norton Internet Security or SELinux that
786) block certain connections, even though you don't realize they do? They
787) could be preventing Tor from making network connections.</li>
788) <li>Are you in China, or behind a restrictive corporate network firewall
789) that blocks the public Tor relays? If so, you should learn about <a

790) href="<page docs/bridges>">Tor bridges</a>.</li>
791) <li>Check your <a href="<wikifaq>#HowdoIsetuploggingorseeTorslogs">Tor

792) logs</a>. Do they give you any hints about what's going wrong?</li>
793) </ol>
794) 
795) <p>
796) Step two is to confirm that Firefox is correctly configured to send its
797) traffic through Tor. Try the <a href="https://check.torproject.org/">Tor
798) Check</a> site and see whether it thinks you are using Tor. See <a

799) href="<wikifaq>#HowcanItellifTorisworkingandthatmyconnectionsreallyareanonymizedArethereexternalserversthatwilltestmyconnection">the

800) Tor Check FAQ entry</a> for details.

801) </p>

802) 
803) <p>
804) If it thinks you're not using Tor, here are some hints:
805) </p>
806) 
807) <ol>
808) <li>Did you install the Torbutton extension for Firefox? The installation
809) bundles include it, but sometimes people forget to install it. Make sure
810) it says "Tor enabled" at the bottom right of your Firefox window. (For
811) expert users, make sure your http proxy is set to localhost port
812) 8118.)</li>
813) <li>Do you have incompatible Firefox extensions like FoxyProxy
814) installed? If so, uninstall them. (Note that using FoxyProxy is NOT
815) a sufficient substitute for Torbutton. There are many known attacks
816) against a browser setup that does not include Torbutton. Read more

817) in the <a href="<page torbutton/torbutton-faq>">Torbutton FAQ</a> and the <a

818) href="https://www.torproject.org/torbutton/design/">Torbutton design</a>
819) specification.)</li>
820) <li>If your browser says "The proxy server is refusing connections.",
821) check that Polipo (the http proxy that passes traffic between Firefox
822) and Tor) is running. On Windows, look in the task manager and check for
823) a polipo.exe. On OS X, open the utilities folder in your applications
824) folder, and open Terminal.app. Then run "ps aux|grep polipo".</li>
825) <li>If you're upgrading from OS X, some of the earlier OS X installers
826) were broken in really unfortunate ways. You may find that <a href="<page
827) docs/tor-doc-osx>#uninstall">uninstalling everything</a> and then
828) installing a fresh bundle helps. Alas, the current uninstall instructions
829) may not apply anymore to your old bundle. Sorry.</li>
830) <li>If you're on Linux, make sure Privoxy isn't running, since it will
831) conflict with the port that our Polipo configuration file picks.</li>
832) <li>If you installed Polipo yourself (not from a bundle), did you edit the

833) config file as described? Did you restart Polipo after this change? Are
834) you sure?</li>

835) <li>For Red Hat Linux and related systems, do you have SELinux enabled? If
836) so, it might be preventing Polipo from talking to Tor. We also run across
837) BSD users periodically who have local firewall rules that prevent some
838) connections to localhost.</li>
839) </ol>
840) 
841) <hr />
842) 
843) <a id="VidaliaPassword"></a>
844) <h3><a class="anchor" href="#VidaliaPassword">Tor/Vidalia prompts for
845) a password at start.</a></h3>
846) 
847) <p>
848) Vidalia interacts with the Tor software via Tor's "control port". The
849) control port lets Vidalia receive status updates from Tor, request a new
850) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
851) Vidalia sets a random password for Tor's control port to prevent other
852) applications from also connecting to the control port and potentially
853) compromising your anonymity.
854) </p>
855) 
856) <p>
857) Usually this process of generating and setting a random control password
858) happens in the background. There are three common situations, though,
859) where Vidalia may prompt you for a password:
860) </p>
861) 
862) <ol>
863) <li>You're already running Vidalia and Tor. For example, this situation
864) can happen if you installed the Vidalia bundle and now you're trying to
865) run the Tor Browser Bundle. In that case, you'll need to close the old
866) Vidalia and Tor before you can run this one.
867) </li>
868) <li>Vidalia crashed, but left Tor running with the last known random
869) password. After you restart Vidalia, it generates a new random password,
870) but Vidalia can't talk to Tor, because the random passwords are different.
871) <br />
872) If the dialog that prompts you for a control password has a Reset button,
873) you can click the button and Vidalia will restart Tor with a new random
874) control password.
875) <br />
876) If you do not see a Reset button, or if Vidalia is unable to restart
877) Tor for you, you can still fix the problem manually. Simply go into your
878) process or task manager, and terminate the Tor process. Then use Vidalia
879) to restart Tor and all will work again.
880) </li>
881) <li>You had previously set Tor to run as a Windows NT service. When Tor
882) is set to
883) run as a service, it starts up when the system boots. If you configured
884) Tor to start as a service through Vidalia, a random password was set
885) and saved in Tor. When you reboot, Tor starts up and uses the random
886) password it saved. You login and start up Vidalia. Vidalia attempts to
887) talk to the already running Tor. Vidalia generates a random password,
888) but it is different than the saved password in the Tor service.
889) <br />
890) You need to reconfigure Tor to not be a service. See the FAQ entry on

891) <a href="<wikifaq>#HowdoIrunmyTorrelayasanNTservice">running Tor as a Windows NT service</a>

892) for more information on how to remove the Tor service.
893) </li>
894) </ol>
895) 

896)     <hr>

897) 

898)     <a id="ChooseEntryExit"></a>
899)     <h3><a class="anchor" href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></h3>

900) 

901)     <p>

902)     Yes. You can set preferred entry and exit nodes as well as
903)     inform Tor which nodes you do not want to use.
904)     The following options can be added to your config file "torrc"

905)     or specified on the command line:
906)     </p>
907)     <dl>
908)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
909)         <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
910)         </dd>
911)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

912)         <dd>A list of preferred nodes to use for the last hop in the circuit, if possible.

913)         </dd>
914)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

915)         <dd>A list of nodes to never use when building a circuit.

916)         </dd>
917)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

918)         <dd>A list of nodes to never use when picking an exit.
919)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in this list.

920)         </dd>
921)     </dl>
922)     <p>

923)     <em>We recommend you do not use these</em>
924)     &mdash; they are intended for testing and may disappear in future versions.
925)     You get the best security that Tor can provide when you leave the
926)     route selection to Tor; overriding the entry / exit nodes can mess
927)     up your anonymity in ways we don't understand.

928)     </p>
929)     <p>

930)     The <tt>EntryNodes</tt> and <tt>ExitNodes</tt> config options are
931)     treated as a request, meaning if the nodes are down or seem slow,
932)     Tor will still avoid them. You can make the option mandatory by
933)     setting <tt>StrictExitNodes 1</tt> or <tt>StrictEntryNodes 1</tt>
934)     &mdash; but if you do, your Tor connections will stop working
935)     if all of the nodes you have specified become unreachable.
936)     See the <a href="<page docs/documentation>#NeatLinks">Tor status pages</a>

937)     for some nodes you might pick.
938)     </p>
939)     <p>

940)     Instead of <tt>$fingerprint</tt> you can also specify a 2 letter
941)     ISO3166 country code in curly braces (for example {de}), or an ip
942)     address pattern (for example 255.254.0.0/8), or a node nickname. Make
943)     sure there are no spaces between the commas and the list items.

944)     </p>
945)     <p>

946)     If you want to access a service directly through Tor's SOCKS interface
947)     (eg. using ssh via connect.c), another option is to set up an
948)     internal mapping in your configuration file using <tt>MapAddress</tt>.

949)     See the manual page for details.
950)     </p>

951) 

952)     <hr>

953) 
954) <a id="GoogleCaptcha"></a>
955) <h3><a class="anchor" href="#GoogleCaptcha">Google makes me solve a
956) Captcha or tells me I have spyware installed.</a></h3>
957) 
958) <p>
959) This is a known and intermittent problem; it does not mean that Google
960) considers Tor to be spyware.
961) </p>
962) 
963) <p>
964) When you use Tor, you are sending queries through exit relays that are also
965) shared by thousands of other users. Tor users typically see this message
966) when many Tor users are querying Google in a short period of time. Google
967) interprets the high volume of traffic from a single IP address (the exit
968) relay you happened to pick) as somebody trying to "crawl" their website,
969) so it slows down traffic from that IP address for a short time.
970) </p>
971) <p>
972) An alternate explanation is that Google tries to detect certain
973) kinds of spyware or viruses that send distinctive queries to Google
974) Search. It notes the IP addresses from which those queries are received
975) (not realizing that they are Tor exit relays), and tries to warn any
976) connections coming from those IP addresses that recent queries indicate
977) an infection.
978) </p>
979) 
980) <p>
981) To our knowledge, Google is not doing anything intentionally specifically
982) to deter or block Tor use. The error message about an infected machine
983) should clear up again after a short time.
984) </p>
985) 
986) <p>
987) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
988) automatically redirect you to a more Tor-friendly search engine such as
989) Ixquick or Bing.
990) </p>
991) 
992) <hr />
993) 
994) <a id="GmailWarning"></a>
995) <h3><a class="anchor" href="#GmailWarning">Gmail warns me that my account
996) may have been compromised.</a></h3>
997) 
998) <p>
999) Sometimes, after you've used Gmail over Tor, Google presents a

1000) pop-up notification that your account may have been compromised.
1001) The notification window lists a series of IP addresses and locations
1002) throughout the world recently used to access your account.

1003) </p>
1004) 
1005) <p>
1006) In general this is a false alarm: Google saw a bunch of logins from

1007) different places, as a result of running the service via Tor, and decided
1008) it was a good idea to confirm the account was being accessed by it's
1009) rightful owner.

1010) </p>
1011) 
1012) <p>

1013) Even though this may be a biproduct of using the service via tor,
1014) that doesn't mean you can entirely ignore the warning. It is
1015) <i>probably</i> a false positive, but it might not be since it is
1016) possible for someone to hijack your Google cookie.
1017) </p>
1018) 
1019) <p>
1020) Cookie hijacking is possible by either physical access to your computer
1021) or by watching your network traffic.  In theory only physical access
1022) should compromise your system because Gmail and similar services
1023) should only send the cookie over an SSL link. In practice, alas, it's <a
1024) href="http://fscked.org/blog/fully-automated-active-https-cookie-hijacking">
1025) way more complex than that</a>.

1026) </p>
1027) 
1028) <p>
1029) And if somebody <i>did</i> steal your google cookie, they might end
1030) up logging in from unusual places (though of course they also might
1031) not). So the summary is that since you're using Tor, this security
1032) measure that Google uses isn't so useful for you, because it's full of
1033) false positives. You'll have to use other approaches, like seeing if
1034) anything looks weird on the account, or looking at the timestamps for
1035) recent logins and wondering if you actually logged in at those times.
1036) </p>
1037) 

1038) <hr>
1039) 
1040) <a id="FirewallPorts"></a>
1041) <h3><a class="anchor" href="#FirewallPorts">My firewall only allows a
1042) few outgoing ports.</a></h3>
1043) 
1044) <p>
1045) If your firewall works by blocking ports, then you can tell Tor to only
1046) use the ports that your firewall permits by adding "FascistFirewall 1" to
1047) your <a href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
1048) configuration file</a>, or by clicking "My firewall only lets me connect
1049) to certain ports" in Vidalia's Network Settings window.
1050) </p>
1051) 
1052) <p>
1053) By default, when you set this Tor assumes that your firewall allows only
1054) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
1055) different set of ports with the FirewallPorts torrc option.
1056) </p>
1057) 
1058) <p>
1059) If you want to be more fine-grained with your controls, you can also
1060) use the ReachableAddresses config options, e.g.:
1061) </p>
1062) 
1063) <pre>
1064)   ReachableDirAddresses *:80
1065)   ReachableORAddresses *:443
1066) </pre>
1067) 
1068) <hr>

1069) 

1070)     <a id="RelayFlexible"></a>
1071)     <h3><a class="anchor" href="#RelayFlexible">How stable does my relay
1072)     need to be?</a></h3>

1073) 

1074)     <p>
1075)     We aim to make setting up a Tor relay easy and convenient:
1076)     </p>

1077) 

1078)     <ul>
1079)     <li>Tor has built-in support for <a

1080)     href="<wikifaq>#LimitBandwidth">

1081)     rate limiting</a>. Further, if you have a fast
1082)     link but want to limit the number of bytes per
1083)     day (or week or month) that you donate, check out the <a

1084)     href="<wikifaq>#Hibernation">hibernation

1085)     feature</a>.
1086)     </li>
1087)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
1088)     specifies what sort of outbound connections are allowed or refused from
1089)     that relay. If you are uncomfortable allowing people to exit from your
1090)     relay, you can set it up to only allow connections to other Tor relays.
1091)     </li>
1092)     <li>It's fine if the relay goes offline sometimes. The directories
1093)     notice this quickly and stop advertising the relay. Just try to make
1094)     sure it's not too often, since connections using the relay when it
1095)     disconnects will break.
1096)     </li>
1097)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
1098)     leave the Address config option blank, and Tor will try to guess.
1099)     </li>
1100)     <li>If your relay is behind a NAT and it doesn't know its public
1101)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

1102)     forwarding. Forwarding TCP connections is system dependent but
1103)     <a href="<wikifaq>#ServerForFirewalledClients">this FAQ entry</a>

1104)     offers some examples on how to do this.
1105)     </li>
1106)     <li>Your relay will passively estimate and advertise its recent
1107)     bandwidth capacity, so high-bandwidth relays will attract more users than
1108)     low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
1109)     </li>
1110)     </ul>

1111) 

1112)     <hr>

1113) 

1114)     <a id="RunARelayBut"></a>
1115)     <a id="ExitPolicies"></a>
1116)     <h3><a class="anchor" href="#ExitPolicies">I'd run a relay, but I don't
1117)     want to deal with abuse issues.</a></h3>

1118) 

1119)     <p>
1120)     Great. That's exactly why we implemented exit policies.
1121)     </p>

1122) 

1123)     <p>
1124)     Each Tor relay has an exit policy that specifies what sort of
1125)     outbound connections are allowed or refused from that relay. The exit
1126)     policies are propagated to Tor clients via the directory, so clients
1127)     will automatically avoid picking exit relays that would refuse to
1128)     exit to their intended destination. This way each relay can decide
1129)     the services, hosts, and networks he wants to allow connections to,

1130)     based on abuse potential and his own situation. Read the FAQ entry on
1131)     <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might encounter</a>
1132)     if you use the default exit policy, and then read Mike Perry's

1133)     <a href="<blog>tips-running-exit-node-minimal-harassment">tips

1134)     for running an exit node with minimal harassment</a>.
1135)     </p>

1136) 

1137)     <p>

1138)     The default exit policy allows access to many popular services
1139)     (e.g. web browsing), but <a href="<wikifaq>#DefaultPorts">restricts</a>

1140)     some due to abuse potential (e.g. mail) and some since
1141)     the Tor network can't handle the load (e.g. default
1142)     file-sharing ports). You can change your exit policy

1143)     using Vidalia's "Sharing" tab, or by manually editing your

1144)     <a href="<wikifaq>#torrc">torrc</a>

1145)     file. If you want to avoid most if not all abuse potential, set it to
1146)     "reject *:*" (or un-check all the boxes in Vidalia). This setting means
1147)     that your relay will be used for relaying traffic inside the Tor network,
1148)     but not for connections to external websites or other services.
1149)     </p>

1150) 

1151)     <p>
1152)     If you do allow any exit connections, make sure name resolution works
1153)     (that is, your computer can resolve Internet addresses correctly).
1154)     If there are any resources that your computer can't reach (for example,
1155)     you are behind a restrictive firewall or content filter), please
1156)     explicitly reject them in your exit policy &mdash; otherwise Tor users
1157)     will be impacted too.
1158)     </p>

1159) 

1160)     <hr>

1161) 

1162)     <a id="RelayOrBridge"></a>
1163)     <h3><a class="anchor" href="#RelayOrBridge">Should I be a normal relay
1164)     or bridge relay?</a></h3>

1165) 

1166)     <p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for short)
1167)     are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't listed
1168)     in the main Tor directory. That means
1169)     that even an ISP or government trying to filter connections to the Tor
1170)     network probably won't be able to block all the bridges.
1171)     </p>

1172) 

1173)     <p>Being a normal relay vs being a bridge relay is almost the same
1174)     configuration: it's just a matter of whether your relay is listed
1175)     publically or not.
1176)     </p>

1177) 

1178)     <p>Right now, there are a small number of places in the world that filter

1179)     connections to the Tor network. So getting a lot of bridges running
1180)     right now is mostly a backup measure, a) in case the Tor network does
1181)     get blocked somewhere, and b) for people who want an extra layer of
1182)     security because they're worried somebody will recognize that it's a
1183)     public Tor relay IP address they're contacting.
1184)     </p>

1185) 

1186)     <p>So should you run a normal relay or bridge relay? If you have
1187)     lots of bandwidth, you should definitely run a normal relay &mdash;

1188)     bridge relays see very little use these days. If you're willing to

1189)     <a href="#ExitPolicies">be an exit</a>, you should definitely run a normal
1190)     relay, since we need more exits. If you can't be an exit and only have
1191)     a little bit of bandwidth, then flip a coin. Thanks for volunteering!
1192)     </p>

1193) 

1194)     <hr>

1195) 

1196) <a id="ManyRelays"></a>
1197) <h3><a class="anchor" href="#ManyRelays">I want to run more than one
1198) relay.</a></h3>
1199) 
1200) <p>
1201) Great. If you want to run several relays to donate more to the network,
1202) we're happy with that. But please don't run more than a few dozen on
1203) the same network, since part of the goal of the Tor network is dispersal
1204) and diversity.
1205) </p>
1206) 
1207) <p>
1208) If you do decide to run more than one relay, please set the "MyFamily"
1209) config option in the torrc of each relay, listing all the relays
1210) (comma-separated) that are under your control:
1211) </p>
1212) 
1213) <pre>
1214)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
1215) </pre>
1216) 
1217) <p>
1218) where each fingerprint is the 40 character identity fingerprint (without
1219) spaces). You can also list them by nickname, but fingerprint is safer. Be
1220) sure to prefix the digest strings with a dollar sign ('$') so that the
1221) digest is not confused with a nickname in the config file.
1222) </p>
1223) 
1224) <p>
1225) That way clients will know to avoid using more than one of your relays
1226) in a single circuit. You should set MyFamily if you have administrative
1227) control of the computers or of their network, even if they're not all in
1228) the same geographic location.
1229) </p>
1230) 
1231)     <hr>
1232) 

1233)     <a id="RelayMemory"></a>
1234)     <h3><a class="anchor" href="#RelayMemory">Why is my Tor relay using so
1235)     much memory?</a></h3>

1236) 

1237)     <p>If your Tor relay is using more memory than you'd like, here are some
1238)     tips for reducing its footprint:
1239)     </p>

1240) 

1241)     <ol>
1242)     <li>If you're on Linux, you may be encountering memory fragmentation
1243)     bugs in glibc's malloc implementation. That is, when Tor releases memory
1244)     back to the system, the pieces of memory are fragmented so they're hard
1245)     to reuse. The Tor tarball ships with OpenBSD's malloc implementation,
1246)     which doesn't have as many fragmentation bugs (but the tradeoff is higher
1247)     CPU load). You can tell Tor to use this malloc implementation instead:
1248)     <tt>./configure --enable-openbsd-malloc</tt></li>

1249) 

1250)     <li>If you're running a fast relay, meaning you have many TLS connections
1251)     open, you are probably losing a lot of memory to OpenSSL's internal
1252)     buffers (38KB+ per socket). We've patched OpenSSL to <a
1253)     href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release
1254)     unused buffer memory more aggressively</a>. If you update to OpenSSL
1255)     1.0.0-beta5, Tor's build process will automatically recognize and use
1256)     this feature.</li>

1257) 

1258)     <li>If you're running on Solaris, OpenBSD, NetBSD, or
1259)     old FreeBSD, Tor is probably forking separate processes
1260)     rather than using threads. Consider switching to a <a

1261)     href="<wikifaq>#RelayOS">better

1262)     operating system</a>.</li>

1263) 

1264)     <li>If you still can't handle the memory load, consider reducing the
1265)     amount of bandwidth your relay advertises. Advertising less bandwidth
1266)     means you will attract fewer users, so your relay shouldn't grow
1267)     as large. See the <tt>MaxAdvertisedBandwidth</tt> option in the man
1268)     page.</li>

1269) 

1270)     </ol>

1271) 

1272)     <p>
1273)     All of this said, fast Tor relays do use a lot of ram. It is not unusual
1274)     for a fast exit relay to use 500-1000 MB of memory.
1275)     </p>

1276) 

1277)     <hr>

1278) 

1279)     <a id="WhyNotNamed"></a>

1280)     <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not
1281)     named?</a></h3>
1282) 

1283)     <p>

1284)     We currently use these metrics to determine if your relay should be named:<br>

1285)     </p>
1286)     <ul>
1287)     <li>The name is not currently mapped to a different key. Existing mappings
1288)     are removed after 6 months of inactivity from a relay.</li>
1289)     <li>The relay must have been around for at least two weeks.</li>
1290)     <li>No other router may have wanted the same name in the past month.</li>
1291)     </ul>

1292) 

1293)     <hr>

1294) 

1295)     <a id="KeyManagement"></a>
1296)     <h3><a class="anchor" href="#KeyManagement">Tell me about all the keys
1297)     Tor uses.</a></h3>

1298) 

1299)     <p>
1300)     Tor uses a variety of different keys, with three goals in mind: 1)
1301)     encryption to ensure privacy of data within the Tor network, 2)
1302)     authentication so clients know they're
1303)     talking to the relays they meant to talk to, and 3) signatures to make
1304)     sure all clients know the same set of relays.
1305)     </p>

1306) 

1307)     <p>
1308)     <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
1309)     so observers can't look inside to see which circuit a given cell is
1310)     intended for. Further, the Tor client establishes an ephemeral encryption
1311)     key with each relay in the circuit, so only the exit relay can read
1312)     the cells. Both sides discard the circuit key when the circuit ends,
1313)     so logging traffic and then breaking into the relay to discover the key
1314)     won't work.
1315)     </p>

1316) 

1317)     <p>
1318)     <b>Authentication</b>:
1319)     Every Tor relay has a public decryption key called the "onion key".
1320)     When the Tor client establishes circuits, at each step it <a
1321)     href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1322)     that the Tor relay prove knowledge of its onion key</a>. That way
1323)     the first node in the path can't just spoof the rest of the path.
1324)     Each relay rotates its onion key once a week.
1325)     </p>

1326) 

1327)     <p>
1328)     <b>Coordination</b>:
1329)     How do clients know what the relays are, and how do they know that they
1330)     have the right keys for them? Each relay has a long-term public signing
1331)     key called the "identity key". Each directory authority additionally has a
1332)     "directory signing key". The directory authorities <a
1333)     href="<gitblob>doc/spec/dir-spec.txt">provide a signed list</a>
1334)     of all the known relays, and in that list are a set of certificates from
1335)     each relay (self-signed by their identity key) specifying their keys,
1336)     locations, exit policies, and so on. So unless the adversary can control
1337)     a threshold of the directory authorities, he can't trick the Tor client
1338)     into using other Tor relays.
1339)     </p>

1340) 

1341)     <p>
1342)     How do clients know what the directory authorities are? The Tor software
1343)     comes with a built-in list of location and public key for each directory
1344)     authority. So the only way to trick users into using a fake Tor network
1345)     is to give them a specially modified version of the software.
1346)     </p>

1347) 

1348)     <p>
1349)     How do users know they've got the right software? When we distribute
1350)     the source code or a package, we digitally sign it with <a
1351)     href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1352)     href="<page docs/verifying-signatures>">instructions
1353)     on how to check Tor's signatures</a>.
1354)     </p>

1355) 

1356)     <p>
1357)     In order to be certain that it's really signed by us, you need to have
1358)     met us in person and gotten a copy of our GPG key fingerprint, or you
1359)     need to know somebody who has. If you're concerned about an attack on
1360)     this level, we recommend you get involved with the security community
1361)     and start meeting people.
1362)     </p>

1363) 

1364)     <hr>

1365) 

1366)     <a id="EverybodyARelay"></a>
1367)     <h3><a class="anchor" href="#EverybodyARelay">You should make every Tor
1368)     user be a relay.</a></h3>

1369) 

1370)     <p>
1371)     Requiring every Tor user to be a relay would help with scaling the

1372)     network to handle all our users, and <a href="<wikifaq>#RelayAnonymity">running a Tor

1373)     relay may help your anonymity</a>. However, many Tor users cannot be good
1374)     relays &mdash; for example, some Tor clients operate from behind restrictive
1375)     firewalls, connect via modem, or otherwise aren't in a position where they
1376)     can relay traffic. Providing service to these clients is a critical
1377)     part of providing effective anonymity for everyone, since many Tor users
1378)     are subject to these or similar constraints and including these clients
1379)     increases the size of the anonymity set.
1380)     </p>

1381) 

1382)     <p>
1383)     That said, we do want to encourage Tor users to run relays, so what we
1384)     really want to do is simplify the process of setting up and maintaining
1385)     a relay. We've made a lot of progress with easy configuration in the past
1386)     few years: Vidalia has an easy relay configuration interface, and supports
1387)     uPnP too. Tor is good at automatically detecting whether it's reachable and
1388)     how much bandwidth it can offer.
1389)     </p>

1390) 

1391)     <p>
1392)     There are five steps we need to address before we can do this though:
1393)     </p>

1394) 

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

1402) 

1403)     <p>
1404)     Second, we still need to get better at automatically estimating
1405)     the right amount of bandwidth to allow. See item #7 on the
1406)     <a href="<page getinvolved/volunteer>#Research">research section of the
1407)     volunteer page</a>: "Tor doesn't work very well when relays
1408)     have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a

1409)     href="<wikifaq>#TransportIPnotTCP">switching

1410)     to UDP transport</a> is the simplest answer here &mdash; which alas is
1411)     not a very simple answer at all.
1412)     </p>

1413) 

1414)     <p>
1415)     Third, we need to work on scalability, both of the network (how to
1416)     stop requiring that all Tor relays be able to connect to all Tor
1417)     relays) and of the directory (how to stop requiring that all Tor
1418)     users know about all Tor relays). Changes like this can have large
1419)     impact on potential and actual anonymity. See Section 5 of the <a
1420)     href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1421)     for details. Again, UDP transport would help here.
1422)     </p>

1423) 

1424)     <p>
1425)     Fourth, we need to better understand the risks from
1426)     letting the attacker send traffic through your relay while
1427)     you're also initiating your own anonymized traffic. <a
1428)     href="http://freehaven.net/anonbib/#back01">Three</a> <a
1429)     href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1430)     <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1431)     describe ways to identify the relays in a circuit by running traffic
1432)     through candidate relays and looking for dips in the traffic while the
1433)     circuit is active. These clogging attacks are not that scary in the Tor
1434)     context so long as relays are never clients too. But if we're trying to
1435)     encourage more clients to turn on relay functionality too (whether as
1436)     <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1437)     we need to understand this threat better and learn how to mitigate it.
1438)     </p>

1439) 

1440)     <p>
1441)     Fifth, we might need some sort of incentive scheme to encourage people
1442)     to relay traffic for others, and/or to become exit nodes. Here are our

1443)     <a href="<blog>two-incentive-designs-tor">current

1444)     thoughts on Tor incentives</a>.
1445)     </p>

1446) 

1447)     <p>
1448)     Please help on all of these!
1449)     </p>

1450) 

1451)     <hr>

1452) 

1453)     <a id="Criminals"></a>

1454)     <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals
1455)     to do bad things?</a></h3>
1456) 

1457)     <p>
1458)     For the answer to this question and others, please see our <a
1459)     href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1460)     </p>

1461) 

1462)     <hr>

1463) 

1464)     <a id="RespondISP"></a>

1465)     <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP
1466)     about my exit relay?</a></h3>
1467) 

1468)     <p>
1469)     A collection of templates for successfully responding to ISPs is <a

1470)     href="<wiki>TheOnionRouter/TorAbuseTemplates">collected

1471)     here</a>.
1472)     </p>

1473) 

1474)     <hr>

1475) 

1476)   </div>
1477)   <!-- END MAINCOL -->
1478)   <div id = "sidecol">
1479) #include "side.wmi"
1480) #include "info.wmi"
1481)   </div>
1482)   <!-- END SIDECOL -->
1483) </div>
1484) <!-- END CONTENT -->