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)     <li><a href="#SSLcertfingerprint">What are your SSL certificate

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

36)     </ul>

37) 

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

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

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

50) 

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

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

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

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

57)     </ul>

58) 

59)     <p>Running a Tor client:</p>
60)     <ul>

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

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

73)     </ul>

74) 

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

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

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

86) 

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

88) 

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

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

93)     </ul>

94) 

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

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

101)     </ul>

102) 

103)     <p>Abuse:</p>

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

109) 

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

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

112) 

113)     <hr>

114) 

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

116) 

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

119) 

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

123) 

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

134) 

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

139) 

140)     <hr>

141) 

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

145)     A typical proxy provider sets up a server somewhere on the Internet and
146) allows you to use it to relay your traffic.  This creates a simple, easy to
147) maintain architecture.  The users all enter and leave through the same server.
148) The provider may charge for use of the proxy, or fund their costs through
149) advertisements on the server.  In the simplest configuration, you don't have to
150) install anything.  You just have to point your browser at their proxy server.
151) Simple proxy providers are fine solutions if you do not want protections for
152) your privacy and anonymity online and you trust the provider from doing bad
153) things.  Some simple proxy providers use SSL to secure your connection to them.
154) This may protect you against local eavesdroppers, such as those at a cafe with
155) free wifi Internet.
156)     </p>
157)     <p>
158)     Simple proxy providers also create a single point of failure.  The provider
159) knows who you are and where you browse on the Internet.  They can see your

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

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

165) stream, and recording your personal details.

166)     </p>
167)     <p>
168)     Tor passes your traffic through at least 3 different servers before sending

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

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

177)     <p>
178)     <dl>

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

192)     </dl>
193)     </p>

194) 

195)     <hr>

196) 

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

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

199) 

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

213) 

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

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

218)     extension</a> if you have Firefox installed. As of version 1.2.0,
219)     Torbutton now takes care of a lot of the connection-level and
220)     application-level worries.
221)     </p>

222) 

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

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

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

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

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

234) 

235)     <hr>

236) 

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

239) 

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

249) 

250)     <p>
251)     (It's also got a fine translation from German and Turkish.)
252)     </p>

253) 

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

261) 

262)     <hr>

263) 

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

266) 

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

273) 

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

281) 

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

293) 

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

299) 

300)     <hr>

301) 

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

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

304) 

305)     <p>
306)     Yes.
307)     </p>

308) 

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

315) 

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

322) 

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

338) 

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

344) 

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

352) 

353)     <hr>

354) 

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

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

357) 

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

359)     <ol>
360)     <li>Read through this <a href="<page docs/faq>">FAQ</a>.</li>
361)     <li>Read through the <a href="<page docs/documentation>">documentation</a>.</li>
362)     <li>Read through the <a

363)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">tor-talk
364)     archives</a> and

365)     see if your question is already answered.</li>
366)     <li>Join our <a href="irc://irc.oftc.net#tor">irc channel</a> and
367)     state the issue and wait for help.</li>
368)     <li>Send an email to tor-assistants at torproject.org. These are
369)     volunteers who may be able to help you but you may not get a response
370)     for days.</li>
371)     </ol>

372) 

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

375) 

376)     <hr>

377) 

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

380) 

381)     <p>
382)     There are many reasons why the Tor network is currently slow.
383)     </p>

384) 

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

392) 

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

399) 

400)     <p>
401)     For the much more in-depth answer, see <a

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

403)     post on the topic</a>, which includes both a detailed PDF and a video
404)     to go with it.
405)     </p>

406) 

407)     <p>
408)     What can you do to help?
409)     </p>

410) 

411)     <ul>

412) 

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

418) 

419)     <li>

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

421)     especially need people to help make it easier to configure your Tor
422)     as a relay. Also, we need help with clear simple documentation to
423)     walk people through setting it up.
424)     </li>

425) 

426)     <li>
427)     There are some bottlenecks in the current Tor network. Help us design
428)     experiments to track down and demonstrate where the problems are, and
429)     then we can focus better on fixing them.
430)     </li>

