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="#OutboundPorts">Do I have to open all these outbound ports

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

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

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

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

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

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

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

59)     </ul>

60) 

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

62) 

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

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

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

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

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

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

74)     </ul>

75) 

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

77)     <ul>

78) 

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

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

82)     </a></li>

83)     <li><a href="#SophosOnMac">I'm using the Sophos anti-virus
84)     software on my Mac, and Tor Browser won't start.</a></li>

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

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

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

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

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

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

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

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

97)     <li><a href="#TorbuttonOtherBrowser">Will Torbutton be available

98)     for other browsers?</a></li>

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

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

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

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

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

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

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

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

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

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

111)     </ul>
112) 

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

114) 
115)     <ul>

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

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

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

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

121)     <li><a href="#PluggableTransports">How do I use pluggable transports?</a></li>

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

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

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

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

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

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

129)     </ul>
130) 

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

132) 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

155)     </ul>

156) 

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

158)     <ul>

159) 
160)     <li><a href="#HowDoIDecide">How do I decide if I should run a relay?
161)     </a></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

208)     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?
209)     </a></li>
210)     <li><a href="#BetterAnonymity">Do I get better anonymity if I run a relay?
211)     </a></li>

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

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

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

216)     </ul>

217) 

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

219) 

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

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

223)     </ul>

224) 

225)     <p>Development:</p>

226) 

227)     <ul>

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

229)     mean?</a></li>
230)     <li><a href="#PrivateTorNetwork">How do I set up my own private
231)     Tor network?</a></li>

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

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

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

236)     into Tor?</a></li>
237)     </ul>
238) 

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

240)     <ul>

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

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

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

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

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

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

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

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

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

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

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

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

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

255)     connections?</a></li>
256)     <li><a href="#PowerfulBlockers">What about powerful blocking mechanisms
257)     </a></li>

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

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

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

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

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

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

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

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

266)     </ul>

267) 

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

269) 

270)     <ul>
271)     <li><a href="#EverybodyARelay">You should make every Tor user be a
272)     relay.</a></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

296)     </ul>

297) 

298)     <p>Abuse:</p>

299)     <ul>

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

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

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

306)     </ul>

307) 

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

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

311) 

312)     <hr>

313) 

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

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

316) 

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

319) 

320)     <p>
321)     The name "Tor" can refer to several different components.
322)     </p>

323) 

324)     <p>

325)     The Tor software is a program you can run on your computer that
326) helps keep
327)     you safe on the Internet. Tor protects you by bouncing your
328) communications

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

330)     the world: it prevents somebody watching your Internet connection
331) from

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

333)     from learning your physical location. This set of volunteer relays
334) is
335)     called the Tor network. You can read more about how Tor works on the
336) <a

337)     href="<page about/overview>">overview page</a>.
338)     </p>

339) 

340)     <p>

341)     The Tor Project is a non-profit (charity) organization that
342) maintains

343)     and develops the Tor software.
344)     </p>

345) 

346)     <hr>

347) 

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

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

372) free wifi Internet.
373)     </p>
374)     <p>

375)     Simple proxy providers also create a single point of failure.  The
376) provider
377) knows who you are and where you browse on the Internet.  They can see
378) your
379) traffic as it passes through their server.  In some cases, they can even
380) see

381) inside your

382) encrypted traffic as they relay it to your banking site or to ecommerce
383) stores.

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

385) watching your traffic, injecting their own advertisements into your
386) traffic

387) stream, and recording your personal details.

388)     </p>
389)     <p>

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

406) packets between themselves.</p>

407)     <p>
408)     <dl>

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

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

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

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

425) e-commerce website, or encrypted mail connections, etc, it will only
426) know the
427) destination.  It won't be able to see the data inside the traffic
428) stream.  You

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

431)     </dl>
432)     </p>

433) 

434)     <hr>

435) 

436) 

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

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

440) 

441)     <p>

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

446)     </p>
447)     <p>
448)     There are plenty of other programs you can use with Tor,
449)     but we haven't researched the application-level anonymity

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

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

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

453)     specific applications</a>.

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

456) 

457)     <hr>

458) 

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

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

462) 

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

472) 

473)     <p>
474)     (It's also got a fine translation from German and Turkish.)
475)     </p>

476) 

477)     <p>

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

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

481)     spot people who haven't read any of our website (and have instead
482) learned
483)     everything they know about Tor from news articles) by the fact that
484) they

485)     spell it wrong.
486)     </p>

487) 

488)     <hr>

489) 

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

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

493) 

494)     <p>

