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="#GetTor">Your website is blocked in my country. How
42)     do I download Tor?</a></li>

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

48) 

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

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

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

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

55)     </ul>

56) 

57)     <p>Running a Tor client:</p>
58)     <ul>

59)     <li><a href="#DoesntWork">I installed Tor and Polipo but it's not
60)     working.</a></li>
61)     <li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at
62)     start.</a></li>
63)     <li><a href="#ChooseEntryExit">Can I control which nodes (or country)
64)     are used for entry/exit?</a></li>
65)     <li><a href="#GoogleCaptcha">Google makes me solve a Captcha or tells
66)     me I have spyware installed.</a></li>
67)     <li><a href="#GmailWarning">Gmail warns me that my account may have
68)     been compromised.</a></li>

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

71)     </ul>

72) 

73)     <p>Running a Tor relay:</p>
74)     <ul>
75)     <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
76)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
77)     with abuse issues.</a></li>
78)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
79)     relay?</a></li>

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

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

84) 

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

86) 

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

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

91)     </ul>

92) 

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

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

99)     </ul>

100) 

101)     <p>Abuse:</p>

102)     <ul>
103)     <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
104)     <li><a href="#RespondISP">How do I respond to my ISP about my exit
105)     relay?</a></li>
106)     </ul>

107) 

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

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

110) 

111)     <hr>

112) 

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

114) 

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

117) 

118)     <p>
119)     The name "Tor" can refer to several different components.
120)     </p>

121) 

122)     <p>
123)     The Tor software is a program you can run on your computer that helps keep
124)     you safe on the Internet. Tor protects you by bouncing your communications
125)     around a distributed network of relays run by volunteers all around
126)     the world: it prevents somebody watching your Internet connection from
127)     learning what sites you visit, and it prevents the sites you visit
128)     from learning your physical location. This set of volunteer relays is
129)     called the Tor network. You can read more about how Tor works on the <a
130)     href="<page about/overview>">overview page</a>.
131)     </p>

132) 

133)     <p>
134)     The Tor Project is a non-profit (charity) organization that maintains
135)     and develops the Tor software.
136)     </p>

137) 

138)     <hr>

139) 

140)     <a id="Torisdifferent"></a>
141)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
142)     <p>

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

173)     <p>
174)     <dl>

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

188)     </dl>
189)     </p>

190) 

191)     <hr>

192) 

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

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

195) 

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

209) 

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

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

214)     extension</a> if you have Firefox installed. As of version 1.2.0,
215)     Torbutton now takes care of a lot of the connection-level and
216)     application-level worries.
217)     </p>

218) 

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

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

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

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

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

230) 

231)     <hr>

232) 

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

235) 

236)     <p>
237)     Because Tor is the onion routing network. When we were starting the
238)     new next-generation design and implementation of onion routing in
239)     2001-2002, we would tell people we were working on onion routing,
240)     and they would say "Neat. Which one?" Even if onion routing has
241)     become a standard household term, Tor was born out of the actual <a
242)     href="http://www.onion-router.net/">onion routing project</a> run by
243)     the Naval Research Lab.
244)     </p>

245) 

246)     <p>
247)     (It's also got a fine translation from German and Turkish.)
248)     </p>

249) 

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

257) 

258)     <hr>

259) 

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

262) 

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

269) 

270)     <p>
271)     We think that putting a backdoor in Tor would be tremendously
272)     irresponsible to our users, and a bad precedent for security software
273)     in general. If we ever put a deliberate backdoor in our security
274)     software, it would ruin our professional reputations. Nobody would
275)     trust our software ever again &mdash; for excellent reason!
276)     </p>

277) 

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

289) 

290)     <p>
291)     Also, there might be accidental bugs in Tor that could affect your
292)     anonymity. We periodically find and fix anonymity-related bugs, so make
293)     sure you keep your Tor versions up-to-date.
294)     </p>

295) 

296)     <hr>

297) 

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

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

300) 

301)     <p>
302)     Yes.
303)     </p>

304) 

305)     <p>
306)     The Tor software is <a href="https://www.fsf.org/">free software</a>. This
307)     means we give you the rights to redistribute the Tor software, either
308)     modified or unmodified, either for a fee or gratis. You don't have to
309)     ask us for specific permission.
310)     </p>

311) 

