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="#WhatIsTheBadExitFlag">What is the BadExit flag?</a></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

207)     </ul>

208) 

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

210) 

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

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

214)     </ul>

215) 

216)     <p>Development:</p>

217) 

218)     <ul>

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

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

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

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

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

227)     into Tor?</a></li>
228)     </ul>
229) 

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

231)     <ul>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

257)     </ul>

258) 

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

260) 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

287)     </ul>

288) 

289)     <p>Abuse:</p>

290)     <ul>

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

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

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

297)     </ul>

298) 

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

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

302) 

303)     <hr>

304) 

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

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

307) 

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

310) 

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

314) 

315)     <p>

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

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

321)     the world: it prevents somebody watching your Internet connection
322) from

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

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

328)     href="<page about/overview>">overview page</a>.
329)     </p>

330) 

331)     <p>

332)     The Tor Project is a non-profit (charity) organization that
333) maintains

334)     and develops the Tor software.
335)     </p>

336) 

337)     <hr>

338) 

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

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

363) free wifi Internet.
364)     </p>
365)     <p>

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

372) inside your

373) encrypted traffic as they relay it to your banking site or to ecommerce
374) stores.

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

376) watching your traffic, injecting their own advertisements into your
377) traffic

378) stream, and recording your personal details.

379)     </p>
380)     <p>

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

397) packets between themselves.</p>

398)     <p>
399)     <dl>

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

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

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

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

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

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

422)     </dl>
423)     </p>

424) 

425)     <hr>

426) 

427) 

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

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

431) 

432)     <p>

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

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

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

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

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

444)     specific applications</a>.

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

447) 

448)     <hr>

449) 

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

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

453) 

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

463) 

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

467) 

468)     <p>

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

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

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

476)     spell it wrong.
477)     </p>

478) 

479)     <hr>

480) 

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

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

484) 

485)     <p>

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

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

493) 

494)     <p>
495)     We think that putting a backdoor in Tor would be tremendously

496)     irresponsible to our users, and a bad precedent for security
497) software

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

502) 

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

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

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

516) 

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

519)     anonymity. We periodically find and fix anonymity-related bugs, so
520) make

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

523) 

524)     <hr>

525) 

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

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

529) 

530)     <p>
531)     Yes.
532)     </p>

533) 

534)     <p>

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

538)     ask us for specific permission.
539)     </p>

540) 

541)     <p>

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

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

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

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

547) 

548)     <p>

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

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

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

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

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

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

560)     </p>

561) 

562)     <p>

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

566)     </p>

567) 

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

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

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

575) 

576)     <hr>

577) 

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

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

581) 

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

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

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

587)     <li>Read through the <a

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

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

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

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

595)     <li>Send an email to <a

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

600)     </ol>

601) 

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

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

605) 

606)     <hr>

607) 

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

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

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

613)     </p>
614) 
615)     <hr>
616) 

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

619) 

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

623) 

624)     <p>

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

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

634) 

635)     <p>

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

642)     handle file-sharing traffic load.
643)     </p>

644) 

645)     <p>
646)     For the much more in-depth answer, see <a

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

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

650)     to go with it.
651)     </p>

652) 

653)     <p>
654)     What can you do to help?
655)     </p>

656) 

657)     <ul>

658) 

659)     <li>

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

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

666) 

667)     <li>

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

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

674) 

675)     <li>

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

680)     then we can focus better on fixing them.
681)     </li>

682) 

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

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

689)     get to spend more time on it.
690)     </li>

691) 

692)     <li>

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

697)     getinvolved/volunteer>">look at our volunteer page</a>.
698)     </li>

699) 

700)     <li>

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

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

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

712)     </li>

713) 

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

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

718)     cause</a>. It adds up!
719)     </li>

720) 

721)     </ul>

722) 

723)     <hr>

724) 

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

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

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

728) 
729)     <p>

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

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

736)     </p>
737) 
738)     <hr>
739) 

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

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

743) 

744)     <p>

745)     The Tor network's <a

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

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

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

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

755)     </p>

756) 

757)     <p>

758)     There are six main development/maintenance pushes that need
759) attention:

760)     </p>

761) 

