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="#UbuntuBlackedOut">I'm using Ubuntu, and I can't type 
84)     anything into my browser.</a></li>
85)     <li><a href="#SophosOnMac">I'm using the Sophos anti-virus
86)     software on my Mac, and Tor Browser won't start.</a></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

111)     <li><a href="#CantSetProxy">What should I do if I can't set a proxy 
112)     with my application?</a></li>

113)     </ul>
114) 

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

116) 
117)     <ul>

118)     <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia) 
119)     go?</a></li>
120)     <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
121)     <li><a href="#VerifyDownload">How do I verify the download 
122)     (sha256sums.txt)?</a></li>

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

124)     <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close 
125)     all my open tabs?</a></li>
126)     <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay 
127)     or bridge?</a></li>
128)     <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>

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

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

131)     </ul>
132) 

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

134) 

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

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

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

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

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

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

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

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

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

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

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

152)     <li><a href="#WarningsAboutSOCKSandDNSInformationLeaks">I keep seeing 
153)     these warnings about SOCKS and DNS information leaks. Should I 
154)     worry?</a></li>

155)     <li><a href="#SocksAndDNS">How do I check if my application that uses 
156)     SOCKS is leaking DNS requests?</a></li>

157)     </ul>

158) 

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

160)     <ul>

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

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

166)     <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li>
167)     <li><a href="#PortscannedMore">Why do I get portscanned more often 
168)     when I run a Tor relay?</a></li>
169)     <li><a href="#MoreThanOneCPU">I have more than one CPU. Does this 
170)     help?</a></li>

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

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

175)     <li><a href="#BandwidthShaping">What bandwidth shaping options are 
176)     available to Tor relays?</a></li>
177)     <li><a href="#LimitTotalBandwidth">How can I limit the total amount 
178)     of bandwidth used by my Tor relay?</a></li>

179)     <li><a href="#RelayWritesMoreThanItReads">Why does my relay write 
180)     more bytes onto the network than it reads?</a></li>
181)     <li><a href="#Hibernation">Why can I not browse anymore after 
182)     limiting bandwidth on my Tor relay?</a></li>

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

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

185)     <li><a href="#BestOSForRelay">Why doesn't my Windows (or other OS) Tor 
186)     relay run well?</a></li>

187)     <li><a href="#WhatIsTheBadExitFlag">What is the BadExit flag?</a></li>
188)     <li><a href="#IGotTheBadExitFlagWhyDidThatHappen">I got the BadExit flag. 
189)     Why did that happen?</a></li>
190)     <li><a href="#MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf">My 
191)     relay recently got the Guard flag and traffic dropped by half.</a></li>
192)     <li><a href="#TorClientOnADifferentComputerThanMyApplications">I want to run my Tor client on a 

193)     different computer than my applications.</a></li>
194)     <li><a href="#ServerClient">Can I install Tor on a central server, and 
195)     have my clients connect to it?</a></li>
196)     <li><a href="#JoinTheNetwork">So I can just configure a nickname and 
197)     ORPort and join the network?</a></li>

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

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

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

204)     <li><a href="#NTService">How do I run my Tor relay as an NT service?
205)     </a></li>
206)     <li><a href="#VirtualServer">Can I run a Tor relay from my virtual server 
207)     account?</a></li>

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

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

214)     <li><a href="#FacingLegalTrouble">I'm facing legal trouble. How do I 
215)     prove that my server was a Tor relay at a given time?</a></li>

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

218)     </ul>

219) 

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

221) 

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

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

225)     </ul>

226) 

227)     <p>Development:</p>

228) 

229)     <ul>
230)     <li><a href="#WhoIsResponsible">Who is responsible for Tor?</a></li>
231)     <li><a href="#VersionNumbers">What do these weird version numbers 
232)     mean?</a></li>
233)     <li><a href="#PrivateTorNetwork">How do I set up my own private
234)     Tor network?</a></li>
235)     <li><a href="#UseTorWithJava">How can I make my Java program use the 
236)     Tor network?</a></li>
237)     <li><a href="#WhatIsLibevent">What is Libevent?</a></li>
238)     <li><a href="#MyNewFeature">What do I need to do to get a new feature 
239)     into Tor?</a></li>
240)     </ul>
241) 

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

243)     <ul>

244)     <li><a href="#WhatProtectionsDoesTorProvide">What protections does Tor 
245)     provide?</a></li>
246)     <li><a href="#CanExitNodesEavesdrop">Can exit nodes eavesdrop on 
247)     communications? Isn't that bad? </a></li>

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

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

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

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

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

255)     <li><a href="#CellSize">Tor uses hundreds of bytes for every IRC line. I 
256)     can't afford that!</a></li>
257)     <li><a href="#OutboundConnections">Why does netstat show these outbound 
258)     connections?</a></li>
259)     <li><a href="#PowerfulBlockers">What about powerful blocking mechanisms
260)     </a></li>
261)     <li><a href="#RemotePhysicalDeviceFingerprinting">Does Tor resist 
262)     "remote physical device fingerprinting"?</a></li>

263)     <li><a href="#IsTorLikeAVPN">Is Tor like a VPN?</a></li>
264)     <li><a href="#ShouldIUseTorWithAVPN">Should I use Tor with a VPN?</a></li>

265)     <li><a href="#Proxychains">Aren't 10 proxies (proxychains) better than 
266)     Tor with only 3 hops?</a></li>

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

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

270)     </ul>

271) 

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

273) 

274)     <ul>
275)     <li><a href="#EverybodyARelay">You should make every Tor user be a
276)     relay.</a></li>

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

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

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

282)     <li><a href="#ChoosePathLength">You should let people choose their path 
283)     length.</a></li>
284)     <li><a href="#SplitEachConnection">You should split each connection over 
285)     many paths.</a></li>

286)     <li><a href="#MigrateApplicationStreamsAcrossCircuits">You should migrate 
287)     application streams across circuits.</a></li>
288)     <li><a href="#LetTheNetworkPickThePath">You should let the network pick 
289)     the path, not the client.</a></li>

290)     <li><a href="#UnallocatedNetBlocks">Your default exit policy should block 
291)     unallocated net blocks too.</a></li>
292)     <li><a href="#BlockWebsites">Exit policies should be able to block 
293)     websites, not just IP addresses.</a></li>
294)     <li><a href="#BlockContent">You should change Tor to prevent users from 
295)     posting certain content.</a></li>

296)     <li><a href="#SendPadding">You should send padding so it's more secure.
297)     </a></li>
298)     <li><a href="#Steganography">You should use steganography to hide Tor 
299)     traffic.</a></li>

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

301)     </ul>

302) 

303)     <p>Abuse:</p>

304)     <ul>

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

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

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

311)     </ul>

312) 

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

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

316) 

317)     <hr>

318) 

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

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

321) 

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

324) 

325)     <p>
326)     The name "Tor" can refer to several different components.
327)     </p>

328) 

329)     <p>

330)     The Tor software is a program you can run on your computer that
331) helps keep
332)     you safe on the Internet. Tor protects you by bouncing your
333) communications

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

335)     the world: it prevents somebody watching your Internet connection
336) from

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

338)     from learning your physical location. This set of volunteer relays
339) is
340)     called the Tor network. You can read more about how Tor works on the
341) <a

342)     href="<page about/overview>">overview page</a>.
343)     </p>

344) 

345)     <p>

346)     The Tor Project is a non-profit (charity) organization that
347) maintains

348)     and develops the Tor software.
349)     </p>

350) 

351)     <hr>

352) 

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

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

377) free wifi Internet.
378)     </p>
379)     <p>

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

386) inside your

387) encrypted traffic as they relay it to your banking site or to ecommerce
388) stores.

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

390) watching your traffic, injecting their own advertisements into your
391) traffic

392) stream, and recording your personal details.

393)     </p>
394)     <p>

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

411) packets between themselves.</p>

412)     <p>
413)     <dl>

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

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

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

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

430) e-commerce website, or encrypted mail connections, etc, it will only
431) know the
432) destination.  It won't be able to see the data inside the traffic
433) stream.  You

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

436)     </dl>
437)     </p>

438) 

439)     <hr>

440) 

441) 

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

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

445) 

446)     <p>

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

451)     </p>
452)     <p>
453)     There are plenty of other programs you can use with Tor,
454)     but we haven't researched the application-level anonymity

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

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

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

458)     specific applications</a>.

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

461) 

462)     <hr>

463) 

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

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

467) 

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

477) 

478)     <p>
479)     (It's also got a fine translation from German and Turkish.)
480)     </p>

481) 

482)     <p>

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

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

486)     spot people who haven't read any of our website (and have instead
487) learned
488)     everything they know about Tor from news articles) by the fact that
489) they

490)     spell it wrong.
491)     </p>

492) 

493)     <hr>

494) 

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

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

498) 

499)     <p>

500)     There is absolutely no backdoor in Tor. Nobody has asked us to put
501) one
502)     in, and we know some smart lawyers who say that it's unlikely that
503) anybody

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

507) 

508)     <p>
509)     We think that putting a backdoor in Tor would be tremendously

510)     irresponsible to our users, and a bad precedent for security
511) software

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

516) 

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

520)     computers, or something like that. Tor is open source, and you
521) should
522)     always check the source (or at least the diffs since the last
523) release)

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

530) 

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

533)     anonymity. We periodically find and fix anonymity-related bugs, so
534) make

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

537) 

538)     <hr>

539) 

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

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

543) 

544)     <p>
545)     Yes.
546)     </p>

547) 

548)     <p>

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

555)     ask us for specific permission.
556)     </p>

557) 

558)     <p>

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

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

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

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

566) 

567)     <p>

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

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

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

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

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

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

583)     </p>

584) 

585)     <p>

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

592)     </p>

593) 

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

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

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

603) 

604)     <hr>

605) 

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

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

609) 

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

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

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

615)     <li>Read through the <a

616) 
617) href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">
618) tor-talk

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

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

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

623)     <li>Send an email to <a

624) 
625) href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.</li>
626)     <li>If all else fails, try <a href="<page about/contact>">contacting
627) us</a> directly.</li>

628)     </ol>

629) 

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

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

633) 

634)     <hr>

635) 

636)     <a id="Forum"></a>
637)     <h3><a class="anchor" href="#Forum">Is there a Tor forum?</a></h3>
638) 

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

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

641)     </p>
642) 
643)     <hr>
644) 

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

647) 

648)     <p>
649)     There are many reasons why the Tor network is currently slow.
650)     </p>

651) 

652)     <p>

653)     Before we answer, though, you should realize that Tor is never going
654) to
655)     be blazing fast. Your traffic is bouncing through volunteers'
656) computers
657)     in various parts of the world, and some bottlenecks and network
658) latency

659)     will always be present. You shouldn't expect to see university-style
660)     bandwidth through Tor.
661)     </p>

662) 