431) 

432)     <li>
433)     There are some steps that individuals
434)     can take to improve their Tor performance. <a

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

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

442) 

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

449) 

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

455) 

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

464) 

465)     <li>
466)     If you can't help out with any of the above, you can still help out
467)     individually by <a href="<page donate/donate>">donating a bit of money to the
468)     cause</a>. It adds up!
469)     </li>

470) 

471)     </ul>

472) 

473)     <hr>

474) 

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

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

477) 

478)     <p>
479)     We have about 1800 relays right now, pushing over 150 MB/s average
480)     traffic. We have several hundred thousand active users. But the Tor
481)     network is not yet self-sustaining.
482)     </p>

483) 

484)     <p>
485)     There are six main development/maintenance pushes that need attention:
486)     </p>

487) 

488)     <ul>

489) 

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

496) 

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

502) 

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

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

510)     </li>

511) 

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

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

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

520) 

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

527) 

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

538) 

539)     </ul>

540) 

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

548) 

549)     <p>
550)     We are also excited about tackling related problems, such as
551)     censorship-resistance.
552)     </p>

553) 

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

560) 

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

567) 

568)     <hr>
569) 

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

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

572) 

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

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

575)     <hr>

576) 

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

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

581)     <pre>

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

583)     The serial number is: 02:DA:41:04:89:A5:FD:A2:B5:DB:DB:F8:ED:15:0D:BE
584)     The SHA-1 fingerprint is: a7e70f8a648fe04a9677f13eedf6f91b5f7f2e25
585)     The SHA-256 fingerprint is: 23b854af6b96co224fd173382c520b46fa94f2d4e7238893f63ad2d783e27b4b
586) 

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

588)     The serial number is: 00:EF:A3
589)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

590)     </pre>

591)     </p>
592)     <hr>
593) 

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

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

596) 

597)     <p>
598)     This depends entirely on how you installed it and which operating system you
599)     have. If you installed a package, then hopefully your package has a way to
600)     uninstall itself. The Windows packages include uninstallers. The proper way to
601)     completely remove Tor, Vidalia, Torbutton for Firefox, and Polipo on any
602)     version of Windows is as follows:
603)     </p>

604) 

605)     <ol>
606)     <li>In your taskbar, right click on Vidalia (the green onion or the black head)
607)     and choose exit.</li>
608)     <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
609)     Process List. If it's running, right click and choose End Process.</li>
610)     <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
611)     This will remove the Vidalia bundle, which includes Tor and Polipo.</li>
612)     <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
613)     Click the Uninstall button.</li>
614)     </ol>

615) 

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

621) 

622)     <p>
623)     For Mac OS X, follow the <a
624)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
625)     </p>

626) 

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

632) 

633)     <hr>

634) 

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

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

637) 

638)     <p>
639)     These are PGP signatures, so you can verify that the file you've downloaded is
640)     exactly the one that we intended you to get.
641)     </p>

642) 

643)     <p>
644)     Please read the <a
645)     href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
646)     </p>

647) 

648) <hr>
649) 
650) <a id="GetTor"></a>
651) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
652) country. How do I download Tor?</a></h3>
653) 
654) <p>
655) Some government or corporate firewalls censor connections to Tor's
656) website. In those cases, you have three options. First, get it from

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

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

660) for the <a href="<page getinvolved/mirrors>">Tor mirrors</a> page
661) and see if any of those copies of our website work for you. Third,
662) you can download Tor via email: log in to your Gmail account and mail
663) '<tt>gettor AT torproject.org</tt>'. If you include the word 'help'
664) in the body of the email, it will reply with instructions. Note that
665) only a few webmail providers are supported, since they need to be able
666) to receive very large attachments.
667) </p>
668) 
669) <p>

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

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

673) </p>
674) 
675) <hr>

676) 

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

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

679) 

680)     <p>
681)     Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
682)     tor-win32-mingw-creation.txt</a>.
683)     </p>

684) 

