tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision: 0 $
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)     </ul>
33)     
34)     <p>Compilation and Installation:</p>
35)     <ul>
36)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
37)     <li><a href="#PGPSigs">What are these "sig" files on the download
38)     page?</a></li>
39)     <li><a href="#CompileTorWindows">How do I compile Tor under Windows?</a></li>
40)     <li><a href="#VirusFalsePositives">Why does my Tor executable appear to
41)     have a virus or spyware?</a></li>
42)     <li><a href="#LiveCD">Is there a LiveCD or other bundle that includes Tor?</a></li>
43)     </ul>
44)     
45)     <p>Running Tor:</p>
46)     
47)     <p>Running a Tor client:</p>
48)     <ul>
49)     <li><a href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></li>
50)     </ul>
51)     
52)     <p>Running a Tor relay:</p>
53)     <ul>
54)     <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
55)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
56)     with abuse issues.</a></li>
57)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
58)     relay?</a></li>
59)     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?</a></li>
60)     <li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li>
61)     </ul>
62)     
63)     <p>Running a Tor hidden service:</p>
64)     
65)     <p>Anonymity and Security:</p>
66)     <ul>
67)     <li><a href="#KeyManagement">Tell me about all the keys Tor uses.</a></li>
68)     </ul>
69)     
70)     <p>Alternate designs that we don't do (yet):</p>
71)     <ul>
72)     <li><a href="#EverybodyARelay">You should make every Tor user be a
73)     relay.</a></li>
74)     </ul>
75)     
76)     <p>Abuse</p>
77)     <ul>
78)     <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
79)     <li><a href="#RespondISP">How do I respond to my ISP about my exit
80)     relay?</a></li>
81)     </ul>
82)     
83)     <p>For other questions not yet on this version of the FAQ, see the <a

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

85)     

86)     <hr>

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

113)     <hr>

114)     
115)     <a id="Torisdifferent"></a>
116)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
117)     <p>
118)     A typical proxy provider sets up a server somewhere on the Internet and allows you to use it to relay your traffic.  This creates a simple, easy to maintain architecture.  The users all enter and leave through the same server.  The provider may charge for use of the proxy, or fund their costs through advertisements on the server.  In the simplest configuration, you don't have to install anything.  You just have to point your browser at their proxy server.  Simple proxy providers are fine solutions if you do not want protections for your privacy and anonymity online and you trust the provider from doing bad things.  Some simple proxy providers use SSL to secure your connection to them.  This may protect you against local eavesdroppers, such as those at a cafe with free wifi Internet.
119)     </p>
120)     <p>
121)     Simple proxy providers also create a single point of failure.  The provider knows who you are and where you browse on the Internet.  They can see your traffic as it passes through their server.  In some cases, they can see your encrypted traffic as they relay it to your banking site or to ecommerce stores.  You have to trust the provider isn't doing any number of things, such as watching your traffic, injecting their own advertisements into your traffic stream, and isn't recording your personal details.
122)     </p>
123)     <p>
124)     Tor passes your traffic through at least 3 different servers before sending it on to the destination.  Tor does not modify, or even know, what you are sending into it.  It merely relays your traffic, completely encrypted through the Tor network and has it pop out somewhere else in the world, completely intact.  The Tor client is required because we assume you trust your local computer.  The Tor client manages the encryption and the path chosen through the network.  The relays located all over the world merely pass encrypted packets between themselves.</p>
125)     <p>
126)     <dl>
127)     <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad first of three servers can see encrypted Tor traffic coming from your computer.  It still doesn't know who you are and what you are doing over Tor.  It merely sees "This IP address is using Tor".  Tor is not illegal anywhere in the world, so using Tor by itself is fine.  You are still protected from this node figuring out who you are and where you are going on the Internet.</dd>
128)     <dt>Can't the third server see my traffic?</dt><dd>Possibly.  A bad third of three servers can see the traffic you sent into Tor.  It won't know who sent this traffic.  If you're using encryption, such as visiting a bank or e-commerce website, or encrypted mail connections, etc, it will only know the destination.  It won't be able to see the data inside the traffic stream.  You are still protected from this node figuring out who you are and if using encryption, what data you're sending to the destination.</dd>
129)     </dl>
130)     </p>
131)     

132)     <hr>

133)     
134)     <a id="CompatibleApplications"></a>
135)     <h3><a class="anchor" href="#CompatibleApplications">What programs can
136)     I use with Tor?</a></h3>
137)     
138)     <p>
139)     There are two pieces to "Torifying" a program: connection-level anonymity
140)     and application-level anonymity. Connection-level anonymity focuses on
141)     making sure the application's Internet connections get sent through Tor.
142)     This step is normally done by configuring
143)     the program to use your Tor client as a "socks" proxy, but there are
144)     other ways to do it too. For application-level anonymity, you need to
145)     make sure that the information the application sends out doesn't hurt
146)     your privacy. (Even if the connections are being routed through Tor, you
147)     still don't want to include sensitive information like your name.) This
148)     second step needs to be done on a program-by-program basis, which is
149)     why we don't yet recommend very many programs for safe use with Tor.
150)     </p>
151)     
152)     <p>
153)     Most of our work so far has focused on the Firefox web browser. The
154)     bundles on the <a href="<page download/download>">download page</a> automatically

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

