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 support?</a></li>

28)     <li><a href="#WhySlow">Why is Tor so slow?</a></li>
29)     <li><a href="#Funding">What would The Tor Project do with more
30)     funding?</a></li>

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

33)     <li><a href="#SSLcertfingerprint">What are your SSL certificate

34)     fingerprints?</a></li>

35)     </ul>

36) 

37)     <p>Compilation and Installation:</p>
38)     <ul>
39)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
40)     <li><a href="#PGPSigs">What are these "sig" files on the download
41)     page?</a></li>

42)     <li><a href="#GetTor">Your website is blocked in my country. How
43)     do I download Tor?</a></li>

44)     <li><a href="#CompileTorWindows">How do I compile Tor under Windows?</a></li>
45)     <li><a href="#VirusFalsePositives">Why does my Tor executable appear to
46)     have a virus or spyware?</a></li>
47)     <li><a href="#LiveCD">Is there a LiveCD or other bundle that includes Tor?</a></li>
48)     </ul>

49) 

50)     <p>Tor Browser Bundle:</p>
51)     <ul>

52) 

53)     <li><a href="#TBBFlash">Why can't I view videos on YouTube and other
54)     Flash-based sites?</a></li>

55)     <li><a href="#TBBSocksPort">I'm on OSX or Linux and I want to
56)     run another application through the Tor launched by Tor Browser

57)     Bundle. How do I predict my Socks port?</a></li>

58)     <li><a href="#TBBPolipo">I need an HTTP proxy. Where did Polipo
59)     go?</a></li>

60)     <li><a href="#TBBOtherExtensions">Can I install other Firefox
61)     extensions?</a></li>

62)     <li><a href="#TBBJavaScriptEnabled">Why is NoScript configured to allow JavaScript by default in the Tor Browser Bundle?  Isn't that unsafe?</a></li>
63)     <li><a href="#TBBCanIBlockJS">I'm an expert!  (No, really!)  Can I configure NoScript to block JavaScript by default?</a></li>

64)     <li><a href="#TBBOtherBrowser">I want to use Chrome/IE/Opera/etc
65)     with Tor.</a></li>
66)     <li><a href="#TBBCloseBrowser">I want to leave Tor Browser Bundle
67)     running but close the browser.</a></li>
68) 

69)     <li><a href="#GoogleCaptcha">Google makes me solve a Captcha or tells
70)     me I have spyware installed.</a></li>
71)     <li><a href="#GmailWarning">Gmail warns me that my account may have
72)     been compromised.</a></li>
73)     </ul>
74) 
75)     <p>Advanced Tor usage:</p>

76)     <ul>
77)     <li><a href="#torrc">I'm supposed to "edit my torrc". What does
78)     that mean?</a></li>

79)     <li><a href="#Logs">How do I set up logging, or see Tor's

80)     logs?</a></li>

81)     <li><a href="#DoesntWork">Tor is running, but it's not working
82)     correctly.</a></li>

83)     <li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at
84)     start.</a></li>
85)     <li><a href="#ChooseEntryExit">Can I control which nodes (or country)
86)     are used for entry/exit?</a></li>

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

89)     </ul>

90) 

91)     <p>Running a Tor relay:</p>
92)     <ul>
93)     <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
94)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
95)     with abuse issues.</a></li>
96)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
97)     relay?</a></li>

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

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

101)     <li><a href="#RelayDonations">Can I donate for a relay rather than
102)     run my own?</a></li>

103)     </ul>

104) 

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

106) 

107)     <p>Anonymity and Security:</p>
108)     <ul>
109)     <li><a href="#KeyManagement">Tell me about all the keys Tor uses.</a></li>

110)     <li><a href="#EntryGuards">What are Entry Guards?</a></li>

111)     </ul>

112) 

113)     <p>Alternate designs that we don't do (yet):</p>
114)     <ul>
115)     <li><a href="#EverybodyARelay">You should make every Tor user be a
116)     relay.</a></li>

117)     <li><a href="#TransportIPnotTCP">You should transport all IP packets,
118)     not just TCP packets.</a></li>

119)     <li><a href="#HideExits">You should hide the list of Tor relays,
120)     so people can't block the exits.</a></li>

121)     </ul>

122) 

123)     <p>Abuse:</p>

124)     <ul>
125)     <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
126)     <li><a href="#RespondISP">How do I respond to my ISP about my exit
127)     relay?</a></li>
128)     </ul>

129) 

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

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

132) 

133)     <hr>

134) 

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

136) 

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

139) 

140)     <p>
141)     The name "Tor" can refer to several different components.
142)     </p>

143) 

144)     <p>
145)     The Tor software is a program you can run on your computer that helps keep
146)     you safe on the Internet. Tor protects you by bouncing your communications
147)     around a distributed network of relays run by volunteers all around
148)     the world: it prevents somebody watching your Internet connection from
149)     learning what sites you visit, and it prevents the sites you visit
150)     from learning your physical location. This set of volunteer relays is
151)     called the Tor network. You can read more about how Tor works on the <a
152)     href="<page about/overview>">overview page</a>.
153)     </p>

154) 

155)     <p>
156)     The Tor Project is a non-profit (charity) organization that maintains
157)     and develops the Tor software.
158)     </p>

159) 

160)     <hr>

161) 

162)     <a id="Torisdifferent"></a>
163)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
164)     <p>

165)     A typical proxy provider sets up a server somewhere on the Internet and
166) allows you to use it to relay your traffic.  This creates a simple, easy to
167) maintain architecture.  The users all enter and leave through the same server.
168) The provider may charge for use of the proxy, or fund their costs through
169) advertisements on the server.  In the simplest configuration, you don't have to
170) install anything.  You just have to point your browser at their proxy server.
171) Simple proxy providers are fine solutions if you do not want protections for
172) your privacy and anonymity online and you trust the provider from doing bad
173) things.  Some simple proxy providers use SSL to secure your connection to them.
174) This may protect you against local eavesdroppers, such as those at a cafe with
175) free wifi Internet.
176)     </p>
177)     <p>
178)     Simple proxy providers also create a single point of failure.  The provider
179) knows who you are and where you browse on the Internet.  They can see your

180) traffic as it passes through their server.  In some cases, they can even see
181) inside your

182) encrypted traffic as they relay it to your banking site or to ecommerce stores.
183) You have to trust the provider isn't doing any number of things, such as
184) watching your traffic, injecting their own advertisements into your traffic

185) stream, and recording your personal details.

186)     </p>
187)     <p>
188)     Tor passes your traffic through at least 3 different servers before sending

189) it on to the destination. Because there's a separate layer of encryption for
190) each of the three relays, Tor does not modify, or even know, what you are

191) sending into it.  It merely relays your traffic, completely encrypted through
192) the Tor network and has it pop out somewhere else in the world, completely
193) intact.  The Tor client is required because we assume you trust your local
194) computer.  The Tor client manages the encryption and the path chosen through
195) the network.  The relays located all over the world merely pass encrypted
196) packets between themselves.</p>

197)     <p>
198)     <dl>

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

212)     </dl>
213)     </p>

214) 

215)     <hr>

216) 

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

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

219) 

220)     <p>
221)     There are two pieces to "Torifying" a program: connection-level anonymity
222)     and application-level anonymity. Connection-level anonymity focuses on
223)     making sure the application's Internet connections get sent through Tor.
224)     This step is normally done by configuring
225)     the program to use your Tor client as a "socks" proxy, but there are
226)     other ways to do it too. For application-level anonymity, you need to
227)     make sure that the information the application sends out doesn't hurt
228)     your privacy. (Even if the connections are being routed through Tor, you
229)     still don't want to include sensitive information like your name.) This
230)     second step needs to be done on a program-by-program basis, which is
231)     why we don't yet recommend very many programs for safe use with Tor.
232)     </p>

233) 

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

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