685)     <p>
686)     (Note that you don't need to compile Tor yourself in order to use
687)     it. Most people just use the packages available on the <a href="<page
688)     download/download>">download page</a>.)
689)     </p>

690) 

691)     <hr>

692) 

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

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

695) 

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

703) 

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

709) 

710)     <hr>

711) 

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

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

714) 

715)     <p>

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

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

719)     </p>

720) 
721) <hr>
722) 

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

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

725) 
726) <p>
727) Tor installs a text file called torrc that contains configuration
728) instructions for how your Tor program should behave. The default
729) configuration should work fine for most Tor users. Users of Vidalia can
730) make common changes through the Vidalia interface &mdash; only advanced
731) users should need to modify their torrc file directly.
732) </p>
733) 
734) <p>
735) The location of your torrc file depends on the way you installed Tor:
736) </p>
737) 
738) <ul>
739) <li>On Windows, if you installed a Tor bundle with Vidalia, you can
740) find your torrc file in the Start menu under Programs -&gt; Vidalia
741) Bundle -&gt; Tor, or you can find it by hand in <code>\Documents and
742) Settings\<i>username</i>\Application Data\Vidalia\torrc</code>. If you
743) installed Tor without Vidalia, you can find your torrc in the Start
744) menu under Programs -&gt; Tor, or manually in either <code>\Documents
745) and Settings\Application Data\tor\torrc</code> or <code>\Documents and
746) Settings\<i>username</i>\Application Data\tor\torrc</code>.
747) </li>
748) <li>On OS X, if you use Vidalia, edit
749) <code>~/.vidalia/torrc</code>. Otherwise, open your favorite text editor
750) and load <code>/Library/Tor/torrc</code>.
751) </li>
752) <li>On Unix, if you installed a pre-built package, look for
753) <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> or consult your
754) package's documentation.
755) </li>
756) <li>Finally, if you installed from source, you may not have a torrc
757) installed yet: look in <code>/usr/local/etc/</code> and note that you
758) may need to manually copy <code>torrc.sample</code> to <code>torrc</code>.
759) </li>
760) </ul>
761) 
762) <p>
763) If you use Vidalia, be sure to exit both Tor and Vidalia before you edit
764) your torrc file. Otherwise Vidalia might overwrite your changes.
765) </p>
766) 
767) <p>
768) Once you've changed your torrc, you will need to restart Tor for the
769) changes to take effect. (For advanced users on OS X and Unix, note that
770) you actually only need to send Tor a HUP signal, not actually restart it.)
771) </p>
772) 
773) <p>
774) For other configuration options you can use, look at the <a href="<page
775) docs/tor-manual>">Tor manual page</a>. Remember, all lines beginning
776) with # in torrc are treated as comments and have no effect on Tor's
777) configuration.
778) </p>
779) 
780) <hr>
781) 

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

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

784) 
785) <p>

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

790) </p>
791) 
792) <p>
793) If you're not using Vidalia, you'll have to go find the log files by

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

795) </p>
796) 
797) <ul>
798) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
799) </li>

800) <li>On Windows, there are no default log files currently. If you enable
801) logs in your torrc file, they default to <code>\username\Application
802) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
803) </li>
804) <li>If you compiled Tor from source, by default your Tor logs to <a
805) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
806) at log-level notice. If you enable logs in your torrc file, they
807) default to <code>/usr/local/var/log/tor/</code>.

808) </li>
809) </ul>
810) 
811) <p>

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

815) </p>
816) 
817) <pre>

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

820) </pre>

821) 
822) <p>

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

824) and err level messages to a file, append the following line to the end
825) of the section:
826) </p>
827) 
828) <pre>
829) Log debug file c:/program files/tor/debug.log
830) </pre>
831) 
832) <p>

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

835) </p>
836) 
837) <hr>
838) 

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

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

841) 
842) <p>
843) Once you've installed the Tor bundle, there are two questions to ask:
844) first, is your Tor able to establish a circuit? Second, is your
845) Firefox correctly configured to send its traffic through Tor?
846) </p>
847) 
848) <p>If Tor can establish a circuit, the onion icon in
849) Vidalia will turn green. You can also check in the Vidalia
850) Control Panel to make sure it says "Connected to the Tor
851) network!" under Status. For those not using Vidalia, check your <a

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