663)     <p>

664)     But that doesn't mean that it can't be improved. The current Tor
665) network
666)     is quite small compared to the number of people trying to use it,
667) and
668)     many of these users don't understand or care that Tor can't
669) currently

670)     handle file-sharing traffic load.
671)     </p>

672) 

673)     <p>
674)     For the much more in-depth answer, see <a

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

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

678)     to go with it.
679)     </p>

680) 

681)     <p>
682)     What can you do to help?
683)     </p>

684) 

685)     <ul>

686) 

687)     <li>

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

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

694) 

695)     <li>

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

698)     especially need people to help make it easier to configure your Tor
699)     as a relay. Also, we need help with clear simple documentation to
700)     walk people through setting it up.
701)     </li>

702) 

703)     <li>

704)     There are some bottlenecks in the current Tor network. Help us
705) design
706)     experiments to track down and demonstrate where the problems are,
707) and

708)     then we can focus better on fixing them.
709)     </li>

710) 

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

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

717)     get to spend more time on it.
718)     </li>

719) 

720)     <li>

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

725)     getinvolved/volunteer>">look at our volunteer page</a>.
726)     </li>

727) 

728)     <li>

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

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

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

740)     </li>

741) 

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

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

746)     cause</a>. It adds up!
747)     </li>

748) 

749)     </ul>

750) 

751)     <hr>

752) 

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

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

756) 
757)     <p>

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

764)     </p>
765) 
766)     <hr>
767) 

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

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

771) 

772)     <p>

773)     The Tor network's <a

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

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

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

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

783)     </p>

784) 

785)     <p>

786)     There are six main development/maintenance pushes that need
787) attention:

788)     </p>

789) 

790)     <ul>

791) 

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

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

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

799) 

800)     <li>

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

807)     </li>

808) 

809)     <li>

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

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

813)     reminders to upgrade, and so on. The network itself is a commons,
814) and
815)     somebody needs to spend some energy making sure the relay operators
816) stay
817)     happy. We also need to work on stability on some platforms —
818) e.g.,

819)     Tor relays have problems on Win XP currently.

820)     </li>

821) 

822)     <li>

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

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

835) 

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

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

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

843) 

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

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

855)     behind these.
856)     </li>

857) 

858)     </ul>

859) 

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

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

864)     can keep up</a>.

865)     Now would be an excellent time to add a few more developers to the
866) effort

867)     so we can continue to grow the network.
868)     </p>

869) 

870)     <p>
871)     We are also excited about tackling related problems, such as
872)     censorship-resistance.
873)     </p>

874) 

875)     <p>

876)     We are proud to have <a href="<page about/sponsors>">sponsorship and
877) support</a>
878)     from the Omidyar Network, the International Broadcasting Bureau,
879) Bell
880)     Security Solutions, the Electronic Frontier Foundation, several
881) government

882)     agencies and research groups, and hundreds of private contributors.
883)     </p>

884) 

885)     <p>

886)     However, this support is not enough to keep Tor abreast of changes
887) in the
888)     Internet privacy landscape. Please <a href="<page
889) donate/donate>">donate</a>
890)     to the project, or <a href="<page about/contact>">contact</a> our
891) executive

892)     director for information on making grants or major donations.
893)     </p>

894) 

895)     <hr>
896) 

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

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

900) 
901)     <p>

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

906)     </p>
907)     <p>

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

915)     </p>
916)     <p>

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

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

919)     </p>
920)     <p>

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

926)     </p>
927)     
928)     <hr>
929)     
930)     <a id="IsItWorking"></a>

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

933) 
934)     <p>

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

938)     </p>
939)     <p>

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

946)     </p>
947)     <p>

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

951)     </p>
952)     <p>

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

959)     </p>
960)     
961)     <hr>
962)     
963)     <a id="FTP"></a>
964)     <h3><a class="anchor" href="#FTP">How do I use my browser for ftp with Tor?
965)     </a></h3>
966) 

967)     <p>

968)     Use the <a href="https://torproject.org/projects/torbrowser.html">Tor 
969)     Browser Bundle</a>. If you want a separate application for an 

970)     ftp client, we've heard good things about  FileZilla for Windows. You can 
971)     configure it to point to Tor as a "socks4a" proxy on "localhost" port 
972)     "9050". 
973)     </p>

974) 

975)     <hr>
976)     

977)     <a id="NoDataScrubbing"></a>
978)     <h3><a class="anchor" href="#NoDataScrubbing">Does Tor remove personal 
979)     information from the data my application sends?</a></h3>
980) 
981)     <p>No, it doesn't. You need to use a separate program that understands 
982)     your application and protocol and knows how to clean or "scrub" the data 
983)     it sends. The Tor Browser Bundle tries to keep application-level data, 
984)     like the user-agent string, uniform for all users. The Tor Browser can't 
985)     do anything about text that you type into forms, though. <a 
986)     href="https://www.torproject.org/download/download-easy.html.en#warning">Be 
987)     careful and be smart.</a>
988)     </p>
989) 
990)     <hr>
991) 

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

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

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

995) 

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

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

999)     <hr>

1000) 

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

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

1004)     <p>

1005)     <pre>

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

1007)     The serial number is:

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

1010)     The SHA-256 fingerprint is:

1011) 3613d2b22a750094760c41ad19db52a4f05bdea80172e2578761ad967f7ed9aa

1012) 

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

1014)     The serial number is: 00:EF:A3
1015)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

1016)     </pre>

1017)     </p>
1018)     <hr>
1019) 

1020)     <a id="CompilationAndInstallation"></a>
1021)     <h2><a class="anchor">Compilation And Installation:</a></h2>
1022) 

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

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

1032) 

1033)     <p>

1034)     If this is not related to Tor Browser, uninstallation depends
1035) entirely on how you installed it and which operating system you
1036)     have. If you installed a package, then hopefully your package has a
1037) way to

1038)     uninstall itself. The Windows packages include uninstallers. 

1039)     </p>

1040) 

1041)     <p>
1042)     For Mac OS X, follow the <a
1043)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
1044)     </p>

1045) 

1046)     <p>

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

1051)     be pretty easy to notice things there.
1052)     </p>

1053) 

1054)     <hr>

1055) 

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

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

1059) 

1060)     <p>

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

1063)     exactly the one that we intended you to get.
1064)     </p>

1065) 

1066)     <p>
1067)     Please read the <a

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

1070)     </p>

1071) 

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

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

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

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

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

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

1089) in the body of the email, it will reply with instructions. Note that
1090) only a few webmail providers are supported, since they need to be able
1091) to receive very large attachments.
1092) </p>
1093) 
1094) <p>

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

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

1099) </p>
1100) 

1101)     <hr>

1102) 

1103)     <a id="VirusFalsePositives"></a>
1104)     <h3><a class="anchor" href="#VirusFalsePositives"></a></h3>
1105)     <p>
1106)     Sometimes, overzealous Windows virus and spyware detectors trigger on 
1107)     some parts of the Tor Windows binary. Our best guess is that these are 
1108)     false positives — after all, the anti-virus and anti-spyware business is 
1109)     just a guessing game anyway. You should contact your vendor and explain 
1110)     that you have a program that seems to be triggering false positives. Or 
1111)     pick a better vendor.
1112)     </p>
1113)     <p>In the meantime, we encourage you to not just take our word for it. 
1114)     Our job is to provide the source; if you're concerned, please do 
1115)     recompile it yourself.</p>
1116) 
1117)     <hr>
1118) 

1119)     <a id="tarballs"></a>
1120)     <h3><a class="anchor" href="#tarballs">How do I open a .tar.gz 

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

1122) 
1123)     <p>
1124)     Tar is a common archive utility for Unix and Linux systems. If your
1125)     system has a mouse, you can usually open them by double clicking. 

1126)     Otherwise open a command prompt and execute</p> 

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

1128)     <p>

1129)     as documented on tar's man page. 

1130)     </p>
1131) 
1132)     <hr>
1133) 

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

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

1137) 

1138)     <p>

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

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

1142)     Bundle</a>.

1143)     </p>

1144) 
1145) <hr>
1146) 

1147) <a id="TBBGeneral"></a>
1148) <h2><a class="anchor">Tor Browser Bundle (general):</a></h2>
1149) 

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

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

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

1154) 
1155) <p>

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

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

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

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

1169) 
1170) <p>

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

1172) support</a> for many of their videos. Often you can get the HTML5 version of 
1173) videos that don't want to play by grabbing the YouTube URL from the "Embed" 
1174) code under a video's "Share" option. The link switches out a URL that looks</p>
1175) <pre>https://www.youtube.com/watch?v=CJNxbpbHA-I</pre>
1176) <p>to something that looks like</p>
1177) <pre>https://www.youtube.com/embed/CJNxbpbHA-I</pre>

1178) 

1179) <hr>
1180) 

1181) <a id="Ubuntu"></a>
1182) <h3><a class="anchor" href="#Ubuntu">

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

1184) <p>

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

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

1189) <p>
1190) from inside the Tor Browser directory.
1191) </p>
1192) 

1193) <hr>
1194) 

1195) <a id="UbuntuBlackedOut"></a>
1196) <h3><a class="anchor" href="#UbuntuBlackedOut">
1197) I'm using Ubuntu, and I can't type anything into my browser.</a></h3>
1198) <p>Another issue affecting Ubuntu users is that when Tor Browser opens, text
1199) fields, including the address bar, are blacked out and can not be used.
1200) This is not so great, and we hope to include a fix in a coming release. 
1201) In the mean time, this issue can be worked around by editing the 
1202) start-tor-browser script and adding the following line below line 1:</p>

1203) <pre>export GTK_IM_MODULE=xim</pre>

1204) <p>This issue is related to the version of IBUS that ships with Ubuntu. 
1205) Some users have also reported success by executing this command</p>

1206) <pre>ibus exit</pre>

1207) <p>To follow the progress of this issue, see this <a 
1208) href="https://trac.torproject.org/projects/tor/ticket/9353">bug ticket.</a>
1209) </p>
1210) 
1211) <hr>
1212) 
1213) <a id="SophosOnMac"></a>
1214) <h3><a class="anchor" href="#SophosOnMac">I'm using the Sophos anti-virus
1215) software on my Mac, and Tor Browser won't start.</a></h3>
1216) <p>
1217) You'll need to modify Sophos anti-virus so that Tor can connect to the 
1218) internet. Go to Preferences -> Web Protection -> General, and turn off 
1219) the protections for "Malicious websites" and "Malicious downloads".
1220) </p>
1221) 

1222) <hr>
1223) 

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

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

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

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

1228) 
1229) <p>

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

1231) on port 9150.

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

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

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