238)     extension</a> if you have Firefox installed. As of version 1.2.0,
239)     Torbutton now takes care of a lot of the connection-level and
240)     application-level worries.
241)     </p>

242) 

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

248)     href="<wiki>doc/TorifyHOWTO">Torifying

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

250)     href="<wiki>doc/SupportPrograms">list

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

254) 

255)     <hr>

256) 

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

259) 

260)     <p>
261)     Because Tor is the onion routing network. When we were starting the
262)     new next-generation design and implementation of onion routing in
263)     2001-2002, we would tell people we were working on onion routing,
264)     and they would say "Neat. Which one?" Even if onion routing has
265)     become a standard household term, Tor was born out of the actual <a
266)     href="http://www.onion-router.net/">onion routing project</a> run by
267)     the Naval Research Lab.
268)     </p>

269) 

270)     <p>
271)     (It's also got a fine translation from German and Turkish.)
272)     </p>

273) 

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

281) 

282)     <hr>

283) 

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

286) 

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

293) 

294)     <p>
295)     We think that putting a backdoor in Tor would be tremendously
296)     irresponsible to our users, and a bad precedent for security software
297)     in general. If we ever put a deliberate backdoor in our security
298)     software, it would ruin our professional reputations. Nobody would
299)     trust our software ever again &mdash; for excellent reason!
300)     </p>

301) 

302)     <p>
303)     But that said, there are still plenty of subtle attacks
304)     people might try. Somebody might impersonate us, or break into our
305)     computers, or something like that. Tor is open source, and you should
306)     always check the source (or at least the diffs since the last release)
307)     for suspicious things. If we (or the distributors) don't give you
308)     source, that's a sure sign something funny might be going on. You
309)     should also check the <a href="<page docs/verifying-signatures>">PGP
310)     signatures</a> on the releases, to make sure nobody messed with the
311)     distribution sites.
312)     </p>

313) 

314)     <p>
315)     Also, there might be accidental bugs in Tor that could affect your
316)     anonymity. We periodically find and fix anonymity-related bugs, so make
317)     sure you keep your Tor versions up-to-date.
318)     </p>

319) 

320)     <hr>

321) 

322)     <a id="DistributingTor"></a>

323)     <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor?</a></h3>

324) 

325)     <p>
326)     Yes.
327)     </p>

328) 

329)     <p>
330)     The Tor software is <a href="https://www.fsf.org/">free software</a>. This
331)     means we give you the rights to redistribute the Tor software, either
332)     modified or unmodified, either for a fee or gratis. You don't have to
333)     ask us for specific permission.
334)     </p>

335) 

336)     <p>
337)     However, if you want to redistribute the Tor software you must follow our
338)     <a href="<gitblob>LICENSE">LICENSE</a>.
339)     Essentially this means that you need to include our LICENSE file along
340)     with whatever part of the Tor software you're distributing.
341)     </p>

342) 

343)     <p>
344)     Most people who ask us this question don't want to distribute just the

345)     Tor software, though. They want to distribute the <a
346)     href="https://www.torproject.org/projects/torbrowser.html.en">Tor
347)     Browser</a>. This includes <a
348)     href="https://www.mozilla.org/en-US/firefox/all-aurora.html">Mozilla
349)     Aurora</a> and <a href="<page projects/vidalia>">Vidalia</a>.

350)     You will need to follow the licenses for those programs
351)     as well. Both of them are distributed under the <a
352)     href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General

353)     Public License</a>. The simplest way to obey their licenses is
354)     to include the source code for these programs everywhere you
355)     include the bundles themselves. Look for "source" packages on
356)     the <a href="<page projects/vidalia>">Vidalia page</a> and <a
357)     href="https://www.mozilla.org/en-US/firefox/all-aurora.html">Mozilla
358)     Aurora</a> pages.

359)     </p>

360) 

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

366) 

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

374) 

375)     <hr>

376) 

377)     <a id="SupportMail"></a>

378)     <h3><a class="anchor" href="#SupportMail">How can I get support?</a></h3>

379) 

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

381)     <ol>
382)     <li>Read through this <a href="<page docs/faq>">FAQ</a>.</li>
383)     <li>Read through the <a href="<page docs/documentation>">documentation</a>.</li>
384)     <li>Read through the <a

385)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">tor-talk

386)     archives</a> and see if your question is already answered.</li>

387)     <li>Join our <a href="irc://irc.oftc.net#tor">irc channel</a> and
388)     state the issue and wait for help.</li>

389)     <li>Send an email to <a

390)     href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.

391)     These are volunteers who may be able to help you but you may not
392)     get a response for days.</li>

393)     </ol>

394) 

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

397) 

398)     <hr>

399) 

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

402) 

403)     <p>
404)     There are many reasons why the Tor network is currently slow.
405)     </p>

406) 

407)     <p>
408)     Before we answer, though, you should realize that Tor is never going to
409)     be blazing fast. Your traffic is bouncing through volunteers' computers
410)     in various parts of the world, and some bottlenecks and network latency
411)     will always be present. You shouldn't expect to see university-style
412)     bandwidth through Tor.
413)     </p>

414) 

415)     <p>
416)     But that doesn't mean that it can't be improved. The current Tor network
417)     is quite small compared to the number of people trying to use it, and
418)     many of these users don't understand or care that Tor can't currently
419)     handle file-sharing traffic load.
420)     </p>

421) 

422)     <p>
423)     For the much more in-depth answer, see <a

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

425)     post on the topic</a>, which includes both a detailed PDF and a video
426)     to go with it.
427)     </p>

428) 

429)     <p>
430)     What can you do to help?
431)     </p>

432) 

433)     <ul>

434) 

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

440) 

441)     <li>

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

443)     especially need people to help make it easier to configure your Tor
444)     as a relay. Also, we need help with clear simple documentation to
445)     walk people through setting it up.
446)     </li>

447) 

448)     <li>
449)     There are some bottlenecks in the current Tor network. Help us design
450)     experiments to track down and demonstrate where the problems are, and
451)     then we can focus better on fixing them.
452)     </li>

453) 

454)     <li>
455)     There are some steps that individuals
456)     can take to improve their Tor performance. <a

457)     href="<wiki>doc/FireFoxTorPerf">You

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

464) 

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

471) 

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

477) 

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

486) 

487)     <li>
488)     If you can't help out with any of the above, you can still help out
489)     individually by <a href="<page donate/donate>">donating a bit of money to the
490)     cause</a>. It adds up!
491)     </li>

492) 

493)     </ul>

494) 

495)     <hr>

496) 

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

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

499) 

500)     <p>

501)     The Tor network's <a
502)     href="https://metrics.torproject.org/network.html#networksize">several
503)     thousand</a> relays push <a
504)     href="https://metrics.torproject.org/network.html#bandwidth">over
505)     1GB per second on average</a>. We have <a
506)     href="https://metrics.torproject.org/users.html#direct-users">several
507)     hundred thousand daily users</a>. But the Tor network is not yet
508)     self-sustaining.

509)     </p>

510) 

511)     <p>
512)     There are six main development/maintenance pushes that need attention:
513)     </p>

514) 

515)     <ul>

516) 

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

523) 

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

529) 

530)     <li>
531)     Relay support: the Tor network is run by volunteers, but they still need
532)     attention with prompt bug fixes, explanations when things go wrong,
533)     reminders to upgrade, and so on. The network itself is a commons, and
534)     somebody needs to spend some energy making sure the relay operators stay

535)     happy. We also need to work on stability on some platforms — e.g.,
536)     Tor relays have problems on Win XP currently.

537)     </li>

538) 

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

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

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

547) 

548)     <li>
549)     Incentives: We need to work on ways to encourage people to configure
550)     their Tors as relays and exit nodes rather than just clients.
551)     <a href="#EverybodyARelay">We need to make it easy to become a relay,
552)     and we need to give people incentives to do it.</a>
553)     </li>

554) 