312)     <p>
313)     However, if you want to redistribute the Tor software you must follow our
314)     <a href="<gitblob>LICENSE">LICENSE</a>.
315)     Essentially this means that you need to include our LICENSE file along
316)     with whatever part of the Tor software you're distributing.
317)     </p>

318) 

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

334) 

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

340) 

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

348) 

349)     <hr>

350) 

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

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

353) 

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

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

367) 

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

370) 

371)     <hr>

372) 

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

375) 

376)     <p>
377)     There are many reasons why the Tor network is currently slow.
378)     </p>

379) 

380)     <p>
381)     Before we answer, though, you should realize that Tor is never going to
382)     be blazing fast. Your traffic is bouncing through volunteers' computers
383)     in various parts of the world, and some bottlenecks and network latency
384)     will always be present. You shouldn't expect to see university-style
385)     bandwidth through Tor.
386)     </p>

387) 

388)     <p>
389)     But that doesn't mean that it can't be improved. The current Tor network
390)     is quite small compared to the number of people trying to use it, and
391)     many of these users don't understand or care that Tor can't currently
392)     handle file-sharing traffic load.
393)     </p>

394) 

395)     <p>
396)     For the much more in-depth answer, see <a

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

398)     post on the topic</a>, which includes both a detailed PDF and a video
399)     to go with it.
400)     </p>

401) 

402)     <p>
403)     What can you do to help?
404)     </p>

405) 

406)     <ul>

407) 

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

413) 

414)     <li>

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

416)     especially need people to help make it easier to configure your Tor
417)     as a relay. Also, we need help with clear simple documentation to
418)     walk people through setting it up.
419)     </li>

420) 

421)     <li>
422)     There are some bottlenecks in the current Tor network. Help us design
423)     experiments to track down and demonstrate where the problems are, and
424)     then we can focus better on fixing them.
425)     </li>

426) 

427)     <li>
428)     There are some steps that individuals
429)     can take to improve their Tor performance. <a

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

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

437) 

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

444) 

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

450) 

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

459) 

460)     <li>
461)     If you can't help out with any of the above, you can still help out
462)     individually by <a href="<page donate/donate>">donating a bit of money to the
463)     cause</a>. It adds up!
464)     </li>

465) 

466)     </ul>

467) 

468)     <hr>

469) 

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

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

472) 

473)     <p>
474)     We have about 1800 relays right now, pushing over 150 MB/s average
475)     traffic. We have several hundred thousand active users. But the Tor
476)     network is not yet self-sustaining.
477)     </p>

478) 

479)     <p>
480)     There are six main development/maintenance pushes that need attention:
481)     </p>

482) 

483)     <ul>

484) 

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

491) 

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

497) 

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

506) 

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

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

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

515) 

516)     <li>
517)     Incentives: We need to work on ways to encourage people to configure
518)     their Tors as relays and exit nodes rather than just clients.
519)     <a href="#EverybodyARelay">We need to make it easy to become a relay,
520)     and we need to give people incentives to do it.</a>
521)     </li>

522) 

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

533) 

534)     </ul>

535) 

536)     <p>
537)     We're continuing to move forward on all of these, but at this rate
538)     <a href="#WhySlow">the Tor network is growing faster than the developers
539)     can keep up</a>.
540)     Now would be an excellent time to add a few more developers to the effort
541)     so we can continue to grow the network.
542)     </p>

543) 

544)     <p>
545)     We are also excited about tackling related problems, such as
546)     censorship-resistance.
547)     </p>

548) 

549)     <p>
550)     We are proud to have <a href="<page about/sponsors>">sponsorship and support</a>
551)     from the Omidyar Network, the International Broadcasting Bureau, Bell
552)     Security Solutions, the Electronic Frontier Foundation, several government
553)     agencies and research groups, and hundreds of private contributors.
554)     </p>

555) 

556)     <p>
557)     However, this support is not enough to keep Tor abreast of changes in the
558)     Internet privacy landscape. Please <a href="<page donate/donate>">donate</a>
559)     to the project, or <a href="<page about/contact>">contact</a> our executive
560)     director for information on making grants or major donations.
561)     </p>

562) 

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

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

565) 

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

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

568)     <hr>

569) 

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

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

572) 

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

580) 

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

591) 

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

597) 

598)     <p>
599)     For Mac OS X, follow the <a
600)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
601)     </p>

602) 

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

608) 

609)     <hr>

610) 

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

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

613) 