1237) </p>
1238) 
1239) <hr>
1240) 
1241) <a id="TBBPolipo"></a>
1242) <h3><a class="anchor" href="#TBBPolipo">I need an HTTP proxy. Where did
1243) Polipo go?</a></h3>
1244) 
1245) <p>
1246) In the past, Tor bundles included an HTTP proxy like Privoxy or Polipo,
1247) solely to work around a bug in Firefox that was finally fixed in Firefox
1248) 6. Now you don't need a separate HTTP proxy to use Tor, and in fact
1249) leaving it out makes you safer because Torbutton has better control over
1250) Firefox's interaction with websites.
1251) </p>
1252) 
1253) <p>
1254) If you are trying to use some external application with Tor, step zero

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

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

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

1258) proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>
1259) for OSX and Linux.
1260) </p>
1261) 
1262) <p>

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

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

1269) </p>
1270) 
1271) <hr>
1272) 

1273) <a id="TBBOtherExtensions"></a>
1274) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
1275) Firefox extensions?</a></h3>
1276) 
1277) <p>

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

1283) </p>

1284) <p>

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

1294) </p>

1295) 

1296) <hr>
1297) 

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

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

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

1303) 
1304) <p>
1305) We configure NoScript to allow JavaScript by default in the Tor
1306) Browser Bundle because many websites will not work with JavaScript
1307) disabled.  Most users would give up on Tor entirely if a website
1308) they want to use requires JavaScript, because they would not know
1309) how to allow a website to use JavaScript (or that enabling
1310) JavaScript might make a website work).
1311) </p>
1312) 

1313) <p>
1314) There's a tradeoff here. On the one hand, we should leave
1315) JavaScript enabled by default so websites work the way
1316) users expect. On the other hand, we should disable JavaScript
1317) by default to better protect against browser vulnerabilities (<a

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

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

1326) 
1327) <p>

1328) Ultimately, we want the default Tor bundles to use
1329) a combination of firewalls (like the iptables rules
1330) in <a href="https://tails.boum.org/">Tails</a>) and <a
1331) href="https://trac.torproject.org/projects/tor/ticket/7680">sandboxes</a>
1332) to make JavaScript not so scary. In
1333) the shorter term, TBB 3.0 will hopefully <a
1334) href="https://trac.torproject.org/projects/tor/ticket/9387">allow users
1335) to choose their JavaScript settings more easily</a> &mdash; but the
1336) partitioning concern will remain.

1337) </p>
1338) 
1339) <p>

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

1342) </p>
1343) 
1344) <hr>
1345) 

1346) <a id="TBBOtherBrowser"></a>
1347) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
1348) Chrome/IE/Opera/etc with Tor.</a></h3>
1349) 
1350) <p>
1351) Unfortunately, Torbutton only works with Firefox right now, and without
1352) <a href="https://www.torproject.org/torbutton/en/design/">Torbutton's
1353) extensive privacy fixes</a> there are many ways for websites or other

1354) attackers to recognize you, track you back to your IP address, and so
1355) on.

1356) In short, using any browser besides Tor Browser Bundle with Tor is a
1357) really bad idea.
1358) </p>
1359) 
1360) <p>
1361) We're working with the Chrome team to <a

1362) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-
1363) and-fingerprinting">fix
1364) some bugs and missing APIs in Chrome</a> so it will be possible to write
1365) a
1366) Torbutton for Chrome. No support for any other browser is on the
1367) horizon.

1368) </p>
1369) 
1370) <hr>
1371) 

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

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

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

1375) 
1376) <p>

1377)  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.

1378) </p>
1379) <p>

1380) 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. 

1381) </p>
1382) 

1383) <hr>

1384) 

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

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

1388) Bundle running but close the browser.</a></h3>
1389) 
1390) <p>
1391) We're working on a way to make this possible on all platforms. Please
1392) be patient.
1393) </p>
1394) 
1395) <hr>
1396) 

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

1400) 
1401) <p>
1402) This is a known and intermittent problem; it does not mean that Google
1403) considers Tor to be spyware.
1404) </p>
1405) 
1406) <p>

1407) When you use Tor, you are sending queries through exit relays that are
1408) also

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

1410) when many Tor users are querying Google in a short period of time.
1411) Google

1412) interprets the high volume of traffic from a single IP address (the exit
1413) relay you happened to pick) as somebody trying to "crawl" their website,
1414) so it slows down traffic from that IP address for a short time.
1415) </p>
1416) <p>
1417) An alternate explanation is that Google tries to detect certain
1418) kinds of spyware or viruses that send distinctive queries to Google
1419) Search. It notes the IP addresses from which those queries are received
1420) (not realizing that they are Tor exit relays), and tries to warn any
1421) connections coming from those IP addresses that recent queries indicate
1422) an infection.
1423) </p>
1424) 
1425) <p>

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

1428) to deter or block Tor use. The error message about an infected machine
1429) should clear up again after a short time.
1430) </p>
1431) 
1432) <p>
1433) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1434) automatically redirect you to a more Tor-friendly search engine such as

1435) DuckDuckGo, ixquick, or Bing.

1436) </p>
1437) 
1438) <hr />
1439) 

1440) <a id="ForeignLanguages"></a>
1441) <h3><a class="anchor" href="#ForeignLanguages">
1442) Why does Google show up in foreign languages?</a></h3>
1443) 
1444) <p>

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

1449) </p>
1450) <p>

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

1457) </p>
1458) <p>

1459) Note that Google search URLs take name/value pairs as arguments and one 
1460) of those names is "hl". If you set "hl" to "en" then Google will return 
1461) search results in English regardless of what Google server you have been 
1462) sent to. On a query this looks like: 
1463) </p>

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

1465) <p>

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

1468) </p>
1469) <hr />

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

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

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

1473) 
1474) <p>
1475) Sometimes, after you've used Gmail over Tor, Google presents a
1476) pop-up notification that your account may have been compromised.
1477) The notification window lists a series of IP addresses and locations
1478) throughout the world recently used to access your account.
1479) </p>
1480) 
1481) <p>
1482) In general this is a false alarm: Google saw a bunch of logins from

1483) different places, as a result of running the service via Tor, and
1484) decided

1485) it was a good idea to confirm the account was being accessed by it's
1486) rightful owner.
1487) </p>
1488) 
1489) <p>
1490) Even though this may be a biproduct of using the service via tor,
1491) that doesn't mean you can entirely ignore the warning. It is
1492) <i>probably</i> a false positive, but it might not be since it is
1493) possible for someone to hijack your Google cookie.
1494) </p>
1495) 
1496) <p>
1497) Cookie hijacking is possible by either physical access to your computer
1498) or by watching your network traffic.  In theory only physical access
1499) should compromise your system because Gmail and similar services
1500) should only send the cookie over an SSL link. In practice, alas, it's <a

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

1503) way more complex than that</a>.
1504) </p>
1505) 
1506) <p>
1507) And if somebody <i>did</i> steal your google cookie, they might end
1508) up logging in from unusual places (though of course they also might
1509) not). So the summary is that since you're using Tor, this security
1510) measure that Google uses isn't so useful for you, because it's full of
1511) false positives. You'll have to use other approaches, like seeing if
1512) anything looks weird on the account, or looking at the timestamps for
1513) recent logins and wondering if you actually logged in at those times.
1514) </p>
1515) 
1516) <hr>
1517) 

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

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

1521) 
1522) <p>
1523) You can set Proxy IP address, port, and authentication information in 
1524) Tor Browser's Network Settings. If you're using Tor another way, check 
1525) out the HTTPProxy and HTTPSProxy config options in the <a 
1526) href="https://www.torproject.org/docs/tor-manual.html.en">man page</a>, 
1527) and modify your torrc file accordingly. You will need an HTTP proxy for 
1528) doing GET requests to fetch the Tor directory, and you will need an 
1529) HTTPS proxy for doing CONNECT requests to get to Tor relays. (It's fine 
1530) if they're the same proxy.) Tor also recognizes the torrc options 
1531) Socks4Proxy and Socks5Proxy. 
1532) </p>
1533) <p>

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

1537) href="http://archives.seul.org/or/talk/Jun-2005/msg00223.html">this post 
1538) in the archives</a> useful. 
1539) </p>
1540) <p>
1541) If your proxies only allow you to connect to certain ports, look at the 
1542) entry on <a href="#FirewallPorts">Firewalled clients</a> for how 
1543) to restrict what ports your Tor will try to access. 
1544) </p>
1545) 
1546) <hr>
1547) 

1548) <a id="CantSetProxy"></a>
1549) <h3><a class="anchor" href="#CantSetProxy">What should I do if I can't 
1550) set a proxy with my application?</a></h3>
1551) 
1552) <p>
1553) On Unix, we recommend you give <a 
1554) href="https://github.com/dgoulet/torsocks/">torsocks</a> a try. 
1555) Alternative proxifying tools like <a 
1556) href="http://www.dest-unreach.org/socat/">socat</a> and <a 
1557) href="http://proxychains.sourceforge.net/">proxychains</a> are also 
1558) available.</p>
1559) <p> 
1560) The Windows way to force applications through Tor is less clear. <a 
1561) href="http://freecap.ru/eng/">Some</a> <a 
1562) href="http://www.freehaven.net/~aphex/torcap/">tools</a> have been <a 
1563) href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1564) </a>, but we'd also like to see further testing done here. 
1565) </p>
1566) 
1567) <hr>
1568) 

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

1571)     <a id="WhereDidVidaliaGo"></a>
1572)     <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map 
1573)     (Vidalia) go?</a></h3>
1574) 
1575)     <p>Vidalia has been replaced with Tor Launcher, which is a Firefox 
1576)     extension that provides similar functionality. Unfortunately, circuit 
1577)     status reporting is still missing, but we are <a 
1578)     href="https://trac.torproject.org/projects/tor/ticket/8641">working 
1579)     on providing it</a>. </p>
1580) 
1581)     <p>In the meantime, we are providing standalone Vidalia packages for 
1582)     people who still want the map. Windows and Linux versions are <a 

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

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