555)     <li>
556)     Research: The anonymous communications field is full
557)     of surprises and gotchas. In our copious free time, we
558)     also help run top anonymity and privacy conferences like <a
559)     href="http://petsymposium.org/">PETS</a>. We've identified a set of
560)     critical <a href="<page getinvolved/volunteer>#Research">Tor research questions</a>
561)     that will help us figure out how to make Tor secure against the variety of
562)     attacks out there. Of course, there are more research questions waiting
563)     behind these.
564)     </li>

565) 

566)     </ul>

567) 

568)     <p>
569)     We're continuing to move forward on all of these, but at this rate
570)     <a href="#WhySlow">the Tor network is growing faster than the developers
571)     can keep up</a>.
572)     Now would be an excellent time to add a few more developers to the effort
573)     so we can continue to grow the network.
574)     </p>

575) 

576)     <p>
577)     We are also excited about tackling related problems, such as
578)     censorship-resistance.
579)     </p>

580) 

581)     <p>
582)     We are proud to have <a href="<page about/sponsors>">sponsorship and support</a>
583)     from the Omidyar Network, the International Broadcasting Bureau, Bell
584)     Security Solutions, the Electronic Frontier Foundation, several government
585)     agencies and research groups, and hundreds of private contributors.
586)     </p>

587) 

588)     <p>
589)     However, this support is not enough to keep Tor abreast of changes in the
590)     Internet privacy landscape. Please <a href="<page donate/donate>">donate</a>
591)     to the project, or <a href="<page about/contact>">contact</a> our executive
592)     director for information on making grants or major donations.
593)     </p>

594) 

595)     <hr>
596) 

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

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

599) 

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

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

602)     <hr>

603) 

604)     <a id="SSLcertfingerprint"></a>
605)     <h3><a class="anchor" href="#SSLcertfingerprint">What are the SSL

606) certificate fingerprints for Tor's various websites?</a></h3>
607)     <p>

608)     <pre>

609)     *.torproject.org SSL certificate from Digicert:

610)     The serial number is: 02:DA:41:04:89:A5:FD:A2:B5:DB:DB:F8:ED:15:0D:BE
611)     The SHA-1 fingerprint is: a7e70f8a648fe04a9677f13eedf6f91b5f7f2e25
612)     The SHA-256 fingerprint is: 23b854af6b96co224fd173382c520b46fa94f2d4e7238893f63ad2d783e27b4b
613) 

614)     blog.torproject.org SSL certificate from RapidSSL:

615)     The serial number is: 00:EF:A3
616)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

617)     </pre>

618)     </p>
619)     <hr>
620) 

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

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

623) 

624)     <p>
625)     This depends entirely on how you installed it and which operating system you
626)     have. If you installed a package, then hopefully your package has a way to
627)     uninstall itself. The Windows packages include uninstallers. The proper way to
628)     completely remove Tor, Vidalia, Torbutton for Firefox, and Polipo on any
629)     version of Windows is as follows:
630)     </p>

631) 

632)     <ol>
633)     <li>In your taskbar, right click on Vidalia (the green onion or the black head)
634)     and choose exit.</li>
635)     <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
636)     Process List. If it's running, right click and choose End Process.</li>
637)     <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
638)     This will remove the Vidalia bundle, which includes Tor and Polipo.</li>
639)     <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
640)     Click the Uninstall button.</li>
641)     </ol>

642) 

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

648) 

649)     <p>
650)     For Mac OS X, follow the <a
651)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
652)     </p>

653) 

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

659) 

660)     <hr>

661) 

662)     <a id="PGPSigs"></a>

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

664) 

665)     <p>
666)     These are PGP signatures, so you can verify that the file you've downloaded is
667)     exactly the one that we intended you to get.
668)     </p>

669) 

670)     <p>
671)     Please read the <a
672)     href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
673)     </p>

674) 

675) <hr>
676) 
677) <a id="GetTor"></a>
678) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
679) country. How do I download Tor?</a></h3>
680) 
681) <p>
682) Some government or corporate firewalls censor connections to Tor's
683) website. In those cases, you have three options. First, get it from

684) a friend &mdash; the <a href="<page projects/torbrowser>">Tor Browser

685) Bundle</a> fits nicely on a USB key. Second, find the <a
686) href="https://encrypted.google.com/search?q=tor+mirrors">google cache</a>

687) for the <a href="<page getinvolved/mirrors>">Tor mirrors</a> page
688) and see if any of those copies of our website work for you. Third,
689) you can download Tor via email: log in to your Gmail account and mail
690) '<tt>gettor AT torproject.org</tt>'. If you include the word 'help'
691) in the body of the email, it will reply with instructions. Note that
692) only a few webmail providers are supported, since they need to be able
693) to receive very large attachments.
694) </p>
695) 
696) <p>

697) Be sure to <a href="<page docs/verifying-signatures>">verify the signature</a>

698) of any package you download, especially when you get it from somewhere
699) other than our official HTTPS website.

700) </p>
701) 
702) <hr>

703) 

704)     <a id="CompileTorWindows"></a>

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

706) 

707)     <p>
708)     Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
709)     tor-win32-mingw-creation.txt</a>.
710)     </p>

711) 

712)     <p>
713)     (Note that you don't need to compile Tor yourself in order to use
714)     it. Most people just use the packages available on the <a href="<page
715)     download/download>">download page</a>.)
716)     </p>

717) 

718)     <hr>

719) 

720)     <a id="VirusFalsePositives"></a>

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

722) 

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

730) 

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

736) 

737)     <hr>

738) 

739)     <a id="LiveCD"></a>

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

741) 

742)     <p>

743)     Yes.  Use <a href="https://tails.boum.org/">The Amnesic Incognito

744)     Live System</a> or <a href="<page projects/torbrowser>">the Tor Browser
745)     Bundle</a>.

746)     </p>

747) 
748) <hr>
749) 

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

751) <h3><a class="anchor" href="#TBBFlash">Why can't I view videos on YouTube
752) and other Flash-based sites?</a></h3>

753) 
754) <p>
755) <a href="https://www.torproject.org/torbutton/torbutton-faq.html.en#noflash">Answer</a>
756) </p>
757) 
758) <hr>
759) 

760) <a id="TBBSocksPort"></a>
761) <h3><a class="anchor" href="#TBBSocksPort">I'm on OSX or Linux and
762) I want to run another application through the Tor launched by Tor

763) Browser Bundle. How do I predict my Socks port?</a></h3>

764) 
765) <p>

766) Typically Tor listens for Socks connections on port 9050. TBB

767) on OSX and Linux has an experimental feature where Tor listens
768) on random unused ports rather than a fixed port each time. The
769) goal is to avoid conflicting with a "system" Tor install,
770) so you can run a system Tor and TBB at the same time. We're <a
771) href="https://trac.torproject.org/projects/tor/ticket/3948">working on
772) a feature</a> where Tor will try the usual ports first and then back
773) off to a random choice if they're already in use. Until then, if you

774) want to configure some other application to use Tor as a Socks proxy,

775) here's a workaround:
776) </p>
777) 
778) <p>
779) In Vidalia, go to Settings-&gt;Advanced and uncheck the box that says
780) 'Configure ControlPort automatically'. Click OK and restart TBB. Your

781) Socks port will then be on 9050.

782) </p>
783) 
784) <hr>
785) 
786) <a id="TBBPolipo"></a>
787) <h3><a class="anchor" href="#TBBPolipo">I need an HTTP proxy. Where did
788) Polipo go?</a></h3>
789) 
790) <p>
791) In the past, Tor bundles included an HTTP proxy like Privoxy or Polipo,
792) solely to work around a bug in Firefox that was finally fixed in Firefox
793) 6. Now you don't need a separate HTTP proxy to use Tor, and in fact
794) leaving it out makes you safer because Torbutton has better control over
795) Firefox's interaction with websites.
796) </p>
797) 
798) <p>
799) If you are trying to use some external application with Tor, step zero

800) should be to <a href="<page download/download>#warning">reread the set