614)     <p>
615)     These are PGP signatures, so you can verify that the file you've downloaded is
616)     exactly the one that we intended you to get.
617)     </p>

618) 

619)     <p>
620)     Please read the <a
621)     href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
622)     </p>

623) 

624) <hr>
625) 
626) <a id="GetTor"></a>
627) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
628) country. How do I download Tor?</a></h3>
629) 
630) <p>
631) Some government or corporate firewalls censor connections to Tor's
632) website. In those cases, you have three options. First, get it from

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

634) Bundle</a> fits nicely on a USB key. Second, find the google cache
635) for the <a href="<page getinvolved/mirrors>">Tor mirrors</a> page
636) and see if any of those copies of our website work for you. Third,
637) you can download Tor via email: log in to your Gmail account and mail
638) '<tt>gettor AT torproject.org</tt>'. If you include the word 'help'
639) in the body of the email, it will reply with instructions. Note that
640) only a few webmail providers are supported, since they need to be able
641) to receive very large attachments.
642) </p>
643) 
644) <p>

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

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

648) </p>
649) 
650) <hr>

651) 

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

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

654) 

655)     <p>
656)     Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
657)     tor-win32-mingw-creation.txt</a>.
658)     </p>

659) 

660)     <p>
661)     (Note that you don't need to compile Tor yourself in order to use
662)     it. Most people just use the packages available on the <a href="<page
663)     download/download>">download page</a>.)
664)     </p>

665) 

666)     <hr>

667) 

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

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

670) 

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

678) 

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

684) 

685)     <hr>

686) 

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

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

689) 

690)     <p>

691)     Yes.  Use <a href="https://amnesia.boum.org/">The (Amnesic) Incognito
692)     Live System</a> or <a href="<page projects/torbrowser>">the Tor Browser
693)     Bundle</a>.

694)     </p>

695) 
696) <hr>
697) 

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

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

700) 
701) <p>
702) Tor installs a text file called torrc that contains configuration
703) instructions for how your Tor program should behave. The default
704) configuration should work fine for most Tor users. Users of Vidalia can
705) make common changes through the Vidalia interface &mdash; only advanced
706) users should need to modify their torrc file directly.
707) </p>
708) 
709) <p>
710) The location of your torrc file depends on the way you installed Tor:
711) </p>
712) 
713) <ul>
714) <li>On Windows, if you installed a Tor bundle with Vidalia, you can
715) find your torrc file in the Start menu under Programs -&gt; Vidalia
716) Bundle -&gt; Tor, or you can find it by hand in <code>\Documents and
717) Settings\<i>username</i>\Application Data\Vidalia\torrc</code>. If you
718) installed Tor without Vidalia, you can find your torrc in the Start
719) menu under Programs -&gt; Tor, or manually in either <code>\Documents
720) and Settings\Application Data\tor\torrc</code> or <code>\Documents and
721) Settings\<i>username</i>\Application Data\tor\torrc</code>.
722) </li>
723) <li>On OS X, if you use Vidalia, edit
724) <code>~/.vidalia/torrc</code>. Otherwise, open your favorite text editor
725) and load <code>/Library/Tor/torrc</code>.
726) </li>
727) <li>On Unix, if you installed a pre-built package, look for
728) <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> or consult your
729) package's documentation.
730) </li>
731) <li>Finally, if you installed from source, you may not have a torrc
732) installed yet: look in <code>/usr/local/etc/</code> and note that you
733) may need to manually copy <code>torrc.sample</code> to <code>torrc</code>.
734) </li>
735) </ul>
736) 
737) <p>
738) If you use Vidalia, be sure to exit both Tor and Vidalia before you edit
739) your torrc file. Otherwise Vidalia might overwrite your changes.
740) </p>
741) 
742) <p>
743) Once you've changed your torrc, you will need to restart Tor for the
744) changes to take effect. (For advanced users on OS X and Unix, note that
745) you actually only need to send Tor a HUP signal, not actually restart it.)
746) </p>
747) 
748) <p>
749) For other configuration options you can use, look at the <a href="<page
750) docs/tor-manual>">Tor manual page</a>. Remember, all lines beginning
751) with # in torrc are treated as comments and have no effect on Tor's
752) configuration.
753) </p>
754) 
755) <hr>
756) 

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

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

759) 
760) <p>

