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
21) proxies?</a></li>

22)     <li><a href="#CompatibleApplications">What programs can I use with
23)     Tor?</a></li>
24)     <li><a href="#WhyCalledTor">Why is it called Tor?</a></li>
25)     <li><a href="#Backdoor">Is there a backdoor in Tor?</a></li>

26)     <li><a href="#DistributingTor">Can I distribute Tor?</a></li>

27)     <li><a href="#SupportMail">How can I get support?</a></li>

28)     <li><a href="#Forum">Is there a Tor forum?</a></li>

29)     <li><a href="#WhySlow">Why is Tor so slow?</a></li>

30)     <li><a href="#FileSharing">How can I share files anonymously through Tor?
31)     </a></li>
32)     <li><a href="#OutboundPorts">Do I have to open all these outbound ports 
33)     on my firewall?</a></li>

34)     <li><a href="#Funding">What would The Tor Project do with more
35)     funding?</a></li>

36)     <li><a href="#IsItWorking">How can I tell if Tor is working, and that my 
37)     connections really are anonymized?</a></li>

38)     <li><a href="#FTP">How do I use my browser for ftp with Tor?</a></li>

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

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

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

43)     </ul>

44) 

45)     <p>Compilation and Installation:</p>
46)     <ul>
47)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
48)     <li><a href="#PGPSigs">What are these "sig" files on the download
49)     page?</a></li>

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

52)     <li><a href="#CompileTorWindows">How do I compile Tor under
53) Windows?</a></li>
54)     <li><a href="#VirusFalsePositives">Why does my Tor executable appear
55) to

56)     have a virus or spyware?</a></li>

57)     <li><a href="#LiveCD">Is there a LiveCD or other bundle that
58) includes Tor?</a></li>

59)     </ul>

60) 

61)     <p>Tor Browser Bundle:</p>
62)     <ul>

63) 

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

66)     <li><a href="#Ubuntu">I'm using Ubuntu and I can't start Tor Browser
67)     </a></li>

68)     <li><a href="#TBBSocksPort">I want to

69)     run another application through the Tor launched by Tor Browser

70)     Bundle.</a></li>

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

73)     <li><a href="#TBBOtherExtensions">Can I install other Firefox

74)     extensions? Which extensions should I avoid using?</a></li>

75)     <li><a href="#TBBJavaScriptEnabled">Why is NoScript configured to
76) allow JavaScript by default in the Tor Browser Bundle?  Isn't that
77) unsafe?</a></li>

78)     <li><a href="#TBBOtherBrowser">I want to use Chrome/IE/Opera/etc
79)     with Tor.</a></li>

80)     <li><a href="#TorbuttonOtherBrowser">Will Torbutton be available for other browsers?</a></li>

81)     <li><a href="#TBBCloseBrowser">I want to leave Tor Browser Bundle
82)     running but close the browser.</a></li>
83) 

84)     <li><a href="#GoogleCAPTCHA">Google makes me solve a CAPTCHA or

85) tells

86)     me I have spyware installed.</a></li>

87)     <li><a href="#ForeignLanguages">Why does Google show up in foreign 
88)     languages?</li></a>

89)     <li><a href="#GmailWarning">Gmail warns me that my account may have
90)     been compromised.</a></li>

91)     <li><a href="#NeedToUseAProxy">My internet connection requires an HTTP 
92)     or SOCKS Proxy</a></li>

93)     <li><a href="#CantSetProxy">What should I do if I can't set a proxy 
94)     with my application?</a></li>
95)     <li><a href="#WarningsAboutSOCKSandDNSInformationLeaks">I keep seeing 
96)     these warnings about SOCKS and DNS information leaks. Should I 
97)     worry?</a></li>

98)     <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia) 
99)     go?</a></li>
100)     <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
101)     <li><a href="#VerifyDownload">How do I verify the download 
102)     (sha256sums.txt)?</a></li>
103)     <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close 
104)     all my open tabs?</a></li>
105)     <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay 
106)     or bridge?</a></li>
107)     <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>
108)     <li><a href="#SourceCode">Where is the source code for the bundle? How do 
109)     I verify a build?</a></li>

110)     </ul>
111) 
112)     <p>Advanced Tor usage:</p>

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

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

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

118)     <li><a href="#LogLevel">What log level should I use?</a></li>

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

121)     <li><a href="#TorCrash">My Tor keeps crashing.</a></li>

122)     <li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at
123)     start.</a></li>

124)     <li><a href="#ChooseEntryExit">Can I control which nodes (or
125) country)

126)     are used for entry/exit?</a></li>

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

129)     <li><a href="#DefaultExitPorts">Is there a list of default exit ports?</a></li>

130)     <li><a href="#SocksAndDNS">How do I check if my application that uses 
131)     SOCKS is leaking DNS requests?</a></li>
132)     <li><a href="#DifferentComputer">I want to run my Tor client on a 
133)     different computer than my applications.</a></li>
134)     <li><a href="#ServerClient">Can I install Tor on a central server, and 
135)     have my clients connect to it?</a></li>
136)     <li><a href="#JoinTheNetwork">So I can just configure a nickname and 
137)     ORPort and join the network?</a></li>

138)     </ul>

139) 

140)     <p>Running a Tor relay:</p>
141)     <ul>

142) 
143)     <li><a href="#HowDoIDecide">How do I decide if I should run a relay?
144)     </a></li>

145)     <li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being 
146)     used more?</a></li>

147)     <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li>
148)     <li><a href="#ModemKeepsCrashing">My cable/dsl modem keeps crashing. 
149)     What's going on?</a></li>
150)     <li><a href="#PortscannedMore">Why do I get portscanned more often 
151)     when I run a Tor relay?</a></li>
152)     <li><a href="#MoreThanOneCPU">I have more than one CPU. Does this 
153)     help?</a></li>

154)     <li><a href="#HighCapacityConnection">How can I get Tor to fully 
155)     make use of my high capacity connection?</a></li>

156)     <li><a href="#RelayFlexible">How stable does my relay need to
157) be?</a></li>

158)     <li><a href="#BandwidthShaping">What bandwidth shaping options are 
159)     available to Tor relays?</a></li>
160)     <li><a href="#LimitTotalBandwidth">How can I limit the total amount 
161)     of bandwidth used by my Tor relay?</a></li>
162)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal

163)     with abuse issues.</a></li>
164)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
165)     relay?</a></li>

166)     <li><a href="#UpgradeOrMove">I want to upgrade/move my relay. How do I 
167)     keep the same key?</a></li>

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

170)     <li><a href="#NTService">How do I run my Tor relay as an NT service?
171)     </a></li>
172)     <li><a href="#VirtualServer">Can I run a Tor relay from my virtual server 
173)     account?</a></li>

174)     <li><a href="#WrongIP">My relay is picking the wrong IP address.</a></li>
175)     <li><a href="#BehindANAT">I'm behind a NAT/Firewall</a></li>

176)     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?
177)     </a></li>
178)     <li><a href="#BetterAnonymity">Do I get better anonymity if I run a relay?
179)     </a></li>

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

182)     </ul>

183) 

184)     <p>Tor hidden services:</p>
185)     <ul>
186)     <li><a href="#AccessHiddenServices">How do I access hidden services?</a></li>
187)     <li><a href="#ProvideAHiddenService">How do I provide a hidden service</a></li>
188)     </ul>

189) 

190)     <p>Development</p>
191)     <ul>
192)     <li><a href="#WhoIsResponsible">Who is responsible for Tor?</a></li>
193)     <li><a href="#VersionNumbers">What do these weird version numbers 
194)     mean?</a></li>
195)     <li><a href="#PrivateTorNetwork">How do I set up my own private
196)     Tor network?</a></li>
197)     <li><a href="#UseTorWithJava">How can I make my Java program use the 
198)     Tor network?</a></li>
199)     <li><a href="#WhatIsLibevent">What is Libevent?</a></li>
200)     <li><a href="#MyNewFeature">What do I need to do to get a new feature 
201)     into Tor?</a></li>
202)     </ul>
203) 

204)     <p>Anonymity and Security:</p>
205)     <ul>

206)     <li><a href="#WhatProtectionsDoesTorProvide">What protections does Tor 
207)     provide?</a></li>
208)     <li><a href="#CanExitNodesEavesdrop">Can exit nodes eavesdrop on 
209)     communications? Isn't that bad? </a></li>

210)     <li><a href="#AmITotallyAnonymous">So I'm totally anonymous if I use 
211)     Tor?</a></li>

212)     <li><a href="#ExitEnclaving">What is Exit Enclaving?</a></li>

213)     <li><a href="#KeyManagement">Tell me about all the keys Tor
214) uses.</a></li>

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

216)     <li><a href="#ChangePaths">How often does Tor change its paths?</a></li>

217)     <li><a href="#CellSize">Tor uses hundreds of bytes for every IRC line. I 
218)     can't afford that!</a></li>
219)     <li><a href="#OutboundConnections">Why does netstat show these outbound 
220)     connections?</a></li>
221)     <li><a href="#PowerfulBlockers">What about powerful blocking mechanisms
222)     </a></li>
223)     <li><a href="#RemotePhysicalDeviceFingerprinting">Does Tor resist 
224)     "remote physical device fingerprinting"?</a></li>

225)     <li><a href="#VPN">What's safer, Tor or a VPN?</a></li>
226)     <li><a href="#Proxychains">Aren't 10 proxies (proxychains) better than 
227)     Tor with only 3 hops?</a></li>

228)     <li><a href="#AttacksOnOnionRouting">What attacks remain against onion 
229)     routing?</a></li>

230)     </ul>

231) 

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

236)     <li><a href="#TransportIPnotTCP">You should transport all IP
237) packets,

238)     not just TCP packets.</a></li>

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

241)     <li><a href="#ChoosePathLength">You should let people choose their path 
242)     length.</a></li>
243)     <li><a href="#SplitEachConnection">You should split each connection over 
244)     many paths.</a></li>
245)     <li><a href="#UnallocatedNetBlocks">Your default exit policy should block 
246)     unallocated net blocks too.</a></li>
247)     <li><a href="#BlockWebsites">Exit policies should be able to block 
248)     websites, not just IP addresses.</a></li>
249)     <li><a href="#BlockContent">You should change Tor to prevent users from 
250)     posting certain content.</a></li>

251)     <li><a href="#SendPadding">You should send padding so it's more secure.
252)     </a></li>
253)     <li><a href="#Steganography">You should use steganography to hide Tor 
254)     traffic.</a></li>

255)     <li><a href="#IPv6">Tor should support IPv6.</a></li>

256)     </ul>

257) 

258)     <p>Abuse:</p>

259)     <ul>

260)     <li><a href="#Criminals">Doesn't Tor enable criminals to do bad
261) things?</a></li>

262)     <li><a href="#RespondISP">How do I respond to my ISP about my exit
263)     relay?</a></li>

264)     <li><a href="#HelpPoliceOrLawyers">I have questions about
265)    a Tor IP address for a legal case.</a></li>

266)     </ul>

267) 

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

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

271) 

272)     <hr>

273) 

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

275) 

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

278) 

279)     <p>
280)     The name "Tor" can refer to several different components.
281)     </p>

282) 

283)     <p>

284)     The Tor software is a program you can run on your computer that
285) helps keep
286)     you safe on the Internet. Tor protects you by bouncing your
287) communications

288)     around a distributed network of relays run by volunteers all around

289)     the world: it prevents somebody watching your Internet connection
290) from

291)     learning what sites you visit, and it prevents the sites you visit

292)     from learning your physical location. This set of volunteer relays
293) is
294)     called the Tor network. You can read more about how Tor works on the
295) <a

296)     href="<page about/overview>">overview page</a>.
297)     </p>

298) 

299)     <p>

300)     The Tor Project is a non-profit (charity) organization that
301) maintains

302)     and develops the Tor software.
303)     </p>

304) 

305)     <hr>

306) 

307)     <a id="Torisdifferent"></a>

308)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different
309) from other proxies?</a></h3>
310)     <p>
311)     A typical proxy provider sets up a server somewhere on the Internet
312) and
313) allows you to use it to relay your traffic.  This creates a simple, easy
314) to
315) maintain architecture.  The users all enter and leave through the same
316) server.
317) The provider may charge for use of the proxy, or fund their costs
318) through
319) advertisements on the server.  In the simplest configuration, you don't
320) have to
321) install anything.  You just have to point your browser at their proxy
322) server.
323) Simple proxy providers are fine solutions if you do not want protections
324) for
325) your privacy and anonymity online and you trust the provider from doing
326) bad
327) things.  Some simple proxy providers use SSL to secure your connection
328) to them.
329) This may protect you against local eavesdroppers, such as those at a
330) cafe with

331) free wifi Internet.
332)     </p>
333)     <p>

334)     Simple proxy providers also create a single point of failure.  The
335) provider
336) knows who you are and where you browse on the Internet.  They can see
337) your
338) traffic as it passes through their server.  In some cases, they can even
339) see

340) inside your

341) encrypted traffic as they relay it to your banking site or to ecommerce
342) stores.

343) You have to trust the provider isn't doing any number of things, such as

344) watching your traffic, injecting their own advertisements into your
345) traffic

346) stream, and recording your personal details.

347)     </p>
348)     <p>

349)     Tor passes your traffic through at least 3 different servers before
350) sending
351) it on to the destination. Because there's a separate layer of encryption
352) for
353) each of the three relays, Tor does not modify, or even know, what you
354) are
355) sending into it.  It merely relays your traffic, completely encrypted
356) through
357) the Tor network and has it pop out somewhere else in the world,
358) completely
359) intact.  The Tor client is required because we assume you trust your
360) local
361) computer.  The Tor client manages the encryption and the path chosen
362) through
363) the network.  The relays located all over the world merely pass
364) encrypted

365) packets between themselves.</p>

366)     <p>
367)     <dl>

368)     <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad
369) first of
370) three servers can see encrypted Tor traffic coming from your computer.
371) It
372) still doesn't know who you are and what you are doing over Tor.  It
373) merely sees
374) "This IP address is using Tor".  Tor is not illegal anywhere in the
375) world, so
376) using Tor by itself is fine.  You are still protected from this node
377) figuring

378) out who you are and where you are going on the Internet.</dd>

379)     <dt>Can't the third server see my traffic?</dt><dd>Possibly.  A bad
380) third
381) of three servers can see the traffic you sent into Tor.  It won't know
382) who sent

383) this traffic.  If you're using encryption, such as visiting a bank or

384) e-commerce website, or encrypted mail connections, etc, it will only
385) know the
386) destination.  It won't be able to see the data inside the traffic
387) stream.  You

388) are still protected from this node figuring out who you are and if using
389) encryption, what data you're sending to the destination.</dd>

390)     </dl>
391)     </p>

392) 

393)     <hr>

394) 

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

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

398) 

399)     <p>