1585) 
1586)     <p>To use these packages, extract them, then run the startup script. 
1587)     On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia. 
1588)     They can be placed in a different directory from TBB (and likely should 
1589)     be). </p>
1590) 
1591)     <p>This Vidalia package will only run properly if Tor Browser has already 
1592)     been launched. You cannot start it before launching Tor Browser. </p>
1593) 
1594)     <p>MacOS is still under development, but in the mean time you can modify 
1595)     your TBB 2.x to be a standalone Vidalia (and then use it after starting 
1596)     TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and 
1597)     replacing its contents with just these lines:</p>
1598) 
1599)     <pre>
1600)     [General]
1601)     LanguageCode=en
1602) 
1603)     [Tor]
1604)     ControlPort=9151
1605)     TorExecutable=.
1606)     Torrc=.
1607)     DataDirectory=.
1608)     AuthenticationMethod=cookie
1609)     </pre> 
1610) 
1611)     <hr>
1612) 
1613)     <a id="DisableJS"></a>
1614)     <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1615)     </h3>
1616) 
1617)     <p>Alas, Mozilla decided to get rid of the config checkbox for JavaScript 
1618)     from earlier Firefox versions. And since TBB 3.5 is based on Firefox 24 
1619)     (FF17 is unmaintained), that means TBB 3.5 doesn't have the config 
1620)     checkbox anymore either, which is unfortunate.</p>
1621) 
1622)     <p>The simplest way to disable JavaScript in TBB 3.5 is to click on the 
1623)     Noscript "S" (between the green onion and the address bar), and select 
1624)     "Forbid scripts globally". Note that vanilla NoScript actually whitelists 
1625)     several domains even when you try to disable scripts globally, whereas 
1626)     Tor Browser's NoScript configuration disables all of them. </p>
1627) 
1628)     <p>The more klunky way to disable JavaScript is to go to about:config, 
1629)     find javascript.enabled, and set it to false.</p>
1630) 
1631)     <p>There is also a very simple addon available at addons.mozilla.org
1632)     called QuickJS, which provides a toolbar toggle for the javascript.enabled
1633)     about:config control. There are no configuration options for the addon, 
1634)     it just switches the javascript.enabled entry between true and false and 
1635)     provides a button for it. </p>
1636) 
1637)     <p>If you want to be extra safe, use both the about:config setting and 
1638)     NoScript. </p>
1639) 
1640)     <p>As for whether you should disable it or leave it enabled, that's <a 

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

1642) 
1643)     <hr>
1644) 
1645)     <a id="VerifyDownload"></a>
1646)     <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1647)     (sha256sums.txt)?</a></h3>
1648) 
1649)     <p>You can still verify your Tor Browser download by downloading the 
1650)     signature file (.asc) along with your package and <a 
1651)     href="https://www.torproject.org/docs/verifying-signatures.html.en">
1652)     checking the GPG signature</a> as before. We now have an additional 
1653)     verification method that allows you to verify the build as well as 
1654)     the download.</p>
1655) 
1656)     <ul>
1657)       <li>Download the Tor Browser package, the sha256sums.txt file, and the
1658)       sha256sums signature files. They can all be found in the same directory 
1659)       under <a href="https://www.torproject.org/dist/torbrowser/">
1660)       https://www.torproject.org/dist/torbrowser/</a>, for example in 3.5 
1661)       for TBB 3.5.</li>
1662)       <li>Retrieve the signers' GPG keys. This can be done from the command 
1663)       line by entering something like 
1664)       <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>
1665)       (This will bring you developer Mike Perry's public key. Other 
1666)       developers' key IDs can be found on
1667)       <a href="https://www.torproject.org/docs/signing-keys.html.en">this 
1668)       page</a>.)</li>
1669)       <li>Verify the sha256sums.txt file by executing this command:
1670)       <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>
1671)       <li>You should see a message like "Good signature from &lt;DEVELOPER 
1672)       NAME&gt;". If you don't, there is a problem. Try these steps again.</li>
1673)       <li>Now you can take the sha256sum of the Tor Browser package. On 
1674)       Windows you can use the <a href="http://md5deep.sourceforge.net/">
1675)       hashdeep utility</a> and run
1676)       <pre>C:\location\where\you\saved\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe</pre>
1677)       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>
1678)       <li>You will see a string of letters and numbers.</li>
1679)       <li>Open sha256sums.txt in a text editor.</li>
1680)       <li>Locate the name of the Tor Browser file you downloaded.</li>
1681)       <li>Compare the string of letters and numbers to the left of your
1682)       filename with the string of letters and numbers that appeared 
1683)       on your command line. If they match, you've successfully verified the 
1684)       build.</li> 
1685)     </ul>
1686) 
1687)     <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">
1688)     Scripts</a> to <a 
1689)     href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate
1690)     </a> these steps have been written, but to use them you will need to 
1691)     modify them yourself with the latest Tor Browser Bundle filename.</p>
1692) 
1693)     <hr>
1694) 
1695)     <a id="PluggableTransports"></a>
1696)     <h3><a class="anchor" href="#PluggableTransports">How do I use pluggable transports?</a></h3>
1697) 
1698)     <p>
1699)     For now, the Pluggable Transports-capable TBB is still a separate 
1700)     unofficial package. Download them <a 
1701)     href="https://people.torproject.org/~dcf/pt-bundle/3.5-pt20131217/">
1702)     here</a>. We hope to have combined packages available in a beta soon.
1703)     </p>
1704) 
1705)     <p>
1706)     The separate Pluggable Transports-capable TBB is different from the 
1707)     Pluggable Transports bundles that have been released in the past. 
1708)     They include the programs necessary to use obfsproxy and flash proxy, 
1709)     but the pluggable transports are not enabled by default. You must 
1710)     enable them manually by adding Bridge lines to the torrc file. 
1711)     (Please see ticket <a 
1712)     href="https://trac.torproject.org/projects/tor/ticket/10418">#10418</a> 
1713)     for how we hope to make it easier to do in the future.)
1714)     </p>
1715) 
1716)     <p>
1717)     To enable <b>obfsproxy</b>, edit the file called Data/Tor/torrc inside the 
1718)     bundle and add the lines: 
1719)     </p>
1720) 
1721)     <pre>

1722) Bridge obfs3 83.212.101.3:60475 A09D536DD1752D542E1FBB3C9CE4449D51298239

1723) Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1724) Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9

1725) Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2
1726) Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F

1727) Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
1728) Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
1729) Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
1730) Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
1731) Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
1732) Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
1733)     </pre>
1734)     <p>
1735)     To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the 

1736)     bundle and add the line: 

1737)     </p>
1738)     <pre>
1739) Bridge flashproxy 0.0.1.0:1
1740)     </pre>
1741) 
1742)     <hr>
1743) 
1744)     <a id="NewIdentityClosingTabs"></a>
1745)     <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New 
1746)     Identity" close all my open tabs?</a></h3>
1747) 
1748)     <p>
1749)     That's actually a feature, since it's discarding your application-level 
1750)     browser data too. But it sure is a surprising feature, for people who 
1751)     are used to Vidalia's "new identity" behavior.
1752)     </p>
1753) 
1754)     <p>

1755)     We're working on ways to make the behavior less surprising, e.g. a popup
1756)     warning or auto restoring tabs. See ticket <a
1757)     href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and
1758)     ticket <a
1759)     href="https://trac.torproject.org/projects/tor/ticket/10400">#10400</a>
1760)     to follow progress there.

1761)     </p>
1762) 
1763)     <p>

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

1767)     </p>
1768) 
1769)     <hr>
1770) 
1771)     <a id="ConfigureRelayOrBridge"></a>
1772)     <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1773) 
1774)     <p>
1775)     You've got three options. 
1776)     </p>
1777) 
1778)     <p>
1779)     First (best option), if you're on Linux, you can install the system 
1780)     Tor package (e.g. apt-get install tor) and then set it up to be a relay 
1781)     (<a href="https://www.torproject.org/docs/tor-relay-debian">instructions</a>). 
1782)     You can then use TBB independent of that.
1783)     </p>
1784) 
1785)     <p>
1786)     Second (simpler option), if you're on Windows, you can fetch the separate 
1787)     "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page 
1788)     and then use that (again you can use TBB independent of it). 
1789)     </p>
1790) 
1791)     <p>
1792)     Third (complex option), you can either hook your Vidalia up to TBB (as 
1793)     described in the FAQ above) or edit your torrc file (in Data/Tor/torrc) 
1794)     directly to add the following lines: 
1795)     </p>
1796)     <pre>
1797)     ORPort 443
1798)     Exitpolicy reject *:*
1799)     BridgeRelay 1  # only add this line if you want to be a bridge
1800)     </pre>
1801)     <p>
1802)     If you've installed <a 
1803)     href="https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions">Obfsproxy</a>, 
1804)     you'll need to add one more line:
1805)     </p>
1806)     <pre>
1807)     ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1808)     </pre>
1809)     <p>
1810)     This third option is pretty klunky right now; see e.g. <a 
1811)     href="https://trac.torproject.org/projects/tor/ticket/10449">this bug</a>; 
1812)     but we're hoping it will become an easy option in the future. 
1813)     </p>
1814) 
1815)     <hr>
1816) 
1817)     <a id="Timestamps"></a>
1818)     <h3><a class="anchor" href="#Timestamps">Why are the file timestamps 
1819)     from 2000?</a></h3>
1820) 
1821)     <p>One of the huge new features in TBB 3.x is the "deterministic build" 
1822)     process, which allows many people to build the Tor Browser Bundle and 
1823)     verify that they all make exactly the same package. See Mike's <a 
1824)     href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">first 
1825)     blog</a> post for the motivation, and his <a 
1826)     href="https://blog.torproject.org/blog/deterministic-builds-part-two-technical-details">second
1827)     blog post</a> for the technical details of how we do it. 
1828)     </p>
1829) 
1830)     <p>Part of creating identical builds is having everybody use the same 
1831)     timestamp. Mike picked the beginning of 2000 for that time. The reason 
1832)     you might see 7pm in 1999 is because of time zones. </p>
1833) 
1834)     <hr>
1835) 

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

1838) 
1839)     <p>
1840)     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>.
1841)     </p>
1842) 
1843) 

1844) <hr>
1845) 

1846) <a id="AdvancedTorUsage"></a>
1847) <h2><a class="anchor">Advanced Tor usage:</a></h2>
1848) 

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

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

1852) 
1853) <p>
1854) Tor installs a text file called torrc that contains configuration
1855) instructions for how your Tor program should behave. The default

1856) configuration should work fine for most Tor users. 

1857) </p>

1858) <p>

1859) If you installed Tor Browser Bundle, look for

1860) <code>Data/Tor/torrc</code> inside your Tor Browser Bundle directory. 

1861) On OS X, you must right-click or command-click on the browser bundle icon, 
1862) and select "Show Package Contents" before the Tor Browser directories become 
1863) visible. 

1864) </p>
1865) <p>

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

1867) 
1868) <p>

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

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

1873) </p>
1874) 
1875) <p>

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

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

1882) </p>
1883) 
1884) <hr>
1885) 

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

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

1889) 
1890) <p>

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

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

1895) </p>
1896) 
1897) <p>
1898) If you're not using Vidalia, you'll have to go find the log files by

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

1900) </p>
1901) 
1902) <ul>
1903) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1904) </li>

1905) <li>On Windows, there are no default log files currently. If you enable
1906) logs in your torrc file, they default to <code>\username\Application
1907) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1908) </li>
1909) <li>If you compiled Tor from source, by default your Tor logs to <a
1910) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1911) at log-level notice. If you enable logs in your torrc file, they
1912) default to <code>/usr/local/var/log/tor/</code>.

1913) </li>
1914) </ul>
1915) 
1916) <p>

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

1919) and find the section (near the top of the file) which contains the
1920) following line:

1921) </p>
1922) 
1923) <pre>

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

1926) </pre>

1927) 
1928) <p>

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

1930) and err level messages to a file, append the following line to the end
1931) of the section:
1932) </p>
1933) 
1934) <pre>
1935) Log debug file c:/program files/tor/debug.log
1936) </pre>
1937) 
1938) <p>

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

1941) </p>
1942) 
1943) <hr>
1944) 

1945) 
1946) <a id="LogLevel"></a>
1947) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1948) 
1949) <p>

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

1952) </p>
1953) 
1954) <ul>

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

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

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

1964)     <li>"debug": for everything louder than info. It is quite loud indeed.</li> 
1965) </ul>
1966) 
1967) <p>

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

1971) </p>
1972) 
1973) <p>

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

1976) </p>
1977) 
1978) <p>

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

1982) </p>
1983) 

1984) <hr>
1985) 

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

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

1989) 
1990) <p>

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

1993) </p>
1994) 
1995) <p>If Tor can establish a circuit, the onion icon in

1996) Vidalia will turn green (and if you're running Tor Browser Bundle, it
1997) will
1998) automatically launch a browser for you). You can also check in the
1999) Vidalia

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

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

2003) a line saying that Tor "has successfully opened a circuit. Looks like
2004) client functionality is working."
2005) </p>
2006) 
2007) <p>
2008) If Tor can't establish a circuit, here are some hints:
2009) </p>
2010) 
2011) <ol>
2012) <li>Are you sure Tor is running? If you're using Vidalia, you may have
2013) to click on the onion and select "Start" to launch Tor.</li>
2014) <li>Check your system clock. If it's more than a few hours off, Tor will

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

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

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

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

2022) </li>

2023) <li>Are you running programs like Norton Internet Security or SELinux
2024) that

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

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

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

2032) </ol>
2033) 
2034) <hr />
2035) 

2036) <a id="TorCrash"></a>
2037) <h3><a class="anchor" href="#TorCrash">My Tor keeps crashing.</a></h3>
2038) <p>
2039)  We want to hear from you! There are supposed to be zero crash bugs in Tor. 
2040)  This FAQ entry describes the best way for you to be helpful to us. But even 
2041)  if you can't work out all the details, we still want to hear about it, so 
2042)  we can help you track it down. 
2043) </p>
2044) <p>
2045) First, make sure you're using the latest version of Tor (either the latest 
2046) stable or the latest development version). 
2047) </p>
2048) <p>
2049) Second, make sure your version of libevent is new enough. We recommend at 
2050) least libevent 1.3a. 
2051) </p>
2052) <p>
2053) Third, see if there's already an entry for your bug in the <a 
2054) href="https://bugs.torproject.org/">Tor bugtracker</a>. If so, 
2055) check if there are any new details that you can add. 
2056) </p>
2057) <p>
2058) Fourth, is the crash repeatable? Can you cause the crash? Can 
2059) you isolate some of the circumstances or config options that 
2060) make it happen? How quickly or often does the bug show up? 
2061) Can you check if it happens with other versions of Tor, for 
2062) example the latest stable release? 
2063) </p>
2064) <p>
2065) Fifth, what sort of crash do you get? 
2066) </p>
2067) <ul>
2068) <li>
2069) Does your Tor log include an "assert failure"? If so, please 
2070) tell us that line, since it helps us figure out what's going on. 
2071) Tell us the previous couple of log messages as well, especially 
2072) if they seem important. 
2073) </li>
2074) <li>
2075) If it says "Segmentation fault - core dumped" then you need to 
2076) do a bit more to track it down. Look for a file like "core" or 
2077) "tor.core" or "core.12345" in your current directory, or in your 
2078) Data Directory. If it's there, run "gdb tor core" and then "bt", 
2079) and include the output. If you can't find a core, run "ulimit -c 
2080) unlimited", restart Tor, and try to make it crash again. (This core 
2081) thing will only work on Unix -- alas, tracking down bugs on Windows 
2082) is harder. If you're on Windows, can you get somebody to duplicate 
2083) your bug on Unix?)
2084) </li>
2085) <li>
2086) If Tor simply vanishes mysteriously, it probably is a segmentation 
2087) fault but you're running Tor in the background (as a daemon) so you 
2088) won't notice. Go look at the end of your log file, and look for a 
2089) core file as above. If you don't find any good hints, you should 
2090) consider running Tor in the foreground (from a shell) so you can 
2091) see how it dies. Warning: if you switch to running Tor in the foreground, 
2092) you might start using a different torrc file, with a different default 
2093) Data Directory; see the <a href="#UpgradeOrMove">relay-upgrade FAQ entry</a> 
2094) for details. 
2095) </li>
2096) <li>
2097) If it's still vanishing mysteriously, perhaps something else is killing it? 
2098) Do you have resource limits (ulimits) configured that kill off processes 
2099) sometimes? (This is especially common on OpenBSD.) On Linux, try running 
2100) "dmesg" to see if the out-of-memory killer removed your process. (Tor will 
2101) exit cleanly if it notices that it's run out of memory, but in some cases 
2102) it might not have time to notice.) In very rare circumstances, hardware 
2103) problems could also be the culprit. 
2104) </li>
2105) </ul>
2106) <p>
2107) Sixth, if the above ideas don't point out the bug, consider increasing your 
2108) log level to "loglevel debug". You can look at the log-configuration FAQ 
2109) entry for instructions on what to put in your torrc file. If it usually 
2110) takes a long time for the crash to show up, you will want to reserve a whole 
2111) lot of disk space for the debug log. Alternatively, you could just send 
2112) debug-level logs to the screen (it's called "stdout" in the torrc), and then 
2113) when it crashes you'll see the last couple of log lines it had printed. 
2114) (Note that running with verbose logging like this will slow Tor down 
2115) considerably, and note also that it's generally not a good idea security-wise 
2116) to keep logs like this sitting around.) 
2117) </p>
2118) 
2119) <hr />
2120) 

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

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

2124) 
2125) <p>
2126) Vidalia interacts with the Tor software via Tor's "control port". The
2127) control port lets Vidalia receive status updates from Tor, request a new
2128) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
2129) Vidalia sets a random password for Tor's control port to prevent other
2130) applications from also connecting to the control port and potentially
2131) compromising your anonymity.
2132) </p>
2133) 
2134) <p>
2135) Usually this process of generating and setting a random control password
2136) happens in the background. There are three common situations, though,
2137) where Vidalia may prompt you for a password:
2138) </p>
2139) 
2140) <ol>
2141) <li>You're already running Vidalia and Tor. For example, this situation
2142) can happen if you installed the Vidalia bundle and now you're trying to
2143) run the Tor Browser Bundle. In that case, you'll need to close the old
2144) Vidalia and Tor before you can run this one.
2145) </li>
2146) <li>Vidalia crashed, but left Tor running with the last known random
2147) password. After you restart Vidalia, it generates a new random password,

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

2150) <br />

2151) If the dialog that prompts you for a control password has a Reset
2152) button,

2153) you can click the button and Vidalia will restart Tor with a new random
2154) control password.
2155) <br />
2156) If you do not see a Reset button, or if Vidalia is unable to restart
2157) Tor for you, you can still fix the problem manually. Simply go into your
2158) process or task manager, and terminate the Tor process. Then use Vidalia
2159) to restart Tor and all will work again.
2160) </li>
2161) <li>You had previously set Tor to run as a Windows NT service. When Tor
2162) is set to
2163) run as a service, it starts up when the system boots. If you configured
2164) Tor to start as a service through Vidalia, a random password was set
2165) and saved in Tor. When you reboot, Tor starts up and uses the random
2166) password it saved. You login and start up Vidalia. Vidalia attempts to
2167) talk to the already running Tor. Vidalia generates a random password,
2168) but it is different than the saved password in the Tor service.
2169) <br />
2170) You need to reconfigure Tor to not be a service. See the FAQ entry on

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

2172) Windows NT service</a>

2173) for more information on how to remove the Tor service.
2174) </li>
2175) </ol>
2176) 

2177)     <hr>

2178) 

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

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

2182) 

2183)     <p>

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

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

2188)     </p>
2189)     <dl>
2190)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>

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

2193)         </dd>
2194)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

2197)         </dd>
2198)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

2200)         </dd>
2201)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

2203)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in
2204) this list.

2205)         </dd>
2206)     </dl>
2207)     <p>

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

2209)     — they are intended for testing and may disappear in future
2210) versions.

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

2214)     </p>
2215)     <p>

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

2223)     </p>
2224)     <p>

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

2226) 
2227) href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2"
2228) >2

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

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

2233)     </p>
2234)     <p>

2235)     If you want to access a service directly through Tor's Socks
2236) interface

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

2238)     internal mapping in your configuration file using
2239) <tt>MapAddress</tt>.

2240)     See the manual page for details.
2241)     </p>

2242) 

2243)     <hr>

2244) 

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

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

2248) 
2249) <p>
2250) If your firewall works by blocking ports, then you can tell Tor to only

2251) use the ports that your firewall permits by adding "FascistFirewall 1"
2252) to

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

2254) configuration file</a>, or by clicking "My firewall only lets me connect
2255) to certain ports" in Vidalia's Network Settings window.
2256) </p>
2257) 
2258) <p>
2259) By default, when you set this Tor assumes that your firewall allows only
2260) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
2261) different set of ports with the FirewallPorts torrc option.
2262) </p>
2263) 
2264) <p>
2265) If you want to be more fine-grained with your controls, you can also
2266) use the ReachableAddresses config options, e.g.:
2267) </p>
2268) 
2269) <pre>
2270)   ReachableDirAddresses *:80
2271)   ReachableORAddresses *:443
2272) </pre>
2273) 
2274) <hr>

2275) 

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

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

2279)     <p>

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

2284)     </p>
2285)     <pre>
2286)   reject 0.0.0.0/8
2287)   reject 169.254.0.0/16
2288)   reject 127.0.0.0/8
2289)   reject 192.168.0.0/16
2290)   reject 10.0.0.0/8
2291)   reject 172.16.0.0/12
2292)   reject *:25
2293)   reject *:119
2294)   reject *:135-139
2295)   reject *:445
2296)   reject *:563
2297)   reject *:1214
2298)   reject *:4661-4666
2299)   reject *:6346-6429
2300)   reject *:6699
2301)   reject *:6881-6999
2302)   accept *:*
2303)     </pre>
2304)     <p>

2305)     A relay will block access to its own IP address, as well local network 
2306)     IP addresses. A relay always blocks itself by default. This prevents 
2307)     Tor users from accidentally accessing any of the exit operator's local 
2308)     services. 
2309)     </p>
2310) 
2311)     <hr>
2312) 

