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><a href="#General">General questions:</a><br />
18)     <a href="#CompilationAndInstallation">Compilation and Installation:</a><br />
19)     <a href="#TBBGeneral">Tor Browser Bundle (general):</a><br />

20)     <a href="#TBB3.x">Tor Browser Bundle (3.x series):</a><br />

21)     <a href="#AdvancedTorUsage">Advanced Tor usage:</a><br />
22)     <a href="#RunningATorRelay">Running a Tor relay:</a><br />
23)     <a href="#TorHiddenServices">Tor hidden services:</a><br />
24)     <a href="#Development">Development:</a><br />
25)     <a href="#AnonymityAndSecurity">Anonymity and Security:</a><br />
26)     <a href="#AlternateDesigns">Alternate designs that we don't do (yet):</a><br />
27)     <a href="#Abuse">Abuse:</a></p>

28) 

29) <hr>
30) 
31)     <p>General questions:</p>

32)     <ul>
33)     <li><a href="#WhatIsTor">What is Tor?</a></li>

34)     <li><a href="#Torisdifferent">How is Tor different from other
35) proxies?</a></li>

36)     <li><a href="#CompatibleApplications">What programs can I use with
37)     Tor?</a></li>
38)     <li><a href="#WhyCalledTor">Why is it called Tor?</a></li>
39)     <li><a href="#Backdoor">Is there a backdoor in Tor?</a></li>

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

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

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

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

44)     <li><a href="#FileSharing">How can I share files anonymously through Tor?
45)     </a></li>

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

48)     <li><a href="#IsItWorking">How can I tell if Tor is working, and that my

49)     connections really are anonymized?</a></li>

50)     <li><a href="#Mobile">Can I use Tor on my phone or mobile device?</a></li>

51)     <li><a href="#OutboundPorts">Do I have to open all these outbound ports

52)     on my firewall?</a></li>

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

54)     <li><a href="#NoDataScrubbing">Does Tor remove personal information

55)     from the data my application sends?</a></li>

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

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

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

60)     </ul>

61) 

62)     <p>Compilation and Installation:</p>

63) 

64)     <ul>
65)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
66)     <li><a href="#PGPSigs">What are these "sig" files on the download
67)     page?</a></li>

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

70)     <li><a href="#VirusFalsePositives">Why does my Tor executable appear to

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

72)     <li><a href="#tarballs">How do I open a .tar.gz or .tar.xz file?</a></li>

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

75)     </ul>

76) 

77)     <p>Tor Browser Bundle (general):</p>

78)     <ul>

79) 

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

82)     <li><a href="#Ubuntu">I'm using Ubuntu, and I can't start Tor Browser.

83)     </a></li>

84)     <li><a href="#SophosOnMac">I'm using the Sophos anti-virus

85)     software on my Mac, and Tor starts but I can't browse anywhere.</a></li>

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

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

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

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

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

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

95)     <li><a href="#ForeignLanguages">Why does Google show up in foreign

96)     languages?</a></li>

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

99)     <li><a href="#NeedToUseAProxy">My internet connection requires an HTTP

100)     or SOCKS Proxy</a></li>

101)     <li><a href="#TBBSocksPort">I want to
102)     run another application through Tor.</a></li>

103)     <li><a href="#CantSetProxy">What should I do if I can't set a proxy

104)     with my application?</a></li>

105)     </ul>
106) 

107)     <p>Tor Browser Bundle (3.x series):</p>

108) 
109)     <ul>

110)     <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia)

111)     go?</a></li>
112)     <li><a href="#DisableJS">How do I disable JavaScript?</a></li>

113)     <li><a href="#VerifyDownload">How do I verify the download

114)     (sha256sums.txt)?</a></li>

115)     <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close

116)     all my open tabs?</a></li>

117)     <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay

118)     or bridge?</a></li>
119)     <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>

120)     <li><a href="#TBBSourceCode">Where is the source code for the bundle? How do

121)     I verify a build?</a></li>

122)     </ul>
123) 

124)     <p>Advanced Tor usage:</p>

125) 

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

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

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

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

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

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

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

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

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

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

141)     <li><a href="#WarningsAboutSOCKSandDNSInformationLeaks">I keep seeing
142)     these warnings about SOCKS and DNS information leaks. Should I

143)     worry?</a></li>

144)     <li><a href="#SocksAndDNS">How do I check if my application that uses

145)     SOCKS is leaking DNS requests?</a></li>

146)     </ul>

147) 

148)     <p>Running a Tor relay:</p>

149)     <ul>

150) 
151)     <li><a href="#HowDoIDecide">How do I decide if I should run a relay?
152)     </a></li>

153)     <li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being

154)     used more?</a></li>

155)     <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li>

156)     <li><a href="#PortscannedMore">Why do I get portscanned more often

157)     when I run a Tor relay?</a></li>

158)     <li><a href="#MoreThanOneCPU">I have more than one CPU. Does this

159)     help?</a></li>

160)     <li><a href="#HighCapacityConnection">How can I get Tor to fully

161)     make use of my high capacity connection?</a></li>

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

164)     <li><a href="#BandwidthShaping">What bandwidth shaping options are

165)     available to Tor relays?</a></li>

166)     <li><a href="#LimitTotalBandwidth">How can I limit the total amount

167)     of bandwidth used by my Tor relay?</a></li>

168)     <li><a href="#RelayWritesMoreThanItReads">Why does my relay write

169)     more bytes onto the network than it reads?</a></li>

170)     <li><a href="#Hibernation">Why can I not browse anymore after

171)     limiting bandwidth on my Tor relay?</a></li>

172)     <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal

173)     with abuse issues.</a></li>

174)     <li><a href="#BestOSForRelay">Why doesn't my Windows (or other OS) Tor

175)     relay run well?</a></li>

176)     <li><a href="#PackagedTor">Should I install Tor from my package manager, 
177)     or build from source?</a></li>

178)     <li><a href="#WhatIsTheBadExitFlag">What is the BadExit flag?</a></li>

179)     <li><a href="#IGotTheBadExitFlagWhyDidThatHappen">I got the BadExit flag.

180)     Why did that happen?</a></li>

181)     <li><a href="#MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf">My

182)     relay recently got the Guard flag and traffic dropped by half.</a></li>

183)     <li><a href="#TorClientOnADifferentComputerThanMyApplications">I want to run my Tor client on a

184)     different computer than my applications.</a></li>

185)     <li><a href="#ServerClient">Can I install Tor on a central server, and

186)     have my clients connect to it?</a></li>

187)     <li><a href="#JoinTheNetwork">So I can just configure a nickname and

188)     ORPort and join the network?</a></li>

189)     <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
190)     relay?</a></li>

191)     <li><a href="#UpgradeOrMove">I want to upgrade/move my relay. How do I

192)     keep the same key?</a></li>

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

195)     <li><a href="#NTService">How do I run my Tor relay as an NT service?
196)     </a></li>

197)     <li><a href="#VirtualServer">Can I run a Tor relay from my virtual server

198)     account?</a></li>

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

201)     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?
202)     </a></li>
203)     <li><a href="#BetterAnonymity">Do I get better anonymity if I run a relay?
204)     </a></li>

205)     <li><a href="#FacingLegalTrouble">I'm facing legal trouble. How do I

206)     prove that my server was a Tor relay at a given time?</a></li>

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

209)     </ul>

210) 

211)     <p>Tor hidden services:</p>

212) 

213)     <ul>
214)     <li><a href="#AccessHiddenServices">How do I access hidden services?</a></li>

215)     <li><a href="#ProvideAHiddenService">How do I provide a hidden service?</a></li>

216)     </ul>

217) 

218)     <p>Development:</p>

219) 

220)     <ul>

221)     <li><a href="#VersionNumbers">What do these weird version numbers

222)     mean?</a></li>
223)     <li><a href="#PrivateTorNetwork">How do I set up my own private
224)     Tor network?</a></li>

225)     <li><a href="#UseTorWithJava">How can I make my Java program use the

226)     Tor network?</a></li>
227)     <li><a href="#WhatIsLibevent">What is Libevent?</a></li>

228)     <li><a href="#MyNewFeature">What do I need to do to get a new feature

229)     into Tor?</a></li>
230)     </ul>
231) 

232)     <p>Anonymity and Security:</p>

233)     <ul>

234)     <li><a href="#WhatProtectionsDoesTorProvide">What protections does Tor

235)     provide?</a></li>

236)     <li><a href="#CanExitNodesEavesdrop">Can exit nodes eavesdrop on