400)     If you want to use Tor with a web browser, we provide the Tor Browser 
401)     Bundle, which includes everything you need to browse the web safely using 
402)     Tor. If you want to use another web browser with Tor, see <a 
403)     href="#TBBOtherBrowser">Other web browsers</a>. 

404)     </p>
405)     <p>
406)     There are plenty of other programs you can use with Tor,
407)     but we haven't researched the application-level anonymity

408)     issues on all of them well enough to be able to recommend a safe

409)     configuration. Our wiki has a list of instructions for <a

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

411)     specific applications</a>.

412)     Please add to these lists and help us keep them accurate!
413)     </p>

414) 

415)     <hr>

416) 

417)     <a id="WhyCalledTor"></a>

418)     <h3><a class="anchor" href="#WhyCalledTor">Why is it called
419) Tor?</a></h3>

420) 

421)     <p>
422)     Because Tor is the onion routing network. When we were starting the
423)     new next-generation design and implementation of onion routing in
424)     2001-2002, we would tell people we were working on onion routing,
425)     and they would say "Neat. Which one?" Even if onion routing has
426)     become a standard household term, Tor was born out of the actual <a
427)     href="http://www.onion-router.net/">onion routing project</a> run by
428)     the Naval Research Lab.
429)     </p>

430) 

431)     <p>
432)     (It's also got a fine translation from German and Turkish.)
433)     </p>

434) 

435)     <p>

436)     Note: even though it originally came from an acronym, Tor is not
437) spelled

438)     "TOR". Only the first letter is capitalized. In fact, we can usually

439)     spot people who haven't read any of our website (and have instead
440) learned
441)     everything they know about Tor from news articles) by the fact that
442) they

443)     spell it wrong.
444)     </p>

445) 

446)     <hr>

447) 

448)     <a id="Backdoor"></a>

449)     <h3><a class="anchor" href="#Backdoor">Is there a backdoor in
450) Tor?</a></h3>

451) 

452)     <p>

453)     There is absolutely no backdoor in Tor. Nobody has asked us to put
454) one
455)     in, and we know some smart lawyers who say that it's unlikely that
456) anybody

457)     will try to make us add one in our jurisdiction (U.S.). If they do
458)     ask us, we will fight them, and (the lawyers say) probably win.
459)     </p>

460) 

461)     <p>
462)     We think that putting a backdoor in Tor would be tremendously

463)     irresponsible to our users, and a bad precedent for security
464) software

465)     in general. If we ever put a deliberate backdoor in our security
466)     software, it would ruin our professional reputations. Nobody would
467)     trust our software ever again — for excellent reason!
468)     </p>

469) 

470)     <p>
471)     But that said, there are still plenty of subtle attacks
472)     people might try. Somebody might impersonate us, or break into our

473)     computers, or something like that. Tor is open source, and you
474) should
475)     always check the source (or at least the diffs since the last
476) release)

477)     for suspicious things. If we (or the distributors) don't give you
478)     source, that's a sure sign something funny might be going on. You
479)     should also check the <a href="<page docs/verifying-signatures>">PGP
480)     signatures</a> on the releases, to make sure nobody messed with the
481)     distribution sites.
482)     </p>

483) 

484)     <p>
485)     Also, there might be accidental bugs in Tor that could affect your

486)     anonymity. We periodically find and fix anonymity-related bugs, so
487) make

488)     sure you keep your Tor versions up-to-date.
489)     </p>

490) 

491)     <hr>

492) 

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

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

496) 

497)     <p>
498)     Yes.
499)     </p>

500) 

501)     <p>

502)     The Tor software is <a href="https://www.fsf.org/">free
503) software</a>. This
504)     means we give you the rights to redistribute the Tor software,
505) either
506)     modified or unmodified, either for a fee or gratis. You don't have
507) to

508)     ask us for specific permission.
509)     </p>

510) 

511)     <p>

512)     However, if you want to redistribute the Tor software you must
513) follow our

514)     <a href="<gitblob>LICENSE">LICENSE</a>.

515)     Essentially this means that you need to include our LICENSE file
516) along

517)     with whatever part of the Tor software you're distributing.
518)     </p>

519) 

520)     <p>

521)     Most people who ask us this question don't want to distribute just
522) the

523)     Tor software, though. They want to distribute the <a

524)     href="<page projects/torbrowser>">Tor Browser</a>. This includes <a

525)     href="https://www.mozilla.org/en-US/firefox/all-aurora.html">Mozilla
526)     Aurora</a> and <a href="<page projects/vidalia>">Vidalia</a>.

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

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

536)     </p>

537) 

538)     <p>

539)     Also, you should make sure not to confuse your readers about what
540) Tor is,
541)     who makes it, and what properties it provides (and doesn't provide).
542) See
543)     our <a href="<page docs/trademark-faq>">trademark FAQ</a> for
544) details.

545)     </p>

546) 

547)     <p>
548)     Lastly, you should realize that we release new versions of the
549)     Tor software frequently, and sometimes we make backward incompatible

550)     changes. So if you distribute a particular version of the Tor
551) software, it
552)     may not be supported — or even work — six months later.
553) This

554)     is a fact of life for all security software under heavy development.
555)     </p>

556) 

557)     <hr>

558) 

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

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

562) 

563)     <p>Your best bet is to first try the following:</p>

564)     <ol>
565)     <li>Read through this <a href="<page docs/faq>">FAQ</a>.</li>

566)     <li>Read through the <a href="<page
567) docs/documentation>">documentation</a>.</li>

568)     <li>Read through the <a

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

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

573)     <li>Join our <a href="ircs://irc.torproject.org#tor">irc channel</a>
574) and

575)     state the issue and wait for help.</li>

576)     <li>Send an email to <a

577) 
578) href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.</li>
579)     <li>If all else fails, try <a href="<page about/contact>">contacting
580) us</a> directly.</li>

581)     </ol>

582) 

583)     <p>If you find your answer, please stick around on the IRC channel
584) or the

585)     mailing list to help others who were once in your position.</p>

586) 

587)     <hr>

588) 

589)     <a id="Forum"></a>
590)     <h3><a class="anchor" href="#Forum">Is there a Tor forum?</a></h3>
591) 

592)     <p>We have a <a href="https://tor.stackexchange.com/">StackExchange 

593)     page</a> that is currently in public beta.

594)     </p>
595) 
596)     <hr>
597) 

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

600) 

601)     <p>
602)     There are many reasons why the Tor network is currently slow.
603)     </p>

604) 

605)     <p>

606)     Before we answer, though, you should realize that Tor is never going
607) to
608)     be blazing fast. Your traffic is bouncing through volunteers'
609) computers
610)     in various parts of the world, and some bottlenecks and network
611) latency

612)     will always be present. You shouldn't expect to see university-style
613)     bandwidth through Tor.
614)     </p>

615) 

616)     <p>

617)     But that doesn't mean that it can't be improved. The current Tor
618) network
619)     is quite small compared to the number of people trying to use it,
620) and
621)     many of these users don't understand or care that Tor can't
622) currently

623)     handle file-sharing traffic load.
624)     </p>

625) 

626)     <p>
627)     For the much more in-depth answer, see <a

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

629)     post on the topic</a>, which includes both a detailed PDF and a
630) video

631)     to go with it.
632)     </p>

633) 

634)     <p>
635)     What can you do to help?
636)     </p>

637) 

638)     <ul>

639) 

640)     <li>

641)     <a href="<page docs/tor-doc-relay>">Configure your Tor to relay
642) traffic
643)     for others</a>. Help make the Tor network large enough that we can
644) handle

645)     all the users who want privacy and security on the Internet.
646)     </li>

647) 

648)     <li>

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

651)     especially need people to help make it easier to configure your Tor
652)     as a relay. Also, we need help with clear simple documentation to
653)     walk people through setting it up.
654)     </li>

655) 

656)     <li>

657)     There are some bottlenecks in the current Tor network. Help us
658) design
659)     experiments to track down and demonstrate where the problems are,
660) and

661)     then we can focus better on fixing them.
662)     </li>

663) 

664)     <li>
665)     Tor needs some architectural changes too. One important change is to

666)     start providing <a href="#EverybodyARelay">better service to people
667) who
668)     relay traffic</a>. We're working on this, and we'll finish faster if
669) we

670)     get to spend more time on it.
671)     </li>

672) 

673)     <li>

674)     Help do other things so we can do the hard stuff. Please take a
675) moment
676)     to figure out what your skills and interests are, and then <a
677) href="<page

678)     getinvolved/volunteer>">look at our volunteer page</a>.
679)     </li>

680) 

681)     <li>

682)     Help find sponsors for Tor. Do you work at a company or government
683) agency

684)     that uses Tor or has a use for Internet privacy, e.g. to browse the

685)     competition's websites discreetly, or to connect back to the home
686) servers
687)     when on the road without revealing affiliations? If your
688) organization has
689)     an interest in keeping the Tor network working, please contact them
690) about
691)     supporting Tor. Without sponsors, Tor is going to become even
692) slower.

693)     </li>

694) 

695)     <li>
696)     If you can't help out with any of the above, you can still help out

697)     individually by <a href="<page donate/donate>">donating a bit of
698) money to the

699)     cause</a>. It adds up!
700)     </li>

701) 

702)     </ul>

703) 

704)     <hr>

705) 

706)     <a id="FileSharing"></a>

707)     <h3><a class="anchor" href="#FileSharing">How can I share files 
708)     anonymously through Tor?</a></h3>

709) 
710)     <p>

711)     File sharing (peer-to-peer/P2P) is widely unwanted in the Tor network, 
712)     and exit nodes are configured to block file sharing traffic by default. 
713)     Tor is not really designed for it, and file sharing through Tor slows 
714)     down everyone's browsing. Also, Bittorrent over Tor <a 
715)     href="https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea">
716)     is not anonymous</a>!

717)     </p>
718) 
719)     <hr>
720) 

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

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

724) 

725)     <p>

726)     The Tor network's <a

727) 
728) href="https://metrics.torproject.org/network.html#networksize">several

729)     thousand</a> relays push <a
730)     href="https://metrics.torproject.org/network.html#bandwidth">over
731)     1GB per second on average</a>. We have <a

732) 
733) href="https://metrics.torproject.org/users.html#direct-users">several

734)     hundred thousand daily users</a>. But the Tor network is not yet
735)     self-sustaining.

736)     </p>

737) 

738)     <p>

739)     There are six main development/maintenance pushes that need
740) attention:

741)     </p>

742) 

743)     <ul>

744) 

745)     <li>
746)     Scalability: We need to keep scaling and decentralizing the Tor
747)     architecture so it can handle thousands of relays and millions of

748)     users. The upcoming stable release is a major improvement, but
749) there's

750)     lots more to be done next in terms of keeping Tor fast and stable.
751)     </li>

752) 

753)     <li>

754)     User support: With this many users, a lot of people are asking
755) questions
756)     all the time, offering to help out with things, and so on. We need
757) good
758)     clean docs, and we need to spend some effort coordinating
759) volunteers.

760)     </li>

761) 

762)     <li>

763)     Relay support: the Tor network is run by volunteers, but they still
764) need

765)     attention with prompt bug fixes, explanations when things go wrong,

766)     reminders to upgrade, and so on. The network itself is a commons,
767) and
768)     somebody needs to spend some energy making sure the relay operators
769) stay
770)     happy. We also need to work on stability on some platforms —
771) e.g.,

772)     Tor relays have problems on Win XP currently.

773)     </li>

774) 

775)     <li>

776)     Usability: Beyond documentation, we also need to work on usability
777) of the
778)     software itself. This includes installers, clean GUIs, easy
779) configuration
780)     to interface with other applications, and generally automating all
781) of
782)     the difficult and confusing steps inside Tor. We've got a start on
783) this
784)     with the <a href="<page projects/vidalia>">Vidalia GUI</a>, but much
785) more work

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

788) 

789)     <li>
790)     Incentives: We need to work on ways to encourage people to configure
791)     their Tors as relays and exit nodes rather than just clients.

792)     <a href="#EverybodyARelay">We need to make it easy to become a
793) relay,

794)     and we need to give people incentives to do it.</a>
795)     </li>

796) 

797)     <li>
798)     Research: The anonymous communications field is full
799)     of surprises and gotchas. In our copious free time, we
800)     also help run top anonymity and privacy conferences like <a
801)     href="http://petsymposium.org/">PETS</a>. We've identified a set of

802)     critical <a href="<page getinvolved/volunteer>#Research">Tor
803) research questions</a>
804)     that will help us figure out how to make Tor secure against the
805) variety of
806)     attacks out there. Of course, there are more research questions
807) waiting

808)     behind these.
809)     </li>

810) 

811)     </ul>

812) 

813)     <p>
814)     We're continuing to move forward on all of these, but at this rate

815)     <a href="#WhySlow">the Tor network is growing faster than the
816) developers

817)     can keep up</a>.

818)     Now would be an excellent time to add a few more developers to the
819) effort

820)     so we can continue to grow the network.
821)     </p>

822) 

823)     <p>
824)     We are also excited about tackling related problems, such as
825)     censorship-resistance.
826)     </p>

827) 

828)     <p>

829)     We are proud to have <a href="<page about/sponsors>">sponsorship and
830) support</a>
831)     from the Omidyar Network, the International Broadcasting Bureau,
832) Bell
833)     Security Solutions, the Electronic Frontier Foundation, several
834) government

835)     agencies and research groups, and hundreds of private contributors.
836)     </p>

837) 

838)     <p>

839)     However, this support is not enough to keep Tor abreast of changes
840) in the
841)     Internet privacy landscape. Please <a href="<page
842) donate/donate>">donate</a>
843)     to the project, or <a href="<page about/contact>">contact</a> our
844) executive

845)     director for information on making grants or major donations.
846)     </p>

847) 

848)     <hr>
849) 

850)      <a id="OutboundPorts"></a>

851)     <h3><a class="anchor" href="#OutboundPorts">Do I have to open all these 
852)     outbound ports on my firewall?</a></h3>

853) 
854)     <p>

855)     Tor may attempt to connect to any port that is advertised in the 
856)     directory as an ORPort (for making Tor connections) or a DirPort (for 
857)     fetching updates to the directory). There are a variety of these ports, 
858)     but many of them are running on 80, 443, 9001, and 9030.

859)     </p>
860)     <p>

861)     So as a client, you could probably get away with opening only those four 
862)     ports. Since Tor does all its connections in the background, it will retry 
863)     ones that fail, and hopefully you'll never have to know that it failed, as 
864)     long as it finds a working one often enough. However, to get the most 
865)     diversity in your entry nodes -- and thus the most security -- as well as 
866)     the most robustness in your connectivity, you'll want to let it connect 
867)     to all of them.

868)     </p>
869)     <p>

870)     If you really need to connect to only a small set of ports, see the FAQ 

871)     entry on <a href="#FirewallPorts">firewalled ports</a>.

872)     </p>
873)     <p>

874)     Note that if you're running Tor as a relay, you must allow outgoing 
875)     connections to every other relay and to anywhere your exit policy 
876)     advertises that you allow. The cleanest way to do that is simply to allow 
877)     all outgoing connections at your firewall. If you don't, clients will try 
878)     to use these connections and things won't work. 