761) If you installed a Tor bundle that includes Vidalia, then Vidalia has a
762) window called "Message Log" that will show you Tor's log messages. You
763) can click on "Settings" to see more details, or to save the messages to
764) a file. You're all set.

765) </p>
766) 
767) <p>
768) If you're not using Vidalia, you'll have to go find the log files by

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

770) </p>
771) 
772) <ul>
773) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
774) </li>

775) <li>On Windows, there are no default log files currently. If you enable
776) logs in your torrc file, they default to <code>\username\Application
777) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
778) </li>
779) <li>If you compiled Tor from source, by default your Tor logs to <a
780) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
781) at log-level notice. If you enable logs in your torrc file, they
782) default to <code>/usr/local/var/log/tor/</code>.

783) </li>
784) </ul>
785) 
786) <p>

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

790) </p>
791) 
792) <pre>

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

795) </pre>

796) 
797) <p>

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

799) and err level messages to a file, append the following line to the end
800) of the section:
801) </p>
802) 
803) <pre>
804) Log debug file c:/program files/tor/debug.log
805) </pre>
806) 
807) <p>

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

810) </p>
811) 
812) <hr>
813) 

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

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

816) 
817) <p>
818) Once you've installed the Tor bundle, there are two questions to ask:
819) first, is your Tor able to establish a circuit? Second, is your
820) Firefox correctly configured to send its traffic through Tor?
821) </p>
822) 
823) <p>If Tor can establish a circuit, the onion icon in
824) Vidalia will turn green. You can also check in the Vidalia
825) Control Panel to make sure it says "Connected to the Tor
826) network!" under Status. For those not using Vidalia, check your <a

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

828) a line saying that Tor "has successfully opened a circuit. Looks like
829) client functionality is working."
830) </p>
831) 
832) <p>
833) If Tor can't establish a circuit, here are some hints:
834) </p>
835) 
836) <ol>
837) <li>Are you sure Tor is running? If you're using Vidalia, you may have
838) to click on the onion and select "Start" to launch Tor.</li>
839) <li>Check your system clock. If it's more than a few hours off, Tor will
840) refuse to build circuits. For XP users, synchronize your clock under
841) the clock -&gt; Internet time tab. In addition, correct the day and date
842) under the 'Date &amp; Time' Tab.</li>
843) <li>Is your Internet connection <a

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

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

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

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

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

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

856) </ol>
857) 
858) <p>
859) Step two is to confirm that Firefox is correctly configured to send its
860) traffic through Tor. Try the <a href="https://check.torproject.org/">Tor
861) Check</a> site and see whether it thinks you are using Tor. See <a

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

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

864) </p>

865) 
866) <p>
867) If it thinks you're not using Tor, here are some hints:
868) </p>
869) 
870) <ol>
871) <li>Did you install the Torbutton extension for Firefox? The installation
872) bundles include it, but sometimes people forget to install it. Make sure
873) it says "Tor enabled" at the bottom right of your Firefox window. (For
874) expert users, make sure your http proxy is set to localhost port
875) 8118.)</li>
876) <li>Do you have incompatible Firefox extensions like FoxyProxy
877) installed? If so, uninstall them. (Note that using FoxyProxy is NOT
878) a sufficient substitute for Torbutton. There are many known attacks
879) against a browser setup that does not include Torbutton. Read more

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

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

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

898) <li>For Red Hat Linux and related systems, do you have SELinux enabled? If
899) so, it might be preventing Polipo from talking to Tor. We also run across
900) BSD users periodically who have local firewall rules that prevent some
901) connections to localhost.</li>
902) </ol>
903) 
904) <hr />
905) 
906) <a id="VidaliaPassword"></a>

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