495)     There is absolutely no backdoor in Tor. Nobody has asked us to put
496) one
497)     in, and we know some smart lawyers who say that it's unlikely that
498) anybody

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

502) 

503)     <p>
504)     We think that putting a backdoor in Tor would be tremendously

505)     irresponsible to our users, and a bad precedent for security
506) software

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

511) 

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

515)     computers, or something like that. Tor is open source, and you
516) should
517)     always check the source (or at least the diffs since the last
518) release)

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

525) 

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

528)     anonymity. We periodically find and fix anonymity-related bugs, so
529) make

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

532) 

533)     <hr>

534) 

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

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

538) 

539)     <p>
540)     Yes.
541)     </p>

542) 

543)     <p>

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

550)     ask us for specific permission.
551)     </p>

552) 

553)     <p>

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

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

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

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

561) 

562)     <p>

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

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

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

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

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

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

578)     </p>

579) 

580)     <p>

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

587)     </p>

588) 

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

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

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

598) 

599)     <hr>

600) 

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

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

604) 

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

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

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

610)     <li>Read through the <a

611) 
612) href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">
613) tor-talk

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

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

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

618)     <li>Send an email to <a

619) 
620) href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.</li>
621)     <li>If all else fails, try <a href="<page about/contact>">contacting
622) us</a> directly.</li>

623)     </ol>

624) 

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

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

628) 

629)     <hr>

630) 

631)     <a id="Forum"></a>
632)     <h3><a class="anchor" href="#Forum">Is there a Tor forum?</a></h3>
633) 

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

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

636)     </p>
637) 
638)     <hr>
639) 

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

642) 

643)     <p>
644)     There are many reasons why the Tor network is currently slow.
645)     </p>

646) 

647)     <p>

648)     Before we answer, though, you should realize that Tor is never going
649) to
650)     be blazing fast. Your traffic is bouncing through volunteers'
651) computers
652)     in various parts of the world, and some bottlenecks and network
653) latency

654)     will always be present. You shouldn't expect to see university-style
655)     bandwidth through Tor.
656)     </p>

657) 

658)     <p>

659)     But that doesn't mean that it can't be improved. The current Tor
660) network
661)     is quite small compared to the number of people trying to use it,
662) and
663)     many of these users don't understand or care that Tor can't
664) currently

665)     handle file-sharing traffic load.
666)     </p>

667) 

668)     <p>
669)     For the much more in-depth answer, see <a

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

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

673)     to go with it.
674)     </p>

675) 

676)     <p>
677)     What can you do to help?
678)     </p>

679) 

680)     <ul>

681) 

682)     <li>

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

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

689) 

690)     <li>

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

693)     especially need people to help make it easier to configure your Tor
694)     as a relay. Also, we need help with clear simple documentation to
695)     walk people through setting it up.
696)     </li>

697) 

698)     <li>

699)     There are some bottlenecks in the current Tor network. Help us
700) design
701)     experiments to track down and demonstrate where the problems are,
702) and

703)     then we can focus better on fixing them.
704)     </li>

705) 

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

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

712)     get to spend more time on it.
713)     </li>

714) 

715)     <li>

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

720)     getinvolved/volunteer>">look at our volunteer page</a>.
721)     </li>

722) 

723)     <li>

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

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

727)     competition's websites discreetly, or to connect back to the home
728) servers
729)     when on the road without revealing affiliations? If your
730) organization has
731)     an interest in keeping the Tor network working, please contact them
732) about
733)     supporting Tor. Without sponsors, Tor is going to become even
734) slower.

735)     </li>

736) 

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

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

741)     cause</a>. It adds up!
742)     </li>

743) 

744)     </ul>

745) 

746)     <hr>

747) 

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

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

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

751) 
752)     <p>

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

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

759)     </p>
760) 
761)     <hr>
762) 

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

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

766) 

767)     <p>

768)     The Tor network's <a

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

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

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

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

778)     </p>

779) 

780)     <p>

781)     There are six main development/maintenance pushes that need
782) attention:

783)     </p>

784) 

785)     <ul>

786) 

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

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

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

794) 

795)     <li>

796)     User support: With this many users, a lot of people are asking
797) questions
798)     all the time, offering to help out with things, and so on. We need
799) good
800)     clean docs, and we need to spend some effort coordinating
801) volunteers.

802)     </li>

803) 

804)     <li>

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

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

808)     reminders to upgrade, and so on. The network itself is a commons,
809) and
810)     somebody needs to spend some energy making sure the relay operators
811) stay
812)     happy. We also need to work on stability on some platforms —
813) e.g.,

814)     Tor relays have problems on Win XP currently.

815)     </li>

816) 

817)     <li>