879)     </p>
880)     
881)     <hr>
882)     
883)     <a id="IsItWorking"></a>

884)     <h3><a class="anchor" href="#IsItWorking">How can I tell if Tor is 
885)     working, and that my connections really are anonymized?</a></h3>

886) 
887)     <p>

888)     There are sites you can visit that will tell you if you appear to be 
889)     coming through the Tor network. Try the <a href="https://check.torproject.org">
890)     Tor Check</a> site and see whether it thinks you are using Tor or not.

891)     </p>
892)     <p>

893)     If that site is down, you can still test, but it will involve more effort. 
894)     Sites like <a href="http://ipid.shat.net">http://ipid.shat.net</a> and 
895)     <a href="http://www.showmyip.com/">http://www.showmyip.com/</a> will tell 
896)     you what your IP address appears to be, but you'll need to know your 
897)     current IP address so you can compare and decide whether you're using Tor 
898)     correctly.

899)     </p>
900)     <p>

901)     To learn your IP address on OS X, Linux, BSD, etc, run "ifconfig". On 
902)     Windows, go to the Start menu, click Run and enter "cmd". At the command 
903)     prompt, enter "ipconfig /a".

904)     </p>
905)     <p>

906)     If you are behind a NAT or firewall, though, your IP address will be 
907)     within the range of 10.XXX.XXX.XXX, 192.168.XXX.XXX, or 172.16.XXX.XXX - 
908)     172.31.XXX.XXX, which is not your public IP address. In this case, you 
909)     should check your IP address with one of the sites above without using 
910)     Tor, and then check again using Tor to see whether your IP address has 
911)     changed. 

912)     </p>
913)     
914)     <hr>
915)     
916)     <a id="FTP"></a>
917)     <h3><a class="anchor" href="#FTP">How do I use my browser for ftp with Tor?
918)     </a></h3>
919) 

920)     <p>
921)     Use the Tor Browser Bundle. If you want a separate application for an 
922)     ftp client, we've heard good things about  FileZilla for Windows. You can 
923)     configure it to point to Tor as a "socks4a" proxy on "localhost" port 
924)     "9050". 
925)     </p>

926)     <hr>
927)     

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

929)     <h3><a class="anchor" href="#Metrics">How many people use Tor? How

930)     many relays or exit nodes are there?</a></h3>

931) 

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

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

935)     <hr>

936) 

937)     <a id="SSLcertfingerprint"></a>

938)     <h3><a class="anchor" href="#SSLcertfingerprint">What are the SSL 
939)     certificate fingerprints for Tor's various websites?</a></h3>

940)     <p>

941)     <pre>

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

943)     The serial number is:

944) 06:DE:97:E5:1D:C3:9D:C2:64:8D:AC:72:DD:41:01:FC
945)     The SHA-1 fingerprint is: 1f9d306e8bfccfcb03981a71a27a9f5d1e0876ce

946)     The SHA-256 fingerprint is:

947) 3613d2b22a750094760c41ad19db52a4f05bdea80172e2578761ad967f7ed9aa

948) 

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

950)     The serial number is: 00:EF:A3
951)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

952)     </pre>

953)     </p>
954)     <hr>
955) 

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

957)     <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall
958) Tor?</a></h3>
959) 
960)     <p>
961)     Tor Browser does not install itself in the classic sense of
962) applications. You just simply delete the folder or directory named "Tor
963) Browser" and it is removed from your system.
964)     </p>

965) 

966)     <p>

967)     If this is not related to Tor Browser, uninstallation depends
968) entirely on how you installed it and which operating system you
969)     have. If you installed a package, then hopefully your package has a
970) way to

971)     uninstall itself. The Windows packages include uninstallers. 

972)     </p>

973) 

974)     <p>
975)     For Mac OS X, follow the <a
976)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
977)     </p>

978) 

979)     <p>

980)     If you installed by source, I'm afraid there is no easy uninstall
981) method. But
982)     on the bright side, by default it only installs into /usr/local/ and
983) it should

984)     be pretty easy to notice things there.
985)     </p>

986) 

987)     <hr>

988) 

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

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

992) 

993)     <p>

994)     These are PGP signatures, so you can verify that the file you've
995) downloaded is

996)     exactly the one that we intended you to get.
997)     </p>

998) 

999)     <p>
1000)     Please read the <a

1001)     href="<page docs/verifying-signatures>">verifying signatures</a>
1002) page for details.

1003)     </p>

1004) 

1005) <hr>
1006) 
1007) <a id="GetTor"></a>
1008) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
1009) country. How do I download Tor?</a></h3>
1010) 
1011) <p>
1012) Some government or corporate firewalls censor connections to Tor's
1013) website. In those cases, you have three options. First, get it from

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

1015) Bundle</a> fits nicely on a USB key. Second, find the <a

1016) href="https://encrypted.google.com/search?q=tor+mirrors">google
1017) cache</a>

1018) for the <a href="<page getinvolved/mirrors>">Tor mirrors</a> page
1019) and see if any of those copies of our website work for you. Third,
1020) you can download Tor via email: log in to your Gmail account and mail

1021) '<tt>gettor@gettor.torproject.org</tt>'. If you include the word 'help'

1022) in the body of the email, it will reply with instructions. Note that
1023) only a few webmail providers are supported, since they need to be able
1024) to receive very large attachments.
1025) </p>
1026) 
1027) <p>

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

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

1032) </p>
1033) 
1034) <hr>

1035) 

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

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

1039) 

1040)     <p>

1041)     Try following the steps at <a
1042) href="<gitblob>doc/tor-win32-mingw-creation.txt">

1043)     tor-win32-mingw-creation.txt</a>.
1044)     </p>

1045) 

1046)     <p>
1047)     (Note that you don't need to compile Tor yourself in order to use

1048)     it. Most people just use the packages available on the <a
1049) href="<page

1050)     download/download>">download page</a>.)
1051)     </p>

1052) 

1053)     <hr>

1054) 

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

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

1058) 

1059)     <p>

1060)     Sometimes, overzealous Windows virus and spyware detectors trigger
1061) on some
1062)     parts of the Tor Windows binary. Our best guess is that these are
1063) false
1064)     positives — after all, the anti-virus and anti-spyware
1065) business is just a
1066)     guessing game anyway. You should contact your vendor and explain
1067) that you have
1068)     a program that seems to be triggering false positives. Or pick a
1069) better vendor.

1070)     </p>

1071) 

1072)     <p>
1073)     In the meantime, we encourage you to not just take our word for

1074)     it. Our job is to provide the source; if you're concerned, please do
1075) <a

1076)     href="#CompileTorWindows">recompile it yourself</a>.
1077)     </p>

1078) 

1079)     <hr>

1080) 

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

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

1084) 

1085)     <p>

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

1087)     Live System</a> or <a href="<page projects/torbrowser>">the Tor
1088) Browser

1089)     Bundle</a>.

1090)     </p>

1091) 
1092) <hr>
1093) 

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

1095) <h3><a class="anchor" href="#TBBFlash">Why can't I view videos on
1096) YouTube

1097) and other Flash-based sites?</a></h3>

1098) 
1099) <p>

1100) YouTube and similar sites require third party browser plugins such as Flash.
1101) Plugins operate independently from Firefox and can perform
1102) activity on your computer that ruins your anonymity. This includes
1103) but is not limited to: <a href="http://decloak.net">completely disregarding
1104) proxy settings</a>, querying your <a

1105) href="http://forums.sun.com/thread.jspa?threadID=5162138&messageID=9618376">
1106) local IP address</a>, and <a

1107) href="http://epic.org/privacy/cookies/flash.html">storing their own
1108) cookies</a>. It is possible to use a LiveCD solution such as

1109) or <a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> 
1110) that creates a secure, transparent proxy to protect you from proxy bypass, 
1111) however issues with local IP address discovery and Flash cookies still remain. 
1112) </p>

1113) 
1114) <p>

1115) <a href="https://www.youtube.com/html5">YouTube offers experimental HTML5 video
1116) support</a> for many of their videos. You can use their Advanced Search to

1117) find HTML5 videos.
1118) </p>
1119) 

1120) <hr>
1121) 

1122) <a id="Ubuntu"></a>
1123) <h3><a class="anchor" href="#Ubuntu">
1124) I'm using Ubuntu and I can't start Tor Browser</a></h3>
1125) <p>

1126) Ubuntu prevents its users from executing shell scripts by clicking them, 
1127) even when the file permissions are set correctly. For now you need to 
1128) start the Tor Browser from the command line by running </p>

1129) <pre>
1130) ./start-tor-browser
1131) </pre>
1132) <p>
1133) from inside the Tor Browser directory.
1134) </p>
1135) 
1136) <hr>
1137) 

1138) <a id="TBBSocksPort"></a>

1139) <h3><a class="anchor" href="#TBBSocksPort">

1140) I want to run another application through the Tor launched by Tor

1141) Browser Bundle.</a></h3>

1142) 
1143) <p>

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

1145) on port 9150.

1146) The goal is to avoid conflicting with a "system" Tor install,

1147) so you can run a system Tor and TBB at the same time. We're <a
1148) href="https://trac.torproject.org/projects/tor/ticket/3948">working on
1149) a feature</a> where Tor will try the usual ports first and then back

1150) off to a random choice if they're already in use.

1151) </p>
1152) 
1153) <hr>
1154) 
1155) <a id="TBBPolipo"></a>
1156) <h3><a class="anchor" href="#TBBPolipo">I need an HTTP proxy. Where did
1157) Polipo go?</a></h3>
1158) 
1159) <p>
1160) In the past, Tor bundles included an HTTP proxy like Privoxy or Polipo,
1161) solely to work around a bug in Firefox that was finally fixed in Firefox
1162) 6. Now you don't need a separate HTTP proxy to use Tor, and in fact
1163) leaving it out makes you safer because Torbutton has better control over
1164) Firefox's interaction with websites.
1165) </p>
1166) 
1167) <p>
1168) If you are trying to use some external application with Tor, step zero

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

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

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

1172) proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>
1173) for OSX and Linux.
1174) </p>
1175) 
1176) <p>

1177) If that fails, feel free to install <a

1178) href="http://www.privoxy.org/">privoxy</a>.
1179) However, please realize that this approach is not recommended for novice
1180) users. Privoxy has an <a
1181) href="http://www.privoxy.org/faq/misc.html#TOR">example
1182) configuration</a> of Tor and Privoxy.

1183) </p>
1184) 
1185) <hr>
1186) 

1187) <a id="TBBOtherExtensions"></a>
1188) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
1189) Firefox extensions?</a></h3>
1190) 
1191) <p>

1192) The Tor Browser is free software, so there is nothing preventing you from 
1193) modifying it any way you like. However, we do not recommend installing any 
1194) additional Firefox add-ons with the Tor Browser Bundle. Add-ons can break 
1195) your anonymity in a number of ways, including browser fingerprinting and 
1196) bypassing proxy settings.

1197) </p>

1198) <p>

1199) Some people have suggested we include ad-blocking software or 
1200) anti-tracking software with the Tor Browser Bundle. Right now, we do not 
1201) think that's such a good idea. The Tor Browser Bundle aims to provide 
1202) sufficient privacy that additional add-ons to stop ads and trackers are 
1203) not necessary. Using add-ons like these may cause some sites to break, which 
1204) <a href="https://www.torproject.org/projects/torbrowser/design/#philosophy">
1205) we don't want to do</a>. Additionally, maintaining a list of "bad" sites that 
1206) should be black-listed provides another opportunity to uniquely fingerprint 
1207) users. 

1208) </p>

1209) 

1210) <hr>
1211) 

1212) <a id="TBBJavaScriptEnabled"></a>

1213) <a id="TBBCanIBlockJS"></a>

1214) <h3><a class="anchor" href="#TBBJavaScriptEnabled">Why is NoScript
1215) configured to allow JavaScript by default in the Tor Browser Bundle?
1216) Isn't that unsafe?</a></h3>

1217) 
1218) <p>
1219) We configure NoScript to allow JavaScript by default in the Tor
1220) Browser Bundle because many websites will not work with JavaScript
1221) disabled.  Most users would give up on Tor entirely if a website
1222) they want to use requires JavaScript, because they would not know
1223) how to allow a website to use JavaScript (or that enabling
1224) JavaScript might make a website work).
1225) </p>
1226) 

1227) <p>
1228) There's a tradeoff here. On the one hand, we should leave
1229) JavaScript enabled by default so websites work the way
1230) users expect. On the other hand, we should disable JavaScript
1231) by default to better protect against browser vulnerabilities (<a

1232) href="https://blog.torproject.org/blog/tor-security-advisory-old-tor-browser-bundles-vulnerable">
1233) not just a theoretical concern!</a>). But there's a third issue: websites

1234) can easily determine whether you have allowed JavaScript for them,
1235) and if you disable JavaScript by default but then allow a few websites
1236) to run scripts (the way most people use NoScript), then your choice of
1237) whitelisted websites acts as a sort of cookie that makes you recognizable
1238) (and distinguishable), thus harming your anonymity.
1239) </p>

1240) 
1241) <p>

1242) Ultimately, we want the default Tor bundles to use
1243) a combination of firewalls (like the iptables rules
1244) in <a href="https://tails.boum.org/">Tails</a>) and <a
1245) href="https://trac.torproject.org/projects/tor/ticket/7680">sandboxes</a>
1246) to make JavaScript not so scary. In
1247) the shorter term, TBB 3.0 will hopefully <a
1248) href="https://trac.torproject.org/projects/tor/ticket/9387">allow users
1249) to choose their JavaScript settings more easily</a> &mdash; but the
1250) partitioning concern will remain.

1251) </p>
1252) 
1253) <p>

1254) Until we get there, feel free to leave JavaScript on or off depending
1255) on your security, anonymity, and usability priorities.

1256) </p>
1257) 
1258) <hr>
1259) 

1260) <a id="TBBOtherBrowser"></a>
1261) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
1262) Chrome/IE/Opera/etc with Tor.</a></h3>
1263) 
1264) <p>
1265) Unfortunately, Torbutton only works with Firefox right now, and without
1266) <a href="https://www.torproject.org/torbutton/en/design/">Torbutton's
1267) extensive privacy fixes</a> there are many ways for websites or other

1268) attackers to recognize you, track you back to your IP address, and so
1269) on.

1270) In short, using any browser besides Tor Browser Bundle with Tor is a
1271) really bad idea.
1272) </p>
1273) 
1274) <p>
1275) We're working with the Chrome team to <a

1276) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-
1277) and-fingerprinting">fix
1278) some bugs and missing APIs in Chrome</a> so it will be possible to write
1279) a
1280) Torbutton for Chrome. No support for any other browser is on the
1281) horizon.

1282) </p>
1283) 
1284) <hr>
1285) 

1286) <a id="TorbuttonOtherBrowser"></a>