908) 
909) <p>
910) Vidalia interacts with the Tor software via Tor's "control port". The
911) control port lets Vidalia receive status updates from Tor, request a new
912) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
913) Vidalia sets a random password for Tor's control port to prevent other
914) applications from also connecting to the control port and potentially
915) compromising your anonymity.
916) </p>
917) 
918) <p>
919) Usually this process of generating and setting a random control password
920) happens in the background. There are three common situations, though,
921) where Vidalia may prompt you for a password:
922) </p>
923) 
924) <ol>
925) <li>You're already running Vidalia and Tor. For example, this situation
926) can happen if you installed the Vidalia bundle and now you're trying to
927) run the Tor Browser Bundle. In that case, you'll need to close the old
928) Vidalia and Tor before you can run this one.
929) </li>
930) <li>Vidalia crashed, but left Tor running with the last known random
931) password. After you restart Vidalia, it generates a new random password,
932) but Vidalia can't talk to Tor, because the random passwords are different.
933) <br />
934) If the dialog that prompts you for a control password has a Reset button,
935) you can click the button and Vidalia will restart Tor with a new random
936) control password.
937) <br />
938) If you do not see a Reset button, or if Vidalia is unable to restart
939) Tor for you, you can still fix the problem manually. Simply go into your
940) process or task manager, and terminate the Tor process. Then use Vidalia
941) to restart Tor and all will work again.
942) </li>
943) <li>You had previously set Tor to run as a Windows NT service. When Tor
944) is set to
945) run as a service, it starts up when the system boots. If you configured
946) Tor to start as a service through Vidalia, a random password was set
947) and saved in Tor. When you reboot, Tor starts up and uses the random
948) password it saved. You login and start up Vidalia. Vidalia attempts to
949) talk to the already running Tor. Vidalia generates a random password,
950) but it is different than the saved password in the Tor service.
951) <br />
952) You need to reconfigure Tor to not be a service. See the FAQ entry on

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

954) for more information on how to remove the Tor service.
955) </li>
956) </ol>
957) 

958)     <hr>

959) 

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

962) 

963)     <p>

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

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

968)     </p>
969)     <dl>
970)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
971)         <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
972)         </dd>
973)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

975)         </dd>
976)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

978)         </dd>
979)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

982)         </dd>
983)     </dl>
984)     <p>

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

990)     </p>
991)     <p>

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

999)     for some nodes you might pick.
1000)     </p>
1001)     <p>

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

1006)     </p>
1007)     <p>

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

1011)     See the manual page for details.
1012)     </p>

1013) 

1014)     <hr>

1015) 
1016) <a id="GoogleCaptcha"></a>

1017) <h3><a class="anchor" href="#GoogleCaptcha">Google makes me solve a Captcha or tells me I have spyware installed.</a></h3>

1018) 
1019) <p>
1020) This is a known and intermittent problem; it does not mean that Google
1021) considers Tor to be spyware.
1022) </p>
1023) 
1024) <p>
1025) When you use Tor, you are sending queries through exit relays that are also
1026) shared by thousands of other users. Tor users typically see this message
1027) when many Tor users are querying Google in a short period of time. Google
1028) interprets the high volume of traffic from a single IP address (the exit
1029) relay you happened to pick) as somebody trying to "crawl" their website,
1030) so it slows down traffic from that IP address for a short time.
1031) </p>
1032) <p>
1033) An alternate explanation is that Google tries to detect certain
1034) kinds of spyware or viruses that send distinctive queries to Google
1035) Search. It notes the IP addresses from which those queries are received
1036) (not realizing that they are Tor exit relays), and tries to warn any
1037) connections coming from those IP addresses that recent queries indicate
1038) an infection.
1039) </p>
1040) 
1041) <p>
1042) To our knowledge, Google is not doing anything intentionally specifically
1043) to deter or block Tor use. The error message about an infected machine
1044) should clear up again after a short time.
1045) </p>
1046) 
1047) <p>
1048) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1049) automatically redirect you to a more Tor-friendly search engine such as
1050) Ixquick or Bing.
1051) </p>
1052) 
1053) <hr />
1054) 
1055) <a id="GmailWarning"></a>

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

1057) 
1058) <p>
1059) Sometimes, after you've used Gmail over Tor, Google presents a

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

1063) </p>
1064) 
1065) <p>
1066) In general this is a false alarm: Google saw a bunch of logins from

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

1070) </p>
1071) 
1072) <p>

1073) Even though this may be a biproduct of using the service via tor,
1074) that doesn't mean you can entirely ignore the warning. It is
1075) <i>probably</i> a false positive, but it might not be since it is
1076) possible for someone to hijack your Google cookie.
1077) </p>
1078) 
1079) <p>
1080) Cookie hijacking is possible by either physical access to your computer
1081) or by watching your network traffic.  In theory only physical access
1082) should compromise your system because Gmail and similar services
1083) should only send the cookie over an SSL link. In practice, alas, it's <a
1084) href="http://fscked.org/blog/fully-automated-active-https-cookie-hijacking">
1085) way more complex than that</a>.