818)     Usability: Beyond documentation, we also need to work on usability
819) of the
820)     software itself. This includes installers, clean GUIs, easy
821) configuration
822)     to interface with other applications, and generally automating all
823) of
824)     the difficult and confusing steps inside Tor. We've got a start on
825) this
826)     with the <a href="<page projects/vidalia>">Vidalia GUI</a>, but much
827) more work

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

830) 

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

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

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

838) 

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

844)     critical <a href="<page getinvolved/volunteer>#Research">Tor
845) research questions</a>
846)     that will help us figure out how to make Tor secure against the
847) variety of
848)     attacks out there. Of course, there are more research questions
849) waiting

850)     behind these.
851)     </li>

852) 

853)     </ul>

854) 

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

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

859)     can keep up</a>.

860)     Now would be an excellent time to add a few more developers to the
861) effort

862)     so we can continue to grow the network.
863)     </p>

864) 

865)     <p>
866)     We are also excited about tackling related problems, such as
867)     censorship-resistance.
868)     </p>

869) 

870)     <p>

871)     We are proud to have <a href="<page about/sponsors>">sponsorship and
872) support</a>
873)     from the Omidyar Network, the International Broadcasting Bureau,
874) Bell
875)     Security Solutions, the Electronic Frontier Foundation, several
876) government

877)     agencies and research groups, and hundreds of private contributors.
878)     </p>

879) 

880)     <p>

881)     However, this support is not enough to keep Tor abreast of changes
882) in the
883)     Internet privacy landscape. Please <a href="<page
884) donate/donate>">donate</a>
885)     to the project, or <a href="<page about/contact>">contact</a> our
886) executive

887)     director for information on making grants or major donations.
888)     </p>

889) 

890)     <hr>
891) 

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

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

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

895) 
896)     <p>

897)     Tor may attempt to connect to any port that is advertised in the
898)     directory as an ORPort (for making Tor connections) or a DirPort (for
899)     fetching updates to the directory). There are a variety of these ports,

900)     but many of them are running on 80, 443, 9001, and 9030.

901)     </p>
902)     <p>

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

909)     to all of them.

910)     </p>
911)     <p>

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

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

914)     </p>
915)     <p>

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

921)     </p>

922)  

923)     <hr>

924)  

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

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

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

928) 
929)     <p>

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

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

933)     </p>
934)     <p>

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

940)     correctly.

941)     </p>
942)     <p>

943)     To learn your IP address on OS X, Linux, BSD, etc, run "ifconfig". On
944)     Windows, go to the Start menu, click Run and enter "cmd". At the command

945)     prompt, enter "ipconfig /a".

946)     </p>
947)     <p>

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

954)     </p>

955)  

956)     <hr>

957)  

958)     <a id="FTP"></a>
959)     <h3><a class="anchor" href="#FTP">How do I use my browser for ftp with Tor?
960)     </a></h3>
961) 

962)     <p>

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

968)     </p>

969) 

970)     <hr>

971)  

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

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

974)     information from the data my application sends?</a></h3>
975) 

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

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

982)     careful and be smart.</a>
983)     </p>
984) 
985)     <hr>
986) 

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

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

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

990) 

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

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

994)     <hr>

995) 

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

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

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

999)     <p>

1000)     <pre>

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

1002)     The serial number is:

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

1005)     The SHA-256 fingerprint is:

1006) 3613d2b22a750094760c41ad19db52a4f05bdea80172e2578761ad967f7ed9aa

1007) 

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

1009)     The serial number is: 00:EF:A3
1010)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

1011)     </pre>

1012)     </p>
1013)     <hr>
1014) 

1015)     <a id="CompilationAndInstallation"></a>
1016)     <h2><a class="anchor">Compilation And Installation:</a></h2>
1017) 

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

1019)     <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall
1020) Tor?</a></h3>
1021) 
1022)     <p>
1023)     Tor Browser does not install itself in the classic sense of
1024) applications. You just simply delete the folder or directory named "Tor
1025) Browser" and it is removed from your system.
1026)     </p>

1027) 

1028)     <p>

1029)     If this is not related to Tor Browser, uninstallation depends
1030) entirely on how you installed it and which operating system you
1031)     have. If you installed a package, then hopefully your package has a
1032) way to

1033)     uninstall itself. The Windows packages include uninstallers.

1034)     </p>

1035) 

1036)     <p>
1037)     For Mac OS X, follow the <a
1038)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
1039)     </p>

1040) 

1041)     <p>

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

1046)     be pretty easy to notice things there.
1047)     </p>

1048) 

1049)     <hr>

1050) 

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

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