1287) <h3><a class="anchor" href="TorbuttonOtherBrowser">
1288) Will ​Torbutton be available for other browsers?</a></h3>

1289) 
1290) <p>

1291)  We don't support IE, Opera or Safari and never plan to. There are too many ways that your privacy can go wrong with those browsers, and because of their closed design it is really hard for us to do anything to change these privacy problems.

1292) </p>
1293) <p>

1294) We are working with the Chrome people to modify Chrome's internals so that we can eventually support it. But for now, Firefox is the only safe choice. 

1295) </p>
1296) 

1297) <hr>

1298) 

1299) <a id="TBBCloseBrowser"></a>

1300) <h3><a class="anchor" href="#TBBCloseBrowser">I want to leave Tor
1301) Browser

1302) Bundle running but close the browser.</a></h3>
1303) 
1304) <p>
1305) We're working on a way to make this possible on all platforms. Please
1306) be patient.
1307) </p>
1308) 
1309) <hr>
1310) 

1311) <a id="GoogleCAPTCHA"></a>
1312) <h3><a class="anchor" href="#GoogleCAPTCHA">Google makes me solve a
1313) CAPTCHA or tells me I have spyware installed.</a></h3>

1314) 
1315) <p>
1316) This is a known and intermittent problem; it does not mean that Google
1317) considers Tor to be spyware.
1318) </p>
1319) 
1320) <p>

1321) When you use Tor, you are sending queries through exit relays that are
1322) also

1323) shared by thousands of other users. Tor users typically see this message

1324) when many Tor users are querying Google in a short period of time.
1325) Google

1326) interprets the high volume of traffic from a single IP address (the exit
1327) relay you happened to pick) as somebody trying to "crawl" their website,
1328) so it slows down traffic from that IP address for a short time.
1329) </p>
1330) <p>
1331) An alternate explanation is that Google tries to detect certain
1332) kinds of spyware or viruses that send distinctive queries to Google
1333) Search. It notes the IP addresses from which those queries are received
1334) (not realizing that they are Tor exit relays), and tries to warn any
1335) connections coming from those IP addresses that recent queries indicate
1336) an infection.
1337) </p>
1338) 
1339) <p>

1340) To our knowledge, Google is not doing anything intentionally
1341) specifically

1342) to deter or block Tor use. The error message about an infected machine
1343) should clear up again after a short time.
1344) </p>
1345) 
1346) <p>
1347) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1348) automatically redirect you to a more Tor-friendly search engine such as

1349) DuckDuckGo, ixquick, or Bing.

1350) </p>
1351) 
1352) <hr />
1353) 

1354) <a id="ForeignLanguages"></a>
1355) <h3><a class="anchor" href="#ForeignLanguages">
1356) Why does Google show up in foreign languages?</a></h3>
1357) 
1358) <p>

1359)  Google uses "geolocation" to determine where in the world you are, so it 
1360)  can give you a personalized experience. This includes using the language 
1361)  it thinks you prefer, and it also includes giving you different results 
1362)  on your queries.

1363) </p>
1364) <p>

1365) If you really want to see Google in English you can click the link that 
1366) provides that. But we consider this a feature with Tor, not a bug --- the 
1367) Internet is not flat, and it in fact does look different depending on 
1368) where you are. This feature reminds people of this fact. The easy way to 
1369) avoid this "feature" is to use 
1370) <a href="https://google.com/ncr">https://google.com/ncr</a>.

1371) </p>
1372) <p>

1373) Note that Google search URLs take name/value pairs as arguments and one 
1374) of those names is "hl". If you set "hl" to "en" then Google will return 
1375) search results in English regardless of what Google server you have been 
1376) sent to. On a query this looks like: 
1377) </p>
1378) <pre>https://encrypted.google.com/search?q=online%20anonymity&hl=en

1379) </pre>

1380) <p>

1381) Another method is to simply use your country code for accessing Google. 
1382) This can be google.be, google.de, google.us and so on. 

1383) </p>
1384) <hr />

1385) <a id="GmailWarning"></a>

1386) <h3><a class="anchor" href="#GmailWarning">Gmail warns me that my

1387) account may have been compromised.</a></h3>

1388) 
1389) <p>
1390) Sometimes, after you've used Gmail over Tor, Google presents a
1391) pop-up notification that your account may have been compromised.
1392) The notification window lists a series of IP addresses and locations
1393) throughout the world recently used to access your account.
1394) </p>
1395) 
1396) <p>
1397) In general this is a false alarm: Google saw a bunch of logins from

1398) different places, as a result of running the service via Tor, and
1399) decided

1400) it was a good idea to confirm the account was being accessed by it's
1401) rightful owner.
1402) </p>
1403) 
1404) <p>
1405) Even though this may be a biproduct of using the service via tor,
1406) that doesn't mean you can entirely ignore the warning. It is
1407) <i>probably</i> a false positive, but it might not be since it is
1408) possible for someone to hijack your Google cookie.
1409) </p>
1410) 
1411) <p>
1412) Cookie hijacking is possible by either physical access to your computer
1413) or by watching your network traffic.  In theory only physical access
1414) should compromise your system because Gmail and similar services
1415) should only send the cookie over an SSL link. In practice, alas, it's <a

1416) href="http://fscked.org/blog/fully-automated-active-https-cookie-
1417) hijacking">

1418) way more complex than that</a>.
1419) </p>
1420) 
1421) <p>
1422) And if somebody <i>did</i> steal your google cookie, they might end
1423) up logging in from unusual places (though of course they also might
1424) not). So the summary is that since you're using Tor, this security
1425) measure that Google uses isn't so useful for you, because it's full of
1426) false positives. You'll have to use other approaches, like seeing if
1427) anything looks weird on the account, or looking at the timestamps for
1428) recent logins and wondering if you actually logged in at those times.
1429) </p>
1430) 
1431) <hr>
1432) 

1433) <a id="NeedToUseAProxy"></a>

1434) <h3><a class="anchor" href="#NeedToUseAProxy">My internet connection 
1435) requires an HTTP or SOCKS Proxy</a></h3>

1436) 
1437) <p>
1438) You can set Proxy IP address, port, and authentication information in 
1439) Tor Browser's Network Settings. If you're using Tor another way, check 
1440) out the HTTPProxy and HTTPSProxy config options in the <a 
1441) href="https://www.torproject.org/docs/tor-manual.html.en">man page</a>, 
1442) and modify your torrc file accordingly. You will need an HTTP proxy for 
1443) doing GET requests to fetch the Tor directory, and you will need an 
1444) HTTPS proxy for doing CONNECT requests to get to Tor relays. (It's fine 
1445) if they're the same proxy.) Tor also recognizes the torrc options 
1446) Socks4Proxy and Socks5Proxy. 
1447) </p>
1448) <p>

1449) Also read up on the HTTPProxyAuthenticator and HTTPSProxyAuthenticator 
1450) options if your proxy requires auth. We only support basic auth currently, 
1451) but if you need NTLM authentication, you may find <a 

1452) href="http://archives.seul.org/or/talk/Jun-2005/msg00223.html">this post 
1453) in the archives</a> useful. 
1454) </p>
1455) <p>
1456) If your proxies only allow you to connect to certain ports, look at the 
1457) entry on <a href="#FirewallPorts">Firewalled clients</a> for how 
1458) to restrict what ports your Tor will try to access. 
1459) </p>
1460) 
1461) <hr>
1462) 

1463) <a id="CantSetProxy"></a>
1464) <h3><a class="anchor" href="#CantSetProxy">What should I do if I can't 
1465) set a proxy with my application?</a></h3>
1466) 
1467) <p>
1468) On Unix, we recommend you give <a 
1469) href="https://github.com/dgoulet/torsocks/">torsocks</a> a try. 
1470) Alternative proxifying tools like <a 
1471) href="http://www.dest-unreach.org/socat/">socat</a> and <a 
1472) href="http://proxychains.sourceforge.net/">proxychains</a> are also 
1473) available.</p>
1474) <p> 
1475) The Windows way to force applications through Tor is less clear. <a 
1476) href="http://freecap.ru/eng/">Some</a> <a 
1477) href="http://www.freehaven.net/~aphex/torcap/">tools</a> have been <a 
1478) href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1479) </a>, but we'd also like to see further testing done here. 
1480) </p>
1481) 
1482) <hr>
1483) 
1484) <a id="WarningsAboutSOCKSandDNSInformationLeaks"></a>
1485) <h3><a class="anchor" href="#WarningsAboutSOCKSandDNSInformationLeaks">I 
1486) keep seeing these warnings about SOCKS and DNS information leaks. 
1487) Should I worry?</a></h3>
1488) <p>
1489) The warning is: 
1490) </p>
1491) <p>
1492) Your application (using socks5 on port %d) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via Polipo or socat) instead. 
1493) </p>
1494) <p>
1495) If you are running Tor to get anonymity, and you are worried about an attacker who is even slightly clever, then yes, you should worry. Here's why. 
1496) </p>
1497) <p>
1498) <b>The Problem.</b> When your applications connect to servers on the Internet, they need to resolve hostnames that you can read (like www.torproject.org) into IP addresses that the Internet can use (like 209.237.230.66). To do this, your application sends a request to a DNS server, telling it the hostname it wants to resolve. The DNS server replies by telling your application the IP address. 
1499) </p>
1500) <p>
1501) Clearly, this is a bad idea if you plan to connect to the remote host anonymously: when your application sends the request to the DNS server, the DNS server (and anybody else who might be watching) can see what hostname you are asking for. Even if your application then uses Tor to connect to the IP anonymously, it will be pretty obvious that the user making the anonymous connection is probably the same person who made the DNS request. 
1502) </p>
1503) <p>
1504) <b>Where SOCKS comes in.</b> Your application uses the SOCKS protocol to connect to your local Tor client. There are 3 versions of SOCKS you are likely to run into: SOCKS 4 (which only uses IP addresses), SOCKS 5 (which usually uses IP addresses in practice), and SOCKS 4a (which uses hostnames). 
1505) </p>
1506) <p>
1507) When your application uses SOCKS 4 or SOCKS 5 to give Tor an IP address, Tor guesses that it 'probably' got the IP address non-anonymously from a DNS server. That's why it gives you a warning message: you probably aren't as anonymous as you think. 
1508) </p>
1509) <p>
1510) <b>So what can I do?</b> We describe a few solutions below. 
1511) </p>
1512) <ul>
1513) <li>If your application speaks SOCKS 4a, use it. </li>
1514) <li>If you only need one or two hosts, or you are good at programming, you may be able to get a socks-based port-forwarder like socat to work for you; see <a href="https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO">the Torify HOWTO</a> for examples. </li>
1515) <li>Tor ships with a program called tor-resolve that can use the Tor network to look up hostnames remotely; if you resolve hostnames to IPs with tor-resolve, then pass the IPs to your applications, you'll be fine. (Tor will still give the warning, but now you know what it means.) </li>
1516) <!-- I'm not sure if this project is still maintained or not
1517) 
1518) <li>You can use TorDNS as a local DNS server to rectify the DNS leakage. See the Torify HOWTO for info on how to run particular applications anonymously. </li>
1519) !-->
1520) </ul>
1521) <p>
1522)  If you think that you applied one of the solutions properly but still experience DNS leaks please verify there is no third-party application using DNS independently of Tor. Please see <a href="#AmITotallyAnonymous">the FAQ entry on whether you're really absolutely anonymous using Tor</a> for some examples. 
1523) </p>
1524) 