237)     communications? Isn't that bad? </a></li>

238)     <li><a href="#AmITotallyAnonymous">So I'm totally anonymous if I use

239)     Tor?</a></li>

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

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

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

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

245)     <li><a href="#CellSize">Tor uses hundreds of bytes for every IRC line. I

246)     can't afford that!</a></li>

247)     <li><a href="#OutboundConnections">Why does netstat show these outbound

248)     connections?</a></li>
249)     <li><a href="#PowerfulBlockers">What about powerful blocking mechanisms
250)     </a></li>

251)     <li><a href="#RemotePhysicalDeviceFingerprinting">Does Tor resist

252)     "remote physical device fingerprinting"?</a></li>

253)     <li><a href="#IsTorLikeAVPN">Is Tor like a VPN?</a></li>

254)     <li><a href="#Proxychains">Aren't 10 proxies (proxychains) better than

255)     Tor with only 3 hops?</a></li>

256)     <li><a href="#AttacksOnOnionRouting">What attacks remain against onion

257)     routing?</a></li>

258)     <li><a href="#LearnMoreAboutAnonymity">Where can I learn more about anonymity?</a></li>

259)     </ul>

260) 

261)     <p>Alternate designs that we don't do (yet):</p>

262) 

263)     <ul>
264)     <li><a href="#EverybodyARelay">You should make every Tor user be a
265)     relay.</a></li>

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

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

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

271)     <li><a href="#ChoosePathLength">You should let people choose their path

272)     length.</a></li>

273)     <li><a href="#SplitEachConnection">You should split each connection over

274)     many paths.</a></li>

275)     <li><a href="#MigrateApplicationStreamsAcrossCircuits">You should migrate

276)     application streams across circuits.</a></li>

277)     <li><a href="#LetTheNetworkPickThePath">You should let the network pick

278)     the path, not the client.</a></li>

279)     <li><a href="#UnallocatedNetBlocks">Your default exit policy should block

280)     unallocated net blocks too.</a></li>

281)     <li><a href="#BlockWebsites">Exit policies should be able to block

282)     websites, not just IP addresses.</a></li>

283)     <li><a href="#BlockContent">You should change Tor to prevent users from

284)     posting certain content.</a></li>

285)     <li><a href="#SendPadding">You should send padding so it's more secure.
286)     </a></li>

287)     <li><a href="#Steganography">You should use steganography to hide Tor

288)     traffic.</a></li>

289)     </ul>

290) 

291)     <p>Abuse:</p>

292)     <ul>

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

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

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

299)     </ul>

300) 

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

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

304) 

305)     <hr>

306) 

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

308)     <h2><a class="anchor">General:</a></h2>

309) 

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

312) 

313)     <p>
314)     The name "Tor" can refer to several different components.
315)     </p>

316) 

317)     <p>

318)     The Tor software is a program you can run on your computer that
319) helps keep
320)     you safe on the Internet. Tor protects you by bouncing your
321) communications

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

323)     the world: it prevents somebody watching your Internet connection
324) from

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

326)     from learning your physical location. This set of volunteer relays
327) is
328)     called the Tor network. You can read more about how Tor works on the
329) <a

330)     href="<page about/overview>">overview page</a>.
331)     </p>

332) 

333)     <p>

334)     The Tor Project is a non-profit (charity) organization that
335) maintains

336)     and develops the Tor software.
337)     </p>

338) 

339)     <hr>

340) 

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

342)     <h3><a class="anchor" href="#Torisdifferent">How is Tor different
343) from other proxies?</a></h3>
344)     <p>
345)     A typical proxy provider sets up a server somewhere on the Internet
346) and
347) allows you to use it to relay your traffic.  This creates a simple, easy
348) to
349) maintain architecture.  The users all enter and leave through the same
350) server.
351) The provider may charge for use of the proxy, or fund their costs
352) through
353) advertisements on the server.  In the simplest configuration, you don't
354) have to
355) install anything.  You just have to point your browser at their proxy
356) server.
357) Simple proxy providers are fine solutions if you do not want protections
358) for
359) your privacy and anonymity online and you trust the provider from doing
360) bad
361) things.  Some simple proxy providers use SSL to secure your connection
362) to them.
363) This may protect you against local eavesdroppers, such as those at a
364) cafe with

365) free wifi Internet.
366)     </p>
367)     <p>

368)     Simple proxy providers also create a single point of failure.  The
369) provider
370) knows who you are and where you browse on the Internet.  They can see
371) your
372) traffic as it passes through their server.  In some cases, they can even
373) see

374) inside your

375) encrypted traffic as they relay it to your banking site or to ecommerce
376) stores.

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

378) watching your traffic, injecting their own advertisements into your
379) traffic

380) stream, and recording your personal details.

381)     </p>
382)     <p>

383)     Tor passes your traffic through at least 3 different servers before
384) sending
385) it on to the destination. Because there's a separate layer of encryption
386) for
387) each of the three relays, Tor does not modify, or even know, what you
388) are
389) sending into it.  It merely relays your traffic, completely encrypted
390) through
391) the Tor network and has it pop out somewhere else in the world,
392) completely
393) intact.  The Tor client is required because we assume you trust your
394) local
395) computer.  The Tor client manages the encryption and the path chosen
396) through
397) the network.  The relays located all over the world merely pass
398) encrypted

399) packets between themselves.</p>

400)     <p>
401)     <dl>

402)     <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad
403) first of
404) three servers can see encrypted Tor traffic coming from your computer.
405) It
406) still doesn't know who you are and what you are doing over Tor.  It
407) merely sees
408) "This IP address is using Tor".  Tor is not illegal anywhere in the
409) world, so
410) using Tor by itself is fine.  You are still protected from this node
411) figuring

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

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

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

418) e-commerce website, or encrypted mail connections, etc, it will only
419) know the
420) destination.  It won't be able to see the data inside the traffic
421) stream.  You

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

424)     </dl>
425)     </p>

426) 

427)     <hr>

428) 

429) 

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

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

433) 

434)     <p>

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

439)     </p>
440)     <p>
441)     There are plenty of other programs you can use with Tor,
442)     but we haven't researched the application-level anonymity

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

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

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

446)     specific applications</a>.

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

449) 

450)     <hr>

451) 

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

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

455) 

456)     <p>
457)     Because Tor is the onion routing network. When we were starting the
458)     new next-generation design and implementation of onion routing in
459)     2001-2002, we would tell people we were working on onion routing,
460)     and they would say "Neat. Which one?" Even if onion routing has
461)     become a standard household term, Tor was born out of the actual <a
462)     href="http://www.onion-router.net/">onion routing project</a> run by
463)     the Naval Research Lab.
464)     </p>

465) 

466)     <p>
467)     (It's also got a fine translation from German and Turkish.)
468)     </p>

469) 

470)     <p>

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

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

474)     spot people who haven't read any of our website (and have instead
475) learned
476)     everything they know about Tor from news articles) by the fact that
477) they

478)     spell it wrong.
479)     </p>

480) 

481)     <hr>

482) 

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

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

486) 

487)     <p>

488)     There is absolutely no backdoor in Tor. Nobody has asked us to put
489) one
490)     in, and we know some smart lawyers who say that it's unlikely that
491) anybody

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

495) 

496)     <p>
497)     We think that putting a backdoor in Tor would be tremendously

498)     irresponsible to our users, and a bad precedent for security
499) software

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

504) 

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

508)     computers, or something like that. Tor is open source, and you
509) should
510)     always check the source (or at least the diffs since the last
511) release)

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

518) 

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

521)     anonymity. We periodically find and fix anonymity-related bugs, so
522) make

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

525) 

526)     <hr>

527) 

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

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

531) 

532)     <p>
533)     Yes.
534)     </p>

535) 

536)     <p>

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

540)     ask us for specific permission.
541)     </p>

542) 

543)     <p>

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

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

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

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

549) 

550)     <p>

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

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

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

554)     href="https://www.mozilla.org/en-US/firefox/organizations/">Firefox
555)     Extended Support Release</a>, and the NoScript and HTTPS-Everywhere 

556)     extensions. You will need to follow the license for those programs as 

557)     well. Both of those Firefox extensions are distributed under 
558)     the <a href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General
559)     Public License</a>, while Firefox ESR is released under the Mozilla Public 
560)     License. The simplest way to obey their licenses is to include the source 
561)     code for these programs everywhere you include the bundles themselves. 

562)     </p>

563) 