853) a line saying that Tor "has successfully opened a circuit. Looks like
854) client functionality is working."
855) </p>
856) 
857) <p>
858) If Tor can't establish a circuit, here are some hints:
859) </p>
860) 
861) <ol>
862) <li>Are you sure Tor is running? If you're using Vidalia, you may have
863) to click on the onion and select "Start" to launch Tor.</li>
864) <li>Check your system clock. If it's more than a few hours off, Tor will
865) refuse to build circuits. For XP users, synchronize your clock under
866) the clock -&gt; Internet time tab. In addition, correct the day and date
867) under the 'Date &amp; Time' Tab.</li>
868) <li>Is your Internet connection <a

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

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

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

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

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

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

881) </ol>
882) 
883) <p>
884) Step two is to confirm that Firefox is correctly configured to send its
885) traffic through Tor. Try the <a href="https://check.torproject.org/">Tor
886) Check</a> site and see whether it thinks you are using Tor. See <a

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

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

889) </p>

890) 
891) <p>
892) If it thinks you're not using Tor, here are some hints:
893) </p>
894) 
895) <ol>
896) <li>Did you install the Torbutton extension for Firefox? The installation
897) bundles include it, but sometimes people forget to install it. Make sure
898) it says "Tor enabled" at the bottom right of your Firefox window. (For
899) expert users, make sure your http proxy is set to localhost port
900) 8118.)</li>
901) <li>Do you have incompatible Firefox extensions like FoxyProxy
902) installed? If so, uninstall them. (Note that using FoxyProxy is NOT
903) a sufficient substitute for Torbutton. There are many known attacks
904) against a browser setup that does not include Torbutton. Read more

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

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

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

923) <li>For Red Hat Linux and related systems, do you have SELinux enabled? If
924) so, it might be preventing Polipo from talking to Tor. We also run across
925) BSD users periodically who have local firewall rules that prevent some
926) connections to localhost.</li>
927) </ol>
928) 
929) <hr />
930) 
931) <a id="VidaliaPassword"></a>

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

933) 
934) <p>
935) Vidalia interacts with the Tor software via Tor's "control port". The
936) control port lets Vidalia receive status updates from Tor, request a new
937) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
938) Vidalia sets a random password for Tor's control port to prevent other
939) applications from also connecting to the control port and potentially
940) compromising your anonymity.
941) </p>
942) 
943) <p>
944) Usually this process of generating and setting a random control password
945) happens in the background. There are three common situations, though,
946) where Vidalia may prompt you for a password:
947) </p>
948) 
949) <ol>
950) <li>You're already running Vidalia and Tor. For example, this situation
951) can happen if you installed the Vidalia bundle and now you're trying to
952) run the Tor Browser Bundle. In that case, you'll need to close the old
953) Vidalia and Tor before you can run this one.
954) </li>
955) <li>Vidalia crashed, but left Tor running with the last known random
956) password. After you restart Vidalia, it generates a new random password,
957) but Vidalia can't talk to Tor, because the random passwords are different.
958) <br />
959) If the dialog that prompts you for a control password has a Reset button,
960) you can click the button and Vidalia will restart Tor with a new random
961) control password.
962) <br />
963) If you do not see a Reset button, or if Vidalia is unable to restart
964) Tor for you, you can still fix the problem manually. Simply go into your
965) process or task manager, and terminate the Tor process. Then use Vidalia
966) to restart Tor and all will work again.
967) </li>
968) <li>You had previously set Tor to run as a Windows NT service. When Tor
969) is set to
970) run as a service, it starts up when the system boots. If you configured
971) Tor to start as a service through Vidalia, a random password was set
972) and saved in Tor. When you reboot, Tor starts up and uses the random
973) password it saved. You login and start up Vidalia. Vidalia attempts to
974) talk to the already running Tor. Vidalia generates a random password,
975) but it is different than the saved password in the Tor service.
976) <br />
977) You need to reconfigure Tor to not be a service. See the FAQ entry on

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