1054) 

1055)     <p>

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

1058)     exactly the one that we intended you to get.
1059)     </p>

1060) 

1061)     <p>
1062)     Please read the <a

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

1065)     </p>

1066) 

1067) <hr>
1068) 
1069) <a id="GetTor"></a>
1070) <h3><a class="anchor" href="#GetTor">Your website is blocked in my
1071) country. How do I download Tor?</a></h3>
1072) 
1073) <p>
1074) Some government or corporate firewalls censor connections to Tor's
1075) website. In those cases, you have three options. First, get it from

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

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

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

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

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

1084) in the body of the email, it will reply with instructions. Note that
1085) only a few webmail providers are supported, since they need to be able
1086) to receive very large attachments.
1087) </p>
1088) 
1089) <p>

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

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

1094) </p>
1095) 

1096)     <hr>

1097) 

1098)     <a id="VirusFalsePositives"></a>
1099)     <h3><a class="anchor" href="#VirusFalsePositives"></a></h3>
1100)     <p>

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

1106)     pick a better vendor.
1107)     </p>

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

1110)     recompile it yourself.</p>
1111) 
1112)     <hr>
1113) 

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

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

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

1117) 
1118)     <p>
1119)     Tar is a common archive utility for Unix and Linux systems. If your

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

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

1123)     <p>

1124)     as documented on tar's man page.

1125)     </p>
1126) 
1127)     <hr>
1128) 

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

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

1132) 

1133)     <p>

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

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

1137)     Bundle</a>.

1138)     </p>

1139) 
1140) <hr>
1141) 

1142) <a id="TBBGeneral"></a>
1143) <h2><a class="anchor">Tor Browser Bundle (general):</a></h2>
1144) 

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

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

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

1149) 
1150) <p>

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

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

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

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

1163) </p>

1164) 
1165) <p>

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

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

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

1173) 

1174) <hr>
1175) 

1176) <a id="Ubuntu"></a>
1177) <h3><a class="anchor" href="#Ubuntu">

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

1179) <p>

1180) Ubuntu prevents its users from executing shell scripts by clicking them,
1181) even when the file permissions are set correctly. For now you need to

1182) start the Tor Browser from the command line by running </p>

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

1184) <p>
1185) from inside the Tor Browser directory.
1186) </p>
1187) 

1188) <hr>
1189) 

1190) <a id="SophosOnMac"></a>
1191) <h3><a class="anchor" href="#SophosOnMac">I'm using the Sophos anti-virus
1192) software on my Mac, and Tor Browser won't start.</a></h3>
1193) <p>

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

1196) the protections for "Malicious websites" and "Malicious downloads".
1197) </p>
1198) 

1199) <hr>
1200) 

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

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

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

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

1205) 
1206) <p>

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

1208) on port 9150.

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

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

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

1214) </p>
1215) 
1216) <hr>
1217) 
1218) <a id="TBBPolipo"></a>
1219) <h3><a class="anchor" href="#TBBPolipo">I need an HTTP proxy. Where did
1220) Polipo go?</a></h3>
1221) 
1222) <p>
1223) In the past, Tor bundles included an HTTP proxy like Privoxy or Polipo,
1224) solely to work around a bug in Firefox that was finally fixed in Firefox
1225) 6. Now you don't need a separate HTTP proxy to use Tor, and in fact
1226) leaving it out makes you safer because Torbutton has better control over
1227) Firefox's interaction with websites.
1228) </p>
1229) 
1230) <p>
1231) If you are trying to use some external application with Tor, step zero

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

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

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

1235) proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>
1236) for OSX and Linux.
1237) </p>
1238) 
1239) <p>

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

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

1246) </p>
1247) 
1248) <hr>
1249) 

1250) <a id="TBBOtherExtensions"></a>
1251) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
1252) Firefox extensions?</a></h3>
1253) 
1254) <p>

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

1259) bypassing proxy settings.

1260) </p>

1261) <p>

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

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

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

1271) </p>

1272) 

1273) <hr>
1274) 

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

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

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

1280) 
1281) <p>
1282) We configure NoScript to allow JavaScript by default in the Tor
1283) Browser Bundle because many websites will not work with JavaScript
1284) disabled.  Most users would give up on Tor entirely if a website
1285) they want to use requires JavaScript, because they would not know
1286) how to allow a website to use JavaScript (or that enabling
1287) JavaScript might make a website work).
1288) </p>
1289) 

1290) <p>
1291) There's a tradeoff here. On the one hand, we should leave
1292) JavaScript enabled by default so websites work the way
1293) users expect. On the other hand, we should disable JavaScript
1294) by default to better protect against browser vulnerabilities (<a

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

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

1303) 
1304) <p>