564)     <p>

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

568)     </p>

569) 

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

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

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

577) 

578)     <hr>

579) 

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

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

583) 

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

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

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

589)     <li>Read through the <a

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

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

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

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

597)     <li>Send an email to <a

598) 
599) href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.</li>
600)     <li>If all else fails, try <a href="<page about/contact>">contacting
601) us</a> directly.</li>

602)     </ol>

603) 

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

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

607) 

608)     <hr>

609) 

610)     <a id="Forum"></a>
611)     <h3><a class="anchor" href="#Forum">Is there a Tor forum?</a></h3>
612) 

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

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

615)     </p>
616) 
617)     <hr>
618) 

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

621) 

622)     <p>
623)     There are many reasons why the Tor network is currently slow.
624)     </p>

625) 

626)     <p>

627)     Before we answer, though, you should realize that Tor is never going
628) to
629)     be blazing fast. Your traffic is bouncing through volunteers'
630) computers
631)     in various parts of the world, and some bottlenecks and network
632) latency

633)     will always be present. You shouldn't expect to see university-style
634)     bandwidth through Tor.
635)     </p>

636) 

637)     <p>

638)     But that doesn't mean that it can't be improved. The current Tor
639) network
640)     is quite small compared to the number of people trying to use it,
641) and
642)     many of these users don't understand or care that Tor can't
643) currently

644)     handle file-sharing traffic load.
645)     </p>

646) 

647)     <p>
648)     For the much more in-depth answer, see <a

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

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

652)     to go with it.
653)     </p>

654) 

655)     <p>
656)     What can you do to help?
657)     </p>

658) 

659)     <ul>

660) 

661)     <li>

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

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

668) 

669)     <li>

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

672)     especially need people to help make it easier to configure your Tor
673)     as a relay. Also, we need help with clear simple documentation to
674)     walk people through setting it up.
675)     </li>

676) 

677)     <li>

678)     There are some bottlenecks in the current Tor network. Help us
679) design
680)     experiments to track down and demonstrate where the problems are,
681) and

682)     then we can focus better on fixing them.
683)     </li>

684) 

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

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

691)     get to spend more time on it.
692)     </li>

693) 

694)     <li>

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

699)     getinvolved/volunteer>">look at our volunteer page</a>.
700)     </li>

701) 

702)     <li>

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

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

706)     competition's websites discreetly, or to connect back to the home
707) servers
708)     when on the road without revealing affiliations? If your
709) organization has
710)     an interest in keeping the Tor network working, please contact them
711) about
712)     supporting Tor. Without sponsors, Tor is going to become even
713) slower.

714)     </li>

715) 

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

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

720)     cause</a>. It adds up!
721)     </li>

722) 

723)     </ul>

724) 

725)     <hr>

726) 

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

728)     <h3><a class="anchor" href="#FileSharing">How can I share files

729)     anonymously through Tor?</a></h3>

730) 
731)     <p>

732)     File sharing (peer-to-peer/P2P) is widely unwanted in the Tor network,
733)     and exit nodes are configured to block file sharing traffic by default.
734)     Tor is not really designed for it, and file sharing through Tor slows
735)     down everyone's browsing. Also, Bittorrent over Tor <a

736)     href="https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea">
737)     is not anonymous</a>!

738)     </p>
739) 
740)     <hr>
741) 

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

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

745) 

746)     <p>

747)     The Tor network's <a

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

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

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

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

757)     </p>

758) 

759)     <p>

760)     There are six main development/maintenance pushes that need
761) attention:

762)     </p>

763) 

764)     <ul>

765) 

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

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

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

773) 

774)     <li>

775)     User support: With this many users, a lot of people are asking
776) questions
777)     all the time, offering to help out with things, and so on. We need
778) good
779)     clean docs, and we need to spend some effort coordinating
780) volunteers.

781)     </li>

782) 

783)     <li>

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

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

787)     reminders to upgrade, and so on. The network itself is a commons,
788) and
789)     somebody needs to spend some energy making sure the relay operators
790) stay
791)     happy. We also need to work on stability on some platforms —
792) e.g.,

793)     Tor relays have problems on Win XP currently.

794)     </li>

795) 

796)     <li>

797)     Usability: Beyond documentation, we also need to work on usability
798) of the
799)     software itself. This includes installers, clean GUIs, easy
800) configuration
801)     to interface with other applications, and generally automating all
802) of
803)     the difficult and confusing steps inside Tor. We've got a start on
804) this
805)     with the <a href="<page projects/vidalia>">Vidalia GUI</a>, but much
806) more work

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

809) 

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

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

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

817) 

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

823)     critical <a href="<page getinvolved/volunteer>#Research">Tor
824) research questions</a>
825)     that will help us figure out how to make Tor secure against the
826) variety of
827)     attacks out there. Of course, there are more research questions
828) waiting

829)     behind these.
830)     </li>

831) 

832)     </ul>

833) 

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

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

838)     can keep up</a>.

839)     Now would be an excellent time to add a few more developers to the
840) effort

841)     so we can continue to grow the network.
842)     </p>

843) 

844)     <p>
845)     We are also excited about tackling related problems, such as
846)     censorship-resistance.
847)     </p>

848) 

849)     <p>

850)     We are proud to have <a href="<page about/sponsors>">sponsorship and
851) support</a>
852)     from the Omidyar Network, the International Broadcasting Bureau,
853) Bell
854)     Security Solutions, the Electronic Frontier Foundation, several
855) government

856)     agencies and research groups, and hundreds of private contributors.
857)     </p>

858) 

859)     <p>

860)     However, this support is not enough to keep Tor abreast of changes
861) in the
862)     Internet privacy landscape. Please <a href="<page
863) donate/donate>">donate</a>
864)     to the project, or <a href="<page about/contact>">contact</a> our
865) executive

866)     director for information on making grants or major donations.
867)     </p>

868) 

869)     <hr>
870) 
871) 
872)     <a id="Mobile"></a>
873)     <h3><a class="anchor" href="#Mobile">Can I use Tor on my phone or mobile 
874)     device?</a></h3>
875) 
876)     <p>
877)     Tor on Android devices is maintained by the <a 
878)     href="https://guardianproject.info">Guardian Project</a>. Currently, there 
879)     is no supported way of using Tor on iOS; the Guardian Project is 
880)     working to make this a reality in the future.
881)     </p>
882) 

883)     <hr>
884) 

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

886)     <h3><a class="anchor" href="#OutboundPorts">Do I have to open all these

887)     outbound ports on my firewall?</a></h3>

888) 
889)     <p>

890)     Tor may attempt to connect to any port that is advertised in the
891)     directory as an ORPort (for making Tor connections) or a DirPort (for

892)     fetching updates to the directory). There are a variety of these ports:
893)     many of them are running on 80, 443, 9001, and 9030, but many use other
894)     ports too.

895)     </p>
896)     <p>

897)     As a client: you could probably get away with opening only those four

898)     ports. Since Tor does all its connections in the background, it will retry
899)     ones that fail, and hopefully you'll never have to know that it failed, as
900)     long as it finds a working one often enough. However, to get the most

901)     diversity in your entry nodes — and thus the most security
902)     — as well as the most robustness in your connectivity, you'll
903)     want to let it connect to all of them.
904)     See the FAQ entry on <a href="#FirewallPorts">firewalled ports</a> if
905)     you want to explicitly tell your Tor client which ports are reachable
906)     for you.
907)     </p>
908)     <p>
909)     As a relay: you must allow outgoing connections to every other relay
910)     and to anywhere your exit policy advertises that you allow. The
911)     cleanest way to do that is simply to allow all outgoing connections
912)     at your firewall. If you don't, clients will ask you to extend to
913)     those relays, and those connections will fail, leading to complex
914)     anonymity implications for the clients which we'd like to avoid.

915)     </p>

916)  

917)     <hr>

918)  

919)     <a id="IsItWorking"></a>

920)     <h3><a class="anchor" href="#IsItWorking">How can I tell if Tor is

921)     working, and that my connections really are anonymized?</a></h3>

922) 
923)     <p>

924)     There are sites you can visit that will tell you if you appear to be

925)     coming through the Tor network. Try the <a href="https://check.torproject.org">
926)     Tor Check</a> site and see whether it thinks you are using Tor or not.

927)     </p>

928)  

929)     <hr>

930)  

931)     <a id="FTP"></a>
932)     <h3><a class="anchor" href="#FTP">How do I use my browser for ftp with Tor?
933)     </a></h3>
934) 