979) for more information on how to remove the Tor service.
980) </li>
981) </ol>
982) 

983)     <hr>

984) 

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

987) 

988)     <p>

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

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

993)     </p>
994)     <dl>
995)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
996)         <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
997)         </dd>
998)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1000)         </dd>
1001)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

1003)         </dd>
1004)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1007)         </dd>
1008)     </dl>
1009)     <p>

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

1015)     </p>
1016)     <p>

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

1024)     for some nodes you might pick.
1025)     </p>
1026)     <p>

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

1031)     </p>
1032)     <p>

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

1036)     See the manual page for details.
1037)     </p>

1038) 

1039)     <hr>

1040) 
1041) <a id="GoogleCaptcha"></a>

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

1043) 
1044) <p>
1045) This is a known and intermittent problem; it does not mean that Google
1046) considers Tor to be spyware.
1047) </p>
1048) 
1049) <p>
1050) When you use Tor, you are sending queries through exit relays that are also
1051) shared by thousands of other users. Tor users typically see this message
1052) when many Tor users are querying Google in a short period of time. Google
1053) interprets the high volume of traffic from a single IP address (the exit
1054) relay you happened to pick) as somebody trying to "crawl" their website,
1055) so it slows down traffic from that IP address for a short time.
1056) </p>
1057) <p>
1058) An alternate explanation is that Google tries to detect certain
1059) kinds of spyware or viruses that send distinctive queries to Google
1060) Search. It notes the IP addresses from which those queries are received
1061) (not realizing that they are Tor exit relays), and tries to warn any
1062) connections coming from those IP addresses that recent queries indicate
1063) an infection.
1064) </p>
1065) 
1066) <p>
1067) To our knowledge, Google is not doing anything intentionally specifically
1068) to deter or block Tor use. The error message about an infected machine
1069) should clear up again after a short time.
1070) </p>
1071) 
1072) <p>
1073) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1074) automatically redirect you to a more Tor-friendly search engine such as
1075) Ixquick or Bing.
1076) </p>
1077) 
1078) <hr />
1079) 
1080) <a id="GmailWarning"></a>

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

1082) 
1083) <p>
1084) Sometimes, after you've used Gmail over Tor, Google presents a

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

1088) </p>
1089) 
1090) <p>
1091) In general this is a false alarm: Google saw a bunch of logins from

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

1095) </p>
1096) 
1097) <p>

1098) Even though this may be a biproduct of using the service via tor,
1099) that doesn't mean you can entirely ignore the warning. It is
1100) <i>probably</i> a false positive, but it might not be since it is
1101) possible for someone to hijack your Google cookie.
1102) </p>
1103) 
1104) <p>
1105) Cookie hijacking is possible by either physical access to your computer
1106) or by watching your network traffic.  In theory only physical access
1107) should compromise your system because Gmail and similar services
1108) should only send the cookie over an SSL link. In practice, alas, it's <a
1109) href="http://fscked.org/blog/fully-automated-active-https-cookie-hijacking">
1110) way more complex than that</a>.

1111) </p>
1112) 
1113) <p>
1114) And if somebody <i>did</i> steal your google cookie, they might end
1115) up logging in from unusual places (though of course they also might
1116) not). So the summary is that since you're using Tor, this security
1117) measure that Google uses isn't so useful for you, because it's full of
1118) false positives. You'll have to use other approaches, like seeing if
1119) anything looks weird on the account, or looking at the timestamps for
1120) recent logins and wondering if you actually logged in at those times.
1121) </p>
1122) 

1123) <hr>
1124) 
1125) <a id="FirewallPorts"></a>

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

1127) 
1128) <p>
1129) If your firewall works by blocking ports, then you can tell Tor to only
1130) use the ports that your firewall permits by adding "FascistFirewall 1" to

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