762)     <ul>

763) 

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

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

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

771) 

772)     <li>

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

779)     </li>

780) 

781)     <li>

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

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

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

791)     Tor relays have problems on Win XP currently.

792)     </li>

793) 

794)     <li>

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

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

807) 

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

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

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

815) 

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

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

827)     behind these.
828)     </li>

829) 

830)     </ul>

831) 

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

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

836)     can keep up</a>.

837)     Now would be an excellent time to add a few more developers to the
838) effort

839)     so we can continue to grow the network.
840)     </p>

841) 

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

846) 

847)     <p>

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

854)     agencies and research groups, and hundreds of private contributors.
855)     </p>

856) 

857)     <p>

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

864)     director for information on making grants or major donations.
865)     </p>

866) 

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

881)     <hr>
882) 

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

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

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

886) 
887)     <p>

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

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

893)     </p>
894)     <p>

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

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

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

913)     </p>

914)  

915)     <hr>

916)  

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

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

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

920) 
921)     <p>

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

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

925)     </p>

926)  

927)     <hr>

928)  

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

933)     <p>

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

939)     </p>

940) 

941)     <hr>

942)  

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

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

945)     information from the data my application sends?</a></h3>
946) 

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

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

953)     careful and be smart.</a>
954)     </p>
955) 
956)     <hr>
957) 

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

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

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

961) 

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

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

965)     <hr>

966) 

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

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

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

970)     <p>

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

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

982)     </pre>

983) <br>
984)     <p>
985) blog.torproject.org SSL certificate from RapidSSL:

986)     </p>

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

997)     <hr>
998) 

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

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

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

1011) 

1012)     <p>

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

1017)     uninstall itself. The Windows packages include uninstallers.

1018)     </p>

1019) 

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

1024) 

1025)     <p>

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

1030)     be pretty easy to notice things there.
1031)     </p>

1032) 

1033)     <hr>

1034) 

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

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

1038) 

1039)     <p>

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

1042)     exactly the one that we intended you to get.
1043)     </p>

1044) 

1045)     <p>
1046)     Please read the <a

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

1049)     </p>

1050) 

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

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

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

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

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

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

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

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

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

1078) </p>
1079) 

1080)     <hr>

1081) 

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

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

1090)     pick a better vendor.
1091)     </p>

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

1094)     recompile it yourself.</p>
1095) 
1096)     <hr>
1097) 

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

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

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

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

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

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

1107)     <p>

1108)     as documented on tar's man page.

1109)     </p>
1110) 
1111)     <hr>
1112) 

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

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

1116) 

1117)     <p>

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

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

1121)     Bundle</a>.

1122)     </p>

1123) 
1124) <hr>
1125) 

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

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

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

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

1133) 
1134) <p>

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

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

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

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

1147) </p>

1148) 
1149) <p>

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

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

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

1157) 

1158) <hr>
1159) 

1160) <a id="Ubuntu"></a>
1161) <h3><a class="anchor" href="#Ubuntu">

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

1163) <p>

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

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

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

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

1171) <p>
1172) from inside the Tor Browser directory.
1173) </p>
1174) 

1175) <hr>
1176) 

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

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

1180) <p>

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

1183) the protections for "Malicious websites" and "Malicious downloads".
1184) </p>

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

1189) 

1190) <hr>
1191) 

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

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

1201) bypassing proxy settings.

1202) </p>

1203) <p>

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

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

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

1213) </p>

1214) 

1215) <hr>
1216) 

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

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

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

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

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

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

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

1245) 
1246) <p>

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

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

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

1261) </p>
1262) 
1263) <hr>
1264) 

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

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

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

1279) </p>
1280) 
1281) <hr>
1282) 

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

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

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

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

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

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

1311) to deter or block Tor use. The error message about an infected machine
1312) should clear up again after a short time.
1313) </p>
1314) 
1315) <p>
1316) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1317) automatically redirect you to a more Tor-friendly search engine such as

1318) DuckDuckGo, ixquick, or Bing.

1319) </p>
1320) 
1321) <hr />
1322) 

1323) <a id="ForeignLanguages"></a>
1324) <h3><a class="anchor" href="#ForeignLanguages">
1325) Why does Google show up in foreign languages?</a></h3>
1326) 
1327) <p>

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