1525)     <hr>
1526) 
1527)     <a id="WhereDidVidaliaGo"></a>
1528)     <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map 
1529)     (Vidalia) go?</a></h3>
1530) 
1531)     <p>Vidalia has been replaced with Tor Launcher, which is a Firefox 
1532)     extension that provides similar functionality. Unfortunately, circuit 
1533)     status reporting is still missing, but we are <a 
1534)     href="https://trac.torproject.org/projects/tor/ticket/8641">working 
1535)     on providing it</a>. </p>
1536) 
1537)     <p>In the meantime, we are providing standalone Vidalia packages for 
1538)     people who still want the map. Windows and Linux versions are <a 
1539)     href="​https://people.torproject.org/~erinn/vidalia-standalone-bundles/">
1540)     available here</a>. 
1541) 
1542)     <p>To use these packages, extract them, then run the startup script. 
1543)     On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia. 
1544)     They can be placed in a different directory from TBB (and likely should 
1545)     be). </p>
1546) 
1547)     <p>This Vidalia package will only run properly if Tor Browser has already 
1548)     been launched. You cannot start it before launching Tor Browser. </p>
1549) 
1550)     <p>MacOS is still under development, but in the mean time you can modify 
1551)     your TBB 2.x to be a standalone Vidalia (and then use it after starting 
1552)     TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and 
1553)     replacing its contents with just these lines:</p>
1554) 
1555)     <pre>
1556)     [General]
1557)     LanguageCode=en
1558) 
1559)     [Tor]
1560)     ControlPort=9151
1561)     TorExecutable=.
1562)     Torrc=.
1563)     DataDirectory=.
1564)     AuthenticationMethod=cookie
1565)     </pre> 
1566) 
1567)     <hr>
1568) 
1569)     <a id="DisableJS"></a>
1570)     <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1571)     </h3>
1572) 
1573)     <p>Alas, Mozilla decided to get rid of the config checkbox for JavaScript 
1574)     from earlier Firefox versions. And since TBB 3.5 is based on Firefox 24 
1575)     (FF17 is unmaintained), that means TBB 3.5 doesn't have the config 
1576)     checkbox anymore either, which is unfortunate.</p>
1577) 
1578)     <p>The simplest way to disable JavaScript in TBB 3.5 is to click on the 
1579)     Noscript "S" (between the green onion and the address bar), and select 
1580)     "Forbid scripts globally". Note that vanilla NoScript actually whitelists 
1581)     several domains even when you try to disable scripts globally, whereas 
1582)     Tor Browser's NoScript configuration disables all of them. </p>
1583) 
1584)     <p>The more klunky way to disable JavaScript is to go to about:config, 
1585)     find javascript.enabled, and set it to false.</p>
1586) 
1587)     <p>There is also a very simple addon available at addons.mozilla.org
1588)     called QuickJS, which provides a toolbar toggle for the javascript.enabled
1589)     about:config control. There are no configuration options for the addon, 
1590)     it just switches the javascript.enabled entry between true and false and 
1591)     provides a button for it. </p>
1592) 
1593)     <p>If you want to be extra safe, use both the about:config setting and 
1594)     NoScript. </p>
1595) 
1596)     <p>As for whether you should disable it or leave it enabled, that's <a 
1597)     href="https://www.torproject.org/docs/faq#TBBJavaScriptEnabled">a 
1598)     tradeoff we leave to you</a>.</p>
1599) 
1600)     <hr>
1601) 
1602)     <a id="VerifyDownload"></a>
1603)     <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1604)     (sha256sums.txt)?</a></h3>
1605) 
1606)     <p>You can still verify your Tor Browser download by downloading the 
1607)     signature file (.asc) along with your package and <a 
1608)     href="https://www.torproject.org/docs/verifying-signatures.html.en">
1609)     checking the GPG signature</a> as before. We now have an additional 
1610)     verification method that allows you to verify the build as well as 
1611)     the download.</p>
1612) 
1613)     <ul>
1614)       <li>Download the Tor Browser package, the sha256sums.txt file, and the
1615)       sha256sums signature files. They can all be found in the same directory 
1616)       under <a href="https://www.torproject.org/dist/torbrowser/">
1617)       https://www.torproject.org/dist/torbrowser/</a>, for example in 3.5 
1618)       for TBB 3.5.</li>
1619)       <li>Retrieve the signers' GPG keys. This can be done from the command 
1620)       line by entering something like 
1621)       <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>
1622)       (This will bring you developer Mike Perry's public key. Other 
1623)       developers' key IDs can be found on
1624)       <a href="https://www.torproject.org/docs/signing-keys.html.en">this 
1625)       page</a>.)</li>
1626)       <li>Verify the sha256sums.txt file by executing this command:
1627)       <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>
1628)       <li>You should see a message like "Good signature from &lt;DEVELOPER 
1629)       NAME&gt;". If you don't, there is a problem. Try these steps again.</li>
1630)       <li>Now you can take the sha256sum of the Tor Browser package. On 
1631)       Windows you can use the <a href="http://md5deep.sourceforge.net/">
1632)       hashdeep utility</a> and run
1633)       <pre>C:\location\where\you\saved\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe</pre>
1634)       On Mac or Linux you can run <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.zip</pre> or <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.tar.gz</pre> without having to download a utility.</li>
1635)       <li>You will see a string of letters and numbers.</li>
1636)       <li>Open sha256sums.txt in a text editor.</li>
1637)       <li>Locate the name of the Tor Browser file you downloaded.</li>
1638)       <li>Compare the string of letters and numbers to the left of your
1639)       filename with the string of letters and numbers that appeared 
1640)       on your command line. If they match, you've successfully verified the 
1641)       build.</li> 
1642)     </ul>
1643) 
1644)     <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">
1645)     Scripts</a> to <a 
1646)     href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate
1647)     </a> these steps have been written, but to use them you will need to 
1648)     modify them yourself with the latest Tor Browser Bundle filename.</p>
1649) 
1650)     <hr>
1651) 
1652)     <a id="PluggableTransports"></a>
1653)     <h3><a class="anchor" href="#PluggableTransports">How do I use pluggable transports?</a></h3>
1654) 
1655)     <p>
1656)     For now, the Pluggable Transports-capable TBB is still a separate 
1657)     unofficial package. Download them <a 
1658)     href="https://people.torproject.org/~dcf/pt-bundle/3.5-pt20131217/">
1659)     here</a>. We hope to have combined packages available in a beta soon.
1660)     </p>
1661) 
1662)     <p>
1663)     The separate Pluggable Transports-capable TBB is different from the 
1664)     Pluggable Transports bundles that have been released in the past. 
1665)     They include the programs necessary to use obfsproxy and flash proxy, 
1666)     but the pluggable transports are not enabled by default. You must 
1667)     enable them manually by adding Bridge lines to the torrc file. 
1668)     (Please see ticket <a 
1669)     href="https://trac.torproject.org/projects/tor/ticket/10418">#10418</a> 
1670)     for how we hope to make it easier to do in the future.)
1671)     </p>
1672) 
1673)     <p>
1674)     To enable <b>obfsproxy</b>, edit the file called Data/Tor/torrc inside the 
1675)     bundle and add the lines: 
1676)     </p>
1677) 
1678)     <pre>
1679) Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1680) Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1681) Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1682) Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1683) Bridge obfs3 209.141.36.236:45496
1684) Bridge obfs3 208.79.90.242:35658
1685) Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
1686) Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
1687) Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
1688) Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
1689) Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
1690) Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
1691) Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1692)     </pre>
1693)     <p>
1694)     To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the 
1695)     bundle and add the lines: 
1696)     </p>
1697)     <pre>
1698) LearnCircuitBuildTimeout 0
1699) CircuitBuildTimeout 60
1700) Bridge flashproxy 0.0.1.0:1
1701)     </pre>
1702) 
1703)     <hr>
1704) 
1705)     <a id="NewIdentityClosingTabs"></a>
1706)     <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New 
1707)     Identity" close all my open tabs?</a></h3>
1708) 
1709)     <p>
1710)     That's actually a feature, since it's discarding your application-level 
1711)     browser data too. But it sure is a surprising feature, for people who 
1712)     are used to Vidalia's "new identity" behavior.
1713)     </p>
1714) 
1715)     <p>
1716)     We're working on ways to make the behavior less surprising, e.g. a popup 
1717)     warning or auto restoring tabs. See ticket <a 
1718)     href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and 
1719)     ticket <a href="https://trac.torproject.org/projects/tor/ticket/10400">
1720)     #10400</a> to follow progress there.
1721)     </p>
1722) 
1723)     <p>
1724)     In the mean time, you can get Vidalia's old "newnym" functionality by 
1725)     attaching a Vidalia to your TBB3.x. See the instructions above.
1726)     </p>
1727) 
1728)     <hr>
1729) 
1730)     <a id="ConfigureRelayOrBridge"></a>
1731)     <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1732) 
1733)     <p>
1734)     You've got three options. 
1735)     </p>
1736) 
1737)     <p>
1738)     First (best option), if you're on Linux, you can install the system 
1739)     Tor package (e.g. apt-get install tor) and then set it up to be a relay 
1740)     (<a href="https://www.torproject.org/docs/tor-relay-debian">instructions</a>). 
1741)     You can then use TBB independent of that.
1742)     </p>
1743) 
1744)     <p>
1745)     Second (simpler option), if you're on Windows, you can fetch the separate 
1746)     "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page 
1747)     and then use that (again you can use TBB independent of it). 
1748)     </p>
1749) 
1750)     <p>
1751)     Third (complex option), you can either hook your Vidalia up to TBB (as 
1752)     described in the FAQ above) or edit your torrc file (in Data/Tor/torrc) 
1753)     directly to add the following lines: 
1754)     </p>
1755)     <pre>
1756)     ORPort 443
1757)     Exitpolicy reject *:*
1758)     BridgeRelay 1  # only add this line if you want to be a bridge
1759)     </pre>
1760)     <p>
1761)     If you've installed <a 
1762)     href="https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions">Obfsproxy</a>, 
1763)     you'll need to add one more line:
1764)     </p>
1765)     <pre>
1766)     ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1767)     </pre>
1768)     <p>
1769)     This third option is pretty klunky right now; see e.g. <a 
1770)     href="https://trac.torproject.org/projects/tor/ticket/10449">this bug</a>; 
1771)     but we're hoping it will become an easy option in the future. 
1772)     </p>
1773) 
1774)     <hr>
1775) 
1776)     <a id="Timestamps"></a>
1777)     <h3><a class="anchor" href="#Timestamps">Why are the file timestamps 
1778)     from 2000?</a></h3>
1779) 
1780)     <p>One of the huge new features in TBB 3.x is the "deterministic build" 
1781)     process, which allows many people to build the Tor Browser Bundle and 
1782)     verify that they all make exactly the same package. See Mike's <a 
1783)     href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">first 
1784)     blog</a> post for the motivation, and his <a 
1785)     href="https://blog.torproject.org/blog/deterministic-builds-part-two-technical-details">second
1786)     blog post</a> for the technical details of how we do it. 
1787)     </p>
1788) 
1789)     <p>Part of creating identical builds is having everybody use the same 
1790)     timestamp. Mike picked the beginning of 2000 for that time. The reason 
1791)     you might see 7pm in 1999 is because of time zones. </p>
1792) 
1793)     <hr>
1794) 
1795)     <a id="SourceCode"></a>
1796)     <h3><a class="anchor" href="#SourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>
1797) 
1798)     <p>
1799)     Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build</a>.
1800)     </p>
1801) 
1802) 

1803) <hr>
1804) 

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

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

1808) 
1809) <p>
1810) Tor installs a text file called torrc that contains configuration
1811) instructions for how your Tor program should behave. The default

1812) configuration should work fine for most Tor users. 

1813) </p>

1814) <p>

1815) If you installed Tor Browser Bundle, look for

1816) <code>Data/Tor/torrc</code> inside your Tor Browser Bundle directory. 
1817) </p>
1818) <p>
1819) Core tor puts the torrc file in <code>/usr/local/etc/tor/torrc</code> if you compiled tor from source, and <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> if you installed a pre-built package.</p>

1820) 
1821) <p>

1822) Once you've changed your torrc, you will need to restart tor for the
1823) changes to take effect. (For advanced users, note that

1824) you actually only need to send Tor a HUP signal, not actually restart
1825) it.)

1826) </p>
1827) 
1828) <p>

1829) For other configuration options you can use, see the <a href="<page
1830) docs/tor-manual>">Tor manual page</a>. Have a look at <a 

1831) href="https://gitweb.torproject.org/tor.git/blob/HEAD:/src/config/torrc.sample.in">
1832) the sample torrc file</a> for hints on common configurations. Remember, all 
1833) lines beginning with # in torrc are treated as comments and have no effect 
1834) on Tor's configuration.

1835) </p>
1836) 
1837) <hr>
1838) 

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

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

1842) 
1843) <p>

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

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

1848) </p>
1849) 
1850) <p>
1851) If you're not using Vidalia, you'll have to go find the log files by

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

1853) </p>
1854) 
1855) <ul>
1856) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1857) </li>

1858) <li>On Windows, there are no default log files currently. If you enable
1859) logs in your torrc file, they default to <code>\username\Application
1860) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1861) </li>
1862) <li>If you compiled Tor from source, by default your Tor logs to <a
1863) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1864) at log-level notice. If you enable logs in your torrc file, they
1865) default to <code>/usr/local/var/log/tor/</code>.

1866) </li>
1867) </ul>
1868) 
1869) <p>

1870) To change your logging setup by hand, <a href="#torrc">edit your
1871) torrc</a>

1872) and find the section (near the top of the file) which contains the
1873) following line:

1874) </p>
1875) 
1876) <pre>

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

1879) </pre>

1880) 
1881) <p>

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

1883) and err level messages to a file, append the following line to the end
1884) of the section:
1885) </p>
1886) 
1887) <pre>
1888) Log debug file c:/program files/tor/debug.log
1889) </pre>
1890) 
1891) <p>

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

1894) </p>
1895) 
1896) <hr>
1897) 

1898) 
1899) <a id="LogLevel"></a>
1900) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1901) 
1902) <p>

1903) There are five log levels (also called "log severities") you might see in 
1904) Tor's logs:

1905) </p>
1906) 
1907) <ul>

1908)     <li>"err": something bad just happened, and we can't recover. Tor will 
1909)     exit.</li>
1910)     <li>"warn": something bad happened, but we're still running. The bad 
1911)     thing might be a bug in the code, some other Tor process doing something 
1912)     unexpected, etc. The operator should examine the message and try to 
1913)     correct the problem.</li>

1914)     <li>"notice": something the operator will want to know about.</li>

1915)     <li>"info": something happened (maybe bad, maybe ok), but there's 
1916)     nothing you need to (or can) do about it.</li>

1917)     <li>"debug": for everything louder than info. It is quite loud indeed.</li> 
1918) </ul>
1919) 
1920) <p>

1921) Alas, some of the warn messages are hard for ordinary users to correct -- the 
1922) developers are slowly making progress at making Tor automatically react 
1923) correctly for each situation.

1924) </p>
1925) 
1926) <p>

1927) We recommend running at the default, which is "notice". You will hear about 
1928) important things, and you won't hear about unimportant things.

1929) </p>
1930) 
1931) <p>

1932) Tor relays in particular should avoid logging at info or debug in normal 
1933) operation, since they might end up recording sensitive information in 
1934) their logs. 

1935) </p>
1936) 

1937) <hr>
1938) 

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

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

1942) 
1943) <p>

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

1946) </p>
1947) 
1948) <p>If Tor can establish a circuit, the onion icon in

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

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

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

1956) a line saying that Tor "has successfully opened a circuit. Looks like
1957) client functionality is working."
1958) </p>
1959) 
1960) <p>
1961) If Tor can't establish a circuit, here are some hints:
1962) </p>
1963) 
1964) <ol>
1965) <li>Are you sure Tor is running? If you're using Vidalia, you may have
1966) to click on the onion and select "Start" to launch Tor.</li>
1967) <li>Check your system clock. If it's more than a few hours off, Tor will

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

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

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

1974) href="<#NeedToUseAProxy">proxy</a>?

1975) </li>

1976) <li>Are you running programs like Norton Internet Security or SELinux
1977) that

1978) block certain connections, even though you don't realize they do? They
1979) could be preventing Tor from making network connections.</li>
1980) <li>Are you in China, or behind a restrictive corporate network firewall
1981) that blocks the public Tor relays? If so, you should learn about <a

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

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

1985) </ol>
1986) 
1987) <hr />
1988) 