156)     extension</a> if you have Firefox installed. As of version 1.2.0,
157)     Torbutton now takes care of a lot of the connection-level and
158)     application-level worries.
159)     </p>
160)     
161)     <p>
162)     There are plenty of other programs you can use with Tor,
163)     but we haven't researched the application-level anonymity
164)     issues on them well enough to be able to recommend a safe
165)     configuration. Our wiki has a list of instructions for <a

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

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

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

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

173)     <hr>

174)     
175)     <a id="WhyCalledTor"></a>
176)     <h3><a class="anchor" href="#WhyCalledTor">Why is it called Tor?</a></h3>
177)     
178)     <p>
179)     Because Tor is the onion routing network. When we were starting the
180)     new next-generation design and implementation of onion routing in
181)     2001-2002, we would tell people we were working on onion routing,
182)     and they would say "Neat. Which one?" Even if onion routing has
183)     become a standard household term, Tor was born out of the actual <a
184)     href="http://www.onion-router.net/">onion routing project</a> run by
185)     the Naval Research Lab.
186)     </p>
187)     
188)     <p>
189)     (It's also got a fine translation from German and Turkish.)
190)     </p>
191)     
192)     <p>
193)     Note: even though it originally came from an acronym, Tor is not spelled
194)     "TOR". Only the first letter is capitalized. In fact, we can usually
195)     spot people who haven't read any of our website (and have instead learned
196)     everything they know about Tor from news articles) by the fact that they
197)     spell it wrong.
198)     </p>
199)     

200)     <hr>

201)     
202)     <a id="Backdoor"></a>
203)     <h3><a class="anchor" href="#Backdoor">Is there a backdoor in Tor?</a></h3>
204)     
205)     <p>
206)     There is absolutely no backdoor in Tor. Nobody has asked us to put one
207)     in, and we know some smart lawyers who say that it's unlikely that anybody
208)     will try to make us add one in our jurisdiction (U.S.). If they do
209)     ask us, we will fight them, and (the lawyers say) probably win.
210)     </p>
211)     
212)     <p>
213)     We think that putting a backdoor in Tor would be tremendously
214)     irresponsible to our users, and a bad precedent for security software
215)     in general. If we ever put a deliberate backdoor in our security
216)     software, it would ruin our professional reputations. Nobody would
217)     trust our software ever again &mdash; for excellent reason!
218)     </p>
219)     
220)     <p>
221)     But that said, there are still plenty of subtle attacks
222)     people might try. Somebody might impersonate us, or break into our
223)     computers, or something like that. Tor is open source, and you should
224)     always check the source (or at least the diffs since the last release)
225)     for suspicious things. If we (or the distributors) don't give you
226)     source, that's a sure sign something funny might be going on. You
227)     should also check the <a href="<page docs/verifying-signatures>">PGP
228)     signatures</a> on the releases, to make sure nobody messed with the
229)     distribution sites.
230)     </p>
231)     
232)     <p>
233)     Also, there might be accidental bugs in Tor that could affect your
234)     anonymity. We periodically find and fix anonymity-related bugs, so make
235)     sure you keep your Tor versions up-to-date.
236)     </p>
237)     

238)     <hr>

239)     
240)     <a id="DistributingTor"></a>
241)     <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor on
242)     my magazine's CD?</a></h3>
243)     
244)     <p>
245)     Yes.
246)     </p>
247)     
248)     <p>
249)     The Tor software is <a href="https://www.fsf.org/">free software</a>. This
250)     means we give you the rights to redistribute the Tor software, either
251)     modified or unmodified, either for a fee or gratis. You don't have to
252)     ask us for specific permission.
253)     </p>
254)     
255)     <p>
256)     However, if you want to redistribute the Tor software you must follow our
257)     <a href="<gitblob>LICENSE">LICENSE</a>.
258)     Essentially this means that you need to include our LICENSE file along
259)     with whatever part of the Tor software you're distributing.
260)     </p>
261)     
262)     <p>
263)     Most people who ask us this question don't want to distribute just the
264)     Tor software, though. They want to distribute the Tor bundles, which
265)     typically include <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
266)     and <a href="<page projects/vidalia>">Vidalia</a>.
267)     You will need to follow the licenses for those programs
268)     as well. Both of them are distributed under the <a
269)     href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General
270)     Public License</a>. The simplest way to obey their licenses is to
271)     include the source code for these programs everywhere you include
272)     the bundles themselves. Look for "source" packages on the <a
273)     href="<page projects/vidalia>">Vidalia page</a> and the <a
274)     href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo
275)     download page</a>.
276)     </p>
277)     
278)     <p>
279)     Also, you should make sure not to confuse your readers about what Tor is,
280)     who makes it, and what properties it provides (and doesn't provide). See
281)     our <a href="<page docs/trademark-faq>">trademark FAQ</a> for details.
282)     </p>
283)     
284)     <p>
285)     Lastly, you should realize that we release new versions of the
286)     Tor software frequently, and sometimes we make backward incompatible
287)     changes. So if you distribute a particular version of the Tor software, it
288)     may not be supported &mdash; or even work &mdash; six months later. This
289)     is a fact of life for all security software under heavy development.
290)     </p>
291)     