935)     <p>

936)     Use the <a href="https://torproject.org/projects/torbrowser.html">Tor
937)     Browser Bundle</a>. If you want a separate application for an
938)     ftp client, we've heard good things about  FileZilla for Windows. You can
939)     configure it to point to Tor as a "socks4a" proxy on "localhost" port
940)     "9050".

941)     </p>

942) 

943)     <hr>

944)  

945)     <a id="NoDataScrubbing"></a>

946)     <h3><a class="anchor" href="#NoDataScrubbing">Does Tor remove personal

947)     information from the data my application sends?</a></h3>
948) 

949)     <p>No, it doesn't. You need to use a separate program that understands
950)     your application and protocol and knows how to clean or "scrub" the data
951)     it sends. The Tor Browser Bundle tries to keep application-level data,
952)     like the user-agent string, uniform for all users. The Tor Browser can't
953)     do anything about text that you type into forms, though. <a

954)     href="<page download/download-easy>#warning">Be

955)     careful and be smart.</a>
956)     </p>
957) 
958)     <hr>
959) 

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

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

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

963) 

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

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

967)     <hr>

968) 

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

970)     <h3><a class="anchor" href="#SSLcertfingerprint">What are the SSL

971)     certificate fingerprints for Tor's various websites?</a></h3>

972)     <p>

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

974)     </p>
975)     <pre>
976) Issued Certificate
977) Version: 3
978) Serial Number: 09 48 B1 A9 3B 25 1D 0D B1 05 10 59 E2 C2 68 0A
979) Not Valid Before: 2013-10-22
980) Not Valid After: 2016-05-03
981) Certificate Fingerprints
982) SHA1: 84 24 56 56 8E D7 90 43 47 AA 89 AB 77 7D A4 94 3B A1 A7 D5
983) MD5: A4 16 66 80 AE B9 A4 EC AA 88 01 1B 6F B9 EB CB

984)     </pre>

985) <br>
986)     <p>
987) blog.torproject.org SSL certificate from RapidSSL:

988)     </p>

989)     <pre>
990) Issued Certificate
991) Version: 3
992) Serial Number: 05 CA 2A A9 A5 D6 ED 44 C7 2D 88 1A 18 B0 E7 DC
993) Not Valid Before: 2014-04-09
994) Not Valid After: 2017-06-14
995) Certificate Fingerprints
996) SHA1: DE 20 3D 46 FD C3 68 EB BA 40 56 39 F5 FA FD F5 4E 3A 1F 83
997) MD5: 8A 8A A2 5E D9 7F 84 4C 8F 00 3B 43 E0 2D E6 4D
998)     </pre>

999)     <hr>
1000) 

1001)     <a id="CompilationAndInstallation"></a>
1002)     <h2><a class="anchor">Compilation And Installation:</a></h2>
1003) 

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

1005)     <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall
1006) Tor?</a></h3>
1007) 
1008)     <p>
1009)     Tor Browser does not install itself in the classic sense of
1010) applications. You just simply delete the folder or directory named "Tor
1011) Browser" and it is removed from your system.
1012)     </p>

1013) 

1014)     <p>

1015)     If this is not related to Tor Browser, uninstallation depends
1016) entirely on how you installed it and which operating system you
1017)     have. If you installed a package, then hopefully your package has a
1018) way to

1019)     uninstall itself. The Windows packages include uninstallers.

1020)     </p>

1021) 

1022)     <p>
1023)     For Mac OS X, follow the <a
1024)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
1025)     </p>

1026) 

1027)     <p>

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

1032)     be pretty easy to notice things there.
1033)     </p>

1034) 

1035)     <hr>

1036) 

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

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

1040) 

1041)     <p>

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

1044)     exactly the one that we intended you to get.
1045)     </p>

1046) 

1047)     <p>
1048)     Please read the <a

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

1051)     </p>

1052) 

1053) <hr>
1054) 
1055) <a id="GetTor"></a>
1056) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
1057) country. How do I download Tor?</a></h3>
1058) 
1059) <p>
1060) Some government or corporate firewalls censor connections to Tor's
1061) website. In those cases, you have three options. First, get it from

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

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

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

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

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

1070) in the body of the email, it will reply with instructions. Note that
1071) only a few webmail providers are supported, since they need to be able
1072) to receive very large attachments.
1073) </p>
1074) 
1075) <p>

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

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

1080) </p>
1081) 

1082)     <hr>

1083) 

1084)     <a id="VirusFalsePositives"></a>
1085)     <h3><a class="anchor" href="#VirusFalsePositives"></a></h3>
1086)     <p>

1087)     Sometimes, overzealous Windows virus and spyware detectors trigger on
1088)     some parts of the Tor Windows binary. Our best guess is that these are
1089)     false positives — after all, the anti-virus and anti-spyware business is
1090)     just a guessing game anyway. You should contact your vendor and explain
1091)     that you have a program that seems to be triggering false positives. Or

1092)     pick a better vendor.
1093)     </p>

1094)     <p>In the meantime, we encourage you to not just take our word for it.
1095)     Our job is to provide the source; if you're concerned, please do

1096)     recompile it yourself.</p>
1097) 
1098)     <hr>
1099) 

1100)     <a id="tarballs"></a>

1101)     <h3><a class="anchor" href="#tarballs">How do I open a .tar.gz

1102)     or .tar.xz file?</a></h3>

1103) 
1104)     <p>
1105)     Tar is a common archive utility for Unix and Linux systems. If your

1106)     system has a mouse, you can usually open them by double clicking.
1107)     Otherwise open a command prompt and execute</p>

1108)     <pre>tar xzf &lt;FILENAME&gt;.tar.gz</pre> or <pre>tar xJf &lt;FILENAME&gt;.tar.xz</pre>

1109)     <p>

1110)     as documented on tar's man page.

1111)     </p>
1112) 
1113)     <hr>
1114) 

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

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

1118) 

1119)     <p>

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

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

1123)     Bundle</a>.

1124)     </p>

1125) 
1126) <hr>
1127) 

1128) <a id="TBBGeneral"></a>
1129) <h2><a class="anchor">Tor Browser Bundle (general):</a></h2>
1130) 

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

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

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

1135) 
1136) <p>

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

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

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

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

1149) </p>

1150) 
1151) <p>

1152) <a href="https://www.youtube.com/html5">YouTube offers experimental HTML5 video

1153) support</a> for many of their videos. Often you can get the HTML5 version of
1154) videos that don't want to play by grabbing the YouTube URL from the "Embed"

1155) code under a video's "Share" option. The link switches out a URL that looks</p>
1156) <pre>https://www.youtube.com/watch?v=CJNxbpbHA-I</pre>
1157) <p>to something that looks like</p>
1158) <pre>https://www.youtube.com/embed/CJNxbpbHA-I</pre>

1159) 

1160) <hr>
1161) 

1162) <a id="Ubuntu"></a>
1163) <h3><a class="anchor" href="#Ubuntu">

1164) I'm using Ubuntu and I can't start Tor Browser.</a></h3>

1165) <p>

1166) You'll need to tell Ubuntu that you want the ability to execute shell scripts 
1167) from the graphical interface. Open "Files" (Unity's explorer), open 

1168) Preferences-> Behavior Tab -> Set "Run executable text files when they are 
1169) opened" to "Ask every time", then OK.

1170) </p>
1171) <p>You can also start the Tor Browser from the command line by running </p>

1172) <pre>./start-tor-browser</pre>

1173) <p>
1174) from inside the Tor Browser directory.
1175) </p>
1176) 

1177) <hr>
1178) 

1179) <a id="SophosOnMac"></a>
1180) <h3><a class="anchor" href="#SophosOnMac">I'm using the Sophos anti-virus

1181)     software on my Mac, and Tor starts but I can't browse anywhere.</a></h3>

1182) <p>

1183) You'll need to modify Sophos anti-virus so that Tor can connect to the
1184) internet. Go to Preferences -> Web Protection -> General, and turn off

1185) the protections for "Malicious websites" and "Malicious downloads".
1186) </p>

1187) <p>
1188) We encourage affected Sophos users to contact Sophos support about 
1189) this issue.
1190) </p>

1191) 

1192) <hr>
1193) 

1194) <a id="TBBOtherExtensions"></a>
1195) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
1196) Firefox extensions?</a></h3>
1197) 
1198) <p>

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

1203) bypassing proxy settings.

1204) </p>

1205) <p>