1086) </p>
1087) 
1088) <p>
1089) And if somebody <i>did</i> steal your google cookie, they might end
1090) up logging in from unusual places (though of course they also might
1091) not). So the summary is that since you're using Tor, this security
1092) measure that Google uses isn't so useful for you, because it's full of
1093) false positives. You'll have to use other approaches, like seeing if
1094) anything looks weird on the account, or looking at the timestamps for
1095) recent logins and wondering if you actually logged in at those times.
1096) </p>
1097) 

1098) <hr>
1099) 
1100) <a id="FirewallPorts"></a>

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

1102) 
1103) <p>
1104) If your firewall works by blocking ports, then you can tell Tor to only
1105) use the ports that your firewall permits by adding "FascistFirewall 1" to

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

1107) configuration file</a>, or by clicking "My firewall only lets me connect
1108) to certain ports" in Vidalia's Network Settings window.
1109) </p>
1110) 
1111) <p>
1112) By default, when you set this Tor assumes that your firewall allows only
1113) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
1114) different set of ports with the FirewallPorts torrc option.
1115) </p>
1116) 
1117) <p>
1118) If you want to be more fine-grained with your controls, you can also
1119) use the ReachableAddresses config options, e.g.:
1120) </p>
1121) 
1122) <pre>
1123)   ReachableDirAddresses *:80
1124)   ReachableORAddresses *:443
1125) </pre>
1126) 
1127) <hr>

1128) 

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

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

1131) 

1132)     <p>
1133)     We aim to make setting up a Tor relay easy and convenient:
1134)     </p>

1135) 

1136)     <ul>
1137)     <li>Tor has built-in support for <a

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

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

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

1143)     feature</a>.
1144)     </li>
1145)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
1146)     specifies what sort of outbound connections are allowed or refused from
1147)     that relay. If you are uncomfortable allowing people to exit from your
1148)     relay, you can set it up to only allow connections to other Tor relays.
1149)     </li>
1150)     <li>It's fine if the relay goes offline sometimes. The directories
1151)     notice this quickly and stop advertising the relay. Just try to make
1152)     sure it's not too often, since connections using the relay when it
1153)     disconnects will break.
1154)     </li>
1155)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
1156)     leave the Address config option blank, and Tor will try to guess.
1157)     </li>
1158)     <li>If your relay is behind a NAT and it doesn't know its public
1159)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

1160)     forwarding. Forwarding TCP connections is system dependent but

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

1162)     offers some examples on how to do this.
1163)     </li>
1164)     <li>Your relay will passively estimate and advertise its recent
1165)     bandwidth capacity, so high-bandwidth relays will attract more users than
1166)     low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
1167)     </li>
1168)     </ul>

1169) 

1170)     <hr>

1171) 

1172)     <a id="RunARelayBut"></a>
1173)     <a id="ExitPolicies"></a>

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

1175) 

1176)     <p>
1177)     Great. That's exactly why we implemented exit policies.
1178)     </p>

1179) 

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

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

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

1191)     for running an exit node with minimal harassment</a>.
1192)     </p>

1193) 

1194)     <p>

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

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

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

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

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

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

1207) 

1208)     <p>
1209)     If you do allow any exit connections, make sure name resolution works
1210)     (that is, your computer can resolve Internet addresses correctly).
1211)     If there are any resources that your computer can't reach (for example,
1212)     you are behind a restrictive firewall or content filter), please
1213)     explicitly reject them in your exit policy &mdash; otherwise Tor users
1214)     will be impacted too.
1215)     </p>

1216) 

1217)     <hr>

1218) 

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

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

1221) 

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

1228) 

1229)     <p>Being a normal relay vs being a bridge relay is almost the same
1230)     configuration: it's just a matter of whether your relay is listed
1231)     publically or not.
1232)     </p>

1233) 

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

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

1241) 

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

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

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

1249) 

1250)     <hr>

1251) 

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

1254) 
1255) <p>
1256) Great. If you want to run several relays to donate more to the network,
1257) we're happy with that. But please don't run more than a few dozen on
1258) the same network, since part of the goal of the Tor network is dispersal
1259) and diversity.
1260) </p>
1261) 
1262) <p>
1263) If you do decide to run more than one relay, please set the "MyFamily"

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