292)     <hr>

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

337)     <hr>

338)     
339)     <a id="WhySlow"></a>
340)     <h3><a class="anchor" href="#WhySlow">Why is Tor so slow?</a></h3>
341)     
342)     <p>
343)     There are many reasons why the Tor network is currently slow.
344)     </p>
345)     
346)     <p>
347)     Before we answer, though, you should realize that Tor is never going to
348)     be blazing fast. Your traffic is bouncing through volunteers' computers
349)     in various parts of the world, and some bottlenecks and network latency
350)     will always be present. You shouldn't expect to see university-style
351)     bandwidth through Tor.
352)     </p>
353)     
354)     <p>
355)     But that doesn't mean that it can't be improved. The current Tor network
356)     is quite small compared to the number of people trying to use it, and
357)     many of these users don't understand or care that Tor can't currently
358)     handle file-sharing traffic load.
359)     </p>
360)     
361)     <p>
362)     For the much more in-depth answer, see <a

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

364)     post on the topic</a>, which includes both a detailed PDF and a video
365)     to go with it.
366)     </p>
367)     
368)     <p>
369)     What can you do to help?
370)     </p>
371)     
372)     <ul>
373)     
374)     <li>
375)     <a href="<page docs/tor-doc-relay>">Configure your Tor to relay traffic
376)     for others</a>. Help make the Tor network large enough that we can handle
377)     all the users who want privacy and security on the Internet.
378)     </li>
379)     
380)     <li>

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

382)     especially need people to help make it easier to configure your Tor
383)     as a relay. Also, we need help with clear simple documentation to
384)     walk people through setting it up.
385)     </li>
386)     
387)     <li>
388)     There are some bottlenecks in the current Tor network. Help us design
389)     experiments to track down and demonstrate where the problems are, and
390)     then we can focus better on fixing them.
391)     </li>
392)     
393)     <li>
394)     There are some steps that individuals
395)     can take to improve their Tor performance. <a

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

397)     can configure your Firefox to handle Tor better</a>, <a
398)     href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
399)     Polipo with Tor</a>, or you can try <a href="<page download/download>">upgrading
400)     to the latest version of Tor</a>.  If this works well, please help by
401)     documenting what you did, and letting us know about it.
402)     </li>
403)     
404)     <li>
405)     Tor needs some architectural changes too. One important change is to
406)     start providing <a href="#EverybodyARelay">better service to people who
407)     relay traffic</a>. We're working on this, and we'll finish faster if we
408)     get to spend more time on it.
409)     </li>
410)     
411)     <li>
412)     Help do other things so we can do the hard stuff. Please take a moment
413)     to figure out what your skills and interests are, and then <a href="<page
414)     getinvolved/volunteer>">look at our volunteer page</a>.
415)     </li>
416)     
417)     <li>
418)     Help find sponsors for Tor. Do you work at a company or government agency
419)     that uses Tor or has a use for Internet privacy, e.g. to browse the
420)     competition's websites discreetly, or to connect back to the home servers
421)     when on the road without revealing affiliations? If your organization has
422)     an interest in keeping the Tor network working, please contact them about
423)     supporting Tor. Without sponsors, Tor is going to become even slower.
424)     </li>
425)     
426)     <li>
427)     If you can't help out with any of the above, you can still help out
428)     individually by <a href="<page donate/donate>">donating a bit of money to the
429)     cause</a>. It adds up!
430)     </li>
431)     
432)     </ul>
433)     

434)     <hr>

435)     
436)     <a id="Funding"></a>
437)     <h3><a class="anchor" href="#Funding">What would The Tor Project do with
438)     more funding?</a></h3>
439)     
440)     <p>
441)     We have about 1800 relays right now, pushing over 150 MB/s average
442)     traffic. We have several hundred thousand active users. But the Tor
443)     network is not yet self-sustaining.
444)     </p>
445)     
446)     <p>
447)     There are six main development/maintenance pushes that need attention:
448)     </p>
449)     
450)     <ul>
451)     
452)     <li>
453)     Scalability: We need to keep scaling and decentralizing the Tor
454)     architecture so it can handle thousands of relays and millions of
455)     users. The upcoming stable release is a major improvement, but there's
456)     lots more to be done next in terms of keeping Tor fast and stable.
457)     </li>
458)     
459)     <li>
460)     User support: With this many users, a lot of people are asking questions
461)     all the time, offering to help out with things, and so on. We need good
462)     clean docs, and we need to spend some effort coordinating volunteers.
463)     </li>
464)     
465)     <li>
466)     Relay support: the Tor network is run by volunteers, but they still need
467)     attention with prompt bug fixes, explanations when things go wrong,
468)     reminders to upgrade, and so on. The network itself is a commons, and
469)     somebody needs to spend some energy making sure the relay operators stay
470)     happy. We also need to work on <a href="#RelayOS">stability</a> on some
471)     platforms &mdash; e.g., Tor relays have problems on Win XP currently.
472)     </li>
473)     
474)     <li>
475)     Usability: Beyond documentation, we also need to work on usability of the
476)     software itself. This includes installers, clean GUIs, easy configuration
477)     to interface with other applications, and generally automating all of
478)     the difficult and confusing steps inside Tor. We've got a start on this

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