2313)     <a id="WarningsAboutSOCKSandDNSInformationLeaks"></a>
2314)     <h3><a class="anchor" href="#WarningsAboutSOCKSandDNSInformationLeaks">I 
2315)     keep seeing these warnings about SOCKS and DNS information leaks. 
2316)     Should I worry?</a></h3>
2317)     <p>
2318)     The warning is: 
2319)     </p>
2320)     <p>
2321)     Your application (using socks5 on port %d) is giving Tor only an IP 
2322)     address. Applications that do DNS resolves themselves may leak 
2323)     information. Consider using Socks4A (e.g. via Polipo or socat) instead. 
2324)     </p>
2325)     <p>
2326)     If you are running Tor to get anonymity, and you are worried about an 
2327)     attacker who is even slightly clever, then yes, you should worry. Here's why. 
2328)     </p>
2329)     <p>
2330)     <b>The Problem.</b> When your applications connect to servers on the 
2331)     Internet, they need to resolve hostnames that you can read (like 
2332)     www.torproject.org) into IP addresses that the Internet can use (like 
2333)     209.237.230.66). To do this, your application sends a request to a DNS 
2334)     server, telling it the hostname it wants to resolve. The DNS server 
2335)     replies by telling your application the IP address. 
2336)     </p>
2337)     <p>
2338)     Clearly, this is a bad idea if you plan to connect to the remote host 
2339)     anonymously: when your application sends the request to the DNS server, 
2340)     the DNS server (and anybody else who might be watching) can see what 
2341)     hostname you are asking for. Even if your application then uses Tor to 
2342)     connect to the IP anonymously, it will be pretty obvious that the user 
2343)     making the anonymous connection is probably the same person who made 
2344)     the DNS request. 
2345)     </p>
2346)     <p>
2347)     <b>Where SOCKS comes in.</b> Your application uses the SOCKS protocol 
2348)     to connect to your local Tor client. There are 3 versions of SOCKS you 
2349)     are likely to run into: SOCKS 4 (which only uses IP addresses), SOCKS 5 
2350)     (which usually uses IP addresses in practice), and SOCKS 4a (which uses 
2351)     hostnames). 
2352)     </p>
2353)     <p>
2354)     When your application uses SOCKS 4 or SOCKS 5 to give Tor an IP address, 
2355)     Tor guesses that it 'probably' got the IP address non-anonymously from a 
2356)     DNS server. That's why it gives you a warning message: you probably aren't 
2357)     as anonymous as you think. 
2358)     </p>
2359)     <p>
2360)     <b>So what can I do?</b> We describe a few solutions below. 
2361)     </p>
2362)     <ul>
2363)     <li>If your application speaks SOCKS 4a, use it. </li>
2364)     <li>If you only need one or two hosts, or you are good at programming, 
2365)     you may be able to get a socks-based port-forwarder like socat to work 
2366)     for you; see <a 
2367)     href="https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO">the 
2368)     Torify HOWTO</a> for examples. </li>
2369)     <li>Tor ships with a program called tor-resolve that can use the Tor 
2370)     network to look up hostnames remotely; if you resolve hostnames to IPs 
2371)     with tor-resolve, then pass the IPs to your applications, you'll be fine. 
2372)     (Tor will still give the warning, but now you know what it means.) </li>
2373) <!-- I'm not sure if this project is still maintained or not
2374) 
2375) <li>You can use TorDNS as a local DNS server to rectify the DNS leakage. See the Torify HOWTO for info on how to run particular applications anonymously. </li>
2376) !-->
2377)     </ul>
2378)     <p>If you think that you applied one of the solutions properly but still 
2379)     experience DNS leaks please verify there is no third-party application 
2380)     using DNS independently of Tor. Please see <a 
2381)     href="#AmITotallyAnonymous">the FAQ entry on whether you're really 
2382)     absolutely anonymous using Tor</a> for some examples. 
2383)     </p>
2384) 
2385)     <hr>
2386) 

2387)     <a id="SocksAndDNS"></a>
2388)     <h3><a class="anchor" href="#SocksAndDNS">How do I check if my application that uses 
2389)     SOCKS is leaking DNS requests?</a></h3>
2390) 
2391)     <p>
2392)     These are two steps you need to take here. The first is to make sure 
2393)     that it's using the correct variant of the SOCKS protocol, and the 
2394)     second is to make sure that there aren't other leaks. 
2395)     </p>
2396) 
2397)     <p>
2398)     Step one: add "TestSocks 1" to your torrc file, and then watch your 
2399)     logs as you use your application. Tor will then log, for each SOCKS 
2400)     connection, whether it was using a 'good' variant or a 'bad' one. 
2401)     (If you want to automatically disable all 'bad' variants, set 
2402)     "SafeSocks 1" in your <a href="#torrc">torrc</a> file.) 
2403)     </p>
2404) 
2405)     <p>
2406)     Step two: even if your application is using the correct variant of 
2407)     the SOCKS protocol, there is still a risk that it could be leaking 
2408)     DNS queries. This problem happens in Firefox extensions that resolve 
2409)     the destination hostname themselves, for example to show you its IP 
2410)     address, what country it's in, etc. These applications may use a safe 
2411)     SOCKS variant when actually making connections, but they still do DNS 
2412)     resolves locally. If you suspect your application might behave like 
2413)     this, you should use a network sniffer like <a 
2414)     href="https://www.wireshark.org/">Wireshark</a> and look for 
2415)     suspicious outbound DNS requests. I'm afraid the details of how to look 
2416)     for these problems are beyond the scope of a FAQ entry though -- find 
2417)     a friend to help if you have problems. 

2418)     </p>
2419) 
2420)     <hr>
2421) 

2422)     <a id="RunningATorRelay"></a>
2423)     <h2><a class="anchor">Running a Tor relay:</a></h2>
2424) 

2425)     <a id="HowDoIDecide"></a>
2426)     <h3><a class="anchor" href="#HowDoIDecide">How do I decide if I should 
2427)     run a relay?</a></h3>
2428)     <p>
2429)     We're looking for people with reasonably reliable Internet connections, 
2430)     that have at least 20 kilobytes/second each way. If that's you, please 
2431)     consider <a href="https://www.torproject.org/docs/tor-relay-debian">helping 
2432)     out</a>. 
2433)     </p>
2434)     
2435)     <hr>
2436)     
2437)     <a id="WhyIsntMyRelayBeingUsedMore"></a>
2438)     <h3><a class="anchor" href="#WhyIsntMyRelayBeingUsedMore">Why isn't my 
2439)     relay being used more?</a></h3>
2440)     <p>
2441)     If your relay is relatively new then give it time. Tor decides which 
2442)     relays it uses heuristically based on reports from Bandwidth 
2443)     Authorities. These authorities take measurements of your relay's 
2444)     capacity and, over time, directs more traffic there until it reaches 
2445)     an optimal load. The lifecycle of a new relay is explained in more 
2446)     depth in <a href="https://blog.torproject.org/blog/lifecycle-of-a-new-relay">
2447)     this blog post</a>.
2448)     </p>
2449)     <p>
2450)     If you've been running a relay for a while and still having issues 
2451)     then try asking on the <a href=
2452)     "https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays/">
2453)     tor-relays list</a>. 
2454)     </p>
2455)     
2456)     <hr>
2457) 

2458)     <a id="IDontHaveAStaticIP"></a>
2459)     <h3><a class="anchor" href="#IDontHaveAStaticIP">I don't have a static 
2460)     IP.</a></h3>
2461) 
2462)     <p>
2463)     Tor can handle relays with dynamic IP addresses just fine. Just leave 
2464)     the "Address" line in your torrc blank, and Tor will guess. 
2465)     </p>
2466) 
2467)     <hr>
2468) 
2469)     <a id="PortscannedMore"></a>
2470)     <h3><a class="anchor" href="#PortscannedMore">Why do I get portscanned 
2471)     more often when I run a Tor relay?</a></h3>
2472) 
2473)     <p>
2474)     If you allow exit connections, some services that people connect to 
2475)     from your relay will connect back to collect more information about you. 
2476)     For example, some IRC servers connect back to your identd port to record 
2477)     which user made the connection. (This doesn't really work for them, 
2478)     because Tor doesn't know this information, but they try anyway.) Also, 
2479)     users exiting from you might attract the attention of other users on the 
2480)     IRC server, website, etc. who want to know more about the host they're 
2481)     relaying through. 
2482)     </p>
2483)     <p>
2484)     Another reason is that groups who scan for open proxies on the Internet 
2485)     have learned that sometimes Tor relays expose their socks port to the 
2486)     world. We recommend that you bind your socksport to local networks only. 
2487)     </p>
2488)     <p>
2489)     In any case, you need to keep up to date with your security. See this <a 
2490)     href="https://trac.torproject.org/projects/tor/wiki/doc/OperationalSecurity">article 
2491)     on operational security for Tor relays</a> for more suggestions. 
2492)     </p>
2493) 
2494)     <hr>
2495) 
2496)     <a id="MoreThanOneCPU"></a>
2497)     <h3><a class="anchor" href="#MoreThanOneCPU">I have more than one CPU. 
2498)     Does this help?</a></h3>
2499) 
2500)     <p>
2501)     Yes. You can set your NumCpus config option in torrc to the number of 
2502)     CPUs you have, and Tor will spawn this many cpuworkers to deal with 
2503)     public key operations in parallel. 
2504)     </p>
2505) 
2506)     <p>
2507)     This option has no effect for clients. 
2508)     </p>
2509) 
2510)     <hr>
2511) 

2512)     <a id="HighCapacityConnection"></a>    
2513)     <h3><a class="anchor" href="#HighCapacityConnection">How can I get Tor to fully 
2514)     make use of my high capacity connection?</a></h3>
2515)     
2516)     <p>
2517)     See <a href="http://archives.seul.org/or/relays/Aug-2010/msg00034.html">this 
2518)     tor-relays thread</a>.
2519)     </p>
2520)     
2521)     <hr>    
2522)     

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

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

2526) 

2527)     <p>
2528)     We aim to make setting up a Tor relay easy and convenient:
2529)     </p>

2530) 

2531)     <ul>
2532)     <li>Tor has built-in support for <a

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

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

2537) 

2538) href="#LimitTotalBandwidth">

2539) hibernation

2540)     feature</a>.
2541)     </li>

2542)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a>
2543) that
2544)     specifies what sort of outbound connections are allowed or refused
2545) from
2546)     that relay. If you are uncomfortable allowing people to exit from
2547) your
2548)     relay, you can set it up to only allow connections to other Tor
2549) relays.

2550)     </li>
2551)     <li>It's fine if the relay goes offline sometimes. The directories
2552)     notice this quickly and stop advertising the relay. Just try to make
2553)     sure it's not too often, since connections using the relay when it
2554)     disconnects will break.
2555)     </li>
2556)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
2557)     leave the Address config option blank, and Tor will try to guess.
2558)     </li>
2559)     <li>If your relay is behind a NAT and it doesn't know its public
2560)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