801) of warnings</a> for ways you can screw up. Step one should be to try

802) to use a Socks proxy rather than an http proxy — Tor runs a Socks

803) proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>
804) for OSX and Linux.
805) </p>
806) 
807) <p>

808) If that fails, feel free to install <a
809) href="http://www.privoxy.org/">privoxy</a> or <a
810) href="https://archive.torproject.org/tor-package-archive/polipo/">polipo</a>.
811) You can use <a

812) href="https://gitweb.torproject.org/torbrowser.git/blob_plain/1ffcd9dafb9dd76c3a29dd686e05a71a95599fb5:/build-scripts/config/polipo.conf">our

813) old polipo config file</a> if you like. However, please realize that

814) this approach is not recommended for novice users.

815) </p>
816) 
817) <hr>
818) 

819) <a id="TBBOtherExtensions"></a>
820) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
821) Firefox extensions?</a></h3>
822) 
823) <p>
824) Yes. Just install them like normal. But be sure to avoid extensions like
825) Foxyproxy that screw up your proxy settings. Also, avoid privacy-invasive
826) extensions (for example, pretty much anything with the word Toolbar in
827) its name).
828) </p>
829) 
830) <hr>
831) 

832) <a id="TBBJavaScriptEnabled"></a>
833) <h3><a class="anchor" href="#TBBJavaScriptEnabled">Why is NoScript configured to allow JavaScript by default in the Tor Browser Bundle?  Isn't that unsafe?</a></h3>
834) 
835) <p>
836) We configure NoScript to allow JavaScript by default in the Tor
837) Browser Bundle because many websites will not work with JavaScript
838) disabled.  Most users would give up on Tor entirely if a website
839) they want to use requires JavaScript, because they would not know
840) how to allow a website to use JavaScript (or that enabling
841) JavaScript might make a website work).
842) </p>
843) 
844) <hr>
845) 
846) <a id="TBBCanIBlockJS"></a>
847) <h3><a class="anchor" href="#CanIBlockJS">I'm an expert!  (No, really!)  Can I configure NoScript to block JavaScript by default?</a></h3>
848) 
849) <p>
850) You can configure your copies of Tor Browser Bundle however you want
851) to.  However, we recommend that even users who know how to use
852) NoScript leave JavaScript enabled if possible, because a website or
853) exit node can easily distinguish users who disable JavaScript from
854) users who use Tor Browser bundle with its default settings (thus
855) users who disable JavaScript are less anonymous).
856) </p>
857) 
858) <p>
859) Disabling JavaScript by default, then allowing a few websites to run
860) scripts, is especially bad for your anonymity: the set of websites
861) which you allow to run scripts is very likely to <em>uniquely</em>
862) identify your browser.
863) </p>
864) 
865) <hr>
866) 

867) <a id="TBBOtherBrowser"></a>
868) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
869) Chrome/IE/Opera/etc with Tor.</a></h3>
870) 
871) <p>
872) Unfortunately, Torbutton only works with Firefox right now, and without
873) <a href="https://www.torproject.org/torbutton/en/design/">Torbutton's
874) extensive privacy fixes</a> there are many ways for websites or other
875) attackers to recognize you, track you back to your IP address, and so on.
876) In short, using any browser besides Tor Browser Bundle with Tor is a
877) really bad idea.
878) </p>
879) 
880) <p>
881) We're working with the Chrome team to <a
882) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">fix
883) some bugs and missing APIs in Chrome</a> so it will be possible to write a
884) Torbutton for Chrome. No support for any other browser is on the horizon.
885) </p>
886) 
887) <hr>
888) 
889) <a id="TBBCloseBrowser"></a>
890) <h3><a class="anchor" href="#TBBCloseBrowser">I want to leave Tor Browser
891) Bundle running but close the browser.</a></h3>
892) 
893) <p>
894) We're working on a way to make this possible on all platforms. Please
895) be patient.
896) </p>
897) 
898) <hr>
899) 

900) <a id="GoogleCaptcha"></a>
901) <h3><a class="anchor" href="#GoogleCaptcha">Google makes me solve a Captcha or tells me I have spyware installed.</a></h3>
902) 
903) <p>
904) This is a known and intermittent problem; it does not mean that Google
905) considers Tor to be spyware.
906) </p>
907) 
908) <p>
909) When you use Tor, you are sending queries through exit relays that are also
910) shared by thousands of other users. Tor users typically see this message
911) when many Tor users are querying Google in a short period of time. Google
912) interprets the high volume of traffic from a single IP address (the exit
913) relay you happened to pick) as somebody trying to "crawl" their website,
914) so it slows down traffic from that IP address for a short time.
915) </p>
916) <p>
917) An alternate explanation is that Google tries to detect certain
918) kinds of spyware or viruses that send distinctive queries to Google
919) Search. It notes the IP addresses from which those queries are received
920) (not realizing that they are Tor exit relays), and tries to warn any
921) connections coming from those IP addresses that recent queries indicate
922) an infection.
923) </p>
924) 
925) <p>
926) To our knowledge, Google is not doing anything intentionally specifically
927) to deter or block Tor use. The error message about an infected machine
928) should clear up again after a short time.
929) </p>
930) 
931) <p>
932) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
933) automatically redirect you to a more Tor-friendly search engine such as

934) DuckDuckGo, ixquick, or Bing.

935) </p>
936) 
937) <hr />
938) 
939) <a id="GmailWarning"></a>

940) <h3><a class="anchor" href="#GmailWarning">Gmail warns me that my account
941) may have been compromised.</a></h3>

942) 
943) <p>
944) Sometimes, after you've used Gmail over Tor, Google presents a
945) pop-up notification that your account may have been compromised.
946) The notification window lists a series of IP addresses and locations
947) throughout the world recently used to access your account.
948) </p>
949) 
950) <p>
951) In general this is a false alarm: Google saw a bunch of logins from
952) different places, as a result of running the service via Tor, and decided
953) it was a good idea to confirm the account was being accessed by it's
954) rightful owner.
955) </p>
956) 
957) <p>
958) Even though this may be a biproduct of using the service via tor,
959) that doesn't mean you can entirely ignore the warning. It is
960) <i>probably</i> a false positive, but it might not be since it is
961) possible for someone to hijack your Google cookie.
962) </p>
963) 
964) <p>
965) Cookie hijacking is possible by either physical access to your computer
966) or by watching your network traffic.  In theory only physical access
967) should compromise your system because Gmail and similar services
968) should only send the cookie over an SSL link. In practice, alas, it's <a
969) href="http://fscked.org/blog/fully-automated-active-https-cookie-hijacking">
970) way more complex than that</a>.
971) </p>
972) 
973) <p>
974) And if somebody <i>did</i> steal your google cookie, they might end
975) up logging in from unusual places (though of course they also might
976) not). So the summary is that since you're using Tor, this security
977) measure that Google uses isn't so useful for you, because it's full of
978) false positives. You'll have to use other approaches, like seeing if
979) anything looks weird on the account, or looking at the timestamps for
980) recent logins and wondering if you actually logged in at those times.
981) </p>
982) 
983) <hr>
984) 

985) <a id="torrc"></a>

986) <h3><a class="anchor" href="#torrc">I'm supposed to "edit my torrc". What does that mean?</a></h3>

987) 
988) <p>
989) Tor installs a text file called torrc that contains configuration
990) instructions for how your Tor program should behave. The default
991) configuration should work fine for most Tor users. Users of Vidalia can
992) make common changes through the Vidalia interface &mdash; only advanced
993) users should need to modify their torrc file directly.
994) </p>

995) <p>

996) Tor Browser Bundle users should edit your torrc through Vidalia. Open the

997) Vidalia Control Panel. Choose Settings. Choose Advanced. Click the button
998) labelled "Edit current torrc". Remember to make sure the checkbox for
999) "Save Settings." is checked. Hit the Ok button and you are done.
1000) </p>