480)     remains — usability for privacy software has never been easy.
481)     </li>
482)     
483)     <li>
484)     Incentives: We need to work on ways to encourage people to configure
485)     their Tors as relays and exit nodes rather than just clients.
486)     <a href="#EverybodyARelay">We need to make it easy to become a relay,
487)     and we need to give people incentives to do it.</a>
488)     </li>
489)     
490)     <li>
491)     Research: The anonymous communications field is full
492)     of surprises and gotchas. In our copious free time, we
493)     also help run top anonymity and privacy conferences like <a
494)     href="http://petsymposium.org/">PETS</a>. We've identified a set of
495)     critical <a href="<page getinvolved/volunteer>#Research">Tor research questions</a>
496)     that will help us figure out how to make Tor secure against the variety of
497)     attacks out there. Of course, there are more research questions waiting
498)     behind these.
499)     </li>
500)     
501)     </ul>
502)     
503)     <p>
504)     We're continuing to move forward on all of these, but at this rate
505)     <a href="#WhySlow">the Tor network is growing faster than the developers
506)     can keep up</a>.
507)     Now would be an excellent time to add a few more developers to the effort
508)     so we can continue to grow the network.
509)     </p>
510)     
511)     <p>
512)     We are also excited about tackling related problems, such as
513)     censorship-resistance.
514)     </p>
515)     
516)     <p>
517)     We are proud to have <a href="<page about/sponsors>">sponsorship and support</a>
518)     from the Omidyar Network, the International Broadcasting Bureau, Bell
519)     Security Solutions, the Electronic Frontier Foundation, several government
520)     agencies and research groups, and hundreds of private contributors.
521)     </p>
522)     
523)     <p>
524)     However, this support is not enough to keep Tor abreast of changes in the
525)     Internet privacy landscape. Please <a href="<page donate/donate>">donate</a>
526)     to the project, or <a href="<page about/contact>">contact</a> our executive
527)     director for information on making grants or major donations.
528)     </p>
529)     

530)     <hr>

531)     
532)     <a id="HowUninstallTor"></a>
533)     <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall Tor?</a></h3>
534)     
535)     <p>
536)     This depends entirely on how you installed it and which operating system you
537)     have. If you installed a package, then hopefully your package has a way to
538)     uninstall itself. The Windows packages include uninstallers. The proper way to
539)     completely remove Tor, Vidalia, Torbutton for Firefox, and Polipo on any
540)     version of Windows is as follows:
541)     </p>
542)     
543)     <ol>
544)     <li>In your taskbar, right click on Vidalia (the green onion or the black head)
545)     and choose exit.</li>
546)     <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
547)     Process List. If it's running, right click and choose End Process.</li>
548)     <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
549)     This will remove the Vidalia bundle, which includes Tor and Polipo.</li>
550)     <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
551)     Click the Uninstall button.</li>
552)     </ol>
553)     
554)     <p>
555)     If you do not follow these steps (for example by trying to uninstall
556)     Vidalia, Tor, and Polipo while they are still running), you will need to
557)     reboot and manually remove the directory "Program Files\Vidalia Bundle".
558)     </p>
559)     
560)     <p>
561)     For Mac OS X, follow the <a
562)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
563)     </p>
564)     
565)     <p>
566)     If you installed by source, I'm afraid there is no easy uninstall method. But
567)     on the bright side, by default it only installs into /usr/local/ and it should
568)     be pretty easy to notice things there.
569)     </p>
570)     

571)     <hr>

572)     
573)     <a id="PGPSigs"></a>
574)     <h3><a class="anchor" href="#PGPSigs">What are these "sig" files on the
575)     download page?</a></h3>
576)     
577)     <p>
578)     These are PGP signatures, so you can verify that the file you've downloaded is
579)     exactly the one that we intended you to get.
580)     </p>
581)     
582)     <p>
583)     Please read the <a
584)     href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
585)     </p>
586)     

587)     <hr>

588)     
589)     <a id="CompileTorWindows"></a>
590)     <h3><a class="anchor" href="#CompileTorWindows">How do I compile Tor under
591)     Windows?</a></h3>
592)     
593)     <p>
594)     Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
595)     tor-win32-mingw-creation.txt</a>.
596)     </p>
597)     
598)     <p>
599)     (Note that you don't need to compile Tor yourself in order to use
600)     it. Most people just use the packages available on the <a href="<page
601)     download/download>">download page</a>.)
602)     </p>
603)     

604)     <hr>

605)     
606)     <a id="VirusFalsePositives"></a>
607)     <h3><a class="anchor" href="#VirusFalsePositives">Why does my Tor
608)     executable appear to have a virus or spyware?</a></h3>
609)     
610)     <p>
611)     Sometimes, overzealous Windows virus and spyware detectors trigger on some
612)     parts of the Tor Windows binary. Our best guess is that these are false
613)     positives &mdash; after all, the anti-virus and anti-spyware business is just a
614)     guessing game anyway. You should contact your vendor and explain that you have
615)     a program that seems to be triggering false positives. Or pick a better vendor.
616)     </p>
617)     
618)     <p>
619)     In the meantime, we encourage you to not just take our word for
620)     it. Our job is to provide the source; if you're concerned, please do <a
621)     href="#CompileTorWindows">recompile it yourself</a>.
622)     </p>
623)     