1989) <a id="TorCrash"></a>
1990) <h3><a class="anchor" href="#TorCrash">My Tor keeps crashing.</a></h3>
1991) <p>
1992)  We want to hear from you! There are supposed to be zero crash bugs in Tor. 
1993)  This FAQ entry describes the best way for you to be helpful to us. But even 
1994)  if you can't work out all the details, we still want to hear about it, so 
1995)  we can help you track it down. 
1996) </p>
1997) <p>
1998) First, make sure you're using the latest version of Tor (either the latest 
1999) stable or the latest development version). 
2000) </p>
2001) <p>
2002) Second, make sure your version of libevent is new enough. We recommend at 
2003) least libevent 1.3a. 
2004) </p>
2005) <p>
2006) Third, see if there's already an entry for your bug in the <a 
2007) href="https://bugs.torproject.org/">Tor bugtracker</a>. If so, 
2008) check if there are any new details that you can add. 
2009) </p>
2010) <p>
2011) Fourth, is the crash repeatable? Can you cause the crash? Can 
2012) you isolate some of the circumstances or config options that 
2013) make it happen? How quickly or often does the bug show up? 
2014) Can you check if it happens with other versions of Tor, for 
2015) example the latest stable release? 
2016) </p>
2017) <p>
2018) Fifth, what sort of crash do you get? 
2019) </p>
2020) <ul>
2021) <li>
2022) Does your Tor log include an "assert failure"? If so, please 
2023) tell us that line, since it helps us figure out what's going on. 
2024) Tell us the previous couple of log messages as well, especially 
2025) if they seem important. 
2026) </li>
2027) <li>
2028) If it says "Segmentation fault - core dumped" then you need to 
2029) do a bit more to track it down. Look for a file like "core" or 
2030) "tor.core" or "core.12345" in your current directory, or in your 
2031) Data Directory. If it's there, run "gdb tor core" and then "bt", 
2032) and include the output. If you can't find a core, run "ulimit -c 
2033) unlimited", restart Tor, and try to make it crash again. (This core 
2034) thing will only work on Unix -- alas, tracking down bugs on Windows 
2035) is harder. If you're on Windows, can you get somebody to duplicate 
2036) your bug on Unix?)
2037) </li>
2038) <li>
2039) If Tor simply vanishes mysteriously, it probably is a segmentation 
2040) fault but you're running Tor in the background (as a daemon) so you 
2041) won't notice. Go look at the end of your log file, and look for a 
2042) core file as above. If you don't find any good hints, you should 
2043) consider running Tor in the foreground (from a shell) so you can 
2044) see how it dies. Warning: if you switch to running Tor in the foreground, 
2045) you might start using a different torrc file, with a different default 
2046) Data Directory; see the <a href="#UpgradeOrMove">relay-upgrade FAQ entry</a> 
2047) for details. 
2048) </li>
2049) <li>
2050) If it's still vanishing mysteriously, perhaps something else is killing it? 
2051) Do you have resource limits (ulimits) configured that kill off processes 
2052) sometimes? (This is especially common on OpenBSD.) On Linux, try running 
2053) "dmesg" to see if the out-of-memory killer removed your process. (Tor will 
2054) exit cleanly if it notices that it's run out of memory, but in some cases 
2055) it might not have time to notice.) In very rare circumstances, hardware 
2056) problems could also be the culprit. 
2057) </li>
2058) </ul>
2059) <p>
2060) Sixth, if the above ideas don't point out the bug, consider increasing your 
2061) log level to "loglevel debug". You can look at the log-configuration FAQ 
2062) entry for instructions on what to put in your torrc file. If it usually 
2063) takes a long time for the crash to show up, you will want to reserve a whole 
2064) lot of disk space for the debug log. Alternatively, you could just send 
2065) debug-level logs to the screen (it's called "stdout" in the torrc), and then 
2066) when it crashes you'll see the last couple of log lines it had printed. 
2067) (Note that running with verbose logging like this will slow Tor down 
2068) considerably, and note also that it's generally not a good idea security-wise 
2069) to keep logs like this sitting around.) 
2070) </p>
2071) 
2072) <hr />
2073) 

2074) <a id="VidaliaPassword"></a>

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

2077) 
2078) <p>
2079) Vidalia interacts with the Tor software via Tor's "control port". The
2080) control port lets Vidalia receive status updates from Tor, request a new
2081) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
2082) Vidalia sets a random password for Tor's control port to prevent other
2083) applications from also connecting to the control port and potentially
2084) compromising your anonymity.
2085) </p>
2086) 
2087) <p>
2088) Usually this process of generating and setting a random control password
2089) happens in the background. There are three common situations, though,
2090) where Vidalia may prompt you for a password:
2091) </p>
2092) 
2093) <ol>
2094) <li>You're already running Vidalia and Tor. For example, this situation
2095) can happen if you installed the Vidalia bundle and now you're trying to
2096) run the Tor Browser Bundle. In that case, you'll need to close the old
2097) Vidalia and Tor before you can run this one.
2098) </li>
2099) <li>Vidalia crashed, but left Tor running with the last known random
2100) password. After you restart Vidalia, it generates a new random password,

2101) but Vidalia can't talk to Tor, because the random passwords are
2102) different.

2103) <br />

2104) If the dialog that prompts you for a control password has a Reset
2105) button,

2106) you can click the button and Vidalia will restart Tor with a new random
2107) control password.
2108) <br />
2109) If you do not see a Reset button, or if Vidalia is unable to restart
2110) Tor for you, you can still fix the problem manually. Simply go into your
2111) process or task manager, and terminate the Tor process. Then use Vidalia
2112) to restart Tor and all will work again.
2113) </li>
2114) <li>You had previously set Tor to run as a Windows NT service. When Tor
2115) is set to
2116) run as a service, it starts up when the system boots. If you configured
2117) Tor to start as a service through Vidalia, a random password was set
2118) and saved in Tor. When you reboot, Tor starts up and uses the random
2119) password it saved. You login and start up Vidalia. Vidalia attempts to
2120) talk to the already running Tor. Vidalia generates a random password,
2121) but it is different than the saved password in the Tor service.
2122) <br />
2123) You need to reconfigure Tor to not be a service. See the FAQ entry on

2124) <a href="#NTservice">running Tor as a

2125) Windows NT service</a>

2126) for more information on how to remove the Tor service.
2127) </li>
2128) </ol>
2129) 

2130)     <hr>

2131) 

2132)     <a id="ChooseEntryExit"></a>

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

2135) 

2136)     <p>

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

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

2141)     </p>
2142)     <dl>
2143)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>

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

2146)         </dd>
2147)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

2150)         </dd>
2151)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

2153)         </dd>
2154)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

2155)         <dd>A list of nodes to never use when picking an exit.

2156)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in
2157) this list.

2158)         </dd>
2159)     </dl>
2160)     <p>

2161)     <em>We recommend you do not use these</em>

2162)     — they are intended for testing and may disappear in future
2163) versions.

2164)     You get the best security that Tor can provide when you leave the
2165)     route selection to Tor; overriding the entry / exit nodes can mess
2166)     up your anonymity in ways we don't understand.

2167)     </p>
2168)     <p>

2169)     Note also that not every circuit is used to deliver traffic outside of 
2170)     the Tor network. It is normal to see non-exit circuits (such as those 
2171)     used to connect to hidden services, those that do directory fetches, 
2172)     those used for relay reachability self-tests, and so on) that end at 
2173)     a non-exit node. To keep a node from being used entirely, see 
2174)     <tt>ExcludeNodes</tt> and <tt>StrictNodes</tt> in the 
2175)     <a href="<page docs/tor-manual>">manual</a>.

2176)     </p>
2177)     <p>

2178)     Instead of <tt>$fingerprint</tt> you can also specify a <a

2179) 
2180) href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2"
2181) >2

2182)     letter ISO3166 country code</a> in curly braces (for example <tt>{de}</tt>),

2183)     or an ip address pattern (for example 255.254.0.0/8), or a node
2184)     nickname. Make sure there are no spaces between the commas and the
2185)     list items.

2186)     </p>
2187)     <p>

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

2190)     (eg. using ssh via connect.c), another option is to set up an

2191)     internal mapping in your configuration file using
2192) <tt>MapAddress</tt>.

2193)     See the manual page for details.
2194)     </p>

2195) 

2196)     <hr>

2197) 

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

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

2201) 
2202) <p>
2203) If your firewall works by blocking ports, then you can tell Tor to only

2204) use the ports that your firewall permits by adding "FascistFirewall 1"
2205) to

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

2207) configuration file</a>, or by clicking "My firewall only lets me connect
2208) to certain ports" in Vidalia's Network Settings window.
2209) </p>
2210) 
2211) <p>
2212) By default, when you set this Tor assumes that your firewall allows only
2213) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
2214) different set of ports with the FirewallPorts torrc option.
2215) </p>
2216) 
2217) <p>
2218) If you want to be more fine-grained with your controls, you can also
2219) use the ReachableAddresses config options, e.g.:
2220) </p>
2221) 
2222) <pre>
2223)   ReachableDirAddresses *:80
2224)   ReachableORAddresses *:443
2225) </pre>
2226) 
2227) <hr>

2228) 

2229)     <a id="DefaultExitPorts"></a>
2230)     <h3><a class="anchor" href="#DefaultExitPorts">Is there a list of default exit 

2231)     ports?</a></h3>

2232)     <p>

2233) The default open ports are listed below but keep in mind that, any port or 
2234) ports can be opened by the relay operator by configuring it in torrc or 
2235) modifying the source code. But the default according to src/or/policies.c 
2236) from the source code release tor-0.2.4.16-rc is: 

2237)     </p>
2238)     <pre>
2239)   reject 0.0.0.0/8
2240)   reject 169.254.0.0/16
2241)   reject 127.0.0.0/8
2242)   reject 192.168.0.0/16
2243)   reject 10.0.0.0/8
2244)   reject 172.16.0.0/12
2245)   reject *:25
2246)   reject *:119
2247)   reject *:135-139
2248)   reject *:445
2249)   reject *:563
2250)   reject *:1214
2251)   reject *:4661-4666
2252)   reject *:6346-6429
2253)   reject *:6699
2254)   reject *:6881-6999
2255)   accept *:*
2256)     </pre>
2257)     <p>

2258)     A relay will block access to its own IP address, as well local network 
2259)     IP addresses. A relay always blocks itself by default. This prevents 
2260)     Tor users from accidentally accessing any of the exit operator's local 
2261)     services. 
2262)     </p>
2263) 
2264)     <hr>
2265) 
2266)     <a id="SocksAndDNS"></a>
2267)     <h3><a class="anchor" href="#SocksAndDNS">How do I check if my application that uses 
2268)     SOCKS is leaking DNS requests?</a></h3>
2269) 
2270)     <p>
2271)     These are two steps you need to take here. The first is to make sure 
2272)     that it's using the correct variant of the SOCKS protocol, and the 
2273)     second is to make sure that there aren't other leaks. 
2274)     </p>
2275) 
2276)     <p>
2277)     Step one: add "TestSocks 1" to your torrc file, and then watch your 
2278)     logs as you use your application. Tor will then log, for each SOCKS 
2279)     connection, whether it was using a 'good' variant or a 'bad' one. 
2280)     (If you want to automatically disable all 'bad' variants, set 
2281)     "SafeSocks 1" in your <a href="#torrc">torrc</a> file.) 
2282)     </p>
2283) 
2284)     <p>
2285)     Step two: even if your application is using the correct variant of 
2286)     the SOCKS protocol, there is still a risk that it could be leaking 
2287)     DNS queries. This problem happens in Firefox extensions that resolve 
2288)     the destination hostname themselves, for example to show you its IP 
2289)     address, what country it's in, etc. These applications may use a safe 
2290)     SOCKS variant when actually making connections, but they still do DNS 
2291)     resolves locally. If you suspect your application might behave like 
2292)     this, you should use a network sniffer like <a 
2293)     href="https://www.wireshark.org/">Wireshark</a> and look for 
2294)     suspicious outbound DNS requests. I'm afraid the details of how to look 
2295)     for these problems are beyond the scope of a FAQ entry though -- find 
2296)     a friend to help if you have problems. 

2297)     </p>
2298) 
2299)     <hr>
2300) 

2301)     <a id="HowDoIDecide"></a>
2302)     <h3><a class="anchor" href="#HowDoIDecide">How do I decide if I should 
2303)     run a relay?</a></h3>
2304)     <p>
2305)     We're looking for people with reasonably reliable Internet connections, 
2306)     that have at least 20 kilobytes/second each way. If that's you, please 
2307)     consider <a href="https://www.torproject.org/docs/tor-relay-debian">helping 
2308)     out</a>. 
2309)     </p>
2310)     
2311)     <hr>
2312)     
2313)     <a id="WhyIsntMyRelayBeingUsedMore"></a>
2314)     <h3><a class="anchor" href="#WhyIsntMyRelayBeingUsedMore">Why isn't my 
2315)     relay being used more?</a></h3>
2316)     <p>
2317)     If your relay is relatively new then give it time. Tor decides which 
2318)     relays it uses heuristically based on reports from Bandwidth 
2319)     Authorities. These authorities take measurements of your relay's 
2320)     capacity and, over time, directs more traffic there until it reaches 
2321)     an optimal load. The lifecycle of a new relay is explained in more 
2322)     depth in <a href="https://blog.torproject.org/blog/lifecycle-of-a-new-relay">
2323)     this blog post</a>.
2324)     </p>
2325)     <p>
2326)     If you've been running a relay for a while and still having issues 
2327)     then try asking on the <a href=
2328)     "https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays/">
2329)     tor-relays list</a>. 
2330)     </p>
2331)     
2332)     <hr>
2333) 

2334)     <a id="IDontHaveAStaticIP"></a>
2335)     <h3><a class="anchor" href="#IDontHaveAStaticIP">I don't have a static 
2336)     IP.</a></h3>
2337) 
2338)     <p>
2339)     Tor can handle relays with dynamic IP addresses just fine. Just leave 
2340)     the "Address" line in your torrc blank, and Tor will guess. 
2341)     </p>
2342) 
2343)     <hr>
2344) 
2345)     <a id="ModemKeepsCrashing"></a>
2346)     <h3><a class="anchor" href="#ModemKeepsCrashing">My cable/DSL modem 
2347)     keeps crashing. What's going on?</h3></a>
2348) 
2349)     <p>
2350)     Tor relays hold many connections open at once. This is more intensive 
2351)     use than your cable modem (or other home router) would ever get normally. 
2352)     So if there are any bugs or instabilities, they might show up now. 
2353)     </p>
2354)     <p>
2355)     If your router keeps crashing, you've got two options. First, you should 
2356)     try to upgrade its firmware. If you need tips on how to do this, ask 
2357)     Google or your cable/router provider, or try the Tor IRC channel. 
2358)     </p>
2359) 
2360)     <p>
2361)     Usually the firmware upgrade will fix it. If it doesn't, you will 
2362)     probably want to get a new (better) router. 
2363)     </p>
2364) 
2365)     <hr>
2366) 
2367)     <a id="PortscannedMore"></a>
2368)     <h3><a class="anchor" href="#PortscannedMore">Why do I get portscanned 
2369)     more often when I run a Tor relay?</a></h3>
2370) 
2371)     <p>
2372)     If you allow exit connections, some services that people connect to 
2373)     from your relay will connect back to collect more information about you. 
2374)     For example, some IRC servers connect back to your identd port to record 
2375)     which user made the connection. (This doesn't really work for them, 
2376)     because Tor doesn't know this information, but they try anyway.) Also, 
2377)     users exiting from you might attract the attention of other users on the 
2378)     IRC server, website, etc. who want to know more about the host they're 
2379)     relaying through. 
2380)     </p>
2381)     <p>
2382)     Another reason is that groups who scan for open proxies on the Internet 
2383)     have learned that sometimes Tor relays expose their socks port to the 
2384)     world. We recommend that you bind your socksport to local networks only. 
2385)     </p>
2386)     <p>
2387)     In any case, you need to keep up to date with your security. See this <a 
2388)     href="https://trac.torproject.org/projects/tor/wiki/doc/OperationalSecurity">article 
2389)     on operational security for Tor relays</a> for more suggestions. 
2390)     </p>
2391) 
2392)     <hr>
2393) 
2394)     <a id="MoreThanOneCPU"></a>
2395)     <h3><a class="anchor" href="#MoreThanOneCPU">I have more than one CPU. 
2396)     Does this help?</a></h3>
2397) 
2398)     <p>
2399)     Yes. You can set your NumCpus config option in torrc to the number of 
2400)     CPUs you have, and Tor will spawn this many cpuworkers to deal with 
2401)     public key operations in parallel. 
2402)     </p>
2403) 
2404)     <p>
2405)     This option has no effect for clients. 
2406)     </p>
2407) 
2408)     <hr>
2409) 