1206) Some people have suggested we include ad-blocking software or
1207) anti-tracking software with the Tor Browser Bundle. Right now, we do not
1208) think that's such a good idea. The Tor Browser Bundle aims to provide
1209) sufficient privacy that additional add-ons to stop ads and trackers are
1210) not necessary. Using add-ons like these may cause some sites to break, which

1211) <a href="https://www.torproject.org/projects/torbrowser/design/#philosophy">

1212) we don't want to do</a>. Additionally, maintaining a list of "bad" sites that
1213) should be black-listed provides another opportunity to uniquely fingerprint
1214) users.

1215) </p>

1216) 

1217) <hr>
1218) 

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

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

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

1224) 
1225) <p>
1226) We configure NoScript to allow JavaScript by default in the Tor
1227) Browser Bundle because many websites will not work with JavaScript
1228) disabled.  Most users would give up on Tor entirely if a website
1229) they want to use requires JavaScript, because they would not know
1230) how to allow a website to use JavaScript (or that enabling
1231) JavaScript might make a website work).
1232) </p>
1233) 

1234) <p>
1235) There's a tradeoff here. On the one hand, we should leave
1236) JavaScript enabled by default so websites work the way
1237) users expect. On the other hand, we should disable JavaScript
1238) by default to better protect against browser vulnerabilities (<a

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

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

1247) 
1248) <p>

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

1258) </p>
1259) 
1260) <p>

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

1263) </p>
1264) 
1265) <hr>
1266) 

1267) <a id="TBBOtherBrowser"></a>
1268) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
1269) Chrome/IE/Opera/etc with Tor.</a></h3>
1270) 
1271) <p>
1272) In short, using any browser besides Tor Browser Bundle with Tor is a
1273) really bad idea.
1274) </p>
1275) 
1276) <p>
1277) We're working with the Chrome team to <a

1278) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">fix some bugs and missing APIs in Chrome</a> so it

1279) will be possible to write a Torbutton for Chrome. No support for any
1280) other browser is on the horizon.

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

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

1288) 
1289) <p>
1290) This is a known and intermittent problem; it does not mean that Google
1291) considers Tor to be spyware.
1292) </p>
1293) 
1294) <p>

1295) When you use Tor, you are sending queries through exit relays that are

1296) also shared by thousands of other users. Tor users typically see this
1297) message when many Tor users are querying Google in a short period of time.
1298) Google interprets the high volume of traffic from a single IP address
1299) (the exit relay you happened to pick) as somebody trying to "crawl" their
1300) website, so it slows down traffic from that IP address for a short time.

1301) </p>
1302) <p>
1303) An alternate explanation is that Google tries to detect certain
1304) kinds of spyware or viruses that send distinctive queries to Google
1305) Search. It notes the IP addresses from which those queries are received
1306) (not realizing that they are Tor exit relays), and tries to warn any
1307) connections coming from those IP addresses that recent queries indicate
1308) an infection.
1309) </p>
1310) 
1311) <p>

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

1313) to deter or block Tor use. The error message about an infected machine
1314) should clear up again after a short time.
1315) </p>
1316) 
1317) <hr />
1318) 

1319) <a id="ForeignLanguages"></a>
1320) <h3><a class="anchor" href="#ForeignLanguages">
1321) Why does Google show up in foreign languages?</a></h3>
1322) 
1323) <p>

1324)  Google uses "geolocation" to determine where in the world you are, so it
1325)  can give you a personalized experience. This includes using the language
1326)  it thinks you prefer, and it also includes giving you different results

1327)  on your queries.

1328) </p>
1329) <p>

1330) If you really want to see Google in English you can click the link that
1331) provides that. But we consider this a feature with Tor, not a bug --- the
1332) Internet is not flat, and it in fact does look different depending on

1333) where you are. This feature reminds people of this fact. 

1334) </p>
1335) <p>

1336) Note that Google search URLs take name/value pairs as arguments and one
1337) of those names is "hl". If you set "hl" to "en" then Google will return
1338) search results in English regardless of what Google server you have been
1339) sent to. On a query this looks like:

1340) </p>

1341) <pre>https://encrypted.google.com/search?q=online%20anonymity&hl=en</pre>

1342) <p>

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

1345) </p>
1346) <hr />

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

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

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

1350) 
1351) <p>
1352) Sometimes, after you've used Gmail over Tor, Google presents a
1353) pop-up notification that your account may have been compromised.
1354) The notification window lists a series of IP addresses and locations
1355) throughout the world recently used to access your account.
1356) </p>
1357) 
1358) <p>
1359) In general this is a false alarm: Google saw a bunch of logins from

1360) different places, as a result of running the service via Tor, and
1361) decided

1362) it was a good idea to confirm the account was being accessed by it's
1363) rightful owner.
1364) </p>
1365) 
1366) <p>
1367) Even though this may be a biproduct of using the service via tor,
1368) that doesn't mean you can entirely ignore the warning. It is
1369) <i>probably</i> a false positive, but it might not be since it is
1370) possible for someone to hijack your Google cookie.
1371) </p>
1372) 
1373) <p>
1374) Cookie hijacking is possible by either physical access to your computer
1375) or by watching your network traffic.  In theory only physical access
1376) should compromise your system because Gmail and similar services
1377) should only send the cookie over an SSL link. In practice, alas, it's <a

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

1380) way more complex than that</a>.
1381) </p>
1382) 
1383) <p>
1384) And if somebody <i>did</i> steal your google cookie, they might end
1385) up logging in from unusual places (though of course they also might
1386) not). So the summary is that since you're using Tor, this security
1387) measure that Google uses isn't so useful for you, because it's full of
1388) false positives. You'll have to use other approaches, like seeing if
1389) anything looks weird on the account, or looking at the timestamps for
1390) recent logins and wondering if you actually logged in at those times.
1391) </p>
1392) 
1393) <hr>
1394) 

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

1396) <h3><a class="anchor" href="#NeedToUseAProxy">My internet connection

1397) requires an HTTP or SOCKS Proxy</a></h3>

1398) 
1399) <p>

1400) You can set Proxy IP address, port, and authentication information in
1401) Tor Browser's Network Settings. If you're using Tor another way, check
1402) out the HTTPProxy and HTTPSProxy config options in the <a

1403) href="<page docs/tor-manual>">man page</a>,

1404) and modify your torrc file accordingly. You will need an HTTP proxy for
1405) doing GET requests to fetch the Tor directory, and you will need an
1406) HTTPS proxy for doing CONNECT requests to get to Tor relays. (It's fine
1407) if they're the same proxy.) Tor also recognizes the torrc options
1408) Socks4Proxy and Socks5Proxy.

1409) </p>
1410) <p>

1411) Also read up on the HTTPProxyAuthenticator and HTTPSProxyAuthenticator
1412) options if your proxy requires auth. We only support basic auth currently,
1413) but if you need NTLM authentication, you may find <a
1414) href="http://archives.seul.org/or/talk/Jun-2005/msg00223.html">this post
1415) in the archives</a> useful.

1416) </p>
1417) <p>

1418) If your proxies only allow you to connect to certain ports, look at the
1419) entry on <a href="#FirewallPorts">Firewalled clients</a> for how
1420) to restrict what ports your Tor will try to access.

1421) </p>
1422) 
1423) <hr>
1424) 

1425) 
1426) <a id="TBBSocksPort"></a>
1427) <h3><a class="anchor" href="#TBBSocksPort">
1428) I want to run another application through Tor.</a></h3>
1429) 
1430) <p>
1431) If you are trying to use some external application with Tor, step zero
1432) should be to <a href="<page download/download>#warning">reread the set
1433) of warnings</a> for ways you can screw up. Step one should be to try
1434) to use a SOCKS proxy rather than an HTTP proxy.
1435) Typically Tor listens for SOCKS connections on port 9050. Tor Browser listens
1436) on port 9150.
1437) </p>
1438) 
1439) <p>
1440) If your application doesn't support SOCKS proxies, feel free to install <a
1441) href="http://www.privoxy.org/">privoxy</a>.
1442) However, please realize that this approach is not recommended for novice
1443) users. Privoxy has an <a
1444) href="http://www.privoxy.org/faq/misc.html#TOR">example
1445) configuration</a> of Tor and Privoxy.
1446) </p>
1447) 
1448) <p>
1449) If you're unable to use the application's native proxy settings, all hope is 
1450) not lost. See <a href="#CantSetProxy">below</a>.
1451) </p>
1452) 
1453) <hr>
1454) 