624)     <hr>

625)     
626)     <a id="LiveCD"></a>
627)     <h3><a class="anchor" href="#LiveCD">Is there a LiveCD or other bundle that
628)     includes Tor?</a></h3>
629)     
630)     <p>
631)     There isn't any official LiveCD at this point. We're still trying to find good
632)     solutions and trying to understand the security and anonymity implications of
633)     the various options. In the mean time, feel free to check out the list below
634)     and use your best judgement:
635)     </p>
636)     
637)     <p>
638)     LiveCDs:
639)     </p>
640)     
641)     <ol>
642)     <li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
643)     System</a> is a Live System aimed at preserving your privacy and
644)     anonymity:
645)     <ul>
646)     <li> All outgoing connections to the Internet are forced to go through
647)     the Tor network.</li>
648)     <li> No trace is left on local storage devices unless explicitely asked.</li>
649)     <li> It includes Firefox, Tor, Torbutton, Vidalia graphical Tor
650)     controller, Pidgin Instant Messaging client, and lots of other
651)     software.</li>
652)     <li> It's based upon Debian gnu/linux and comes with the GNOME desktop
653)     environment.</li>
654)     </ul>
655)     <li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
656)     is Knoppix-based with an emphasis on user-friendliness. You can work
657)     anonymously or non-anonymously while TorK tries to keep you informed of the
658)     consequences of your activity. The TorK LiveCD is experimental, so the aim is
659)     to provide regular releases through 2007 and beyond.</li>
660)     <li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> is a
661)     debian based live-system including tor, firefox and torbutton which can save
662)     bookmarks and other settings or data on an encrypted usb-key</li>
663)     </li>
664)     </ol>
665)     
666)     <p>
667)     Windows bundles:
668)     </p>
669)     
670)     <ol>
671)     <li><a href="<page projects/torbrowser>">Tor Browser Bundle</a>
672)     for Windows comes with a pre-configured web browser and is self contained
673)     so you can run it from a USB stick.</li>
674)     <li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> is a successor
675)     to JanusVM. It needs testing from you!</li>
676)     <li><a href="http://janusvm.com/">JanusVM</a> is a Linux kernel and software
677)     running in VMWare that sits between your Windows computer and the Internet,
678)     making sure that your Internet traffic is scrubbed and anonymized.</li>
679)     <li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>,
680)     previously known as Torpark, is a Firefox+Tor package for Win32 that can
681)     installed on a USB key. It needs a host Win32 operating system.</li>
682)     </ol>
683)     
684)     <p>
685)     Not currently maintained as far as we know:
686)     </p>
687)     
688)     <ol>
689)     <li>Polippix / Privatlivets Fred is a Danish Knoppix-based LiveCD with Tor
690)     and utilities to encrypt IP-telephony. <a href="http://polippix.org/">Info and
691)     download</a>.</li>
692)     <li>ELE is a Linux LiveCD which is focused on privacy related
693)     software. It includes Tor and you can download it at
694)     <a
695)     href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
696)     <li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
697)     Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
698)     non-Tor traffic from accidentally leaving your computer. More information at
699)     <a

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

701)     <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
702)     than Linux for maximum security. It was designed to be anonymous and secure
703)     from the ground up, and thus has some features and limitations not found in
704)     other LiveCDs (Tor related or otherwise). You can obtain more information and
705)     download Anonym.OS from <a href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
706)     <li>Phantomix is a LiveCD for anonymous surfing and chatting based on the most
707)     recent KNOPPIX release. It comes preconfigured with Privoxy, Tor and Polipo. You can
708)     get it from the <a href="http://phantomix.ytternhagen.de/">Phantomix
709)     Website</a>.</li>
710)     </ol>
711)     
712)     <p>
713)     Please contact us if you know any others.
714)     </p>
715)     

716)     <hr>

717)     
718)     <a id="ChooseEntryExit"></a>
719)     <h3><a class="anchor" href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></h3>
720)     
721)     <p>
722)     Yes. You can set preferred entry and exit nodes as well as 
723)     inform Tor which nodes you do not want to use. 
724)     The following options can be added to your config file "torrc" 
725)     or specified on the command line:
726)     </p>
727)     <dl>
728)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
729)         <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
730)         </dd>
731)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>
732)         <dd>A list of preferred nodes to use for the last hop in the circuit, if possible. 
733)         </dd>
734)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>
735)         <dd>A list of nodes to never use when building a circuit. 
736)         </dd>
737)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>
738)         <dd>A list of nodes to never use when picking an exit. 
739)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in this list. 
740)         </dd>
741)     </dl>
742)     <p>
743)     <em>We recommend you do not use these</em> 
744)     &mdash; they are intended for testing and may disappear in future versions. 
745)     You get the best security that Tor can provide when you leave the route selection to Tor; 
746)     overriding the entry / exit nodes can mess up your anonymity in ways we don't understand.
747)     </p>
748)     <p>
749)     The <tt>EntryNodes</tt> and <tt>ExitNodes</tt> config options are treated as a request, 
750)     meaning if the nodes are down or seem slow, Tor will still avoid them. 
751)     You can make the option mandatory by setting 
752)     <tt>StrictExitNodes 1</tt> or <tt>StrictEntryNodes 1</tt> 
753)     &mdash; but if you do, your Tor connections will stop working 
754)     if all of the nodes you have specified become unreachable. 
755)     See the <a href="https://www.torproject.org/documentation.html.en#NeatLinks">Tor status pages</a> 
756)     for some nodes you might pick.
757)     </p>
758)     <p>
759)     Instead of <tt>$fingerprint</tt> you can also specify 
760)     a 2 letter ISO3166 country code in curly braces 
761)     (for example {de}), 
762)     or an ip address pattern (for example 255.254.0.0/8), 
763)     or a node nickname. 
764)     Make sure there are no spaces between the commas and the list items. 
765)     </p>
766)     <p>
767)     If you want to access a service directly through Tor's SOCKS interface 
768)     (eg. using ssh via connect.c), another option is to 
769)     set up an internal mapping in your configuration file using <tt>MapAddress</tt>. 
770)     See the manual page for details.
771)     </p>
772)     