1305) Ultimately, we want the default Tor bundles to use
1306) a combination of firewalls (like the iptables rules
1307) in <a href="https://tails.boum.org/">Tails</a>) and <a
1308) href="https://trac.torproject.org/projects/tor/ticket/7680">sandboxes</a>
1309) to make JavaScript not so scary. In
1310) the shorter term, TBB 3.0 will hopefully <a
1311) href="https://trac.torproject.org/projects/tor/ticket/9387">allow users
1312) to choose their JavaScript settings more easily</a> &mdash; but the
1313) partitioning concern will remain.

1314) </p>
1315) 
1316) <p>

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

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

1323) <a id="TBBOtherBrowser"></a>
1324) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
1325) Chrome/IE/Opera/etc with Tor.</a></h3>
1326) 
1327) <p>
1328) Unfortunately, Torbutton only works with Firefox right now, and without
1329) <a href="https://www.torproject.org/torbutton/en/design/">Torbutton's
1330) extensive privacy fixes</a> there are many ways for websites or other

1331) attackers to recognize you, track you back to your IP address, and so
1332) on.

1333) In short, using any browser besides Tor Browser Bundle with Tor is a
1334) really bad idea.
1335) </p>
1336) 
1337) <p>
1338) We're working with the Chrome team to <a

1339) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-
1340) and-fingerprinting">fix
1341) some bugs and missing APIs in Chrome</a> so it will be possible to write
1342) a
1343) Torbutton for Chrome. No support for any other browser is on the
1344) horizon.

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

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

1350) <h3><a class="anchor" href="#TorbuttonOtherBrowser">

1351) Will Torbutton be available for other browsers?</a></h3>

1352) 
1353) <p>

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

1355) </p>
1356) <p>

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

1358) </p>
1359) 

1360) <hr>

1361) 

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

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

1365) Bundle running but close the browser.</a></h3>
1366) 
1367) <p>
1368) We're working on a way to make this possible on all platforms. Please
1369) be patient.
1370) </p>
1371) 
1372) <hr>
1373) 

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

1377) 
1378) <p>
1379) This is a known and intermittent problem; it does not mean that Google
1380) considers Tor to be spyware.
1381) </p>
1382) 
1383) <p>

1384) When you use Tor, you are sending queries through exit relays that are
1385) also

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

1387) when many Tor users are querying Google in a short period of time.
1388) Google

1389) interprets the high volume of traffic from a single IP address (the exit
1390) relay you happened to pick) as somebody trying to "crawl" their website,
1391) so it slows down traffic from that IP address for a short time.
1392) </p>
1393) <p>
1394) An alternate explanation is that Google tries to detect certain
1395) kinds of spyware or viruses that send distinctive queries to Google
1396) Search. It notes the IP addresses from which those queries are received
1397) (not realizing that they are Tor exit relays), and tries to warn any
1398) connections coming from those IP addresses that recent queries indicate
1399) an infection.
1400) </p>
1401) 
1402) <p>

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

1405) to deter or block Tor use. The error message about an infected machine
1406) should clear up again after a short time.
1407) </p>
1408) 
1409) <p>
1410) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1411) automatically redirect you to a more Tor-friendly search engine such as

1412) DuckDuckGo, ixquick, or Bing.

1413) </p>
1414) 
1415) <hr />
1416) 

1417) <a id="ForeignLanguages"></a>
1418) <h3><a class="anchor" href="#ForeignLanguages">
1419) Why does Google show up in foreign languages?</a></h3>
1420) 
1421) <p>

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

1425)  on your queries.

1426) </p>
1427) <p>

1428) If you really want to see Google in English you can click the link that
1429) provides that. But we consider this a feature with Tor, not a bug --- the
1430) Internet is not flat, and it in fact does look different depending on
1431) where you are. This feature reminds people of this fact. The easy way to
1432) avoid this "feature" is to use

1433) <a href="https://google.com/ncr">https://google.com/ncr</a>.

1434) </p>
1435) <p>

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

1440) </p>

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

1442) <p>

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

1445) </p>
1446) <hr />

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

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

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

1450) 
1451) <p>
1452) Sometimes, after you've used Gmail over Tor, Google presents a
1453) pop-up notification that your account may have been compromised.
1454) The notification window lists a series of IP addresses and locations
1455) throughout the world recently used to access your account.
1456) </p>
1457) 
1458) <p>
1459) In general this is a false alarm: Google saw a bunch of logins from

1460) different places, as a result of running the service via Tor, and
1461) decided