1001) <p>

1002) Otherwise, you will need to edit the file manually.

1003) The location of your torrc file depends on the way you installed Tor:
1004) </p>
1005) <ul>

1006) <li>If you installed Tor Browser Bundle, look for
1007) <code>Data/Tor/torrc</code> inside your Tor Browser Bundle directory.
1008) </li>

1009) <li>On Windows, if you installed a Tor bundle with Vidalia, you can
1010) find your torrc file in the Start menu under Programs -&gt; Vidalia
1011) Bundle -&gt; Tor, or you can find it by hand in <code>\Documents and
1012) Settings\<i>username</i>\Application Data\Vidalia\torrc</code>. If you
1013) installed Tor without Vidalia, you can find your torrc in the Start
1014) menu under Programs -&gt; Tor, or manually in either <code>\Documents
1015) and Settings\Application Data\tor\torrc</code> or <code>\Documents and
1016) Settings\<i>username</i>\Application Data\tor\torrc</code>.
1017) </li>
1018) <li>On OS X, if you use Vidalia, edit
1019) <code>~/.vidalia/torrc</code>. Otherwise, open your favorite text editor
1020) and load <code>/Library/Tor/torrc</code>.
1021) </li>
1022) <li>On Unix, if you installed a pre-built package, look for
1023) <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> or consult your
1024) package's documentation.
1025) </li>
1026) <li>Finally, if you installed from source, you may not have a torrc
1027) installed yet: look in <code>/usr/local/etc/</code> and note that you
1028) may need to manually copy <code>torrc.sample</code> to <code>torrc</code>.
1029) </li>
1030) </ul>
1031) 
1032) <p>
1033) If you use Vidalia, be sure to exit both Tor and Vidalia before you edit

1034) your torrc file manually. Otherwise Vidalia might overwrite your changes.

1035) </p>
1036) 
1037) <p>
1038) Once you've changed your torrc, you will need to restart Tor for the
1039) changes to take effect. (For advanced users on OS X and Unix, note that
1040) you actually only need to send Tor a HUP signal, not actually restart it.)
1041) </p>
1042) 
1043) <p>
1044) For other configuration options you can use, look at the <a href="<page
1045) docs/tor-manual>">Tor manual page</a>. Remember, all lines beginning
1046) with # in torrc are treated as comments and have no effect on Tor's
1047) configuration.
1048) </p>
1049) 
1050) <hr>
1051) 

1052) <a id="Logs"></a>

1053) <h3><a class="anchor" href="#Logs">How do I set up logging, or see Tor's logs?</a></h3>

1054) 
1055) <p>

1056) If you installed a Tor bundle that includes Vidalia, then Vidalia has a

1057) window called "Message Log" that will show you Tor's log messages. Click
1058) on "Advanced" to see more details. You can click on "Settings" to change
1059) your log verbosity or save the messages to a file. You're all set.

1060) </p>
1061) 
1062) <p>
1063) If you're not using Vidalia, you'll have to go find the log files by

1064) hand. Here are some likely places for your logs to be:

1065) </p>
1066) 
1067) <ul>
1068) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1069) </li>

1070) <li>On Windows, there are no default log files currently. If you enable
1071) logs in your torrc file, they default to <code>\username\Application
1072) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1073) </li>
1074) <li>If you compiled Tor from source, by default your Tor logs to <a
1075) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1076) at log-level notice. If you enable logs in your torrc file, they
1077) default to <code>/usr/local/var/log/tor/</code>.

1078) </li>
1079) </ul>
1080) 
1081) <p>

1082) To change your logging setup by hand, <a href="#torrc">edit your torrc</a>
1083) and find the section (near the top of the file) which contains the
1084) following line:

1085) </p>
1086) 
1087) <pre>

1088) \## Logs go to stdout at level "notice" unless redirected by something
1089) \## else, like one of the below lines.

1090) </pre>

1091) 
1092) <p>

1093) For example, if you want Tor to send complete debug, info, notice, warn,

1094) and err level messages to a file, append the following line to the end
1095) of the section:
1096) </p>
1097) 
1098) <pre>
1099) Log debug file c:/program files/tor/debug.log
1100) </pre>
1101) 
1102) <p>

1103) Replace <code>c:/program files/tor/debug.log</code> with a directory
1104) and filename for your Tor log.

1105) </p>
1106) 
1107) <hr>
1108) 

1109) <a id="DoesntWork"></a>

1110) <h3><a class="anchor" href="#DoesntWork">I installed Tor but it's not working.</a></h3>

1111) 
1112) <p>

1113) Once you've got the Tor bundle up and running, the first question to
1114) ask is whether your Tor client is able to establish a circuit.

1115) </p>
1116) 
1117) <p>If Tor can establish a circuit, the onion icon in

1118) Vidalia will turn green (and if you're running Tor Browser Bundle, it will
1119) automatically launch a browser for you). You can also check in the Vidalia

1120) Control Panel to make sure it says "Connected to the Tor
1121) network!" under Status. For those not using Vidalia, check your <a

1122) href="#Logs">Tor logs</a> for

1123) a line saying that Tor "has successfully opened a circuit. Looks like
1124) client functionality is working."
1125) </p>
1126) 
1127) <p>
1128) If Tor can't establish a circuit, here are some hints:
1129) </p>
1130) 
1131) <ol>
1132) <li>Are you sure Tor is running? If you're using Vidalia, you may have
1133) to click on the onion and select "Start" to launch Tor.</li>
1134) <li>Check your system clock. If it's more than a few hours off, Tor will

1135) refuse to build circuits. For Microsoft Windows users, synchronize your
1136) clock under the clock -> Internet time tab. In addition, correct the

1137) day and date under the 'Date & Time' Tab. Also make sure your time
1138) zone is correct.</li>

1139) <li>Is your Internet connection <a href="#FirewallPorts">firewalled
1140) by port</a>, or do you normally need to use a <a

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

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

1148) href="<page docs/bridges>">Tor bridges</a>.</li>

1149) <li>Check your <a href="#Logs">Tor logs</a>. Do they give you any hints
1150) about what's going wrong?</li>

1151) </ol>
1152) 
1153) <hr />
1154) 
1155) <a id="VidaliaPassword"></a>

1156) <h3><a class="anchor" href="#VidaliaPassword">Tor/Vidalia prompts for a password at start.</a></h3>

1157) 
1158) <p>
1159) Vidalia interacts with the Tor software via Tor's "control port". The
1160) control port lets Vidalia receive status updates from Tor, request a new
1161) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
1162) Vidalia sets a random password for Tor's control port to prevent other
1163) applications from also connecting to the control port and potentially
1164) compromising your anonymity.
1165) </p>
1166) 
1167) <p>
1168) Usually this process of generating and setting a random control password
1169) happens in the background. There are three common situations, though,
1170) where Vidalia may prompt you for a password:
1171) </p>
1172) 
1173) <ol>
1174) <li>You're already running Vidalia and Tor. For example, this situation
1175) can happen if you installed the Vidalia bundle and now you're trying to
1176) run the Tor Browser Bundle. In that case, you'll need to close the old
1177) Vidalia and Tor before you can run this one.
1178) </li>
1179) <li>Vidalia crashed, but left Tor running with the last known random
1180) password. After you restart Vidalia, it generates a new random password,
1181) but Vidalia can't talk to Tor, because the random passwords are different.
1182) <br />
1183) If the dialog that prompts you for a control password has a Reset button,
1184) you can click the button and Vidalia will restart Tor with a new random
1185) control password.
1186) <br />
1187) If you do not see a Reset button, or if Vidalia is unable to restart
1188) Tor for you, you can still fix the problem manually. Simply go into your
1189) process or task manager, and terminate the Tor process. Then use Vidalia
1190) to restart Tor and all will work again.
1191) </li>
1192) <li>You had previously set Tor to run as a Windows NT service. When Tor
1193) is set to
1194) run as a service, it starts up when the system boots. If you configured
1195) Tor to start as a service through Vidalia, a random password was set
1196) and saved in Tor. When you reboot, Tor starts up and uses the random
1197) password it saved. You login and start up Vidalia. Vidalia attempts to
1198) talk to the already running Tor. Vidalia generates a random password,
1199) but it is different than the saved password in the Tor service.
1200) <br />
1201) You need to reconfigure Tor to not be a service. See the FAQ entry on

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