2561)     forwarding. Forwarding TCP connections is system dependent but

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

2563)     offers some examples on how to do this.
2564)     </li>
2565)     <li>Your relay will passively estimate and advertise its recent

2566)     bandwidth capacity, so high-bandwidth relays will attract more users
2567) than
2568)     low-bandwidth ones. Therefore having low-bandwidth relays is useful
2569) too.

2570)     </li>
2571)     </ul>

2572) 

2573)     <hr>

2574)     
2575)     <a id="BandwidthShaping"></a>
2576)     <h3><a class="anchor" href="#BandwidthShaping">What bandwidth shaping 
2577)     options are available to Tor relays?</a></h3>
2578) 
2579)     <p>
2580)     There are two options you can add to your torrc file: 
2581)     </p>
2582)     <ul>
2583)     <li>
2584)     BandwidthRate is the maximum long-term bandwidth allowed (bytes per 
2585)     second). For example, you might want to choose "BandwidthRate 2 MB" 
2586)     for 2 megabytes per second (a fast connection), or "BandwidthRate 50 
2587)     KB" for 50 kilobytes per second (a medium-speed cable connection). 
2588)     The minimum BandwidthRate is 20 kilobytes per second. 
2589)     </li>
2590)     <li>
2591)     BandwidthBurst is a pool of bytes used to fulfill requests during 
2592)     short periods of traffic above BandwidthRate but still keeps the 
2593)     average over a long period to BandwidthRate. A low Rate but a high 
2594)     Burst enforces a long-term average while still allowing more traffic 
2595)     during peak times if the average hasn't been reached lately. For example, 
2596)     if you choose "BandwidthBurst 50 KB" and also use that for your 
2597)     BandwidthRate, then you will never use more than 50 kilobytes per second; 
2598)     but if you choose a higher BandwidthBurst (like 1 MB), it will allow 
2599)     more bytes through until the pool is empty.
2600)     </li>
2601)     </ul>
2602)     <p>
2603)     If you have an asymmetric connection (upload less than download) such 
2604)     as a cable modem, you should set BandwidthRate to less than your smaller 
2605)     bandwidth (Usually that's the upload bandwidth). (Otherwise, you could 
2606)     drop many packets during periods of maximum bandwidth usage -- you may 
2607)     need to experiment with which values make your connection comfortable.) 
2608)     Then set BandwidthBurst to the same as BandwidthRate. 
2609)     </p>
2610)     <p>
2611)     Linux-based Tor nodes have another option at their disposal: they can 
2612)     prioritize Tor traffic below other traffic on their machine, so that 

2613)     their own personal traffic is not impacted by Tor load. A <a 

2614)     href="https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/linux-tor-prio.sh">script
2615)     to do this</a> can be found in the Tor source distribution's contrib 
2616)     directory. 
2617)     </p>
2618)     <p>
2619)     Additionally, there are hibernation options where you can tell Tor to 
2620)     only serve a certain amount of bandwidth per time period (such as 100 
2621)     GB per month). These are covered in the <a 
2622)     href="#LimitTotalBandwidth">hibernation entry</a> below. 
2623)     </p>
2624)     <p>
2625)     Note that BandwidthRate and BandwidthBurst are in <b>Bytes,</b>not Bits. 
2626)     </p>
2627) 
2628)     <hr>
2629) 
2630)     <a id="LimitTotalBandwidth"></a>
2631)     <h3><a class="anchor" href="#LimitTotalBandwidth">How can I limit the 
2632)     total amount of bandwidth used by my Tor relay?</a></h3>
2633)     <p>
2634)     The accounting options in the torrc file allow you to specify the maximum 
2635)     amount of bytes your relay uses for a time period. 
2636)     </p>
2637)     <pre>
2638)     AccountingStart day week month [day] HH:MM
2639)     </pre>
2640)     <p>
2641)     This specifies when the accounting should reset. For instance, to setup 
2642)     a total amount of bytes served for a week (that resets every Wednesday 
2643)     at 10:00am), you would use: 
2644)     </p>
2645)     <pre>
2646)     AccountingStart week 3 10:00
2647)     AccountingMax N bytes KB MB GB TB
2648)     </pre>
2649)     <p>
2650)     This specifies the maximum amount of data your relay will send during an 
2651)     accounting period, and the maximum amount of data your relay will receive 
2652)     during an account period. When the accounting period resets (from 
2653)     AccountingStart), then the counters for AccountingMax are reset to 0.
2654)     </p>
2655)     <p>
2656)     Example. Let's say you want to allow 1 GB of traffic every day in each 
2657)     direction and the accounting should reset at noon each day: 
2658)     </p>
2659)     <pre>
2660)     AccountingStart day 12:00
2661)     AccountingMax 1 GB
2662)     </pre>
2663)     <p>
2664)     Note that your relay won't wake up exactly at the beginning of each 
2665)     accounting period. It will keep track of how quickly it used its 
2666)     quota in the last period, and choose a random point in the new interval 
2667)     to wake up. This way we avoid having hundreds of relays working at the 
2668)     beginning of each month but none still up by the end. 
2669)     </p>
2670)     <p>
2671)     If you have only a small amount of bandwidth to donate compared to your 
2672)     connection speed, we recommend you use daily accounting, so you don't 
2673)     end up using your entire monthly quota in the first day. Just divide 
2674)     your monthly amount by 30. You might also consider rate limiting to 
2675)     spread your usefulness over more of the day: if you want to offer X GB 
2676)     in each direction, you could set your BandwidthRate to 20*X. For example, 
2677)     if you have 10 GB to offer each way, you might set your BandwidthRate to 
2678)     200 KB: this way your relay will always be useful for at least half of 
2679)     each day. 
2680)     </p>

2681) 
2682)     <hr>
2683) 
2684)     <a id="RelayWritesMoreThanItReads"></a>

2685)     <h3><a class="anchor" href="#RelayWritesMoreThanItReads">Why does my relay 
2686)     write more bytes onto the network than it reads?</a></h3>

2687) 
2688)     <p>You're right, for the most part a byte into your Tor relay means a 
2689)     byte out, and vice versa. But there are a few exceptions:</p>
2690) 
2691)     <p>If you open your DirPort, then Tor clients will ask you for a copy of 
2692)     the directory. The request they make (an HTTP GET) is quite small, and the 
2693)     response is sometimes quite large. This probably accounts for most of the 
2694)     difference between your "write" byte count and your "read" byte count.</p>
2695) 
2696)     <p>Another minor exception shows up when you operate as an exit node, and 
2697)     you read a few bytes from an exit connection (for example, an instant 
2698)     messaging or ssh connection) and wrap it up into an entire 512 byte cell 
2699)     for transport through the Tor network.</p>
2700) 
2701)     <hr>
2702) 
2703)     <a id="Hibernation"></a>
2704)     <h3><a class="anchor" href="#Hibernation">Why can I not browse anymore 

2705)     after limiting bandwidth on my Tor relay?</a></h3>

2706) 
2707)     <p>The parameters assigned in the <a 
2708)     href="#LimitTotalBandwidth">AccountingMax</a> and <a 
2709)     href="#BandwidthShaping">BandwidthRate</a> apply to both client and 
2710)     relay functions of the Tor process. Thus you may find that you are unable 
2711)     to browse as soon as your Tor goes into hibernation, signaled by this 
2712)     entry in the log:</p>
2713) 
2714)     <pre>Bandwidth soft limit reached; commencing hibernation. No new 
2715)     connections will be accepted</pre>
2716) 
2717)     <p>The solution is to run two Tor processes - one relay and one client, 
2718)     each with its own config. One way to do this (if you are starting from a 
2719)     working relay setup) is as follows:</p>
2720) 
2721)     <ul>
2722)         <li>In the relay Tor torrc file, simply set the SocksPort to 0.</li>
2723)         <li>Create a new client torrc file from the torrc.sample and ensure 
2724)         it uses a different log file from the relay. One naming convention 
2725)         may be torrc.client and torrc.relay.</li>
2726)         <li>Modify the Tor client and relay startup scripts to include 
2727)         '-f /path/to/correct/torrc'.</li>
2728)         <li>In Linux/BSD/OSX, changing the startup scripts to Tor.client 
2729)         and Tor.relay may make separation of configs easier.</li>
2730)     </ul>
2731) 

2732)     <hr>

2733) 

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

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

2737) 

2738)     <p>
2739)     Great. That's exactly why we implemented exit policies.
2740)     </p>

2741) 

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

2744)     outbound connections are allowed or refused from that relay. The
2745) exit

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

2750)     based on abuse potential and his own situation. Read the FAQ entry
2751) on
2752)     <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might
2753) encounter</a>

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

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

2756)     for running an exit node with minimal harassment</a>.
2757)     </p>

2758) 

2759)     <p>

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

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

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

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

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

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

2768)     file. If you want to avoid most if not all abuse potential, set it
2769) to
2770)     "reject *:*" (or un-check all the boxes in Vidalia). This setting
2771) means
2772)     that your relay will be used for relaying traffic inside the Tor
2773) network,

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

2776) 

2777)     <p>

2778)     If you do allow any exit connections, make sure name resolution
2779) works

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

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

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

2784)     explicitly reject them in your exit policy — otherwise Tor
2785) users

2786)     will be impacted too.
2787)     </p>

2788) 

2789)     <hr>

2790) 

2791)     <a id="BestOSForRelay"></a>

2792)     <h3><a class="anchor" href="#BestOSForRelay">Why doesn't my Windows (or other OS) Tor relay run well?</h3></a>

2793) 
2794)     <p>
2795)     Tor relays work best on Linux, FreeBSD 5.x+, OS X Tiger or
2796)     later, and Windows Server 2003 or later.
2797)     </p>
2798) 
2799)     <p>You can probably get it working just fine on other operating
2800)     systems too, but note the following caveats:
2801)     </p>
2802) 
2803)     <ul>
2804)     <li>
2805)     Versions of Windows without the word "server" in their name
2806)     sometimes have problems. This is especially the case for Win98,
2807)     but it also happens in some cases for XP, especially if you don't
2808)     have much memory. The problem is that we don't use the networking
2809)     system calls in a very Windows-like way, so we run out of space in
2810)     a fixed-size memory space known as the non-page pool, and then
2811)     everything goes bad. The symptom is an assert error with the
2812)     message "No buffer space available [WSAENOBUFS ] [10055]".  <a
2813)     href="https://trac.torproject.org/projects/tor/wiki/doc/WindowsBufferProblems">You
2814)     can read more here.</a>
2815)     </li>
2816) 
2817)     <li>
2818)     Most developers who contribute to Tor work with Unix-like operating
2819)     systems. It would be great if more people with Windows experience help
2820)     out, so we can improve Tor's usability and stability in
2821)     Windows.
2822)     </li>
2823) 
2824)     <li>
2825)     More esoteric or archaic operating systems, like SunOS 5.9 or
2826)     Irix64, may have problems with some libevent methods (devpoll,
2827)     etc), probably due to bugs in libevent. If you experience crashes,
2828)     try setting the EVENT_NODEVPOLL or equivalent environment
2829)     variable.
2830)     </li>
2831)     </ul>
2832) 
2833)     <hr>
2834) 