1266) </p>
1267) 
1268) <pre>
1269)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
1270) </pre>
1271) 
1272) <p>
1273) where each fingerprint is the 40 character identity fingerprint (without
1274) spaces). You can also list them by nickname, but fingerprint is safer. Be
1275) sure to prefix the digest strings with a dollar sign ('$') so that the
1276) digest is not confused with a nickname in the config file.
1277) </p>
1278) 
1279) <p>
1280) That way clients will know to avoid using more than one of your relays
1281) in a single circuit. You should set MyFamily if you have administrative
1282) control of the computers or of their network, even if they're not all in
1283) the same geographic location.
1284) </p>
1285) 
1286)     <hr>
1287) 

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

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

1290) 

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

1294) 

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

1303) 

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

1311) 

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

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

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

1317) 

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

1323) 

1324)     </ol>

1325) 

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

1330) 

1331)     <hr>

1332) 

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

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

1335) 

1336)     <p>

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

1338)     </p>
1339)     <ul>
1340)     <li>The name is not currently mapped to a different key. Existing mappings
1341)     are removed after 6 months of inactivity from a relay.</li>
1342)     <li>The relay must have been around for at least two weeks.</li>
1343)     <li>No other router may have wanted the same name in the past month.</li>
1344)     </ul>

1345) 

1346)     <hr>

1347) 

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

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

1350) 

1351)     <p>
1352)     Tor uses a variety of different keys, with three goals in mind: 1)
1353)     encryption to ensure privacy of data within the Tor network, 2)
1354)     authentication so clients know they're
1355)     talking to the relays they meant to talk to, and 3) signatures to make
1356)     sure all clients know the same set of relays.
1357)     </p>

1358) 

1359)     <p>
1360)     <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
1361)     so observers can't look inside to see which circuit a given cell is
1362)     intended for. Further, the Tor client establishes an ephemeral encryption
1363)     key with each relay in the circuit, so only the exit relay can read
1364)     the cells. Both sides discard the circuit key when the circuit ends,
1365)     so logging traffic and then breaking into the relay to discover the key
1366)     won't work.
1367)     </p>

1368) 

1369)     <p>
1370)     <b>Authentication</b>:
1371)     Every Tor relay has a public decryption key called the "onion key".
1372)     When the Tor client establishes circuits, at each step it <a
1373)     href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1374)     that the Tor relay prove knowledge of its onion key</a>. That way
1375)     the first node in the path can't just spoof the rest of the path.
1376)     Each relay rotates its onion key once a week.
1377)     </p>

1378) 

1379)     <p>
1380)     <b>Coordination</b>:
1381)     How do clients know what the relays are, and how do they know that they
1382)     have the right keys for them? Each relay has a long-term public signing
1383)     key called the "identity key". Each directory authority additionally has a
1384)     "directory signing key". The directory authorities <a

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

1386)     of all the known relays, and in that list are a set of certificates from
1387)     each relay (self-signed by their identity key) specifying their keys,
1388)     locations, exit policies, and so on. So unless the adversary can control
1389)     a threshold of the directory authorities, he can't trick the Tor client
1390)     into using other Tor relays.
1391)     </p>

1392) 

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

1399) 

1400)     <p>
1401)     How do users know they've got the right software? When we distribute
1402)     the source code or a package, we digitally sign it with <a
1403)     href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1404)     href="<page docs/verifying-signatures>">instructions
1405)     on how to check Tor's signatures</a>.
1406)     </p>

1407) 

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

1415) 

1416)     <hr>

1417) 

1418) <a id="EntryGuards"></a>
1419) <h3><a class="anchor" href="#EntryGuards">What are Entry Guards?</a></h3>
1420) 
1421) <p>
1422) Tor (like all current practical low-latency anonymity designs) fails
1423) when the attacker can see both ends of the communications channel. For

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

1426) this case, the research community knows no practical low-latency design
1427) that can reliably stop the attacker from correlating volume and timing
1428) information on the two sides.
1429) </p>
1430) 
1431) <p>
1432) So, what should we do? Suppose the attacker controls, or can observe,

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

1441) </p>
1442) 
1443) <p>
1444) The solution is "entry guards": each user selects a few relays at random

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

1452) </p>
1453) 
1454) <p>

1455) You can read more at <a href="http://freehaven.net/anonbib/#wright02">An
1456) Analysis of the Degradation of Anonymous Protocols</a>, <a
1457) href="http://freehaven.net/anonbib/#wright03">Defending Anonymous
1458) Communication Against Passive Logging Attacks</a>, and especially
1459) <a href="http://freehaven.net/anonbib/#hs-attack06">Locating Hidden
1460) Servers</a>.