1203) for more information on how to remove the Tor service.
1204) </li>
1205) </ol>
1206) 

1207)     <hr>

1208) 

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

1211) 

1212)     <p>

1213)     Yes. You can set preferred entry and exit nodes as well as
1214)     inform Tor which nodes you do not want to use.

1215)     The following options can be added to your config file <a
1216)     href="#torrc">"torrc"</a> or specified on the command line:

1217)     </p>
1218)     <dl>
1219)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
1220)         <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
1221)         </dd>
1222)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1224)         </dd>
1225)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

1227)         </dd>
1228)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1231)         </dd>
1232)     </dl>
1233)     <p>

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

1239)     </p>
1240)     <p>

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

1248)     for some nodes you might pick.
1249)     </p>
1250)     <p>

1251)     Instead of <tt>$fingerprint</tt> you can also specify a <a
1252)     href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2">2
1253)     letter ISO3166 country code</a> in curly braces (for example {de}),
1254)     or an ip address pattern (for example 255.254.0.0/8), or a node
1255)     nickname. Make sure there are no spaces between the commas and the
1256)     list items.

1257)     </p>
1258)     <p>

1259)     If you want to access a service directly through Tor's Socks interface

1260)     (eg. using ssh via connect.c), another option is to set up an
1261)     internal mapping in your configuration file using <tt>MapAddress</tt>.

1262)     See the manual page for details.
1263)     </p>

1264) 

1265)     <hr>

1266) 

1267) <a id="FirewallPorts"></a>

1268) <h3><a class="anchor" href="#FirewallPorts">My firewall only allows a few outgoing ports.</a></h3>

1269) 
1270) <p>
1271) If your firewall works by blocking ports, then you can tell Tor to only
1272) use the ports that your firewall permits by adding "FascistFirewall 1" to

1273) your <a href="<page docs/faq>#torrc">torrc

1274) configuration file</a>, or by clicking "My firewall only lets me connect
1275) to certain ports" in Vidalia's Network Settings window.
1276) </p>
1277) 
1278) <p>
1279) By default, when you set this Tor assumes that your firewall allows only
1280) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
1281) different set of ports with the FirewallPorts torrc option.
1282) </p>
1283) 
1284) <p>
1285) If you want to be more fine-grained with your controls, you can also
1286) use the ReachableAddresses config options, e.g.:
1287) </p>
1288) 
1289) <pre>
1290)   ReachableDirAddresses *:80
1291)   ReachableORAddresses *:443
1292) </pre>
1293) 
1294) <hr>

1295) 

1296)     <a id="RelayFlexible"></a>

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

1298) 

1299)     <p>
1300)     We aim to make setting up a Tor relay easy and convenient:
1301)     </p>

1302) 

1303)     <ul>
1304)     <li>Tor has built-in support for <a

1305)     href="<wikifaq>#WhatbandwidthshapingoptionsareavailabletoTorrelays">

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

1309)     href="<wikifaq>#HowcanIlimitthetotalamountofbandwidthusedbymyTorrelay">hibernation

1310)     feature</a>.
1311)     </li>
1312)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
1313)     specifies what sort of outbound connections are allowed or refused from
1314)     that relay. If you are uncomfortable allowing people to exit from your
1315)     relay, you can set it up to only allow connections to other Tor relays.
1316)     </li>
1317)     <li>It's fine if the relay goes offline sometimes. The directories
1318)     notice this quickly and stop advertising the relay. Just try to make
1319)     sure it's not too often, since connections using the relay when it
1320)     disconnects will break.
1321)     </li>
1322)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
1323)     leave the Address config option blank, and Tor will try to guess.
1324)     </li>
1325)     <li>If your relay is behind a NAT and it doesn't know its public
1326)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

1327)     forwarding. Forwarding TCP connections is system dependent but

1328)     <a href="<wikifaq>#ImbehindaNATFirewall">this FAQ entry</a>

1329)     offers some examples on how to do this.
1330)     </li>
1331)     <li>Your relay will passively estimate and advertise its recent
1332)     bandwidth capacity, so high-bandwidth relays will attract more users than
1333)     low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
1334)     </li>
1335)     </ul>

1336) 

1337)     <hr>

1338) 

1339)     <a id="RunARelayBut"></a>
1340)     <a id="ExitPolicies"></a>

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

1342) 

1343)     <p>
1344)     Great. That's exactly why we implemented exit policies.
1345)     </p>

1346) 

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

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

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

1358)     for running an exit node with minimal harassment</a>.
1359)     </p>

1360) 

1361)     <p>

1362)     The default exit policy allows access to many popular services

1363)     (e.g. web browsing), but <a href="<wikifaq>#Istherealistofdefaultexitports">restricts</a>

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

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

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

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

1374) 

1375)     <p>
1376)     If you do allow any exit connections, make sure name resolution works
1377)     (that is, your computer can resolve Internet addresses correctly).
1378)     If there are any resources that your computer can't reach (for example,
1379)     you are behind a restrictive firewall or content filter), please
1380)     explicitly reject them in your exit policy &mdash; otherwise Tor users
1381)     will be impacted too.
1382)     </p>

1383) 

1384)     <hr>

1385) 

1386)     <a id="RelayOrBridge"></a>

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

1388) 

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

1395) 

1396)     <p>Being a normal relay vs being a bridge relay is almost the same
1397)     configuration: it's just a matter of whether your relay is listed
1398)     publically or not.
1399)     </p>

1400) 

1401)     <p>Right now, China is the main place in the world that filters
1402)     connections to the Tor network. So bridges are useful a) for users in
1403)     China, b) as a backup measure in case the Tor network gets blocked in
1404)     more places, and c) for people who want an extra layer of security
1405)     because they're worried somebody will recognize that it's a public
1406)     Tor relay IP address they're contacting.

1407)     </p>

1408) 

1409)     <p>So should you run a normal relay or bridge relay? If you have lots
1410)     of bandwidth, you should definitely run a normal relay &mdash; the
1411)     average bridge doesn't see much load these days. If you're willing
1412)     to <a href="#ExitPolicies">be an exit</a>, you should definitely
1413)     run a normal relay, since we need more exits. If you can't be an
1414)     exit and only have a little bit of bandwidth, be a bridge. Thanks
1415)     for volunteering!

1416)     </p>

1417) 

1418)     <hr>

1419) 

1420) <a id="MultipleRelays"></a>
1421) <h3><a class="anchor" href="#MultipleRelays">I want to run more than one relay.</a></h3>

1422) 
1423) <p>
1424) Great. If you want to run several relays to donate more to the network,
1425) we're happy with that. But please don't run more than a few dozen on
1426) the same network, since part of the goal of the Tor network is dispersal
1427) and diversity.
1428) </p>
1429) 
1430) <p>
1431) If you do decide to run more than one relay, please set the "MyFamily"

1432) config option in the <a href="#torrc">torrc</a> of each relay, listing
1433) all the relays (comma-separated) that are under your control:

1434) </p>
1435) 
1436) <pre>
1437)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
1438) </pre>
1439) 
1440) <p>
1441) where each fingerprint is the 40 character identity fingerprint (without
1442) spaces). You can also list them by nickname, but fingerprint is safer. Be
1443) sure to prefix the digest strings with a dollar sign ('$') so that the
1444) digest is not confused with a nickname in the config file.
1445) </p>
1446) 
1447) <p>
1448) That way clients will know to avoid using more than one of your relays
1449) in a single circuit. You should set MyFamily if you have administrative
1450) control of the computers or of their network, even if they're not all in
1451) the same geographic location.
1452) </p>
1453) 
1454)     <hr>
1455) 