773)     <hr>

774)     
775)     <a id="RelayFlexible"></a>
776)     <h3><a class="anchor" href="#RelayFlexible">How stable does my relay
777)     need to be?</a></h3>
778)     
779)     <p>
780)     We aim to make setting up a Tor relay easy and convenient:
781)     </p>
782)     
783)     <ul>
784)     <li>Tor has built-in support for <a

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

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

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

790)     feature</a>.
791)     </li>
792)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
793)     specifies what sort of outbound connections are allowed or refused from
794)     that relay. If you are uncomfortable allowing people to exit from your
795)     relay, you can set it up to only allow connections to other Tor relays.
796)     </li>
797)     <li>It's fine if the relay goes offline sometimes. The directories
798)     notice this quickly and stop advertising the relay. Just try to make
799)     sure it's not too often, since connections using the relay when it
800)     disconnects will break.
801)     </li>
802)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
803)     leave the Address config option blank, and Tor will try to guess.
804)     </li>
805)     <li>If your relay is behind a NAT and it doesn't know its public
806)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
807)     forwarding. Forwarding TCP connections is system dependent but 

808)     <a href="<wikifaq>#ServerForFirewalledClients">this FAQ entry</a> 

809)     offers some examples on how to do this.
810)     </li>
811)     <li>Your relay will passively estimate and advertise its recent
812)     bandwidth capacity, so high-bandwidth relays will attract more users than
813)     low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
814)     </li>
815)     </ul>
816)     

817)     <hr>

818)     
819)     <a id="RunARelayBut"></a>
820)     <a id="ExitPolicies"></a>
821)     <h3><a class="anchor" href="#ExitPolicies">I'd run a relay, but I don't
822)     want to deal with abuse issues.</a></h3>
823)     
824)     <p>
825)     Great. That's exactly why we implemented exit policies.
826)     </p>
827)     
828)     <p>
829)     Each Tor relay has an exit policy that specifies what sort of
830)     outbound connections are allowed or refused from that relay. The exit
831)     policies are propagated to Tor clients via the directory, so clients
832)     will automatically avoid picking exit relays that would refuse to
833)     exit to their intended destination. This way each relay can decide
834)     the services, hosts, and networks he wants to allow connections to,
835)     based on abuse potential and his own situation. Read the FAQ entry on 
836)     <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might encounter</a> 
837)     if you use the default exit policy, and then read Mike Perry's 

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

839)     for running an exit node with minimal harassment</a>.
840)     </p>
841)     
842)     <p>
843)     The default exit policy allows access to many popular services (e.g. web browsing), but 

844)     <a href="<wikifaq>#DefaultPorts">restricts</a>

845)     some due to abuse potential (e.g. mail) and some since
846)     the Tor network can't handle the load (e.g. default
847)     file-sharing ports). You can change your exit policy
848)     using Vidalia's "Sharing" tab, or by manually editing your 

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

850)     file. If you want to avoid most if not all abuse potential, set it to
851)     "reject *:*" (or un-check all the boxes in Vidalia). This setting means
852)     that your relay will be used for relaying traffic inside the Tor network,
853)     but not for connections to external websites or other services.
854)     </p>
855)     
856)     <p>
857)     If you do allow any exit connections, make sure name resolution works
858)     (that is, your computer can resolve Internet addresses correctly).
859)     If there are any resources that your computer can't reach (for example,
860)     you are behind a restrictive firewall or content filter), please
861)     explicitly reject them in your exit policy &mdash; otherwise Tor users
862)     will be impacted too.
863)     </p>
864)     

865)     <hr>