1462) it was a good idea to confirm the account was being accessed by it's
1463) rightful owner.
1464) </p>
1465) 
1466) <p>
1467) Even though this may be a biproduct of using the service via tor,
1468) that doesn't mean you can entirely ignore the warning. It is
1469) <i>probably</i> a false positive, but it might not be since it is
1470) possible for someone to hijack your Google cookie.
1471) </p>
1472) 
1473) <p>
1474) Cookie hijacking is possible by either physical access to your computer
1475) or by watching your network traffic.  In theory only physical access
1476) should compromise your system because Gmail and similar services
1477) should only send the cookie over an SSL link. In practice, alas, it's <a

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

1480) way more complex than that</a>.
1481) </p>
1482) 
1483) <p>
1484) And if somebody <i>did</i> steal your google cookie, they might end
1485) up logging in from unusual places (though of course they also might
1486) not). So the summary is that since you're using Tor, this security
1487) measure that Google uses isn't so useful for you, because it's full of
1488) false positives. You'll have to use other approaches, like seeing if
1489) anything looks weird on the account, or looking at the timestamps for
1490) recent logins and wondering if you actually logged in at those times.
1491) </p>
1492) 
1493) <hr>
1494) 

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

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

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

1498) 
1499) <p>

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

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

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

1509) </p>
1510) <p>

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

1516) </p>
1517) <p>

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

1521) </p>
1522) 
1523) <hr>
1524) 

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

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

1527) set a proxy with my application?</a></h3>
1528) 
1529) <p>

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

1535) available.</p>

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

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

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

1542) </p>
1543) 
1544) <hr>
1545) 

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

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

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

1550)     (Vidalia) go?</a></h3>
1551) 

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

1556)     on providing it</a>. </p>
1557) 

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

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

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

1562) 

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

1566)     be). </p>
1567) 

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

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

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

1574)     replacing its contents with just these lines:</p>
1575) 
1576)     <pre>
1577)     [General]
1578)     LanguageCode=en
1579) 
1580)     [Tor]
1581)     ControlPort=9151
1582)     TorExecutable=.
1583)     Torrc=.
1584)     DataDirectory=.
1585)     AuthenticationMethod=cookie

1586)     </pre>

1587) 
1588)     <hr>
1589) 
1590)     <a id="DisableJS"></a>
1591)     <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1592)     </h3>
1593) 

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

1597)     checkbox anymore either, which is unfortunate.</p>
1598) 

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

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

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

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

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

1612)     provides a button for it. </p>
1613) 

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

1615)     NoScript. </p>
1616) 

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

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

1619) 
1620)     <hr>
1621) 
1622)     <a id="VerifyDownload"></a>
1623)     <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1624)     (sha256sums.txt)?</a></h3>
1625) 

1626)     <p>You can still verify your Tor Browser download by downloading the
1627)     signature file (.asc) along with your package and <a

1628)     href="<page docs/verifying-signatures>">

1629)     checking the GPG signature</a> as before. We now have an additional
1630)     verification method that allows you to verify the build as well as

1631)     the download.</p>
1632) 
1633)     <ul>
1634)       <li>Download the Tor Browser package, the sha256sums.txt file, and the

1635)       sha256sums signature files. They can all be found in the same directory

1636)       under <a href="https://www.torproject.org/dist/torbrowser/">

1637)       https://www.torproject.org/dist/torbrowser/</a>, for example in 3.5

1638)       for TBB 3.5.</li>

1639)       <li>Retrieve the signers' GPG keys. This can be done from the command
1640)       line by entering something like

1641)       <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>

1642)       (This will bring you developer Mike Perry's public key. Other

1643)       developers' key IDs can be found on

1644)       <a href="<page docs/signing-keys>">this

1645)       page</a>.)</li>
1646)       <li>Verify the sha256sums.txt file by executing this command:
1647)       <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>

1648)       <li>You should see a message like "Good signature from &lt;DEVELOPER

1649)       NAME&gt;". If you don't, there is a problem. Try these steps again.</li>

1650)       <li>Now you can take the sha256sum of the Tor Browser package. On

1651)       Windows you can use the <a href="http://md5deep.sourceforge.net/">
1652)       hashdeep utility</a> and run
1653)       <pre>C:\location\where\you\saved\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe</pre>
1654)       On Mac or Linux you can run <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.zip</pre> or <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.tar.gz</pre> without having to download a utility.</li>
1655)       <li>You will see a string of letters and numbers.</li>
1656)       <li>Open sha256sums.txt in a text editor.</li>
1657)       <li>Locate the name of the Tor Browser file you downloaded.</li>
1658)       <li>Compare the string of letters and numbers to the left of your