1455) <a id="CantSetProxy"></a>

1456) <h3><a class="anchor" href="#CantSetProxy">What should I do if I can't

1457) set a proxy with my application?</a></h3>
1458) 
1459) <p>

1460) On Unix, we recommend you give <a
1461) href="https://github.com/dgoulet/torsocks/">torsocks</a> a try.
1462) Alternative proxifying tools like <a
1463) href="http://www.dest-unreach.org/socat/">socat</a> and <a
1464) href="http://proxychains.sourceforge.net/">proxychains</a> are also

1465) available.</p>

1466) <p>
1467) The Windows way to force applications through Tor is less clear. <a
1468) href="http://freecap.ru/eng/">Some</a> <a
1469) href="http://www.freehaven.net/~aphex/torcap/">tools</a> have been <a

1470) href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed

1471) </a>, but we'd also like to see further testing done here.

1472) </p>
1473) 
1474) <hr>
1475) 

1476) <a id="TBB3.x"></a>
1477) <h2><a class="anchor">Tor Browser Bundle (3.x series):</a></h2>

1478)     <a id="WhereDidVidaliaGo"></a>

1479)     <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map

1480)     (Vidalia) go?</a></h3>
1481) 

1482)     <p>Vidalia has been replaced with Tor Launcher, which is a Firefox
1483)     extension that provides similar functionality. Unfortunately, circuit
1484)     status reporting is still missing, but we are <a
1485)     href="https://trac.torproject.org/projects/tor/ticket/8641">working

1486)     on providing it</a>. </p>
1487) 

1488)     <p>In the meantime, we are providing standalone Vidalia packages for
1489)     people who still want the map. Windows and Linux versions are <a

1490)     href="https://people.torproject.org/~erinn/vidalia-standalone-bundles/">

1491)     available here</a>.</p>

1492) 

1493)     <p>To use these packages, extract them, then run the startup script.
1494)     On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia.
1495)     They can be placed in a different directory from TBB (and likely should

1496)     be). </p>
1497) 

1498)     <p>This Vidalia package will only run properly if Tor Browser has already

1499)     been launched. You cannot start it before launching Tor Browser. </p>
1500) 

1501)     <p>MacOS is still under development, but in the mean time you can modify
1502)     your TBB 2.x to be a standalone Vidalia (and then use it after starting
1503)     TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and

1504)     replacing its contents with just these lines:</p>
1505) 
1506)     <pre>
1507)     [General]
1508)     LanguageCode=en
1509) 
1510)     [Tor]
1511)     ControlPort=9151
1512)     TorExecutable=.
1513)     Torrc=.
1514)     DataDirectory=.
1515)     AuthenticationMethod=cookie

1516)     </pre>

1517) 
1518)     <hr>
1519) 
1520)     <a id="DisableJS"></a>
1521)     <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1522)     </h3>
1523) 

1524)     <p>Alas, Mozilla decided to get rid of the config checkbox for JavaScript
1525)     from earlier Firefox versions. And since TBB 3.5 is based on Firefox 24
1526)     (FF17 is unmaintained), that means TBB 3.5 doesn't have the config

1527)     checkbox anymore either, which is unfortunate.</p>
1528) 

1529)     <p>The simplest way to disable JavaScript in TBB 3.5 is to click on the
1530)     Noscript "S" (between the green onion and the address bar), and select
1531)     "Forbid scripts globally". Note that vanilla NoScript actually whitelists
1532)     several domains even when you try to disable scripts globally, whereas

1533)     Tor Browser's NoScript configuration disables all of them. </p>
1534) 

1535)     <p>The more klunky way to disable JavaScript is to go to about:config,

1536)     find javascript.enabled, and set it to false.</p>
1537) 
1538)     <p>There is also a very simple addon available at addons.mozilla.org
1539)     called QuickJS, which provides a toolbar toggle for the javascript.enabled

1540)     about:config control. There are no configuration options for the addon,
1541)     it just switches the javascript.enabled entry between true and false and

1542)     provides a button for it. </p>
1543) 

1544)     <p>If you want to be extra safe, use both the about:config setting and

1545)     NoScript. </p>
1546) 

1547)     <p>As for whether you should disable it or leave it enabled, that's <a

1548)     href="#TBBJavaScriptEnabled">a tradeoff we leave to you</a>.</p>

1549) 
1550)     <hr>
1551) 
1552)     <a id="VerifyDownload"></a>
1553)     <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1554)     (sha256sums.txt)?</a></h3>
1555) 

1556)     <p>Instructions are on the <a 

1557)     href="<page docs/verifying-signatures>#BuildVerification">verifying 

1558)     signatures</a> page.</p>

1559) 
1560)     <hr>

1561)     

1562)     <a id="NewIdentityClosingTabs"></a>

1563)     <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New

1564)     Identity" close all my open tabs?</a></h3>
1565) 
1566)     <p>

1567)     That's actually a feature, since it's discarding your application-level
1568)     browser data too. But it sure is a surprising feature, for people who

1569)     are used to Vidalia's "new identity" behavior.
1570)     </p>
1571) 
1572)     <p>

1573)     We're working on ways to make the behavior less surprising, e.g. a popup
1574)     warning or auto restoring tabs. See ticket <a
1575)     href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and
1576)     ticket <a
1577)     href="https://trac.torproject.org/projects/tor/ticket/10400">#10400</a>
1578)     to follow progress there.

1579)     </p>
1580) 
1581)     <p>

1582)     In the mean time, you can get Vidalia's old "newnym" functionality by
1583)     attaching a Vidalia to your TBB 3.x. See the instructions <a
1584)     href="#WhereDidVidaliaGo">above</a>.

1585)     </p>
1586) 
1587)     <hr>
1588) 
1589)     <a id="ConfigureRelayOrBridge"></a>
1590)     <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1591) 
1592)     <p>

1593)     You've got three options.

1594)     </p>
1595) 
1596)     <p>

1597)     First (best option), if you're on Linux, you can install the system
1598)     Tor package (e.g. apt-get install tor) and then set it up to be a relay
1599)     (<a href="https://www.torproject.org/docs/tor-relay-debian">instructions</a>).

1600)     You can then use TBB independent of that.
1601)     </p>
1602) 
1603)     <p>

1604)     Second (simpler option), if you're on Windows, you can fetch the separate
1605)     "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page
1606)     and then use that (again you can use TBB independent of it).

1607)     </p>
1608) 
1609)     <p>

1610)     Third (complex option), you can either hook your Vidalia up to TBB (as
1611)     described in the FAQ above) or edit your torrc file (in Data/Tor/torrc)
1612)     directly to add the following lines:

1613)     </p>
1614)     <pre>
1615)     ORPort 443
1616)     Exitpolicy reject *:*
1617)     BridgeRelay 1  # only add this line if you want to be a bridge
1618)     </pre>
1619)     <p>

1620)     If you've installed <a

1621)     href="<page projects/obfsproxy-debian-instructions>#instructions">Obfsproxy</a>,

1622)     you'll need to add one more line:
1623)     </p>
1624)     <pre>
1625)     ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1626)     </pre>
1627)     <p>

1628)     This third option is pretty klunky right now; see e.g. <a
1629)     href="https://trac.torproject.org/projects/tor/ticket/10449">this bug</a>;
1630)     but we're hoping it will become an easy option in the future.

1631)     </p>
1632) 
1633)     <hr>
1634) 
1635)     <a id="Timestamps"></a>

1636)     <h3><a class="anchor" href="#Timestamps">Why are the file timestamps

1637)     from 2000?</a></h3>
1638) 

1639)     <p>One of the huge new features in TBB 3.x is the "deterministic build"
1640)     process, which allows many people to build the Tor Browser Bundle and
1641)     verify that they all make exactly the same package. See Mike's <a
1642)     href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">first
1643)     blog</a> post for the motivation, and his <a

1644)     href="https://blog.torproject.org/blog/deterministic-builds-part-two-technical-details">second

1645)     blog post</a> for the technical details of how we do it.

1646)     </p>
1647) 

1648)     <p>Part of creating identical builds is having everybody use the same
1649)     timestamp. Mike picked the beginning of 2000 for that time. The reason

1650)     you might see 7pm in 1999 is because of time zones. </p>
1651) 
1652)     <hr>
1653) 

1654)     <a id="TBBSourceCode"></a>
1655)     <h3><a class="anchor" href="#TBBSourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>

1656) 
1657)     <p>
1658)     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>.
1659)     </p>
1660) 
1661) 