2410)     <a id="HighCapacityConnection"></a>    
2411)     <h3><a class="anchor" href="#HighCapacityConnection">How can I get Tor to fully 
2412)     make use of my high capacity connection?</a></h3>
2413)     
2414)     <p>
2415)     See <a href="http://archives.seul.org/or/relays/Aug-2010/msg00034.html">this 
2416)     tor-relays thread</a>.
2417)     </p>
2418)     
2419)     <hr>    
2420)     

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

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

2424) 

2425)     <p>
2426)     We aim to make setting up a Tor relay easy and convenient:
2427)     </p>

2428) 

2429)     <ul>
2430)     <li>Tor has built-in support for <a

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

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

2435) 
2436) href="<wikifaq>#HowcanIlimitthetotalamountofbandwidthusedbymyTorrelay">
2437) hibernation

2438)     feature</a>.
2439)     </li>

2440)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a>
2441) that
2442)     specifies what sort of outbound connections are allowed or refused
2443) from
2444)     that relay. If you are uncomfortable allowing people to exit from
2445) your
2446)     relay, you can set it up to only allow connections to other Tor
2447) relays.

2448)     </li>
2449)     <li>It's fine if the relay goes offline sometimes. The directories
2450)     notice this quickly and stop advertising the relay. Just try to make
2451)     sure it's not too often, since connections using the relay when it
2452)     disconnects will break.
2453)     </li>
2454)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
2455)     leave the Address config option blank, and Tor will try to guess.
2456)     </li>
2457)     <li>If your relay is behind a NAT and it doesn't know its public
2458)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

2459)     forwarding. Forwarding TCP connections is system dependent but

2460)     <a href="#BehindANAT">this FAQ entry</a>

2461)     offers some examples on how to do this.
2462)     </li>
2463)     <li>Your relay will passively estimate and advertise its recent

2464)     bandwidth capacity, so high-bandwidth relays will attract more users
2465) than
2466)     low-bandwidth ones. Therefore having low-bandwidth relays is useful
2467) too.

2468)     </li>
2469)     </ul>

2470) 

2471)     <hr>

2472)     
2473)     <a id="BandwidthShaping"></a>
2474)     <h3><a class="anchor" href="#BandwidthShaping">What bandwidth shaping 
2475)     options are available to Tor relays?</a></h3>
2476) 
2477)     <p>
2478)     There are two options you can add to your torrc file: 
2479)     </p>
2480)     <ul>
2481)     <li>
2482)     BandwidthRate is the maximum long-term bandwidth allowed (bytes per 
2483)     second). For example, you might want to choose "BandwidthRate 2 MB" 
2484)     for 2 megabytes per second (a fast connection), or "BandwidthRate 50 
2485)     KB" for 50 kilobytes per second (a medium-speed cable connection). 
2486)     The minimum BandwidthRate is 20 kilobytes per second. 
2487)     </li>
2488)     <li>
2489)     BandwidthBurst is a pool of bytes used to fulfill requests during 
2490)     short periods of traffic above BandwidthRate but still keeps the 
2491)     average over a long period to BandwidthRate. A low Rate but a high 
2492)     Burst enforces a long-term average while still allowing more traffic 
2493)     during peak times if the average hasn't been reached lately. For example, 
2494)     if you choose "BandwidthBurst 50 KB" and also use that for your 
2495)     BandwidthRate, then you will never use more than 50 kilobytes per second; 
2496)     but if you choose a higher BandwidthBurst (like 1 MB), it will allow 
2497)     more bytes through until the pool is empty.
2498)     </li>
2499)     </ul>
2500)     <p>
2501)     If you have an asymmetric connection (upload less than download) such 
2502)     as a cable modem, you should set BandwidthRate to less than your smaller 
2503)     bandwidth (Usually that's the upload bandwidth). (Otherwise, you could 
2504)     drop many packets during periods of maximum bandwidth usage -- you may 
2505)     need to experiment with which values make your connection comfortable.) 
2506)     Then set BandwidthBurst to the same as BandwidthRate. 
2507)     </p>
2508)     <p>
2509)     Linux-based Tor nodes have another option at their disposal: they can 
2510)     prioritize Tor traffic below other traffic on their machine, so that 
2511)     their own personal traffic is not impacted by Tor load. A ​<a 
2512)     href="https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/linux-tor-prio.sh">script
2513)     to do this</a> can be found in the Tor source distribution's contrib 
2514)     directory. 
2515)     </p>
2516)     <p>
2517)     Additionally, there are hibernation options where you can tell Tor to 
2518)     only serve a certain amount of bandwidth per time period (such as 100 
2519)     GB per month). These are covered in the <a 
2520)     href="#LimitTotalBandwidth">hibernation entry</a> below. 
2521)     </p>
2522)     <p>
2523)     Note that BandwidthRate and BandwidthBurst are in <b>Bytes,</b>not Bits. 
2524)     </p>
2525) 
2526)     <hr>
2527) 
2528)     <a id="LimitTotalBandwidth"></a>
2529)     <h3><a class="anchor" href="#LimitTotalBandwidth">How can I limit the 
2530)     total amount of bandwidth used by my Tor relay?</a></h3>
2531)     <p>
2532)     The accounting options in the torrc file allow you to specify the maximum 
2533)     amount of bytes your relay uses for a time period. 
2534)     </p>
2535)     <pre>
2536)     AccountingStart day week month [day] HH:MM
2537)     </pre>
2538)     <p>
2539)     This specifies when the accounting should reset. For instance, to setup 
2540)     a total amount of bytes served for a week (that resets every Wednesday 
2541)     at 10:00am), you would use: 
2542)     </p>
2543)     <pre>
2544)     AccountingStart week 3 10:00
2545)     AccountingMax N bytes KB MB GB TB
2546)     </pre>
2547)     <p>
2548)     This specifies the maximum amount of data your relay will send during an 
2549)     accounting period, and the maximum amount of data your relay will receive 
2550)     during an account period. When the accounting period resets (from 
2551)     AccountingStart), then the counters for AccountingMax are reset to 0.
2552)     </p>
2553)     <p>
2554)     Example. Let's say you want to allow 1 GB of traffic every day in each 
2555)     direction and the accounting should reset at noon each day: 
2556)     </p>
2557)     <pre>
2558)     AccountingStart day 12:00
2559)     AccountingMax 1 GB
2560)     </pre>
2561)     <p>
2562)     Note that your relay won't wake up exactly at the beginning of each 
2563)     accounting period. It will keep track of how quickly it used its 
2564)     quota in the last period, and choose a random point in the new interval 
2565)     to wake up. This way we avoid having hundreds of relays working at the 
2566)     beginning of each month but none still up by the end. 
2567)     </p>
2568)     <p>
2569)     If you have only a small amount of bandwidth to donate compared to your 
2570)     connection speed, we recommend you use daily accounting, so you don't 
2571)     end up using your entire monthly quota in the first day. Just divide 
2572)     your monthly amount by 30. You might also consider rate limiting to 
2573)     spread your usefulness over more of the day: if you want to offer X GB 
2574)     in each direction, you could set your BandwidthRate to 20*X. For example, 
2575)     if you have 10 GB to offer each way, you might set your BandwidthRate to 
2576)     200 KB: this way your relay will always be useful for at least half of 
2577)     each day. 
2578)     </p>
2579)     <hr>

2580) 

2581)     <a id="ExitPolicies"></a>

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

2584) 

2585)     <p>
2586)     Great. That's exactly why we implemented exit policies.
2587)     </p>

2588) 

2589)     <p>
2590)     Each Tor relay has an exit policy that specifies what sort of

2591)     outbound connections are allowed or refused from that relay. The
2592) exit

2593)     policies are propagated to Tor clients via the directory, so clients
2594)     will automatically avoid picking exit relays that would refuse to
2595)     exit to their intended destination. This way each relay can decide
2596)     the services, hosts, and networks he wants to allow connections to,

2597)     based on abuse potential and his own situation. Read the FAQ entry
2598) on
2599)     <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might
2600) encounter</a>

2601)     if you use the default exit policy, and then read Mike Perry's

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

2603)     for running an exit node with minimal harassment</a>.
2604)     </p>

2605) 

2606)     <p>

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

2608)     (e.g. web browsing), but <a

2609) href="#DefaultExitPorts">restricts</a>

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

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

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

2615)     file. If you want to avoid most if not all abuse potential, set it
2616) to
2617)     "reject *:*" (or un-check all the boxes in Vidalia). This setting
2618) means
2619)     that your relay will be used for relaying traffic inside the Tor
2620) network,

2621)     but not for connections to external websites or other services.
2622)     </p>

2623) 

2624)     <p>

2625)     If you do allow any exit connections, make sure name resolution
2626) works

2627)     (that is, your computer can resolve Internet addresses correctly).

2628)     If there are any resources that your computer can't reach (for
2629) example,

2630)     you are behind a restrictive firewall or content filter), please

2631)     explicitly reject them in your exit policy — otherwise Tor
2632) users

2633)     will be impacted too.
2634)     </p>

2635) 

2636)     <hr>

2637) 

2638)     <a id="DifferentComputer"></a>

2639)     <h3><a class="anchor" href="#DifferentComputer">I want to run my 
2640)     Tor client on a different computer than my applications.</a></h3>

2641)     <p>

2642)     By default, your Tor client only listens for applications that 
2643)     connect from localhost. Connections from other computers are 
2644)     refused. If you want to torify applications on different computers 
2645)     than the Tor client, you should edit your torrc to define 
2646)     SocksListenAddress 0.0.0.0 g and then restart (or hup) Tor. If you 
2647)     want to get more advanced, you can configure your Tor client on a 
2648)     firewall to bind to your internal IP but not your external IP.  

2649)     </p>
2650) 
2651)     <hr>
2652) 
2653)     <a id="ServerClient"></a>

2654)     <h3><a class="anchor" href="#ServerClient">Can I install Tor on a 
2655)     central server, and have my clients connect to it?</a></h3>
2656)     <p>
2657)      Yes. Tor can be configured as a client or a relay on another 
2658)      machine, and allow other machines to be able to connect to it 
2659)      for anonymity. This is most useful in an environment where many 
2660)      computers want a gateway of anonymity to the rest of the world. 
2661)      However, be forwarned that with this configuration, anyone within 
2662)      your private network (existing between you and the Tor 
2663)      client/relay) can see what traffic you are sending in clear text. 
2664)      The anonymity doesn't start until you get to the Tor relay. 
2665)      Because of this, if you are the controller of your domain and you 
2666)      know everything's locked down, you will be OK, but this configuration 
2667)      may not be suitable for large private networks where security is 
2668)      key all around.
2669)     </p>
2670)     <p>
2671) Configuration is simple, editing your torrc file's SocksListenAddress 
2672) according to the following examples:

2673)     </p>
2674)     <pre>

2675) 
2676)   #This provides local interface access only, 
2677)   #needs SocksPort to be greater than 0
2678)   SocksListenAddress 127.0.0.1 
2679) 
2680)   #This provides access to Tor on a specified interface
2681)   SocksListenAddress 192.168.x.x:9100 
2682) 
2683)   #Accept from all interfaces
2684)   SocksListenAddress 0.0.0.0:9100
2685)    </pre>

2686)     <p>

2687) You can state multiple listen addresses, in the case that you are 
2688) part of several networks or subnets.

2689)     </p>
2690)     <pre>
2691)   SocksListenAddress 192.168.x.x:9100 #eth0
2692)   SocksListenAddress 10.x.x.x:9100 #eth1
2693)     </pre>
2694)     <p>

2695) After this, your clients on their respective networks/subnets would specify 
2696) a socks proxy with the address and port you specified SocksListenAddress 
2697) to be. 

2698)     </p>
2699)     <p>

2700) Please note that the SocksPort configuration option gives the port ONLY for 
2701) localhost (127.0.0.1). When setting up your SocksListenAddress(es), you need 
2702) to give the port with the address, as shown above.

2703)     <p>

2704) If you are interested in forcing all outgoing data through the central Tor 
2705) client/relay, instead of the server only being an optional proxy, you may find 
2706) the program iptables (for *nix) useful. 

2707)     </p>
2708) 
2709)     <hr>
2710) 

2711)     <a id="JoinTheNetwork"></a>

2712)     <h3><a class="anchor" href="#JoinTheNetwork">So I can just configure a 
2713)     nickname and ORPort and join the network?</a></h3>

2714) 
2715)     <p>

2716)      Yes. You can join the network and be a useful relay just by configuring 
2717)      your Tor to be a relay and making sure it's reachable from the outside.

2718)     </p>
2719)     <p>
2720) 30 Seconds to a Tor Relay:
2721)     </p>
2722)     <ul><li>
2723)     Configure a Nickname: 
2724)     </li></ul>
2725)     <pre>
2726) Nickname ididnteditheconfig
2727)     </pre>

2728)     <ul><li>

2729)     Configure ORPort: 

2730)     </li></ul>

2731)     <pre>
2732) ORPort 9001
2733)     </pre>

2734)     <ul><li>

2735)     Configure Contact Info: 

2736)     </li></ul>

2737) 
2738)     <pre>
2739) ContactInfo human@…

2740)     </pre>
2741)     <ul><li>

2742)     Start Tor. Watch the log file for a log entry that states: "Self-testing 
2743)     indicates your ORPort is reachable from the outside. Excellent. Publishing 
2744)     server descriptor."

2745)     </li></ul>

2746) 
2747)     <hr />

2748) 

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

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

2752) 

2753)     <p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for
2754) short)
2755)     are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't

2756)     listed in the public Tor directory.

2757)     That means that ISPs or governments trying to block access to the

2758)     Tor network can't simply block all bridges.

2759)     </p>

2760) 

2761)     <p>Being a normal relay vs being a bridge relay is almost the same
2762)     configuration: it's just a matter of whether your relay is listed

2763)     publicly or not.

2764)     </p>

2765) 

2766)     <p>

2767)     So bridges are useful a) for Tor users in oppressive regimes,

2768)     and b) for people who want an extra layer of security

2769)     because they're worried somebody will recognize that it's a public
2770)     Tor relay IP address they're contacting.

2771)     </p>

2772) 

2773)     <p>
2774)     Several countries, including China and Iran, have found ways to

2775)     detect and block connections to Tor bridges.

2776)     <a href="<page projects/obfsproxy>">Obfsproxy</a> bridges address

2777)     this by adding another layer of obfuscation.

2778)     </p>
2779) 

2780)     <p>So should you run a normal relay or bridge relay? If you have
2781) lots

2782)     of bandwidth, you should definitely run a normal relay.
2783)     If you're willing

2784)     to <a href="#ExitPolicies">be an exit</a>, you should definitely
2785)     run a normal relay, since we need more exits. If you can't be an
2786)     exit and only have a little bit of bandwidth, be a bridge. Thanks
2787)     for volunteering!

2788)     </p>

2789) 

2790)     <hr>

2791) 

2792) <a id="UpgradeOrMove"></a>