1331)  on your queries.

1332) </p>
1333) <p>

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

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

1338) </p>
1339) <p>

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

1344) </p>

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

1346) <p>

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

1349) </p>
1350) <hr />

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

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

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

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

1364) different places, as a result of running the service via Tor, and
1365) decided

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

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

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

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

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

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

1402) 
1403) <p>

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

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

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

1413) </p>
1414) <p>

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

1420) </p>
1421) <p>

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

1425) </p>
1426) 
1427) <hr>
1428) 

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

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

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

1461) set a proxy with my application?</a></h3>
1462) 
1463) <p>

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

1469) available.</p>

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

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

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

1476) </p>
1477) 
1478) <hr>
1479) 

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

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

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

1484)     (Vidalia) go?</a></h3>
1485) 

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

1490)     on providing it</a>. </p>
1491) 

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

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

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

1496) 

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

1500)     be). </p>
1501) 

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

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

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

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

1520)     </pre>

1521) 
1522)     <hr>
1523) 
1524)     <a id="DisableJS"></a>
1525)     <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1526)     </h3>
1527) 

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

1531)     checkbox anymore either, which is unfortunate.</p>
1532) 

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

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

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

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

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

1546)     provides a button for it. </p>
1547) 

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

1549)     NoScript. </p>
1550) 

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

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

1553) 
1554)     <hr>
1555) 
1556)     <a id="VerifyDownload"></a>
1557)     <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1558)     (sha256sums.txt)?</a></h3>
1559) 

1560)     <p>Instructions are on the <a 

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

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

1563) 
1564)     <hr>

1565)     

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

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

1568)     Identity" close all my open tabs?</a></h3>
1569) 
1570)     <p>

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

1573)     are used to Vidalia's "new identity" behavior.
1574)     </p>
1575) 
1576)     <p>

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

1583)     </p>
1584) 
1585)     <p>

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

1589)     </p>
1590) 
1591)     <hr>
1592) 
1593)     <a id="ConfigureRelayOrBridge"></a>
1594)     <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1595) 
1596)     <p>

1597)     You've got three options.

1598)     </p>
1599) 
1600)     <p>

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

1604)     You can then use TBB independent of that.
1605)     </p>
1606) 
1607)     <p>

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

1611)     </p>
1612) 
1613)     <p>

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

1617)     </p>
1618)     <pre>
1619)     ORPort 443
1620)     Exitpolicy reject *:*
1621)     BridgeRelay 1  # only add this line if you want to be a bridge
1622)     </pre>
1623)     <p>

1624)     If you've installed <a

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

1626)     you'll need to add one more line:
1627)     </p>
1628)     <pre>
1629)     ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1630)     </pre>
1631)     <p>

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

1635)     </p>
1636) 
1637)     <hr>
1638) 
1639)     <a id="Timestamps"></a>

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

1641)     from 2000?</a></h3>
1642) 

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

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

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

1650)     </p>
1651) 

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

1654)     you might see 7pm in 1999 is because of time zones. </p>
1655) 
1656)     <hr>
1657) 

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

1660) 
1661)     <p>
1662)     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>.
1663)     </p>
1664) 
1665) 

1666) <hr>
1667) 

1668) <a id="AdvancedTorUsage"></a>
1669) <h2><a class="anchor">Advanced Tor usage:</a></h2>
1670) 

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

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

1674) 
1675) <p>
1676) Tor installs a text file called torrc that contains configuration
1677) instructions for how your Tor program should behave. The default

1678) configuration should work fine for most Tor users.

1679) </p>

1680) <p>

1681) If you installed Tor Browser Bundle, look for

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

1686) </p>
1687) <p>

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

1689) 
1690) <p>

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

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

1695) </p>
1696) 
1697) <p>

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

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

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

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

1703) on Tor's configuration.

1704) </p>
1705) 
1706) <hr>
1707) 

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

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

1711) 
1712) <p>

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

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

1717) </p>
1718) 
1719) <p>
1720) If you're not using Vidalia, you'll have to go find the log files by

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