1659)       filename with the string of letters and numbers that appeared
1660)       on your command line. If they match, you've successfully verified the
1661)       build.</li>

1662)     </ul>
1663) 
1664)     <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">

1665)     Scripts</a> to <a

1666)     href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate

1667)     </a> these steps have been written, but to use them you will need to

1668)     modify them yourself with the latest Tor Browser Bundle filename.</p>
1669) 
1670)     <hr>
1671) 
1672)     <a id="PluggableTransports"></a>
1673)     <h3><a class="anchor" href="#PluggableTransports">How do I use pluggable transports?</a></h3>
1674) 
1675)     <p>

1676)     For now, the Pluggable Transports-capable TBB is still a separate
1677)     unofficial package. Download them <a

1678)     href="https://people.torproject.org/~dcf/pt-bundle/3.5-pt20131217/">
1679)     here</a>. We hope to have combined packages available in a beta soon.
1680)     </p>
1681) 
1682)     <p>

1683)     The separate Pluggable Transports-capable TBB is different from the
1684)     Pluggable Transports bundles that have been released in the past.
1685)     They include the programs necessary to use obfsproxy and flash proxy,
1686)     but the pluggable transports are not enabled by default. You must
1687)     enable them manually by adding Bridge lines to the torrc file.
1688)     (Please see ticket <a
1689)     href="https://trac.torproject.org/projects/tor/ticket/10418">#10418</a>

1690)     for how we hope to make it easier to do in the future.)
1691)     </p>
1692) 
1693)     <p>

1694)     To enable <b>obfsproxy</b>, edit the file called Data/Tor/torrc inside the
1695)     bundle and add the lines:

1696)     </p>
1697) 
1698)     <pre>

1699) Bridge obfs3 83.212.101.3:60475 A09D536DD1752D542E1FBB3C9CE4449D51298239

1700) Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1701) Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9

1702) Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2
1703) Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F

1704) Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
1705) Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
1706) Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
1707) Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
1708) Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
1709) Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
1710)     </pre>
1711)     <p>

1712)     To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the
1713)     bundle and add the line:

1714)     </p>
1715)     <pre>
1716) Bridge flashproxy 0.0.1.0:1
1717)     </pre>
1718) 
1719)     <hr>
1720) 
1721)     <a id="NewIdentityClosingTabs"></a>

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

1723)     Identity" close all my open tabs?</a></h3>
1724) 
1725)     <p>

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

1728)     are used to Vidalia's "new identity" behavior.
1729)     </p>
1730) 
1731)     <p>

1732)     We're working on ways to make the behavior less surprising, e.g. a popup
1733)     warning or auto restoring tabs. See ticket <a
1734)     href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and
1735)     ticket <a
1736)     href="https://trac.torproject.org/projects/tor/ticket/10400">#10400</a>
1737)     to follow progress there.

1738)     </p>
1739) 
1740)     <p>

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

1744)     </p>
1745) 
1746)     <hr>
1747) 
1748)     <a id="ConfigureRelayOrBridge"></a>
1749)     <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1750) 
1751)     <p>

1752)     You've got three options.

1753)     </p>
1754) 
1755)     <p>

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

1759)     You can then use TBB independent of that.
1760)     </p>
1761) 
1762)     <p>

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

1766)     </p>
1767) 
1768)     <p>

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

1772)     </p>
1773)     <pre>
1774)     ORPort 443
1775)     Exitpolicy reject *:*
1776)     BridgeRelay 1  # only add this line if you want to be a bridge
1777)     </pre>
1778)     <p>

1779)     If you've installed <a

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

1781)     you'll need to add one more line:
1782)     </p>
1783)     <pre>
1784)     ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1785)     </pre>
1786)     <p>

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

1790)     </p>
1791) 
1792)     <hr>
1793) 
1794)     <a id="Timestamps"></a>

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

1796)     from 2000?</a></h3>
1797) 

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

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

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

1805)     </p>
1806) 

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

1809)     you might see 7pm in 1999 is because of time zones. </p>
1810) 
1811)     <hr>
1812) 

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

1815) 
1816)     <p>
1817)     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>.
1818)     </p>
1819) 
1820) 

1821) <hr>
1822) 

1823) <a id="AdvancedTorUsage"></a>
1824) <h2><a class="anchor">Advanced Tor usage:</a></h2>
1825) 

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

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

1829) 
1830) <p>
1831) Tor installs a text file called torrc that contains configuration
1832) instructions for how your Tor program should behave. The default

1833) configuration should work fine for most Tor users.

1834) </p>

1835) <p>