2793) <h3><a class="anchor" href="#UpgradeOrMove">I want to upgrade/move my relay. 
2794) How do I keep the same key?</a></h3>

2795) 
2796) <p>

2797)  When upgrading your Tor relay, or running it on a different computer, 
2798)  the important part is to keep the same nickname (defined in your torrc 
2799)  file) and the same identity key (stored in "keys/secret_id_key" in 
2800)  your DataDirectory).

2801) </p>
2802) <p>

2803) This means that if you're upgrading your Tor relay and you keep the same 
2804) torrc and the same DataDirectory, then the upgrade should just work and 
2805) your relay will keep using the same key. If you need to pick a new 
2806) DataDirectory, be sure to copy your old keys/secret_id_key over. 

2807) </p>
2808) 
2809)     <hr>
2810) 
2811) <a id="NTService"></a>

2812) <h3><a class="anchor" href="#NTService">How do I run my Tor relay as an NT 
2813) service?</a></h3>

2814) 
2815) <p>

2816)  You can run Tor as a service on all versions of Windows except Windows 
2817)  95/98/ME. This way you can run a Tor relay without needing to always have 
2818)  Vidalia running.

2819) </p>
2820) <p>

2821) If you've already configured your Tor to be a relay, please note that when 
2822) you enable Tor as a service, it will use a different DatagDirectory, and 
2823) thus will generate a different key. If you want to keep using the old key, 
2824) see the Upgrading your Tor relay FAQ entry for how to restore the old 
2825) identity key.

2826) </p>
2827) <p>
2828) To install Tor as a service, you can simply run:
2829) </p>
2830) <pre>
2831) tor --service install
2832) </pre>
2833) <p>

2834) A service called Tor Win32 Service will be installed and started. This 
2835) service will also automatically start every time Windows boots, unless 
2836) you change the Start-up type. An easy way to check the status of Tor, 
2837) start or stop the service, and change the start-up type is by running 
2838) services.msc and finding the Tor service in the list of currently 
2839) installed services.

2840) </p>
2841) <p>

2842) Optionally, you can specify additional options for the Tor service using 
2843) the -options argument. For example, if you want Tor to use C:\tor\torrc, 
2844) instead of the default torrc, and open a control port on port 9151, you 
2845) would run:

2846) </p>
2847) <pre>
2848) tor --service install -options -f C:\tor\torrc ControlPort 9151
2849) </pre>
2850) <p>
2851) You can also start or stop the Tor service from the command line by typing:
2852) </p>
2853) <pre>
2854)  tor --service start
2855) </pre>
2856) <p>
2857) or
2858) </p>
2859) <pre>
2860)  tor --service stop
2861) </pre>
2862) <p>
2863) To remove the Tor service, you can run the following command:
2864) </p>
2865) <pre>
2866) tor --service remove
2867) </pre>
2868) <p>

2869) If you are running Tor as a service and you want to uninstall Tor entirely, 
2870) be sure to run the service removal command (shown above) first before 
2871) running the uninstaller from "Add/Remove Programs". The uninstaller is 
2872) currently not capable of removing the active service.

2873) </p>
2874) 
2875) <hr>
2876) 
2877) <a id="VirtualServer"></a>

2878) <h3><a class="anchor" href="#VirtualServer">Can I run a Tor relay from my 
2879) virtual server account?</a></h3>

2880) 
2881) <p>

2882) Some ISPs are selling "vserver" accounts that provide what they call a 
2883) virtual server -- you can't actually interact with the hardware, and 
2884) they can artificially limit certain resources such as the number of file 
2885) descriptors you can open at once. Competent vserver admins are able to 
2886) configure your server to not hit these limits. For example, in SWSoft's 
2887) Virtuozzo, investigate /proc/user_beancounters. Look for "failcnt" in 
2888) tcpsndbuf, tcprecvbuf, numothersock, and othersockbuf. Ask for these to 
2889) be increased accordingly. Some users have seen settings work well as follows: 

2890) <p>

2891) <table border="1">

2892) <tr>
2893) <td>
2894) <i>resource</i>
2895) </td>
2896) <td>
2897) <i>held</i>
2898) </td>
2899) <td>
2900) <i>maxheld</i>
2901) </td>
2902) <td>
2903) <i>barrier</i>
2904) </td>
2905) <td>
2906) <i>limit</i>
2907) </td>
2908) <td>
2909) <i>failcnt</i>
2910) </td>
2911) </tr>
2912) <tr>
2913) <td>
2914) tcpsndbuf
2915) </td>
2916) <td>
2917) 46620
2918) </td>
2919) <td>
2920) 48840
2921) </td>
2922) <td>
2923) 3440640
2924) </td>
2925) <td>
2926) 5406720
2927) </td>
2928) <td>
2929) 0
2930) </td>
2931) </tr>
2932) <tr>
2933) <td>
2934) tcprcvbuf
2935) </td>
2936) <td>
2937) 0
2938) </td>
2939) <td>
2940) 2220
2941) </td>
2942) <td>
2943) 3440640
2944) </td>
2945) <td>
2946) 5406720
2947) </td>
2948) <td>
2949) 0
2950) </td>
2951) </tr>
2952) <tr>
2953) <td>
2954) othersockbuf
2955) </td>
2956) <td>
2957) 243516
2958) </td>
2959) <td>
2960) 260072
2961) </td>
2962) <td>
2963) 2252160
2964) </td>
2965) <td>
2966) 4194304
2967) </td>
2968) <td>
2969) 0
2970) </td>
2971) </tr>
2972) <tr>
2973) <td>
2974) numothersock
2975) </td>
2976) <td>
2977) 151
2978) </td>
2979) <td>
2980) 153
2981) </td>
2982) <td>
2983) 720
2984) </td>
2985) <td>
2986) 720
2987) </td>
2988) <td>
2989) 0
2990) </td>
2991) </tr>
2992) </table>
2993) <p>
2994)  Xen, Virtual Box and VMware virtual servers have no such limits normally.
2995) </p>
2996) <p>

2997) If the vserver admin will not increase system limits another option is 
2998) to reduce the memory allocated to the send and receive buffers on TCP 
2999) connections Tor uses. An experimental feature to constrain socket buffers 
3000) has recently been added. If your version of Tor supports it, set 
3001) "ConstrainedSockets 1" in your configuration. See the tor man page for 
3002) additional details about this option.

3003) </p>
3004) <p>

3005) Unfortunately, since Tor currently requires you to be able to connect to 
3006) all the other Tor relays, we need you to be able to use at least 1024 file 
3007) descriptors. This means we can't make use of Tor relays that are crippled 
3008) in this way.

3009) </p>
3010) <p>

3011) We hope to fix this in the future, once we know how to build a Tor network 
3012) with restricted topologies -- that is, where each node connects to only a 
3013) few other nodes. But this is still a long way off.

3014) </p>
3015) 

3016) <hr>
3017) 

3018) <a id="MultipleRelays"></a>

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

3021) 
3022) <p>
3023) Great. If you want to run several relays to donate more to the network,
3024) we're happy with that. But please don't run more than a few dozen on
3025) the same network, since part of the goal of the Tor network is dispersal
3026) and diversity.
3027) </p>
3028) 
3029) <p>
3030) If you do decide to run more than one relay, please set the "MyFamily"

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

3033) </p>
3034) 
3035) <pre>
3036)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
3037) </pre>
3038) 
3039) <p>
3040) where each fingerprint is the 40 character identity fingerprint (without

3041) spaces). You can also list them by nickname, but fingerprint is safer.
3042) Be

3043) sure to prefix the digest strings with a dollar sign ('$') so that the
3044) digest is not confused with a nickname in the config file.
3045) </p>
3046) 
3047) <p>
3048) That way clients will know to avoid using more than one of your relays
3049) in a single circuit. You should set MyFamily if you have administrative
3050) control of the computers or of their network, even if they're not all in
3051) the same geographic location.
3052) </p>
3053) 
3054)     <hr>
3055) 

3056)     <a id="WrongIP"></a>

3057)     <h3><a class="anchor" href="#WrongIP">My relay is picking the wrong 
3058)     IP address.</a></h3>

3059)     <p>

3060)  Tor guesses its IP address by asking the computer for its hostname, and 
3061)  then resolving that hostname. Often people have old entries in their 
3062)  /etc/hosts file that point to old IP addresses.

3063)     </p>
3064)     <p>

3065) If that doesn't fix it, you should use the "Address" config option to 
3066) specify the IP you want it to pick. If your computer is behind a NAT and 
3067) it only has an internal IP address, see the following FAQ entry on <a 
3068) href="https://www.torproject.org/docs/faq.html.en#RelayFlexible">dynamic 
3069) IP addresses</a>.

3070)     </p>
3071)     <p>

3072) Also, if you have many addresses, you might also want to set 
3073) "OutboundBindAddress" so external connections come from the IP you intend 
3074) to present to the world. 

3075)     </p>
3076) 
3077)     <hr>
3078) 
3079)     <a id="BehindANAT"></a>
3080)     <h3><a class="anchor" href="#BehindANAT">I'm behind a NAT/Firewall.</a></h3>
3081) 
3082)     <p>

3083) See <a>​http://portforward.com/</a> for directions on how to port forward with 
3084) your NAT/router device.

3085) </p>
3086) <p>

3087) If your relay is running on a internal net you need to setup port forwarding. 
3088) Forwarding TCP connections is system dependent but the firewalled-clients FAQ 
3089) entry offers some examples on how to do this.

3090) </p>
3091) <p>

3092) Also, here's an example of how you would do this on GNU/Linux if you're using 
3093) iptables:

3094) </p>
3095) <pre>
3096) /sbin/iptables -A INPUT -i eth0 -p tcp --destination-port 9001 -j ACCEPT
3097) </pre>
3098) <p>

3099) You may have to change "eth0" if you have a different external interface 
3100) (the one connected to the Internet). Chances are you have only one (except 
3101) the loopback) so it shouldn't be too hard to figure out. 

3102)     </p>
3103)     <hr>
3104) 

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

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

3108) 

3109)     <p>If your Tor relay is using more memory than you'd like, here are
3110) some

3111)     tips for reducing its footprint:
3112)     </p>

3113) 

3114)     <ol>
3115)     <li>If you're on Linux, you may be encountering memory fragmentation

3116)     bugs in glibc's malloc implementation. That is, when Tor releases
3117) memory
3118)     back to the system, the pieces of memory are fragmented so they're
3119) hard
3120)     to reuse. The Tor tarball ships with OpenBSD's malloc
3121) implementation,
3122)     which doesn't have as many fragmentation bugs (but the tradeoff is
3123) higher
3124)     CPU load). You can tell Tor to use this malloc implementation
3125) instead:

3126)     <tt>./configure --enable-openbsd-malloc</tt></li>

3127) 

3128)     <li>If you're running a fast relay, meaning you have many TLS
3129) connections

3130)     open, you are probably losing a lot of memory to OpenSSL's internal
3131)     buffers (38KB+ per socket). We've patched OpenSSL to <a

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

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

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

3138)     this feature.</li>

3139) 

3140) <!-- Nickm says he's not sure this is still accurate
3141) 

3142)     <li>If you're running on Solaris, OpenBSD, NetBSD, or
3143)     old FreeBSD, Tor is probably forking separate processes
3144)     rather than using threads. Consider switching to a <a
3145)     href="<wikifaq>#WhydoesntmyWindowsorotherOSTorrelayrunwell">better
3146)     operating system</a>.</li>

3147) -->

3148)     <li>If you still can't handle the memory load, consider reducing the

3149)     amount of bandwidth your relay advertises. Advertising less
3150) bandwidth

3151)     means you will attract fewer users, so your relay shouldn't grow
3152)     as large. See the <tt>MaxAdvertisedBandwidth</tt> option in the man
3153)     page.</li>

3154) 

3155)     </ol>

3156) 

3157)     <p>

3158)     All of this said, fast Tor relays do use a lot of ram. It is not
3159) unusual

3160)     for a fast exit relay to use 500-1000 MB of memory.
3161)     </p>

3162) 

3163)     <hr>

3164) 

3165)     <a id="BetterAnonymity"></a>

3166)     <h3><a class="anchor" href="#BetterAnonymity">Do I get better anonymity 
3167)     if I run a relay?</a></h3>

3168) 

3169)     <p>

3170) Yes, you do get better anonymity against some attacks.
3171)     </p>
3172)     <p>

3173) The simplest example is an attacker who owns a small number of Tor relays. 
3174) He will see a connection from you, but he won't be able to know whether 
3175) the connection originated at your computer or was relayed from somebody else.

3176)     </p>
3177)     <p>

3178) There are some cases where it doesn't seem to help: if an attacker can 
3179) watch all of your incoming and outgoing traffic, then it's easy for him 
3180) to learn which connections were relayed and which started at you. (In 
3181) this case he still doesn't know your destinations unless he is watching 
3182) them too, but you're no better off than if you were an ordinary client.)

3183)     </p>
3184)     <p>

3185) There are also some downsides to running a Tor relay. First, while we 
3186) only have a few hundred relays, the fact that you're running one might 
3187) signal to an attacker that you place a high value on your anonymity. 
3188) Second, there are some more esoteric attacks that are not as 
3189) well-understood or well-tested that involve making use of the knowledge 
3190) that you're running a relay -- for example, an attacker may be able to 
3191) "observe" whether you're sending traffic even if he can't actually watch 
3192) your network, by relaying traffic through your Tor relay and noticing 
3193) changes in traffic timing.

3194)     </p>
3195)     <p>

3196) It is an open research question whether the benefits outweigh the risks. 
3197) A lot of that depends on the attacks you are most worried about. For 
3198) most users, we think it's a smart move. 

3199)     </p>

3200) 

3201)     <hr>

3202) 

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

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

3206) 
3207)     <p>

3208)     Sure! We recommend these non-profit charities that are happy to turn

3209)     your donations into better speed and anonymity for the Tor network:
3210)     </p>
3211)     <ul>
3212)     <li><a href="https://www.torservers.net/">torservers.net</a>
3213)     is a German charitable non-profit that runs a wide variety of

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

3216)     <li><a

3217) href="https://www.noisebridge.net/wiki/Noisebridge_Tor">Noisebridge</a>

3218)     is a US-based 501(c)(3) non-profit that collects donations and turns

3219)     them into more US-based exit relay capacity.</li>
3220)     <li><a href="https://nos-oignons.net/">Nos Oignons</a> is a French
3221)     charitable non-profit that runs fast exit relays in France.</li>

3222)     </ul>
3223) 
3224)     <p>
3225)     These organizations are not the same as <a href="<page
3226)     donate/donate>">The Tor Project, Inc</a>, but we consider that a

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

3229)     </p>
3230) 
3231)     <p>
3232)     Note that there can be a tradeoff here between anonymity and

3233)     performance. The Tor network's anonymity comes in part from
3234) diversity,

3235)     so if you are in a position to run your own relay, you will be

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

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

3239)     several larger relays is more efficient at improving network