1722) </p>
1723) 
1724) <ul>
1725) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1726) </li>

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

1735) </li>
1736) </ul>
1737) 
1738) <p>

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

1741) and find the section (near the top of the file) which contains the
1742) following line:

1743) </p>
1744) 
1745) <pre>

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

1748) </pre>

1749) 
1750) <p>

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

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

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

1763) </p>
1764) 
1765) <hr>
1766) 

1767) 
1768) <a id="LogLevel"></a>
1769) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1770) 
1771) <p>

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

1773) Tor's logs:

1774) </p>
1775) 
1776) <ul>

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

1778)     exit.</li>

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

1782)     correct the problem.</li>

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

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

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

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

1787) </ul>
1788) 
1789) <p>

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

1792) correctly for each situation.

1793) </p>
1794) 
1795) <p>

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

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

1798) </p>
1799) 
1800) <p>

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

1804) </p>
1805) 

1806) <hr>
1807) 

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

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

1811) 
1812) <p>

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

1815) </p>
1816) 
1817) <p>If Tor can establish a circuit, the onion icon in

1818) Vidalia will turn green (and if you're running Tor Browser Bundle, it
1819) will
1820) automatically launch a browser for you). You can also check in the
1821) Vidalia

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

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

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

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

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

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

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

1844) </li>

1845) <li>Are you running programs like Norton Internet Security or SELinux
1846) that

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

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

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

1854) </ol>
1855) 
1856) <hr />
1857) 

1858) <a id="TorCrash"></a>
1859) <h3><a class="anchor" href="#TorCrash">My Tor keeps crashing.</a></h3>
1860) <p>

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

1865) </p>
1866) <p>

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

1869) </p>
1870) <p>

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

1873) </p>
1874) <p>

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

1878) </p>
1879) <p>

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

1885) </p>
1886) <p>

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

1888) </p>
1889) <ul>
1890) <li>

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

1895) </li>
1896) <li>

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

1905) your bug on Unix?)
1906) </li>
1907) <li>

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

1917) </li>
1918) <li>

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

1926) </li>
1927) </ul>
1928) <p>

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

1939) </p>
1940) 
1941) <hr />
1942) 

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

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

1946) 

1947)     <p>

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

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

1952)     </p>
1953)     <dl>
1954)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>

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

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

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

1961)         </dd>
1962)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

1964)         </dd>
1965)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

1967)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in
1968) this list.

1969)         </dd>
1970)     </dl>
1971)     <p>

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

1973)     — they are intended for testing and may disappear in future
1974) versions.

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

1978)     </p>
1979)     <p>

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

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

1987)     </p>
1988)     <p>

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

1990) 
1991) href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2"
1992) >2

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

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

1997)     </p>
1998)     <p>

1999)     If you want to access a service directly through Tor's Socks
2000) interface

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

2002)     internal mapping in your configuration file using
2003) <tt>MapAddress</tt>.

2004)     See the manual page for details.
2005)     </p>

2006) 

2007)     <hr>

2008) 

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

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

2012) 
2013) <p>
2014) If your firewall works by blocking ports, then you can tell Tor to only

2015) use the ports that your firewall permits by adding "FascistFirewall 1"
2016) to

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

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

2039) 

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

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

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

2043)     <p>

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

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

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

2073)     </p>
2074) 
2075)     <hr>
2076) 

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

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

2080)     Should I worry?</a></h3>
2081)     <p>

2082)     The warning is:

2083)     </p>
2084)     <p>

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

2088)     </p>
2089)     <p>

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

2092)     </p>
2093)     <p>

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

2100)     </p>
2101)     <p>

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

2109)     </p>
2110)     <p>

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

2116)     </p>
2117)     <p>

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

2122)     </p>
2123)     <p>

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

2125)     </p>
2126)     <ul>
2127)     <li>If your application speaks SOCKS 4a, use it. </li>

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

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

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

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

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

2147)     </p>
2148) 
2149)     <hr>
2150) 

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

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

2153)     SOCKS is leaking DNS requests?</a></h3>
2154) 
2155)     <p>

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

2159)     </p>
2160) 
2161)     <p>

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

2167)     </p>
2168) 
2169)     <p>