1456)     <a id="RelayMemory"></a>

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

1458) 

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

1462) 

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

1471) 

1472)     <li>If you're running a fast relay, meaning you have many TLS connections
1473)     open, you are probably losing a lot of memory to OpenSSL's internal
1474)     buffers (38KB+ per socket). We've patched OpenSSL to <a

1475)     href="https://lists.torproject.org/pipermail/tor-dev/2008-June/001519.html">release

1476)     unused buffer memory more aggressively</a>. If you update to OpenSSL

1477)     1.0.0 or newer, Tor's build process will automatically recognize and use

1478)     this feature.</li>

1479) 

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

1483)     href="<wikifaq>#WhydoesntmyWindowsorotherOSTorrelayrunwell">better

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

1485) 

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

1491) 

1492)     </ol>

1493) 

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

1498) 

1499)     <hr>

1500) 

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

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

1503) 

1504)     <p>

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

1506)     </p>
1507)     <ul>
1508)     <li>The name is not currently mapped to a different key. Existing mappings
1509)     are removed after 6 months of inactivity from a relay.</li>
1510)     <li>The relay must have been around for at least two weeks.</li>
1511)     <li>No other router may have wanted the same name in the past month.</li>
1512)     </ul>

1513) 

1514)     <hr>

1515) 

1516)     <a id="RelayDonations"></a>

1517)     <h3><a class="anchor" href="#RelayDonations">Can I donate for a
1518)     relay rather than run my own?</a></h3>

1519) 
1520)     <p>
1521)     Sure! We recommend two non-profit charities that are happy to turn
1522)     your donations into better speed and anonymity for the Tor network:
1523)     </p>
1524)     <ul>
1525)     <li><a href="https://www.torservers.net/">torservers.net</a>
1526)     is a German charitable non-profit that runs a wide variety of

1527)     exit relays. They also like donations of bandwidth from ISPs.</li>

1528)     <li><a
1529)     href="https://www.noisebridge.net/wiki/Noisebridge_Tor">Noisebridge</a>
1530)     is a US-based 501(c)(3) non-profit that collects donations and turns
1531)     them into more exit relay capacity.</li>
1532)     </ul>
1533) 
1534)     <p>
1535)     These organizations are not the same as <a href="<page
1536)     donate/donate>">The Tor Project, Inc</a>, but we consider that a

1537)     good thing. They're both run by nice people who are part of the
1538)     Tor community.

1539)     </p>
1540) 
1541)     <p>
1542)     Note that there can be a tradeoff here between anonymity and
1543)     performance. The Tor network's anonymity comes in part from diversity,
1544)     so if you are in a position to run your own relay, you will be

1545)     improving Tor's anonymity more than by donating. At the same time
1546)     though, economies

1547)     of scale for bandwidth mean that combining many small donations into

1548)     several larger relays is more efficient at improving network

1549)     performance. Improving anonymity and improving performance are both
1550)     worthwhile goals, so however you can help is great!
1551)     </p>
1552) 
1553)     <hr>
1554) 

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

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

1557) 

1558)     <p>
1559)     Tor uses a variety of different keys, with three goals in mind: 1)
1560)     encryption to ensure privacy of data within the Tor network, 2)
1561)     authentication so clients know they're
1562)     talking to the relays they meant to talk to, and 3) signatures to make
1563)     sure all clients know the same set of relays.
1564)     </p>

1565) 

1566)     <p>
1567)     <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
1568)     so observers can't look inside to see which circuit a given cell is
1569)     intended for. Further, the Tor client establishes an ephemeral encryption

1570)     key with each relay in the circuit; these extra layers of encryption
1571)     mean that only the exit relay can read

1572)     the cells. Both sides discard the circuit key when the circuit ends,
1573)     so logging traffic and then breaking into the relay to discover the key
1574)     won't work.
1575)     </p>

1576) 

1577)     <p>
1578)     <b>Authentication</b>:
1579)     Every Tor relay has a public decryption key called the "onion key".

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

1581)     When the Tor client establishes circuits, at each step it <a
1582)     href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1583)     that the Tor relay prove knowledge of its onion key</a>. That way
1584)     the first node in the path can't just spoof the rest of the path.

1585)     Because the Tor client chooses the path, it can make sure to get
1586)     Tor's "distributed trust" property: no single relay in the path can
1587)     know about both the client and what the client is doing.

1588)     </p>

1589) 

1590)     <p>
1591)     <b>Coordination</b>:
1592)     How do clients know what the relays are, and how do they know that they
1593)     have the right keys for them? Each relay has a long-term public signing
1594)     key called the "identity key". Each directory authority additionally has a
1595)     "directory signing key". The directory authorities <a

1596)     href="<specblob>dir-spec.txt">provide a signed list</a>

1597)     of all the known relays, and in that list are a set of certificates from
1598)     each relay (self-signed by their identity key) specifying their keys,
1599)     locations, exit policies, and so on. So unless the adversary can control

1600)     a majority of the directory authorities (as of 2012 there are 8

1601)     directory authorities), he can't trick the Tor client into using
1602)     other Tor relays.

1603)     </p>

1604) 

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

1611) 

1612)     <p>
1613)     How do users know they've got the right software? When we distribute
1614)     the source code or a package, we digitally sign it with <a
1615)     href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1616)     href="<page docs/verifying-signatures>">instructions
1617)     on how to check Tor's signatures</a>.
1618)     </p>

1619) 

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

1627) 

1628)     <hr>

1629) 

1630) <a id="EntryGuards"></a>
1631) <h3><a class="anchor" href="#EntryGuards">What are Entry Guards?</a></h3>
1632) 
1633) <p>
1634) Tor (like all current practical low-latency anonymity designs) fails
1635) when the attacker can see both ends of the communications channel. For

1636) example, suppose the attacker controls or watches the Tor relay you choose
1637) to enter the network, and also controls or watches the website you visit. In

1638) this case, the research community knows no practical low-latency design
1639) that can reliably stop the attacker from correlating volume and timing
1640) information on the two sides.
1641) </p>
1642) 
1643) <p>
1644) So, what should we do? Suppose the attacker controls, or can observe,

1645) <i>C</i> relays. Suppose there are <i>N</i> relays total. If you select
1646) new entry and exit relays each time you use the network, the attacker
1647) will be able to correlate all traffic you send with probability
1648) <i>(c/n)<sup>2</sup></i>. But profiling is, for most users, as bad
1649) as being traced all the time: they want to do something often without
1650) an attacker noticing, and the attacker noticing once is as bad as the
1651) attacker noticing more often. Thus, choosing many random entries and exits
1652) gives the user no chance of escaping profiling by this kind of attacker.

1653) </p>
1654) 
1655) <p>

1656) The solution is "entry guards": each Tor client selects a few relays at random

1657) to use as entry points, and uses only those relays for her first hop. If
1658) those relays are not controlled or observed, the attacker can't win,
1659) ever, and the user is secure. If those relays <i>are</i> observed or
1660) controlled by the attacker, the attacker sees a larger <i>fraction</i>
1661) of the user's traffic &mdash; but still the user is no more profiled than
1662) before. Thus, the user has some chance (on the order of <i>(n-c)/n</i>)
1663) of avoiding profiling, whereas she had none before.

1664) </p>
1665) 
1666) <p>

1667) You can read more at <a href="http://freehaven.net/anonbib/#wright02">An
1668) Analysis of the Degradation of Anonymous Protocols</a>, <a
1669) href="http://freehaven.net/anonbib/#wright03">Defending Anonymous
1670) Communication Against Passive Logging Attacks</a>, and especially
1671) <a href="http://freehaven.net/anonbib/#hs-attack06">Locating Hidden
1672) Servers</a>.