866)     
867)     <a id="RelayOrBridge"></a>
868)     <h3><a class="anchor" href="#RelayOrBridge">Should I be a normal relay
869)     or bridge relay?</a></h3>
870)     
871)     <p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for short)
872)     are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't listed
873)     in the main Tor directory. That means
874)     that even an ISP or government trying to filter connections to the Tor
875)     network probably won't be able to block all the bridges.
876)     </p>
877)     
878)     <p>Being a normal relay vs being a bridge relay is almost the same
879)     configuration: it's just a matter of whether your relay is listed
880)     publically or not.
881)     </p>
882)     
883)     <p>Right now, there are roughly zero places in the world that filter
884)     connections to the Tor network. So getting a lot of bridges running
885)     right now is mostly a backup measure, a) in case the Tor network does
886)     get blocked somewhere, and b) for people who want an extra layer of
887)     security because they're worried somebody will recognize that it's a
888)     public Tor relay IP address they're contacting.
889)     </p>
890)     
891)     <p>So should you run a normal relay or bridge relay? If you have
892)     lots of bandwidth, you should definitely run a normal relay &mdash;
893)     bridge relays see very little use these days. If you're willing to 
894)     <a href="#ExitPolicies">be an exit</a>, you should definitely run a normal
895)     relay, since we need more exits. If you can't be an exit and only have
896)     a little bit of bandwidth, then flip a coin. Thanks for volunteering!
897)     </p>
898)     

899)     <hr>

900)     
901)     <a id="RelayMemory"></a>
902)     <h3><a class="anchor" href="#RelayMemory">Why is my Tor relay using so
903)     much memory?</a></h3>
904)     
905)     <p>If your Tor relay is using more memory than you'd like, here are some
906)     tips for reducing its footprint:
907)     </p>
908)     
909)     <ol>
910)     <li>If you're on Linux, you may be encountering memory fragmentation
911)     bugs in glibc's malloc implementation. That is, when Tor releases memory
912)     back to the system, the pieces of memory are fragmented so they're hard
913)     to reuse. The Tor tarball ships with OpenBSD's malloc implementation,
914)     which doesn't have as many fragmentation bugs (but the tradeoff is higher
915)     CPU load). You can tell Tor to use this malloc implementation instead:
916)     <tt>./configure --enable-openbsd-malloc</tt></li>
917)     
918)     <li>If you're running a fast relay, meaning you have many TLS connections
919)     open, you are probably losing a lot of memory to OpenSSL's internal
920)     buffers (38KB+ per socket). We've patched OpenSSL to <a
921)     href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release
922)     unused buffer memory more aggressively</a>. If you update to OpenSSL
923)     1.0.0-beta5, Tor's build process will automatically recognize and use
924)     this feature.</li>
925)     
926)     <li>If you're running on Solaris, OpenBSD, NetBSD, or
927)     old FreeBSD, Tor is probably forking separate processes
928)     rather than using threads. Consider switching to a <a

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

930)     operating system</a>.</li>
931)     
932)     <li>If you still can't handle the memory load, consider reducing the
933)     amount of bandwidth your relay advertises. Advertising less bandwidth
934)     means you will attract fewer users, so your relay shouldn't grow
935)     as large. See the <tt>MaxAdvertisedBandwidth</tt> option in the man
936)     page.</li>
937)     
938)     </ol>
939)     
940)     <p>
941)     All of this said, fast Tor relays do use a lot of ram. It is not unusual
942)     for a fast exit relay to use 500-1000 MB of memory.
943)     </p>
944)     

945)     <hr>

946)     
947)     <a id="WhyNotNamed"></a>
948)     <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3>
949)     
950)     <p>

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

952)     </p>
953)     <ul>
954)     <li>The name is not currently mapped to a different key. Existing mappings
955)     are removed after 6 months of inactivity from a relay.</li>
956)     <li>The relay must have been around for at least two weeks.</li>
957)     <li>No other router may have wanted the same name in the past month.</li>
958)     </ul>
959)     

960)     <hr>

961)     
962)     <a id="KeyManagement"></a>
963)     <h3><a class="anchor" href="#KeyManagement">Tell me about all the keys
964)     Tor uses.</a></h3>
965)     
966)     <p>
967)     Tor uses a variety of different keys, with three goals in mind: 1)
968)     encryption to ensure privacy of data within the Tor network, 2)
969)     authentication so clients know they're
970)     talking to the relays they meant to talk to, and 3) signatures to make
971)     sure all clients know the same set of relays.
972)     </p>
973)     
974)     <p>
975)     <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
976)     so observers can't look inside to see which circuit a given cell is
977)     intended for. Further, the Tor client establishes an ephemeral encryption
978)     key with each relay in the circuit, so only the exit relay can read
979)     the cells. Both sides discard the circuit key when the circuit ends,
980)     so logging traffic and then breaking into the relay to discover the key
981)     won't work.
982)     </p>
983)     
984)     <p>
985)     <b>Authentication</b>:
986)     Every Tor relay has a public decryption key called the "onion key".
987)     When the Tor client establishes circuits, at each step it <a
988)     href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
989)     that the Tor relay prove knowledge of its onion key</a>. That way
990)     the first node in the path can't just spoof the rest of the path.
991)     Each relay rotates its onion key once a week.
992)     </p>
993)     
994)     <p>
995)     <b>Coordination</b>:
996)     How do clients know what the relays are, and how do they know that they
997)     have the right keys for them? Each relay has a long-term public signing
998)     key called the "identity key". Each directory authority additionally has a
999)     "directory signing key". The directory authorities <a
1000)     href="<gitblob>doc/spec/dir-spec.txt">provide a signed list</a>
1001)     of all the known relays, and in that list are a set of certificates from
1002)     each relay (self-signed by their identity key) specifying their keys,
1003)     locations, exit policies, and so on. So unless the adversary can control
1004)     a threshold of the directory authorities, he can't trick the Tor client
1005)     into using other Tor relays.
1006)     </p>
1007)     
1008)     <p>
1009)     How do clients know what the directory authorities are? The Tor software
1010)     comes with a built-in list of location and public key for each directory
1011)     authority. So the only way to trick users into using a fake Tor network
1012)     is to give them a specially modified version of the software.
1013)     </p>
1014)     
1015)     <p>
1016)     How do users know they've got the right software? When we distribute
1017)     the source code or a package, we digitally sign it with <a
1018)     href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1019)     href="<page docs/verifying-signatures>">instructions
1020)     on how to check Tor's signatures</a>.
1021)     </p>
1022)     
1023)     <p>
1024)     In order to be certain that it's really signed by us, you need to have
1025)     met us in person and gotten a copy of our GPG key fingerprint, or you
1026)     need to know somebody who has. If you're concerned about an attack on
1027)     this level, we recommend you get involved with the security community
1028)     and start meeting people.
1029)     </p>
1030)     