1132) configuration file</a>, or by clicking "My firewall only lets me connect
1133) to certain ports" in Vidalia's Network Settings window.
1134) </p>
1135) 
1136) <p>
1137) By default, when you set this Tor assumes that your firewall allows only
1138) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
1139) different set of ports with the FirewallPorts torrc option.
1140) </p>
1141) 
1142) <p>
1143) If you want to be more fine-grained with your controls, you can also
1144) use the ReachableAddresses config options, e.g.:
1145) </p>
1146) 
1147) <pre>
1148)   ReachableDirAddresses *:80
1149)   ReachableORAddresses *:443
1150) </pre>
1151) 
1152) <hr>

1153) 

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

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

1156) 

1157)     <p>
1158)     We aim to make setting up a Tor relay easy and convenient:
1159)     </p>

1160) 

1161)     <ul>
1162)     <li>Tor has built-in support for <a

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

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

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

1168)     feature</a>.
1169)     </li>
1170)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
1171)     specifies what sort of outbound connections are allowed or refused from
1172)     that relay. If you are uncomfortable allowing people to exit from your
1173)     relay, you can set it up to only allow connections to other Tor relays.
1174)     </li>
1175)     <li>It's fine if the relay goes offline sometimes. The directories
1176)     notice this quickly and stop advertising the relay. Just try to make
1177)     sure it's not too often, since connections using the relay when it
1178)     disconnects will break.
1179)     </li>
1180)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
1181)     leave the Address config option blank, and Tor will try to guess.
1182)     </li>
1183)     <li>If your relay is behind a NAT and it doesn't know its public
1184)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

1185)     forwarding. Forwarding TCP connections is system dependent but

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

1187)     offers some examples on how to do this.
1188)     </li>
1189)     <li>Your relay will passively estimate and advertise its recent
1190)     bandwidth capacity, so high-bandwidth relays will attract more users than
1191)     low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
1192)     </li>
1193)     </ul>

1194) 

1195)     <hr>

1196) 

1197)     <a id="RunARelayBut"></a>
1198)     <a id="ExitPolicies"></a>

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

1200) 

1201)     <p>
1202)     Great. That's exactly why we implemented exit policies.
1203)     </p>

1204) 

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

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

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

1216)     for running an exit node with minimal harassment</a>.
1217)     </p>

1218) 

1219)     <p>

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

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

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

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

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

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

1232) 

1233)     <p>
1234)     If you do allow any exit connections, make sure name resolution works
1235)     (that is, your computer can resolve Internet addresses correctly).
1236)     If there are any resources that your computer can't reach (for example,
1237)     you are behind a restrictive firewall or content filter), please
1238)     explicitly reject them in your exit policy &mdash; otherwise Tor users
1239)     will be impacted too.
1240)     </p>

1241) 

1242)     <hr>

1243) 

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

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

1246) 

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

1253) 

1254)     <p>Being a normal relay vs being a bridge relay is almost the same
1255)     configuration: it's just a matter of whether your relay is listed
1256)     publically or not.
1257)     </p>

1258) 

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

1265)     </p>

1266) 

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

1274)     </p>

1275) 

1276)     <hr>

1277) 

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

1280) 
1281) <p>
1282) Great. If you want to run several relays to donate more to the network,
1283) we're happy with that. But please don't run more than a few dozen on
1284) the same network, since part of the goal of the Tor network is dispersal
1285) and diversity.
1286) </p>
1287) 
1288) <p>
1289) If you do decide to run more than one relay, please set the "MyFamily"

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

1292) </p>
1293) 
1294) <pre>
1295)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
1296) </pre>
1297) 
1298) <p>
1299) where each fingerprint is the 40 character identity fingerprint (without
1300) spaces). You can also list them by nickname, but fingerprint is safer. Be
1301) sure to prefix the digest strings with a dollar sign ('$') so that the
1302) digest is not confused with a nickname in the config file.
1303) </p>
1304) 
1305) <p>
1306) That way clients will know to avoid using more than one of your relays
1307) in a single circuit. You should set MyFamily if you have administrative
1308) control of the computers or of their network, even if they're not all in
1309) the same geographic location.
1310) </p>
1311) 
1312)     <hr>
1313) 

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

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