1673) </p>
1674) 
1675) <p>
1676) Restricting your entry nodes may also help against attackers who want
1677) to run a few Tor nodes and easily enumerate all of the Tor user IP
1678) addresses. (Even though they can't learn what destinations the users
1679) are talking to, they still might be able to do bad things with just a

1680) list of users.) However, that feature won't really become useful until
1681) we move to a "directory guard" design as well.

1682) </p>
1683) 
1684)     <hr>
1685) 

1686)     <a id="EverybodyARelay"></a>

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

1688) 

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

1691)     network to handle all our users, and <a
1692)     href="<wikifaq>#DoIgetbetteranonymityifIrunarelay">running a Tor

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

1701) 

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

1710) 

1711)     <p>
1712)     There are five steps we need to address before we can do this though:
1713)     </p>

1714) 

1715)     <p>
1716)     First, we need to make Tor stable as a relay on all common
1717)     operating systems. The main remaining platform is Windows,

1718)     and we're mostly there. See Section 4.1 of <a

1719)     href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">our
1720)     development roadmap</a>.
1721)     </p>

1722) 

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

1729)     href="<page docs/faq>#TransportIPnotTCP">switching

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

1733) 

1734)     <p>
1735)     Third, we need to work on scalability, both of the network (how to
1736)     stop requiring that all Tor relays be able to connect to all Tor
1737)     relays) and of the directory (how to stop requiring that all Tor
1738)     users know about all Tor relays). Changes like this can have large
1739)     impact on potential and actual anonymity. See Section 5 of the <a
1740)     href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1741)     for details. Again, UDP transport would help here.
1742)     </p>

1743) 

1744)     <p>
1745)     Fourth, we need to better understand the risks from
1746)     letting the attacker send traffic through your relay while
1747)     you're also initiating your own anonymized traffic. <a
1748)     href="http://freehaven.net/anonbib/#back01">Three</a> <a
1749)     href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1750)     <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1751)     describe ways to identify the relays in a circuit by running traffic
1752)     through candidate relays and looking for dips in the traffic while the
1753)     circuit is active. These clogging attacks are not that scary in the Tor
1754)     context so long as relays are never clients too. But if we're trying to
1755)     encourage more clients to turn on relay functionality too (whether as
1756)     <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1757)     we need to understand this threat better and learn how to mitigate it.
1758)     </p>

1759) 

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

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

1764)     thoughts on Tor incentives</a>.
1765)     </p>

1766) 

1767)     <p>
1768)     Please help on all of these!
1769)     </p>

1770) 

1771) <hr>
1772) 
1773) <a id="TransportIPnotTCP"></a>

1774) <h3><a class="anchor" href="#TransportIPnotTCP">You should transport all IP packets, not just TCP packets.</a></h3>

1775) 
1776) <p>

1777) This would be handy, because it would make Tor better able to handle
1778) new protocols like VoIP, it could solve the whole need to socksify
1779) applications, and it would solve the fact that exit relays need to
1780) allocate a lot of file descriptors to hold open all the exit connections.

1781) </p>
1782) 
1783) <p>

1784) We're heading in this direction: see <a
1785) href="https://trac.torproject.org/projects/tor/ticket/1855">this trac
1786) ticket</a> for directions we should investigate. Some of the hard
1787) problems are:

1788) </p>
1789) 

1790) <ol>

1791) <li>IP packets reveal OS characteristics. We would still need to do
1792) IP-level packet normalization, to stop things like TCP fingerprinting
1793) attacks. Given the diversity and complexity of TCP stacks, along with <a

1794) href="<wikifaq>#DoesTorresistremotephysicaldevicefingerprinting">device

1795) fingerprinting attacks</a>, it looks like our best bet is shipping our
1796) own user-space TCP stack.

1797) </li>

1798) <li>Application-level streams still need scrubbing. We will still need
1799) user-side applications like Torbutton. So it won't become just a matter
1800) of capturing packets and anonymizing them at the IP layer.

1801) </li>
1802) <li>Certain protocols will still leak information. For example, we must
1803) rewrite DNS requests so they are delivered to an unlinkable DNS server
1804) rather than the DNS server at a user's ISP; thus, we must understand
1805) the protocols we are transporting.
1806) </li>
1807) <li><a
1808) href="http://crypto.stanford.edu/~nagendra/projects/dtls/dtls.html">DTLS</a>

1809) (datagram TLS) basically has no users, and IPsec sure is big. Once we've
1810) picked a transport mechanism, we need to design a new end-to-end Tor
1811) protocol for avoiding tagging attacks and other potential anonymity and
1812) integrity issues now that we allow drops, resends, et cetera.

1813) </li>
1814) <li>Exit policies for arbitrary IP packets mean building a secure
1815) IDS. Our node operators tell us that exit policies are one of the main
1816) reasons they're willing to run Tor. Adding an Intrusion Detection System
1817) to handle exit policies would increase the security complexity of Tor,
1818) and would likely not work anyway, as evidenced by the entire field of IDS
1819) and counter-IDS papers. Many potential abuse issues are resolved by the
1820) fact that Tor only transports valid TCP streams (as opposed to arbitrary
1821) IP including malformed packets and IP floods), so exit policies become
1822) even <i>more</i> important as we become able to transport IP packets. We
1823) also need to compactly describe exit policies in the Tor directory,
1824) so clients can predict which nodes will allow their packets to exit &mdash;
1825) and clients need to predict all the packets they will want to send in
1826) a session before picking their exit node!
1827) </li>

1828) <li>The Tor-internal name spaces would need to be redesigned. We support
1829) hidden service ".onion" addresses by intercepting the addresses when
1830) they are passed to the Tor client. Doing so at the IP level will require
1831) a more complex interface between Tor and the local DNS resolver.

1832) </li>

1833) </ol>
1834) 
1835) <hr>
1836) 
1837) <a id="HideExits"></a>
1838) <h3><a class="anchor" href="#HideExits">You should hide the list of Tor
1839) relays, so people can't block the exits.</a></h3>
1840) 
1841) <p>
1842) There are a few reasons we don't:
1843) </p>
1844) 
1845) <ol>
1846) <li>We can't help but make the information available, since Tor clients
1847) need to use it to pick their paths. So if the "blockers" want it, they
1848) can get it anyway. Further, even if we didn't tell clients about the
1849) list of relays directly, somebody could still make a lot of connections
1850) through Tor to a test site and build a list of the addresses they see.
1851) </li>
1852) 
1853) <li>If people want to block us, we believe that they should be allowed to
1854) do so.  Obviously, we would prefer for everybody to allow Tor users to
1855) connect to them, but people have the right to decide who their services
1856) should allow connections from, and if they want to block anonymous users,
1857) they can.
1858) </li>
1859) 
1860) <li>Being blockable also has tactical advantages: it may be a persuasive

1861) response to website maintainers who feel threatened by Tor. Giving them
1862) the option may inspire them to <a href="<page docs/faq-abuse>#Bans">stop
1863) and think</a> about whether they really want to eliminate private access
1864) to their system, and if not, what other options they might have. The
1865) time they might otherwise have spent blocking Tor, they may instead
1866) spend rethinking their overall approach to privacy and anonymity.

1867) </li>

1868) </ol>
1869) 

1870)     <hr>

1871) 

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

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

1874) 

1875)     <p>
1876)     For the answer to this question and others, please see our <a
1877)     href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1878)     </p>

1879) 

1880)     <hr>

1881) 

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

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

1884) 

1885)     <p>
1886)     A collection of templates for successfully responding to ISPs is <a

1887)     href="<wiki>doc/TorAbuseTemplates">collected

1888)     here</a>.
1889)     </p>

1890) 

1891)     <hr>

1892) 

1893)   </div>
1894)   <!-- END MAINCOL -->
1895)   <div id = "sidecol">
1896) #include "side.wmi"
1897) #include "info.wmi"
1898)   </div>
1899)   <!-- END SIDECOL -->
1900) </div>
1901) <!-- END CONTENT -->