1662) <hr>
1663) 

1664) <a id="AdvancedTorUsage"></a>
1665) <h2><a class="anchor">Advanced Tor usage:</a></h2>
1666) 

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

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

1670) 
1671) <p>
1672) Tor installs a text file called torrc that contains configuration
1673) instructions for how your Tor program should behave. The default

1674) configuration should work fine for most Tor users.

1675) </p>

1676) <p>

1677) If you installed Tor Browser Bundle, look for

1678) <code>Data/Tor/torrc</code> inside your Tor Browser Bundle directory.
1679) On OS X, you must right-click or command-click on the browser bundle icon,
1680) and select "Show Package Contents" before the Tor Browser directories become
1681) visible.

1682) </p>
1683) <p>

1684) 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>

1685) 
1686) <p>

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

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

1691) </p>
1692) 
1693) <p>

1694) For other configuration options you can use, see the <a href="<page

1695) docs/tor-manual>">Tor manual page</a>. Have a look at <a

1696) href="https://gitweb.torproject.org/tor.git/blob/HEAD:/src/config/torrc.sample.in">

1697) the sample torrc file</a> for hints on common configurations. Remember, all
1698) lines beginning with # in torrc are treated as comments and have no effect

1699) on Tor's configuration.

1700) </p>
1701) 
1702) <hr>
1703) 

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

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

1707) 
1708) <p>

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

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

1713) </p>
1714) 
1715) <p>
1716) If you're not using Vidalia, you'll have to go find the log files by

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

1718) </p>
1719) 
1720) <ul>
1721) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1722) </li>

1723) <li>On Windows, there are no default log files currently. If you enable
1724) logs in your torrc file, they default to <code>\username\Application
1725) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1726) </li>
1727) <li>If you compiled Tor from source, by default your Tor logs to <a
1728) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1729) at log-level notice. If you enable logs in your torrc file, they
1730) default to <code>/usr/local/var/log/tor/</code>.

1731) </li>
1732) </ul>
1733) 
1734) <p>

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

1737) and find the section (near the top of the file) which contains the
1738) following line:

1739) </p>
1740) 
1741) <pre>

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

1744) </pre>

1745) 
1746) <p>

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

1748) and err level messages to a file, append the following line to the end
1749) of the section:
1750) </p>
1751) 
1752) <pre>
1753) Log debug file c:/program files/tor/debug.log
1754) </pre>
1755) 
1756) <p>

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

1759) </p>
1760) 
1761) <hr>
1762) 

1763) 
1764) <a id="LogLevel"></a>
1765) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1766) 
1767) <p>

1768) There are five log levels (also called "log severities") you might see in

1769) Tor's logs:

1770) </p>
1771) 
1772) <ul>

1773)     <li>"err": something bad just happened, and we can't recover. Tor will

1774)     exit.</li>

1775)     <li>"warn": something bad happened, but we're still running. The bad
1776)     thing might be a bug in the code, some other Tor process doing something
1777)     unexpected, etc. The operator should examine the message and try to

1778)     correct the problem.</li>

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

1780)     <li>"info": something happened (maybe bad, maybe ok), but there's

1781)     nothing you need to (or can) do about it.</li>

1782)     <li>"debug": for everything louder than info. It is quite loud indeed.</li>

1783) </ul>
1784) 
1785) <p>

1786) Alas, some of the warn messages are hard for ordinary users to correct -- the
1787) developers are slowly making progress at making Tor automatically react

1788) correctly for each situation.

1789) </p>
1790) 
1791) <p>

1792) We recommend running at the default, which is "notice". You will hear about

1793) important things, and you won't hear about unimportant things.

1794) </p>
1795) 
1796) <p>

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

1800) </p>
1801) 

1802) <hr>
1803) 

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

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

1807) 
1808) <p>

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

1811) </p>
1812) 
1813) <p>If Tor can establish a circuit, the onion icon in

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

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

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

1821) a line saying that Tor "has successfully opened a circuit. Looks like
1822) client functionality is working."
1823) </p>
1824) 
1825) <p>
1826) If Tor can't establish a circuit, here are some hints:
1827) </p>
1828) 
1829) <ol>
1830) <li>Are you sure Tor is running? If you're using Vidalia, you may have
1831) to click on the onion and select "Start" to launch Tor.</li>
1832) <li>Check your system clock. If it's more than a few hours off, Tor will

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

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

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

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

1840) </li>

1841) <li>Are you running programs like Norton Internet Security or SELinux
1842) that

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

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

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

1850) </ol>
1851) 
1852) <hr />
1853) 

1854) <a id="TorCrash"></a>
1855) <h3><a class="anchor" href="#TorCrash">My Tor keeps crashing.</a></h3>
1856) <p>

1857)  We want to hear from you! There are supposed to be zero crash bugs in Tor.
1858)  This FAQ entry describes the best way for you to be helpful to us. But even
1859)  if you can't work out all the details, we still want to hear about it, so
1860)  we can help you track it down.

1861) </p>
1862) <p>

1863) First, make sure you're using the latest version of Tor (either the latest
1864) stable or the latest development version).

1865) </p>
1866) <p>

1867) Second, make sure your version of libevent is new enough. We recommend at
1868) least libevent 1.3a.

1869) </p>
1870) <p>

1871) Third, see if there's already an entry for your bug in the <a
1872) href="https://bugs.torproject.org/">Tor bugtracker</a>. If so,
1873) check if there are any new details that you can add.

1874) </p>
1875) <p>

1876) Fourth, is the crash repeatable? Can you cause the crash? Can
1877) you isolate some of the circumstances or config options that
1878) make it happen? How quickly or often does the bug show up?
1879) Can you check if it happens with other versions of Tor, for
1880) example the latest stable release?

1881) </p>
1882) <p>

1883) Fifth, what sort of crash do you get?

1884) </p>
1885) <ul>
1886) <li>

1887) Does your Tor log include an "assert failure"? If so, please
1888) tell us that line, since it helps us figure out what's going on.
1889) Tell us the previous couple of log messages as well, especially
1890) if they seem important.

1891) </li>
1892) <li>

1893) If it says "Segmentation fault - core dumped" then you need to
1894) do a bit more to track it down. Look for a file like "core" or
1895) "tor.core" or "core.12345" in your current directory, or in your
1896) Data Directory. If it's there, run "gdb tor core" and then "bt",
1897) and include the output. If you can't find a core, run "ulimit -c
1898) unlimited", restart Tor, and try to make it crash again. (This core
1899) thing will only work on Unix -- alas, tracking down bugs on Windows
1900) is harder. If you're on Windows, can you get somebody to duplicate

1901) your bug on Unix?)
1902) </li>
1903) <li>

1904) If Tor simply vanishes mysteriously, it probably is a segmentation
1905) fault but you're running Tor in the background (as a daemon) so you
1906) won't notice. Go look at the end of your log file, and look for a
1907) core file as above. If you don't find any good hints, you should
1908) consider running Tor in the foreground (from a shell) so you can
1909) see how it dies. Warning: if you switch to running Tor in the foreground,
1910) you might start using a different torrc file, with a different default
1911) Data Directory; see the <a href="#UpgradeOrMove">relay-upgrade FAQ entry</a>
1912) for details.

1913) </li>
1914) <li>

1915) If it's still vanishing mysteriously, perhaps something else is killing it?
1916) Do you have resource limits (ulimits) configured that kill off processes
1917) sometimes? (This is especially common on OpenBSD.) On Linux, try running
1918) "dmesg" to see if the out-of-memory killer removed your process. (Tor will
1919) exit cleanly if it notices that it's run out of memory, but in some cases
1920) it might not have time to notice.) In very rare circumstances, hardware
1921) problems could also be the culprit.

1922) </li>
1923) </ul>
1924) <p>

1925) Sixth, if the above ideas don't point out the bug, consider increasing your
1926) log level to "loglevel debug". You can look at the log-configuration FAQ
1927) entry for instructions on what to put in your torrc file. If it usually
1928) takes a long time for the crash to show up, you will want to reserve a whole
1929) lot of disk space for the debug log. Alternatively, you could just send
1930) debug-level logs to the screen (it's called "stdout" in the torrc), and then
1931) when it crashes you'll see the last couple of log lines it had printed.
1932) (Note that running with verbose logging like this will slow Tor down
1933) considerably, and note also that it's generally not a good idea security-wise
1934) to keep logs like this sitting around.)

1935) </p>
1936) 
1937) <hr />
1938) 

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

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