1316) 

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

1320) 

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

1329) 

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

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

1334)     unused buffer memory more aggressively</a>. If you update to OpenSSL
1335)     1.0.0-beta5, Tor's build process will automatically recognize and use
1336)     this feature.</li>

1337) 

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

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

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

1343) 

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

1349) 

1350)     </ol>

1351) 

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

1356) 

1357)     <hr>

1358) 

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

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

1361) 

1362)     <p>

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

1364)     </p>
1365)     <ul>
1366)     <li>The name is not currently mapped to a different key. Existing mappings
1367)     are removed after 6 months of inactivity from a relay.</li>
1368)     <li>The relay must have been around for at least two weeks.</li>
1369)     <li>No other router may have wanted the same name in the past month.</li>
1370)     </ul>

1371) 

1372)     <hr>

1373) 

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

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

1376) 

1377)     <p>
1378)     Tor uses a variety of different keys, with three goals in mind: 1)
1379)     encryption to ensure privacy of data within the Tor network, 2)
1380)     authentication so clients know they're
1381)     talking to the relays they meant to talk to, and 3) signatures to make
1382)     sure all clients know the same set of relays.
1383)     </p>

1384) 

1385)     <p>
1386)     <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
1387)     so observers can't look inside to see which circuit a given cell is
1388)     intended for. Further, the Tor client establishes an ephemeral encryption
1389)     key with each relay in the circuit, so only the exit relay can read
1390)     the cells. Both sides discard the circuit key when the circuit ends,
1391)     so logging traffic and then breaking into the relay to discover the key
1392)     won't work.
1393)     </p>

1394) 

1395)     <p>
1396)     <b>Authentication</b>:
1397)     Every Tor relay has a public decryption key called the "onion key".
1398)     When the Tor client establishes circuits, at each step it <a
1399)     href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1400)     that the Tor relay prove knowledge of its onion key</a>. That way
1401)     the first node in the path can't just spoof the rest of the path.
1402)     Each relay rotates its onion key once a week.
1403)     </p>

1404) 

1405)     <p>
1406)     <b>Coordination</b>:
1407)     How do clients know what the relays are, and how do they know that they
1408)     have the right keys for them? Each relay has a long-term public signing
1409)     key called the "identity key". Each directory authority additionally has a
1410)     "directory signing key". The directory authorities <a

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

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

1418) 

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

1425) 

1426)     <p>
1427)     How do users know they've got the right software? When we distribute
1428)     the source code or a package, we digitally sign it with <a
1429)     href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1430)     href="<page docs/verifying-signatures>">instructions
1431)     on how to check Tor's signatures</a>.
1432)     </p>

1433) 

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

1441) 

1442)     <hr>

1443) 

1444) <a id="EntryGuards"></a>
1445) <h3><a class="anchor" href="#EntryGuards">What are Entry Guards?</a></h3>
1446) 
1447) <p>
1448) Tor (like all current practical low-latency anonymity designs) fails
1449) when the attacker can see both ends of the communications channel. For

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

1452) this case, the research community knows no practical low-latency design
1453) that can reliably stop the attacker from correlating volume and timing
1454) information on the two sides.
1455) </p>
1456) 
1457) <p>
1458) So, what should we do? Suppose the attacker controls, or can observe,

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

1467) </p>
1468) 
1469) <p>

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

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

1478) </p>
1479) 
1480) <p>

1481) You can read more at <a href="http://freehaven.net/anonbib/#wright02">An
1482) Analysis of the Degradation of Anonymous Protocols</a>, <a
1483) href="http://freehaven.net/anonbib/#wright03">Defending Anonymous
1484) Communication Against Passive Logging Attacks</a>, and especially
1485) <a href="http://freehaven.net/anonbib/#hs-attack06">Locating Hidden
1486) Servers</a>.

1487) </p>
1488) 
1489) <p>
1490) Restricting your entry nodes may also help against attackers who want
1491) to run a few Tor nodes and easily enumerate all of the Tor user IP
1492) addresses. (Even though they can't learn what destinations the users
1493) are talking to, they still might be able to do bad things with just a

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