1031)     <hr>

1032)     
1033)     <a id="EverybodyARelay"></a>
1034)     <h3><a class="anchor" href="#EverybodyARelay">You should make every Tor
1035)     user be a relay.</a></h3>
1036)     
1037)     <p>
1038)     Requiring every Tor user to be a relay would help with scaling the

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

1040)     relay may help your anonymity</a>. However, many Tor users cannot be good
1041)     relays &mdash; for example, some Tor clients operate from behind restrictive
1042)     firewalls, connect via modem, or otherwise aren't in a position where they
1043)     can relay traffic. Providing service to these clients is a critical
1044)     part of providing effective anonymity for everyone, since many Tor users
1045)     are subject to these or similar constraints and including these clients
1046)     increases the size of the anonymity set.
1047)     </p>
1048)     
1049)     <p>
1050)     That said, we do want to encourage Tor users to run relays, so what we
1051)     really want to do is simplify the process of setting up and maintaining
1052)     a relay. We've made a lot of progress with easy configuration in the past
1053)     few years: Vidalia has an easy relay configuration interface, and supports
1054)     uPnP too. Tor is good at automatically detecting whether it's reachable and
1055)     how much bandwidth it can offer.
1056)     </p>
1057)     
1058)     <p>
1059)     There are five steps we need to address before we can do this though:
1060)     </p>
1061)     
1062)     <p>
1063)     First, we need to make Tor stable as a relay on all common
1064)     operating systems. The main remaining platform is Windows,
1065)     and we plan to finally address that in 2009. See Section 4.1 of <a
1066)     href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">our
1067)     development roadmap</a>.
1068)     </p>
1069)     
1070)     <p>
1071)     Second, we still need to get better at automatically estimating
1072)     the right amount of bandwidth to allow. See item #7 on the
1073)     <a href="<page getinvolved/volunteer>#Research">research section of the
1074)     volunteer page</a>: "Tor doesn't work very well when relays
1075)     have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a

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

1077)     to UDP transport</a> is the simplest answer here &mdash; which alas is
1078)     not a very simple answer at all.
1079)     </p>
1080)     
1081)     <p>
1082)     Third, we need to work on scalability, both of the network (how to
1083)     stop requiring that all Tor relays be able to connect to all Tor
1084)     relays) and of the directory (how to stop requiring that all Tor
1085)     users know about all Tor relays). Changes like this can have large
1086)     impact on potential and actual anonymity. See Section 5 of the <a
1087)     href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1088)     for details. Again, UDP transport would help here.
1089)     </p>
1090)     
1091)     <p>
1092)     Fourth, we need to better understand the risks from
1093)     letting the attacker send traffic through your relay while
1094)     you're also initiating your own anonymized traffic. <a
1095)     href="http://freehaven.net/anonbib/#back01">Three</a> <a
1096)     href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1097)     <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1098)     describe ways to identify the relays in a circuit by running traffic
1099)     through candidate relays and looking for dips in the traffic while the
1100)     circuit is active. These clogging attacks are not that scary in the Tor
1101)     context so long as relays are never clients too. But if we're trying to
1102)     encourage more clients to turn on relay functionality too (whether as
1103)     <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1104)     we need to understand this threat better and learn how to mitigate it.
1105)     </p>
1106)     
1107)     <p>
1108)     Fifth, we might need some sort of incentive scheme to encourage people
1109)     to relay traffic for others, and/or to become exit nodes. Here are our

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

1111)     thoughts on Tor incentives</a>.
1112)     </p>
1113)     
1114)     <p>
1115)     Please help on all of these!
1116)     </p>
1117)     

1118)     <hr>

1119)     
1120)     <a id="Criminals"></a>
1121)     <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals to do bad
1122)     things?</a></h3>
1123)     
1124)     <p>
1125)     For the answer to this question and others, please see our <a
1126)     href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1127)     </p>
1128)     

1129)     <hr>

1130)     
1131)     <a id="RespondISP"></a>
1132)     <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP about my
1133)     exit relay?</a></h3>
1134)     
1135)     <p>
1136)     A collection of templates for successfully responding to ISPs is <a

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

1138)     here</a>.
1139)     </p>
1140)     

1141)     <hr>