1942) 

1943)     <p>

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

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

1948)     </p>
1949)     <dl>
1950)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>

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

1953)         </dd>
1954)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1957)         </dd>
1958)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

1960)         </dd>
1961)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1963)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in
1964) this list.

1965)         </dd>
1966)     </dl>
1967)     <p>

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

1969)     — they are intended for testing and may disappear in future
1970) versions.

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

1974)     </p>
1975)     <p>

1976)     Note also that not every circuit is used to deliver traffic outside of
1977)     the Tor network. It is normal to see non-exit circuits (such as those
1978)     used to connect to hidden services, those that do directory fetches,
1979)     those used for relay reachability self-tests, and so on) that end at
1980)     a non-exit node. To keep a node from being used entirely, see
1981)     <tt>ExcludeNodes</tt> and <tt>StrictNodes</tt> in the

1982)     <a href="<page docs/tor-manual>">manual</a>.

1983)     </p>
1984)     <p>

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

1986) 
1987) href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2"
1988) >2

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

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

1993)     </p>
1994)     <p>

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

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

1998)     internal mapping in your configuration file using
1999) <tt>MapAddress</tt>.

2000)     See the manual page for details.
2001)     </p>

2002) 

2003)     <hr>

2004) 

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

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

2008) 
2009) <p>
2010) If your firewall works by blocking ports, then you can tell Tor to only

2011) use the ports that your firewall permits by adding "FascistFirewall 1"
2012) to

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

2014) configuration file</a>, or by clicking "My firewall only lets me connect
2015) to certain ports" in Vidalia's Network Settings window.
2016) </p>
2017) 
2018) <p>
2019) By default, when you set this Tor assumes that your firewall allows only
2020) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
2021) different set of ports with the FirewallPorts torrc option.
2022) </p>
2023) 
2024) <p>
2025) If you want to be more fine-grained with your controls, you can also
2026) use the ReachableAddresses config options, e.g.:
2027) </p>
2028) 
2029) <pre>
2030)   ReachableDirAddresses *:80
2031)   ReachableORAddresses *:443
2032) </pre>
2033) 
2034) <hr>

2035) 

2036)     <a id="DefaultExitPorts"></a>

2037)     <h3><a class="anchor" href="#DefaultExitPorts">Is there a list of default exit

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

2039)     <p>

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

2044)     </p>
2045)     <pre>
2046)   reject 0.0.0.0/8
2047)   reject 169.254.0.0/16
2048)   reject 127.0.0.0/8
2049)   reject 192.168.0.0/16
2050)   reject 10.0.0.0/8
2051)   reject 172.16.0.0/12
2052)   reject *:25
2053)   reject *:119
2054)   reject *:135-139
2055)   reject *:445
2056)   reject *:563
2057)   reject *:1214
2058)   reject *:4661-4666
2059)   reject *:6346-6429
2060)   reject *:6699
2061)   reject *:6881-6999
2062)   accept *:*
2063)     </pre>
2064)     <p>

2065)     A relay will block access to its own IP address, as well local network
2066)     IP addresses. A relay always blocks itself by default. This prevents
2067)     Tor users from accidentally accessing any of the exit operator's local
2068)     services.

2069)     </p>
2070) 
2071)     <hr>
2072) 

2073)     <a id="WarningsAboutSOCKSandDNSInformationLeaks"></a>

2074)     <h3><a class="anchor" href="#WarningsAboutSOCKSandDNSInformationLeaks">I
2075)     keep seeing these warnings about SOCKS and DNS information leaks.

2076)     Should I worry?</a></h3>
2077)     <p>

2078)     The warning is:

2079)     </p>
2080)     <p>

2081)     Your application (using socks5 on port %d) is giving Tor only an IP
2082)     address. Applications that do DNS resolves themselves may leak
2083)     information. Consider using Socks4A (e.g. via Polipo or socat) instead.

2084)     </p>
2085)     <p>

2086)     If you are running Tor to get anonymity, and you are worried about an
2087)     attacker who is even slightly clever, then yes, you should worry. Here's why.

2088)     </p>
2089)     <p>

2090)     <b>The Problem.</b> When your applications connect to servers on the
2091)     Internet, they need to resolve hostnames that you can read (like
2092)     www.torproject.org) into IP addresses that the Internet can use (like
2093)     209.237.230.66). To do this, your application sends a request to a DNS
2094)     server, telling it the hostname it wants to resolve. The DNS server
2095)     replies by telling your application the IP address.

2096)     </p>
2097)     <p>

2098)     Clearly, this is a bad idea if you plan to connect to the remote host
2099)     anonymously: when your application sends the request to the DNS server,
2100)     the DNS server (and anybody else who might be watching) can see what
2101)     hostname you are asking for. Even if your application then uses Tor to
2102)     connect to the IP anonymously, it will be pretty obvious that the user
2103)     making the anonymous connection is probably the same person who made
2104)     the DNS request.

2105)     </p>
2106)     <p>

2107)     <b>Where SOCKS comes in.</b> Your application uses the SOCKS protocol
2108)     to connect to your local Tor client. There are 3 versions of SOCKS you
2109)     are likely to run into: SOCKS 4 (which only uses IP addresses), SOCKS 5
2110)     (which usually uses IP addresses in practice), and SOCKS 4a (which uses
2111)     hostnames).

2112)     </p>
2113)     <p>

2114)     When your application uses SOCKS 4 or SOCKS 5 to give Tor an IP address,
2115)     Tor guesses that it 'probably' got the IP address non-anonymously from a
2116)     DNS server. That's why it gives you a warning message: you probably aren't
2117)     as anonymous as you think.

2118)     </p>
2119)     <p>

2120)     <b>So what can I do?</b> We describe a few solutions below.

2121)     </p>
2122)     <ul>
2123)     <li>If your application speaks SOCKS 4a, use it. </li>

2124)     <li>If you only need one or two hosts, or you are good at programming,
2125)     you may be able to get a socks-based port-forwarder like socat to work
2126)     for you; see <a
2127)     href="https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO">the

2128)     Torify HOWTO</a> for examples. </li>

2129)     <li>Tor ships with a program called tor-resolve that can use the Tor
2130)     network to look up hostnames remotely; if you resolve hostnames to IPs
2131)     with tor-resolve, then pass the IPs to your applications, you'll be fine.

2132)     (Tor will still give the warning, but now you know what it means.) </li>
2133) <!-- I'm not sure if this project is still maintained or not
2134) 
2135) <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>
2136) !-->
2137)     </ul>

2138)     <p>If you think that you applied one of the solutions properly but still
2139)     experience DNS leaks please verify there is no third-party application
2140)     using DNS independently of Tor. Please see <a
2141)     href="#AmITotallyAnonymous">the FAQ entry on whether you're really
2142)     absolutely anonymous using Tor</a> for some examples.

2143)     </p>
2144) 
2145)     <hr>
2146) 

2147)     <a id="SocksAndDNS"></a>

2148)     <h3><a class="anchor" href="#SocksAndDNS">How do I check if my application that uses

2149)     SOCKS is leaking DNS requests?</a></h3>
2150) 
2151)     <p>

2152)     These are two steps you need to take here. The first is to make sure
2153)     that it's using the correct variant of the SOCKS protocol, and the
2154)     second is to make sure that there aren't other leaks.

2155)     </p>
2156) 
2157)     <p>

2158)     Step one: add "TestSocks 1" to your torrc file, and then watch your
2159)     logs as you use your application. Tor will then log, for each SOCKS
2160)     connection, whether it was using a 'good' variant or a 'bad' one.
2161)     (If you want to automatically disable all 'bad' variants, set
2162)     "SafeSocks 1" in your <a href="#torrc">torrc</a> file.)

2163)     </p>
2164) 
2165)     <p>

2166)     Step two: even if your application is using the correct variant of
2167)     the SOCKS protocol, there is still a risk that it could be leaking
2168)     DNS queries. This problem happens in Firefox extensions that resolve
2169)     the destination hostname themselves, for example to show you its IP
2170)     address, what country it's in, etc. These applications may use a safe
2171)     SOCKS variant when actually making connections, but they still do DNS
2172)     resolves locally. If you suspect your application might behave like
2173)     this, you should use a network sniffer like <a
2174)     href="https://www.wireshark.org/">Wireshark</a> and look for
2175)     suspicious outbound DNS requests. I'm afraid the details of how to look
2176)     for these problems are beyond the scope of a FAQ entry though -- find
2177)     a friend to help if you have problems.