1496) </p>
1497) 
1498)     <hr>
1499) 

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

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

1502) 

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

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

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

1515) 

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

1524) 

1525)     <p>
1526)     There are five steps we need to address before we can do this though:
1527)     </p>

1528) 

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

1536) 

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

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

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

1547) 

1548)     <p>
1549)     Third, we need to work on scalability, both of the network (how to
1550)     stop requiring that all Tor relays be able to connect to all Tor
1551)     relays) and of the directory (how to stop requiring that all Tor
1552)     users know about all Tor relays). Changes like this can have large
1553)     impact on potential and actual anonymity. See Section 5 of the <a
1554)     href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1555)     for details. Again, UDP transport would help here.
1556)     </p>

1557) 

1558)     <p>
1559)     Fourth, we need to better understand the risks from
1560)     letting the attacker send traffic through your relay while
1561)     you're also initiating your own anonymized traffic. <a
1562)     href="http://freehaven.net/anonbib/#back01">Three</a> <a
1563)     href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1564)     <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1565)     describe ways to identify the relays in a circuit by running traffic
1566)     through candidate relays and looking for dips in the traffic while the
1567)     circuit is active. These clogging attacks are not that scary in the Tor
1568)     context so long as relays are never clients too. But if we're trying to
1569)     encourage more clients to turn on relay functionality too (whether as
1570)     <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1571)     we need to understand this threat better and learn how to mitigate it.
1572)     </p>

1573) 

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

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

1578)     thoughts on Tor incentives</a>.
1579)     </p>

1580) 

1581)     <p>
1582)     Please help on all of these!
1583)     </p>

1584) 

1585) <hr>
1586) 
1587) <a id="TransportIPnotTCP"></a>

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

1589) 
1590) <p>

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

1595) </p>
1596) 
1597) <p>

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

1602) </p>
1603) 

1604) <ol>

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

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

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

1611) </li>

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

1615) </li>
1616) <li>Certain protocols will still leak information. For example, we must
1617) rewrite DNS requests so they are delivered to an unlinkable DNS server
1618) rather than the DNS server at a user's ISP; thus, we must understand
1619) the protocols we are transporting.
1620) </li>
1621) <li><a
1622) href="http://crypto.stanford.edu/~nagendra/projects/dtls/dtls.html">DTLS</a>

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

1627) </li>
1628) <li>Exit policies for arbitrary IP packets mean building a secure
1629) IDS. Our node operators tell us that exit policies are one of the main
1630) reasons they're willing to run Tor. Adding an Intrusion Detection System
1631) to handle exit policies would increase the security complexity of Tor,
1632) and would likely not work anyway, as evidenced by the entire field of IDS
1633) and counter-IDS papers. Many potential abuse issues are resolved by the
1634) fact that Tor only transports valid TCP streams (as opposed to arbitrary
1635) IP including malformed packets and IP floods), so exit policies become
1636) even <i>more</i> important as we become able to transport IP packets. We
1637) also need to compactly describe exit policies in the Tor directory,
1638) so clients can predict which nodes will allow their packets to exit &mdash;
1639) and clients need to predict all the packets they will want to send in
1640) a session before picking their exit node!
1641) </li>

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

1646) </li>
1647) </ol>
1648) 

1649)     <hr>

1650) 

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

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

1653) 

1654)     <p>
1655)     For the answer to this question and others, please see our <a
1656)     href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1657)     </p>

1658) 

1659)     <hr>

1660) 

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

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

1663) 

1664)     <p>
1665)     A collection of templates for successfully responding to ISPs is <a

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

1667)     here</a>.
1668)     </p>

1669) 

1670)     <hr>

1671) 

1672)   </div>
1673)   <!-- END MAINCOL -->
1674)   <div id = "sidecol">
1675) #include "side.wmi"
1676) #include "info.wmi"
1677)   </div>
1678)   <!-- END SIDECOL -->
1679) </div>
1680) <!-- END CONTENT -->