1461) </p>
1462) 
1463) <p>
1464) Restricting your entry nodes may also help against attackers who want
1465) to run a few Tor nodes and easily enumerate all of the Tor user IP
1466) addresses. (Even though they can't learn what destinations the users
1467) are talking to, they still might be able to do bad things with just a

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

1470) </p>
1471) 
1472)     <hr>
1473) 

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

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

1476) 

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

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

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

1489) 

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

1498) 

1499)     <p>
1500)     There are five steps we need to address before we can do this though:
1501)     </p>

1502) 

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

1510) 

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

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

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

1521) 

1522)     <p>
1523)     Third, we need to work on scalability, both of the network (how to
1524)     stop requiring that all Tor relays be able to connect to all Tor
1525)     relays) and of the directory (how to stop requiring that all Tor
1526)     users know about all Tor relays). Changes like this can have large
1527)     impact on potential and actual anonymity. See Section 5 of the <a
1528)     href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1529)     for details. Again, UDP transport would help here.
1530)     </p>

1531) 

1532)     <p>
1533)     Fourth, we need to better understand the risks from
1534)     letting the attacker send traffic through your relay while
1535)     you're also initiating your own anonymized traffic. <a
1536)     href="http://freehaven.net/anonbib/#back01">Three</a> <a
1537)     href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1538)     <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1539)     describe ways to identify the relays in a circuit by running traffic
1540)     through candidate relays and looking for dips in the traffic while the
1541)     circuit is active. These clogging attacks are not that scary in the Tor
1542)     context so long as relays are never clients too. But if we're trying to
1543)     encourage more clients to turn on relay functionality too (whether as
1544)     <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1545)     we need to understand this threat better and learn how to mitigate it.
1546)     </p>

1547) 

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

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

1552)     thoughts on Tor incentives</a>.
1553)     </p>

1554) 

1555)     <p>
1556)     Please help on all of these!
1557)     </p>

1558) 

1559) <hr>
1560) 
1561) <a id="TransportIPnotTCP"></a>

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

1563) 
1564) <p>

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

1569) </p>
1570) 
1571) <p>

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

1576) </p>
1577) 

1578) <ol>

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

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

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

1585) </li>

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

1589) </li>
1590) <li>Certain protocols will still leak information. For example, we must
1591) rewrite DNS requests so they are delivered to an unlinkable DNS server
1592) rather than the DNS server at a user's ISP; thus, we must understand
1593) the protocols we are transporting.
1594) </li>
1595) <li><a
1596) href="http://crypto.stanford.edu/~nagendra/projects/dtls/dtls.html">DTLS</a>

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

1601) </li>
1602) <li>Exit policies for arbitrary IP packets mean building a secure
1603) IDS. Our node operators tell us that exit policies are one of the main
1604) reasons they're willing to run Tor. Adding an Intrusion Detection System
1605) to handle exit policies would increase the security complexity of Tor,
1606) and would likely not work anyway, as evidenced by the entire field of IDS
1607) and counter-IDS papers. Many potential abuse issues are resolved by the
1608) fact that Tor only transports valid TCP streams (as opposed to arbitrary
1609) IP including malformed packets and IP floods), so exit policies become
1610) even <i>more</i> important as we become able to transport IP packets. We
1611) also need to compactly describe exit policies in the Tor directory,
1612) so clients can predict which nodes will allow their packets to exit &mdash;
1613) and clients need to predict all the packets they will want to send in
1614) a session before picking their exit node!
1615) </li>

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

1620) </li>
1621) </ol>
1622) 

1623)     <hr>

1624) 

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

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

1627) 

1628)     <p>
1629)     For the answer to this question and others, please see our <a
1630)     href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1631)     </p>

1632) 

1633)     <hr>

1634) 

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

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

1637) 

1638)     <p>
1639)     A collection of templates for successfully responding to ISPs is <a

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

1641)     here</a>.
1642)     </p>

1643) 

1644)     <hr>

1645) 

1646)   </div>
1647)   <!-- END MAINCOL -->
1648)   <div id = "sidecol">
1649) #include "side.wmi"
1650) #include "info.wmi"
1651)   </div>
1652)   <!-- END SIDECOL -->
1653) </div>
1654) <!-- END CONTENT -->