1836) If you installed Tor Browser Bundle, look for

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

1841) </p>
1842) <p>

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

1844) 
1845) <p>

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

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

1850) </p>
1851) 
1852) <p>

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

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

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

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

1858) on Tor's configuration.

1859) </p>
1860) 
1861) <hr>
1862) 

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

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

1866) 
1867) <p>

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

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

1872) </p>
1873) 
1874) <p>
1875) If you're not using Vidalia, you'll have to go find the log files by

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

1877) </p>
1878) 
1879) <ul>
1880) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1881) </li>

1882) <li>On Windows, there are no default log files currently. If you enable
1883) logs in your torrc file, they default to <code>\username\Application
1884) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1885) </li>
1886) <li>If you compiled Tor from source, by default your Tor logs to <a
1887) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1888) at log-level notice. If you enable logs in your torrc file, they
1889) default to <code>/usr/local/var/log/tor/</code>.

1890) </li>
1891) </ul>
1892) 
1893) <p>

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

1896) and find the section (near the top of the file) which contains the
1897) following line:

1898) </p>
1899) 
1900) <pre>

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

1903) </pre>

1904) 
1905) <p>

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

1907) and err level messages to a file, append the following line to the end
1908) of the section:
1909) </p>
1910) 
1911) <pre>
1912) Log debug file c:/program files/tor/debug.log
1913) </pre>
1914) 
1915) <p>

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

1918) </p>
1919) 
1920) <hr>
1921) 

1922) 
1923) <a id="LogLevel"></a>
1924) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1925) 
1926) <p>

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

1928) Tor's logs:

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

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

1933)     exit.</li>

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

1937)     correct the problem.</li>

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

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

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

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

1942) </ul>
1943) 
1944) <p>

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

1947) correctly for each situation.

1948) </p>
1949) 
1950) <p>

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

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

1953) </p>
1954) 
1955) <p>

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

1959) </p>
1960) 

1961) <hr>
1962) 

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

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

1966) 
1967) <p>

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

1970) </p>
1971) 
1972) <p>If Tor can establish a circuit, the onion icon in

1973) Vidalia will turn green (and if you're running Tor Browser Bundle, it
1974) will
1975) automatically launch a browser for you). You can also check in the
1976) Vidalia

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

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

1980) a line saying that Tor "has successfully opened a circuit. Looks like
1981) client functionality is working."
1982) </p>
1983) 
1984) <p>
1985) If Tor can't establish a circuit, here are some hints:
1986) </p>
1987) 
1988) <ol>
1989) <li>Are you sure Tor is running? If you're using Vidalia, you may have
1990) to click on the onion and select "Start" to launch Tor.</li>
1991) <li>Check your system clock. If it's more than a few hours off, Tor will

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

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

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

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

1999) </li>

2000) <li>Are you running programs like Norton Internet Security or SELinux
2001) that

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

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

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

2009) </ol>
2010) 
2011) <hr />
2012) 

2013) <a id="TorCrash"></a>
2014) <h3><a class="anchor" href="#TorCrash">My Tor keeps crashing.</a></h3>
2015) <p>

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

2020) </p>
2021) <p>

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

2024) </p>
2025) <p>

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

2028) </p>
2029) <p>

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

2033) </p>
2034) <p>

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

2040) </p>
2041) <p>

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

2043) </p>
2044) <ul>
2045) <li>

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

2050) </li>
2051) <li>

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

2060) your bug on Unix?)
2061) </li>
2062) <li>

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

2072) </li>
2073) <li>

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

2081) </li>
2082) </ul>
2083) <p>

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

2094) </p>
2095) 
2096) <hr />
2097) 

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

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

2101) 
2102) <p>
2103) Vidalia interacts with the Tor software via Tor's "control port". The
2104) control port lets Vidalia receive status updates from Tor, request a new
2105) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
2106) Vidalia sets a random password for Tor's control port to prevent other
2107) applications from also connecting to the control port and potentially
2108) compromising your anonymity.
2109) </p>
2110) 
2111) <p>
2112) Usually this process of generating and setting a random control password
2113) happens in the background. There are three common situations, though,
2114) where Vidalia may prompt you for a password:
2115) </p>
2116) 
2117) <ol>
2118) <li>You're already running Vidalia and Tor. For example, this situation
2119) can happen if you installed the Vidalia bundle and now you're trying to
2120) run the Tor Browser Bundle. In that case, you'll need to close the old
2121) Vidalia and Tor before you can run this one.
2122) </li>
2123) <li>Vidalia crashed, but left Tor running with the last known random
2124) password. After you restart Vidalia, it generates a new random password,

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