2835)     <a id="WhatIsTheBadExitFlag"></a>
2836)     <h3><a class="anchor" href="#WhatIsTheBadExitFlag">What is the 
2837)     BadExit flag?</a></h3>
2838) 
2839)     <p>When an exit is misconfigured or malicious it's assigned the BadExit 
2840)     flag. This tells Tor to avoid exiting through that relay. In effect, 
2841)     relays with this flag become non-exits.</p>
2842) 
2843)     <hr>
2844) 
2845)     <a id="IGotTheBadExitFlagWhyDidThatHappen"></a>
2846)     <h3><a class="anchor" href="#IGotTheBadExitFlagWhyDidThatHappen">I got
2847)     the BadExit flag why did that happen?</a></h3>
2848) 
2849)     <p>If you got this flag then we either discovered a problem or suspicious 
2850)     activity coming from your exit and weren't able to contact you. The reason 
2851)     for most flaggings are documented on the <a 
2852)     href="https://trac.torproject.org/projects/tor/wiki/doc/badRelays">bad 
2853)     relays wiki</a>. Please <a 
2854)     href="https://torproject.org/about/contact.html.en">contact us</a> so 
2855)     we can sort out the issue.</p>
2856) 
2857)     <hr>
2858) 
2859)     <a id="MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf"></a>
2860)     <h3><a class="anchor" href="#MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf">My 
2861)     relay recently got the Guard flag and traffic dropped by half.</a></h3>
2862)     <p>
2863)     Since it's now a guard, clients are using it less in other positions, but 
2864)     not many clients have rotated their existing guards out to use it as a 
2865)     guard yet. Read more details in this <a 
2866)     href="https://blog.torproject.org/blog/lifecycle-of-a-new-relay">blog 
2867)     post</a> or in <a href="http://freehaven.net/anonbib/#wpes12-cogs">Changing 
2868)     of the Guards: A Framework for Understanding and Improving Entry Guard 
2869)     Selection in Tor</a>.
2870)     </p>
2871)     
2872)     <hr>
2873) 
2874)     <a id="TorClientOnADifferentComputerThanMyApplications"></a>
2875)     <h3><a class="anchor" href="#TorClientOnADifferentComputerThanMyApplications">I 
2876)     want to run my Tor client on a different computer than my applications.
2877)     </a></h3>

2878)     <p>

2879)     By default, your Tor client only listens for applications that 
2880)     connect from localhost. Connections from other computers are 
2881)     refused. If you want to torify applications on different computers 
2882)     than the Tor client, you should edit your torrc to define 

2883)     SocksListenAddress 0.0.0.0 and then restart (or hup) Tor. If you 

2884)     want to get more advanced, you can configure your Tor client on a 
2885)     firewall to bind to your internal IP but not your external IP.  

2886)     </p>
2887) 
2888)     <hr>
2889) 
2890)     <a id="ServerClient"></a>

2891)     <h3><a class="anchor" href="#ServerClient">Can I install Tor on a 
2892)     central server, and have my clients connect to it?</a></h3>
2893)     <p>
2894)      Yes. Tor can be configured as a client or a relay on another 
2895)      machine, and allow other machines to be able to connect to it 
2896)      for anonymity. This is most useful in an environment where many 
2897)      computers want a gateway of anonymity to the rest of the world. 
2898)      However, be forwarned that with this configuration, anyone within 
2899)      your private network (existing between you and the Tor 
2900)      client/relay) can see what traffic you are sending in clear text. 
2901)      The anonymity doesn't start until you get to the Tor relay. 
2902)      Because of this, if you are the controller of your domain and you 
2903)      know everything's locked down, you will be OK, but this configuration 
2904)      may not be suitable for large private networks where security is 
2905)      key all around.
2906)     </p>
2907)     <p>
2908) Configuration is simple, editing your torrc file's SocksListenAddress 
2909) according to the following examples:

2910)     </p>
2911)     <pre>

2912) 
2913)   #This provides local interface access only, 
2914)   #needs SocksPort to be greater than 0
2915)   SocksListenAddress 127.0.0.1 
2916) 
2917)   #This provides access to Tor on a specified interface
2918)   SocksListenAddress 192.168.x.x:9100 
2919) 
2920)   #Accept from all interfaces
2921)   SocksListenAddress 0.0.0.0:9100
2922)    </pre>

2923)     <p>

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

2926)     </p>
2927)     <pre>
2928)   SocksListenAddress 192.168.x.x:9100 #eth0
2929)   SocksListenAddress 10.x.x.x:9100 #eth1
2930)     </pre>
2931)     <p>

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

2935)     </p>
2936)     <p>

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

2940)     <p>

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

2944)     </p>
2945) 
2946)     <hr>
2947) 

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

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

2951) 

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

2955)     listed in the public Tor directory.

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

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

2958)     </p>

2959) 

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

2962)     publicly or not.

2963)     </p>

2964) 

2965)     <p>

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

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

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

2970)     </p>

2971) 

2972)     <p>
2973)     Several countries, including China and Iran, have found ways to

2974)     detect and block connections to Tor bridges.

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

2976)     this by adding another layer of obfuscation.

2977)     </p>
2978) 

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

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

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

2987)     </p>

2988) 

2989)     <hr>

2990) 

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

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

2994) 
2995) <p>

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

3000) </p>
3001) <p>

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

3006) </p>
3007) 
3008)     <hr>
3009) 
3010) <a id="NTService"></a>

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

3013) 
3014) <p>

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

3018) </p>
3019) <p>

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

3025) </p>
3026) <p>
3027) To install Tor as a service, you can simply run:
3028) </p>
3029) <pre>
3030) tor --service install
3031) </pre>
3032) <p>

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

3039) </p>
3040) <p>

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

3045) </p>
3046) <pre>
3047) tor --service install -options -f C:\tor\torrc ControlPort 9151
3048) </pre>
3049) <p>
3050) You can also start or stop the Tor service from the command line by typing:
3051) </p>
3052) <pre>
3053)  tor --service start
3054) </pre>
3055) <p>
3056) or
3057) </p>
3058) <pre>
3059)  tor --service stop
3060) </pre>
3061) <p>
3062) To remove the Tor service, you can run the following command:
3063) </p>
3064) <pre>
3065) tor --service remove
3066) </pre>
3067) <p>

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

3072) </p>
3073) 
3074) <hr>
3075) 
3076) <a id="VirtualServer"></a>

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

3079) 
3080) <p>

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

3089) <p>

3090) <table border="1">

3091) <tr>
3092) <td>
3093) <i>resource</i>
3094) </td>
3095) <td>
3096) <i>held</i>
3097) </td>
3098) <td>
3099) <i>maxheld</i>
3100) </td>
3101) <td>
3102) <i>barrier</i>
3103) </td>
3104) <td>
3105) <i>limit</i>
3106) </td>
3107) <td>
3108) <i>failcnt</i>
3109) </td>
3110) </tr>
3111) <tr>
3112) <td>
3113) tcpsndbuf
3114) </td>
3115) <td>
3116) 46620
3117) </td>
3118) <td>
3119) 48840
3120) </td>
3121) <td>
3122) 3440640
3123) </td>
3124) <td>
3125) 5406720
3126) </td>
3127) <td>
3128) 0
3129) </td>
3130) </tr>
3131) <tr>
3132) <td>
3133) tcprcvbuf
3134) </td>
3135) <td>
3136) 0
3137) </td>
3138) <td>
3139) 2220
3140) </td>
3141) <td>
3142) 3440640
3143) </td>
3144) <td>
3145) 5406720
3146) </td>
3147) <td>
3148) 0
3149) </td>
3150) </tr>
3151) <tr>
3152) <td>
3153) othersockbuf
3154) </td>
3155) <td>
3156) 243516
3157) </td>
3158) <td>
3159) 260072
3160) </td>
3161) <td>
3162) 2252160
3163) </td>
3164) <td>
3165) 4194304
3166) </td>
3167) <td>
3168) 0
3169) </td>
3170) </tr>
3171) <tr>
3172) <td>
3173) numothersock
3174) </td>
3175) <td>
3176) 151
3177) </td>
3178) <td>
3179) 153
3180) </td>
3181) <td>
3182) 720
3183) </td>
3184) <td>
3185) 720
3186) </td>
3187) <td>
3188) 0
3189) </td>
3190) </tr>
3191) </table>
3192) <p>
3193)  Xen, Virtual Box and VMware virtual servers have no such limits normally.
3194) </p>
3195) <p>

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

3202) </p>
3203) <p>

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

3208) </p>
3209) <p>

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

3213) </p>
3214) 

3215) <hr>
3216) 

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

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

3220) 
3221) <p>
3222) Great. If you want to run several relays to donate more to the network,
3223) we're happy with that. But please don't run more than a few dozen on
3224) the same network, since part of the goal of the Tor network is dispersal
3225) and diversity.
3226) </p>
3227) 
3228) <p>
3229) If you do decide to run more than one relay, please set the "MyFamily"

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

3232) </p>
3233) 
3234) <pre>
3235)     MyFamily $fingerprint1,$fingerprint2,$fingerprint3
3236) </pre>
3237) 
3238) <p>
3239) where each fingerprint is the 40 character identity fingerprint (without

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

3242) sure to prefix the digest strings with a dollar sign ('$') so that the
3243) digest is not confused with a nickname in the config file.
3244) </p>
3245) 
3246) <p>
3247) That way clients will know to avoid using more than one of your relays
3248) in a single circuit. You should set MyFamily if you have administrative
3249) control of the computers or of their network, even if they're not all in
3250) the same geographic location.
3251) </p>
3252) 
3253)     <hr>
3254) 

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

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

3258)     <p>

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

3262)     </p>
3263)     <p>

3264) If that doesn't fix it, you should use the "Address" config option to 
3265) specify the IP you want it to pick. If your computer is behind a NAT and 
3266) it only has an internal IP address, see the following FAQ entry on <a 

3267) href="#RelayFlexible">dynamic IP addresses</a>.

3268)     </p>
3269)     <p>

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

3273)     </p>
3274) 
3275)     <hr>
3276) 
3277)     <a id="BehindANAT"></a>
3278)     <h3><a class="anchor" href="#BehindANAT">I'm behind a NAT/Firewall.</a></h3>
3279) 
3280)     <p>

3281) See <a>http://portforward.com/</a> for directions on how to port forward with 

3282) your NAT/router device.

3283) </p>
3284) <p>

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