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></p>
18) 

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

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

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

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

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

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

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

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

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

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

37)     <li><a href="#OutboundPorts">Do I have to open all these outbound ports 
38)     on my firewall?</a></li>

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

40)     <li><a href="#NoDataScrubbing">Does Tor remove personal information 
41)     from the data my application sends?</a></li>

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

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

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

46)     </ul>

47) 

48)     <p><a href="#CompilationAndInstallation">Compilation and Installation:</a></p>
49) 

50)     <ul>
51)     <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
52)     <li><a href="#PGPSigs">What are these "sig" files on the download
53)     page?</a></li>

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

56)     <li><a href="#CompileTorWindows">How do I compile Tor under
57) Windows?</a></li>

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

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

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

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

63)     </ul>

64) 

65)     <p><a href="#TBBGeneral">Tor Browser Bundle (general):</a></p>

66)     <ul>

67) 

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

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

71)     </a></li>

72)     <li><a href="#UbuntuBlackedOut">I'm using Ubuntu, and I can't type 
73)     anything into my browser.</a></li>
74)     <li><a href="#SophosOnMac">I'm using the Sophos anti-virus
75)     software on my Mac, and Tor Browser won't start.</a></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

102)     </ul>
103) 
104)     <p><a href="#TBB3.x">Tor Browser Bundle (3.x series):</a></p>
105) 
106)     <ul>

107)     <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia) 
108)     go?</a></li>
109)     <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
110)     <li><a href="#VerifyDownload">How do I verify the download 
111)     (sha256sums.txt)?</a></li>

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

113)     <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close 
114)     all my open tabs?</a></li>
115)     <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay 
116)     or bridge?</a></li>
117)     <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>

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

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

120)     </ul>
121) 

122)     <p><a href="#AdvancedTorUsage">Advanced Tor usage:</a></p>
123) 

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

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

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

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

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

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

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

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

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

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

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

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

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

146)     </ul>

147) 

148)     <p><a href="#RunningATorRelay">Running a Tor relay:</a></p>

149)     <ul>

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

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

155)     <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li>
156)     <li><a href="#ModemKeepsCrashing">My cable/dsl modem keeps crashing. 
157)     What's going on?</a></li>
158)     <li><a href="#PortscannedMore">Why do I get portscanned more often 
159)     when I run a Tor relay?</a></li>
160)     <li><a href="#MoreThanOneCPU">I have more than one CPU. Does this 
161)     help?</a></li>

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

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

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

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

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

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

176)     <li><a href="#WhatIsTheBadExitFlag">What is the BadExit flag?</a></li>
177)     <li><a href="#IGotTheBadExitFlagWhyDidThatHappen">I got the BadExit flag. 
178)     Why did that happen?</a></li>
179)     <li><a href="#MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf">My 
180)     relay recently got the Guard flag and traffic dropped by half.</a></li>
181)     <li><a href="#TorClientOnADifferentComputerThanMyApplications">I want to run my Tor client on a 

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

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

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

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

193)     <li><a href="#NTService">How do I run my Tor relay as an NT service?
194)     </a></li>
195)     <li><a href="#VirtualServer">Can I run a Tor relay from my virtual server 
196)     account?</a></li>

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

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

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

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

207)     </ul>

208) 

209)     <p><a href="#TorHiddenServices">Tor hidden services:</a></p>
210) 

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

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

214)     </ul>

215) 

216)     <p><a href="#Development">Development:</a></p>
217) 

218)     <ul>
219)     <li><a href="#WhoIsResponsible">Who is responsible for Tor?</a></li>
220)     <li><a href="#VersionNumbers">What do these weird version numbers 
221)     mean?</a></li>
222)     <li><a href="#PrivateTorNetwork">How do I set up my own private
223)     Tor network?</a></li>
224)     <li><a href="#UseTorWithJava">How can I make my Java program use the 
225)     Tor network?</a></li>
226)     <li><a href="#WhatIsLibevent">What is Libevent?</a></li>
227)     <li><a href="#MyNewFeature">What do I need to do to get a new feature 
228)     into Tor?</a></li>
229)     </ul>
230) 

231)     <p><a href="#AnonymityAndSecurity">Anonymity and Security:</a></p>

232)     <ul>

233)     <li><a href="#WhatProtectionsDoesTorProvide">What protections does Tor 
234)     provide?</a></li>
235)     <li><a href="#CanExitNodesEavesdrop">Can exit nodes eavesdrop on 
236)     communications? Isn't that bad? </a></li>

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

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

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

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

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

244)     <li><a href="#CellSize">Tor uses hundreds of bytes for every IRC line. I 
245)     can't afford that!</a></li>
246)     <li><a href="#OutboundConnections">Why does netstat show these outbound 
247)     connections?</a></li>
248)     <li><a href="#PowerfulBlockers">What about powerful blocking mechanisms
249)     </a></li>
250)     <li><a href="#RemotePhysicalDeviceFingerprinting">Does Tor resist 
251)     "remote physical device fingerprinting"?</a></li>

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

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

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

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

259)     </ul>

260) 

261)     <p><a href="#AlternateDesigns">Alternate designs that we don't do (yet):</a></p>
262) 

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

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

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

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

271)     <li><a href="#ChoosePathLength">You should let people choose their path 
272)     length.</a></li>
273)     <li><a href="#SplitEachConnection">You should split each connection over 
274)     many paths.</a></li>

275)     <li><a href="#MigrateApplicationStreamsAcrossCircuits">You should migrate 
276)     application streams across circuits.</a></li>
277)     <li><a href="#LetTheNetworkPickThePath">You should let the network pick 
278)     the path, not the client.</a></li>

279)     <li><a href="#UnallocatedNetBlocks">Your default exit policy should block 
280)     unallocated net blocks too.</a></li>
281)     <li><a href="#BlockWebsites">Exit policies should be able to block 
282)     websites, not just IP addresses.</a></li>
283)     <li><a href="#BlockContent">You should change Tor to prevent users from 
284)     posting certain content.</a></li>

285)     <li><a href="#SendPadding">You should send padding so it's more secure.
286)     </a></li>
287)     <li><a href="#Steganography">You should use steganography to hide Tor 
288)     traffic.</a></li>

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

290)     </ul>

291) 

292)     <p><a href="#Abuse">Abuse:</a></p>

293)     <ul>

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

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

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

300)     </ul>

301) 

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

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

305) 

306)     <hr>

307) 

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

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

310) 

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

313) 

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

317) 

318)     <p>

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

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

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

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

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

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

333) 

334)     <p>

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

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

339) 

340)     <hr>

341) 

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

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

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

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

375) inside your

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

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

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

381) stream, and recording your personal details.

382)     </p>
383)     <p>

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

400) packets between themselves.</p>

401)     <p>
402)     <dl>

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

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

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

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

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

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

425)     </dl>
426)     </p>

427) 

428)     <hr>

429) 

430) 

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

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

434) 

435)     <p>

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

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

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

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

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

447)     specific applications</a>.

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

450) 

451)     <hr>

452) 

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

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

456) 

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

466) 

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

470) 

471)     <p>

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

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

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

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

481) 

482)     <hr>

483) 

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

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

487) 

488)     <p>

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

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

496) 

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

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

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

505) 

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

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

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

519) 

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

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

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

526) 

527)     <hr>

528) 

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

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

532) 

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

536) 

537)     <p>

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

544)     ask us for specific permission.
545)     </p>

546) 

547)     <p>

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

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

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

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

555) 

556)     <p>

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

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

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

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

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

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

572)     </p>

573) 

574)     <p>

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

581)     </p>

582) 

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

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

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

592) 

593)     <hr>

594) 

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

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

598) 

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

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

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

604)     <li>Read through the <a

605) 
606) href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">
607) tor-talk

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

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

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

612)     <li>Send an email to <a

613) 
614) href="mailto:help@rt.torproject.org">help@rt.torproject.org</a>.</li>
615)     <li>If all else fails, try <a href="<page about/contact>">contacting
616) us</a> directly.</li>

617)     </ol>

618) 

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

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

622) 

623)     <hr>

624) 

625)     <a id="Forum"></a>
626)     <h3><a class="anchor" href="#Forum">Is there a Tor forum?</a></h3>
627) 

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

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

630)     </p>
631) 
632)     <hr>
633) 

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

636) 

637)     <p>
638)     There are many reasons why the Tor network is currently slow.
639)     </p>

640) 

641)     <p>

642)     Before we answer, though, you should realize that Tor is never going
643) to
644)     be blazing fast. Your traffic is bouncing through volunteers'
645) computers
646)     in various parts of the world, and some bottlenecks and network
647) latency

648)     will always be present. You shouldn't expect to see university-style
649)     bandwidth through Tor.
650)     </p>

651) 

652)     <p>

653)     But that doesn't mean that it can't be improved. The current Tor
654) network
655)     is quite small compared to the number of people trying to use it,
656) and
657)     many of these users don't understand or care that Tor can't
658) currently

659)     handle file-sharing traffic load.
660)     </p>

661) 

662)     <p>
663)     For the much more in-depth answer, see <a

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

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

667)     to go with it.
668)     </p>

669) 

670)     <p>
671)     What can you do to help?
672)     </p>

673) 

674)     <ul>

675) 

676)     <li>

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

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

683) 

684)     <li>

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

687)     especially need people to help make it easier to configure your Tor
688)     as a relay. Also, we need help with clear simple documentation to
689)     walk people through setting it up.
690)     </li>

691) 

692)     <li>

693)     There are some bottlenecks in the current Tor network. Help us
694) design
695)     experiments to track down and demonstrate where the problems are,
696) and

697)     then we can focus better on fixing them.
698)     </li>

699) 

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

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

706)     get to spend more time on it.
707)     </li>

708) 

709)     <li>

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

714)     getinvolved/volunteer>">look at our volunteer page</a>.
715)     </li>

716) 

717)     <li>

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

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

721)     competition's websites discreetly, or to connect back to the home
722) servers
723)     when on the road without revealing affiliations? If your
724) organization has
725)     an interest in keeping the Tor network working, please contact them
726) about
727)     supporting Tor. Without sponsors, Tor is going to become even
728) slower.

729)     </li>

730) 

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

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

735)     cause</a>. It adds up!
736)     </li>

737) 

738)     </ul>

739) 

740)     <hr>

741) 

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

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

745) 
746)     <p>

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

753)     </p>
754) 
755)     <hr>
756) 

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

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

760) 

761)     <p>

762)     The Tor network's <a

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

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

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

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

772)     </p>

773) 

774)     <p>

775)     There are six main development/maintenance pushes that need
776) attention:

777)     </p>

778) 

779)     <ul>

780) 

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

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

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

788) 

789)     <li>

790)     User support: With this many users, a lot of people are asking
791) questions
792)     all the time, offering to help out with things, and so on. We need
793) good
794)     clean docs, and we need to spend some effort coordinating
795) volunteers.

796)     </li>

797) 

798)     <li>

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

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

802)     reminders to upgrade, and so on. The network itself is a commons,
803) and
804)     somebody needs to spend some energy making sure the relay operators
805) stay
806)     happy. We also need to work on stability on some platforms —
807) e.g.,

808)     Tor relays have problems on Win XP currently.

809)     </li>

810) 

811)     <li>

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

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

824) 

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

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

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

832) 

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

838)     critical <a href="<page getinvolved/volunteer>#Research">Tor
839) research questions</a>
840)     that will help us figure out how to make Tor secure against the
841) variety of
842)     attacks out there. Of course, there are more research questions
843) waiting

844)     behind these.
845)     </li>

846) 

847)     </ul>

848) 

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

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

853)     can keep up</a>.

854)     Now would be an excellent time to add a few more developers to the
855) effort

856)     so we can continue to grow the network.
857)     </p>

858) 

859)     <p>
860)     We are also excited about tackling related problems, such as
861)     censorship-resistance.
862)     </p>

863) 

864)     <p>

865)     We are proud to have <a href="<page about/sponsors>">sponsorship and
866) support</a>
867)     from the Omidyar Network, the International Broadcasting Bureau,
868) Bell
869)     Security Solutions, the Electronic Frontier Foundation, several
870) government

871)     agencies and research groups, and hundreds of private contributors.
872)     </p>

873) 

874)     <p>

875)     However, this support is not enough to keep Tor abreast of changes
876) in the
877)     Internet privacy landscape. Please <a href="<page
878) donate/donate>">donate</a>
879)     to the project, or <a href="<page about/contact>">contact</a> our
880) executive

881)     director for information on making grants or major donations.
882)     </p>

883) 

884)     <hr>
885) 

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

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

889) 
890)     <p>

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

895)     </p>
896)     <p>

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

904)     </p>
905)     <p>

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

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

908)     </p>
909)     <p>

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

915)     </p>
916)     
917)     <hr>
918)     
919)     <a id="IsItWorking"></a>

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

922) 
923)     <p>

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

927)     </p>
928)     <p>

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

935)     </p>
936)     <p>

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

940)     </p>
941)     <p>

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

948)     </p>
949)     
950)     <hr>
951)     
952)     <a id="FTP"></a>
953)     <h3><a class="anchor" href="#FTP">How do I use my browser for ftp with Tor?
954)     </a></h3>
955) 

956)     <p>

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

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

963) 

964)     <hr>
965)     

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

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

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

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

984) 

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

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

988)     <hr>

989) 

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

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

993)     <p>

994)     <pre>

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

996)     The serial number is:

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

999)     The SHA-256 fingerprint is:

1000) 3613d2b22a750094760c41ad19db52a4f05bdea80172e2578761ad967f7ed9aa

1001) 

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

1003)     The serial number is: 00:EF:A3
1004)     The SHA-1 fingerprint is: 50af43db8438e67f305a3257d8ef198e8c42f13f

1005)     </pre>

1006)     </p>
1007)     <hr>
1008) 

1009)     <a id="CompilationAndInstallation"></a>
1010)     <h2><a class="anchor">Compilation And Installation:</a></h2>
1011) 

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

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

1021) 

1022)     <p>

1023)     If this is not related to Tor Browser, uninstallation depends
1024) entirely on how you installed it and which operating system you
1025)     have. If you installed a package, then hopefully your package has a
1026) way to

1027)     uninstall itself. The Windows packages include uninstallers. 

1028)     </p>

1029) 

1030)     <p>
1031)     For Mac OS X, follow the <a
1032)     href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
1033)     </p>

1034) 

1035)     <p>

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

1040)     be pretty easy to notice things there.
1041)     </p>

1042) 

1043)     <hr>

1044) 

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

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

1048) 

1049)     <p>

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

1052)     exactly the one that we intended you to get.
1053)     </p>

1054) 

1055)     <p>
1056)     Please read the <a

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

1059)     </p>

1060) 

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

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

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

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

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

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

1078) in the body of the email, it will reply with instructions. Note that
1079) only a few webmail providers are supported, since they need to be able
1080) to receive very large attachments.
1081) </p>
1082) 
1083) <p>

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

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

1088) </p>
1089) 
1090) <hr>

1091) 

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

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

1095) 

1096)     <p>

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

1099)     tor-win32-mingw-creation.txt</a>.
1100)     </p>

1101) 

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

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

1106)     download/download>">download page</a>.)
1107)     </p>

1108) 

1109)     <hr>

1110) 

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

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

1114) 

1115)     <p>

1116)     Sometimes, overzealous Windows virus and spyware detectors trigger
1117) on some
1118)     parts of the Tor Windows binary. Our best guess is that these are
1119) false
1120)     positives — after all, the anti-virus and anti-spyware
1121) business is just a
1122)     guessing game anyway. You should contact your vendor and explain
1123) that you have
1124)     a program that seems to be triggering false positives. Or pick a
1125) better vendor.

1126)     </p>

1127) 

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

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

1132)     href="#CompileTorWindows">recompile it yourself</a>.
1133)     </p>

1134) 

1135)     <hr>

1136) 

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

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

1140) 
1141)     <p>
1142)     Tar is a common archive utility for Unix and Linux systems. If your
1143)     system has a mouse, you can usually open them by double clicking. 
1144)     Otherwise open a command prompt and execute 

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

1146)     <p>

1147)     as documented on tar's man page. 

1148)     </p>
1149) 
1150)     <hr>
1151) 

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

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

1155) 

1156)     <p>

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

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

1160)     Bundle</a>.

1161)     </p>

1162) 
1163) <hr>
1164) 

1165) <a id="TBBGeneral"></a>
1166) <h2><a class="anchor">Tor Browser Bundle (general):</a></h2>
1167) 

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

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

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

1172) 
1173) <p>

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

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

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

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

1187) 
1188) <p>

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

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

1196) 

1197) <hr>
1198) 

1199) <a id="Ubuntu"></a>
1200) <h3><a class="anchor" href="#Ubuntu">

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

1202) <p>

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

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

1207) <p>
1208) from inside the Tor Browser directory.
1209) </p>
1210) 

1211) <hr>
1212) 

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

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

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

1224) <pre>ibus exit</pre>

1225) <p>To follow the progress of this issue, see this <a 
1226) href="https://trac.torproject.org/projects/tor/ticket/9353">bug ticket.</a>
1227) </p>
1228) 
1229) <hr>
1230) 
1231) <a id="SophosOnMac"></a>
1232) <h3><a class="anchor" href="#SophosOnMac">I'm using the Sophos anti-virus
1233) software on my Mac, and Tor Browser won't start.</a></h3>
1234) <p>
1235) You'll need to modify Sophos anti-virus so that Tor can connect to the 
1236) internet. Go to Preferences -> Web Protection -> General, and turn off 
1237) the protections for "Malicious websites" and "Malicious downloads".
1238) </p>
1239) 

1240) <hr>
1241) 

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

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

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

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

1246) 
1247) <p>

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

1249) on port 9150.

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

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

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

1255) </p>
1256) 
1257) <hr>
1258) 
1259) <a id="TBBPolipo"></a>
1260) <h3><a class="anchor" href="#TBBPolipo">I need an HTTP proxy. Where did
1261) Polipo go?</a></h3>
1262) 
1263) <p>
1264) In the past, Tor bundles included an HTTP proxy like Privoxy or Polipo,
1265) solely to work around a bug in Firefox that was finally fixed in Firefox
1266) 6. Now you don't need a separate HTTP proxy to use Tor, and in fact
1267) leaving it out makes you safer because Torbutton has better control over
1268) Firefox's interaction with websites.
1269) </p>
1270) 
1271) <p>
1272) If you are trying to use some external application with Tor, step zero

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

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

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

1276) proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>
1277) for OSX and Linux.
1278) </p>
1279) 
1280) <p>

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

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

1287) </p>
1288) 
1289) <hr>
1290) 

1291) <a id="TBBOtherExtensions"></a>
1292) <h3><a class="anchor" href="#TBBOtherExtensions">Can I install other
1293) Firefox extensions?</a></h3>
1294) 
1295) <p>

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

1301) </p>

1302) <p>

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

1312) </p>

1313) 

1314) <hr>
1315) 

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

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

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

1321) 
1322) <p>
1323) We configure NoScript to allow JavaScript by default in the Tor
1324) Browser Bundle because many websites will not work with JavaScript
1325) disabled.  Most users would give up on Tor entirely if a website
1326) they want to use requires JavaScript, because they would not know
1327) how to allow a website to use JavaScript (or that enabling
1328) JavaScript might make a website work).
1329) </p>
1330) 

1331) <p>
1332) There's a tradeoff here. On the one hand, we should leave
1333) JavaScript enabled by default so websites work the way
1334) users expect. On the other hand, we should disable JavaScript
1335) by default to better protect against browser vulnerabilities (<a

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

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

1344) 
1345) <p>

1346) Ultimately, we want the default Tor bundles to use
1347) a combination of firewalls (like the iptables rules
1348) in <a href="https://tails.boum.org/">Tails</a>) and <a
1349) href="https://trac.torproject.org/projects/tor/ticket/7680">sandboxes</a>
1350) to make JavaScript not so scary. In
1351) the shorter term, TBB 3.0 will hopefully <a
1352) href="https://trac.torproject.org/projects/tor/ticket/9387">allow users
1353) to choose their JavaScript settings more easily</a> &mdash; but the
1354) partitioning concern will remain.

1355) </p>
1356) 
1357) <p>

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

1360) </p>
1361) 
1362) <hr>
1363) 

1364) <a id="TBBOtherBrowser"></a>
1365) <h3><a class="anchor" href="#TBBOtherBrowser">I want to use
1366) Chrome/IE/Opera/etc with Tor.</a></h3>
1367) 
1368) <p>
1369) Unfortunately, Torbutton only works with Firefox right now, and without
1370) <a href="https://www.torproject.org/torbutton/en/design/">Torbutton's
1371) extensive privacy fixes</a> there are many ways for websites or other

1372) attackers to recognize you, track you back to your IP address, and so
1373) on.

1374) In short, using any browser besides Tor Browser Bundle with Tor is a
1375) really bad idea.
1376) </p>
1377) 
1378) <p>
1379) We're working with the Chrome team to <a

1380) href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-
1381) and-fingerprinting">fix
1382) some bugs and missing APIs in Chrome</a> so it will be possible to write
1383) a
1384) Torbutton for Chrome. No support for any other browser is on the
1385) horizon.

1386) </p>
1387) 
1388) <hr>
1389) 

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

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

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

1393) 
1394) <p>

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

1396) </p>
1397) <p>

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

1399) </p>
1400) 

1401) <hr>

1402) 

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

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

1406) Bundle running but close the browser.</a></h3>
1407) 
1408) <p>
1409) We're working on a way to make this possible on all platforms. Please
1410) be patient.
1411) </p>
1412) 
1413) <hr>
1414) 

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

1418) 
1419) <p>
1420) This is a known and intermittent problem; it does not mean that Google
1421) considers Tor to be spyware.
1422) </p>
1423) 
1424) <p>

1425) When you use Tor, you are sending queries through exit relays that are
1426) also

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

1428) when many Tor users are querying Google in a short period of time.
1429) Google

1430) interprets the high volume of traffic from a single IP address (the exit
1431) relay you happened to pick) as somebody trying to "crawl" their website,
1432) so it slows down traffic from that IP address for a short time.
1433) </p>
1434) <p>
1435) An alternate explanation is that Google tries to detect certain
1436) kinds of spyware or viruses that send distinctive queries to Google
1437) Search. It notes the IP addresses from which those queries are received
1438) (not realizing that they are Tor exit relays), and tries to warn any
1439) connections coming from those IP addresses that recent queries indicate
1440) an infection.
1441) </p>
1442) 
1443) <p>

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

1446) to deter or block Tor use. The error message about an infected machine
1447) should clear up again after a short time.
1448) </p>
1449) 
1450) <p>
1451) Torbutton 1.2.5 (released in mid 2010) detects Google captchas and can
1452) automatically redirect you to a more Tor-friendly search engine such as

1453) DuckDuckGo, ixquick, or Bing.

1454) </p>
1455) 
1456) <hr />
1457) 

1458) <a id="ForeignLanguages"></a>
1459) <h3><a class="anchor" href="#ForeignLanguages">
1460) Why does Google show up in foreign languages?</a></h3>
1461) 
1462) <p>

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

1467) </p>
1468) <p>

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

1475) </p>
1476) <p>

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

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

1483) <p>

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

1486) </p>
1487) <hr />

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

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

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

1491) 
1492) <p>
1493) Sometimes, after you've used Gmail over Tor, Google presents a
1494) pop-up notification that your account may have been compromised.
1495) The notification window lists a series of IP addresses and locations
1496) throughout the world recently used to access your account.
1497) </p>
1498) 
1499) <p>
1500) In general this is a false alarm: Google saw a bunch of logins from

1501) different places, as a result of running the service via Tor, and
1502) decided

1503) it was a good idea to confirm the account was being accessed by it's
1504) rightful owner.
1505) </p>
1506) 
1507) <p>
1508) Even though this may be a biproduct of using the service via tor,
1509) that doesn't mean you can entirely ignore the warning. It is
1510) <i>probably</i> a false positive, but it might not be since it is
1511) possible for someone to hijack your Google cookie.
1512) </p>
1513) 
1514) <p>
1515) Cookie hijacking is possible by either physical access to your computer
1516) or by watching your network traffic.  In theory only physical access
1517) should compromise your system because Gmail and similar services
1518) should only send the cookie over an SSL link. In practice, alas, it's <a

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

1521) way more complex than that</a>.
1522) </p>
1523) 
1524) <p>
1525) And if somebody <i>did</i> steal your google cookie, they might end
1526) up logging in from unusual places (though of course they also might
1527) not). So the summary is that since you're using Tor, this security
1528) measure that Google uses isn't so useful for you, because it's full of
1529) false positives. You'll have to use other approaches, like seeing if
1530) anything looks weird on the account, or looking at the timestamps for
1531) recent logins and wondering if you actually logged in at those times.
1532) </p>
1533) 
1534) <hr>
1535) 

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

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

1539) 
1540) <p>
1541) You can set Proxy IP address, port, and authentication information in 
1542) Tor Browser's Network Settings. If you're using Tor another way, check 
1543) out the HTTPProxy and HTTPSProxy config options in the <a 
1544) href="https://www.torproject.org/docs/tor-manual.html.en">man page</a>, 
1545) and modify your torrc file accordingly. You will need an HTTP proxy for 
1546) doing GET requests to fetch the Tor directory, and you will need an 
1547) HTTPS proxy for doing CONNECT requests to get to Tor relays. (It's fine 
1548) if they're the same proxy.) Tor also recognizes the torrc options 
1549) Socks4Proxy and Socks5Proxy. 
1550) </p>
1551) <p>

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

1555) href="http://archives.seul.org/or/talk/Jun-2005/msg00223.html">this post 
1556) in the archives</a> useful. 
1557) </p>
1558) <p>
1559) If your proxies only allow you to connect to certain ports, look at the 
1560) entry on <a href="#FirewallPorts">Firewalled clients</a> for how 
1561) to restrict what ports your Tor will try to access. 
1562) </p>
1563) 
1564) <hr>
1565) 

1566) <a id="CantSetProxy"></a>
1567) <h3><a class="anchor" href="#CantSetProxy">What should I do if I can't 
1568) set a proxy with my application?</a></h3>
1569) 
1570) <p>
1571) On Unix, we recommend you give <a 
1572) href="https://github.com/dgoulet/torsocks/">torsocks</a> a try. 
1573) Alternative proxifying tools like <a 
1574) href="http://www.dest-unreach.org/socat/">socat</a> and <a 
1575) href="http://proxychains.sourceforge.net/">proxychains</a> are also 
1576) available.</p>
1577) <p> 
1578) The Windows way to force applications through Tor is less clear. <a 
1579) href="http://freecap.ru/eng/">Some</a> <a 
1580) href="http://www.freehaven.net/~aphex/torcap/">tools</a> have been <a 
1581) href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1582) </a>, but we'd also like to see further testing done here. 
1583) </p>
1584) 
1585) <hr>
1586) 

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

1589)     <a id="WhereDidVidaliaGo"></a>
1590)     <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map 
1591)     (Vidalia) go?</a></h3>
1592) 
1593)     <p>Vidalia has been replaced with Tor Launcher, which is a Firefox 
1594)     extension that provides similar functionality. Unfortunately, circuit 
1595)     status reporting is still missing, but we are <a 
1596)     href="https://trac.torproject.org/projects/tor/ticket/8641">working 
1597)     on providing it</a>. </p>
1598) 
1599)     <p>In the meantime, we are providing standalone Vidalia packages for 
1600)     people who still want the map. Windows and Linux versions are <a 

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

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

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

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

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

1744) Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2
1745) Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F

1746) Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
1747) Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
1748) Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
1749) Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
1750) Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
1751) Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
1752) Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1753)     </pre>
1754)     <p>
1755)     To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the 

1756)     bundle and add the line: 

1757)     </p>
1758)     <pre>
1759) Bridge flashproxy 0.0.1.0:1
1760)     </pre>
1761) 
1762)     <hr>
1763) 
1764)     <a id="NewIdentityClosingTabs"></a>
1765)     <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New 
1766)     Identity" close all my open tabs?</a></h3>
1767) 
1768)     <p>
1769)     That's actually a feature, since it's discarding your application-level 
1770)     browser data too. But it sure is a surprising feature, for people who 
1771)     are used to Vidalia's "new identity" behavior.
1772)     </p>
1773) 
1774)     <p>

1775)     We're working on ways to make the behavior less surprising, e.g. a popup
1776)     warning or auto restoring tabs. See ticket <a
1777)     href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and
1778)     ticket <a
1779)     href="https://trac.torproject.org/projects/tor/ticket/10400">#10400</a>
1780)     to follow progress there.

1781)     </p>
1782) 
1783)     <p>

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

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

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

1858) 
1859)     <p>
1860)     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>.
1861)     </p>
1862) 
1863) 

1864) <hr>
1865) 

1866) <a id="AdvancedTorUsage"></a>
1867) <h2><a class="anchor">Advanced Tor usage:</a></h2>
1868) 

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

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

1872) 
1873) <p>
1874) Tor installs a text file called torrc that contains configuration
1875) instructions for how your Tor program should behave. The default

1876) configuration should work fine for most Tor users. 

1877) </p>

1878) <p>

1879) If you installed Tor Browser Bundle, look for

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

1884) 
1885) <p>

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

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

1890) </p>
1891) 
1892) <p>

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

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

1899) </p>
1900) 
1901) <hr>
1902) 

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

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

1906) 
1907) <p>

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

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

1912) </p>
1913) 
1914) <p>
1915) If you're not using Vidalia, you'll have to go find the log files by

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

1917) </p>
1918) 
1919) <ul>
1920) <li>On OS X, Debian, Red Hat, etc, the logs are in /var/log/tor/
1921) </li>

1922) <li>On Windows, there are no default log files currently. If you enable
1923) logs in your torrc file, they default to <code>\username\Application
1924) Data\tor\log\</code> or <code>\Application Data\tor\log\</code>
1925) </li>
1926) <li>If you compiled Tor from source, by default your Tor logs to <a
1927) href="http://en.wikipedia.org/wiki/Standard_streams">"stdout"</a>
1928) at log-level notice. If you enable logs in your torrc file, they
1929) default to <code>/usr/local/var/log/tor/</code>.

1930) </li>
1931) </ul>
1932) 
1933) <p>

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

1936) and find the section (near the top of the file) which contains the
1937) following line:

1938) </p>
1939) 
1940) <pre>

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

1943) </pre>

1944) 
1945) <p>

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

1947) and err level messages to a file, append the following line to the end
1948) of the section:
1949) </p>
1950) 
1951) <pre>
1952) Log debug file c:/program files/tor/debug.log
1953) </pre>
1954) 
1955) <p>

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

1958) </p>
1959) 
1960) <hr>
1961) 

1962) 
1963) <a id="LogLevel"></a>
1964) <h3><a class="anchor" href="#LogLevel">What log level should I use?</a></h3>
1965) 
1966) <p>

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

1969) </p>
1970) 
1971) <ul>

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

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

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

1981)     <li>"debug": for everything louder than info. It is quite loud indeed.</li> 
1982) </ul>
1983) 
1984) <p>

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

1988) </p>
1989) 
1990) <p>

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

1993) </p>
1994) 
1995) <p>

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

1999) </p>
2000) 

2001) <hr>
2002) 

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

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

2006) 
2007) <p>

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

2010) </p>
2011) 
2012) <p>If Tor can establish a circuit, the onion icon in

2013) Vidalia will turn green (and if you're running Tor Browser Bundle, it
2014) will
2015) automatically launch a browser for you). You can also check in the
2016) Vidalia

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

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

2020) a line saying that Tor "has successfully opened a circuit. Looks like
2021) client functionality is working."
2022) </p>
2023) 
2024) <p>
2025) If Tor can't establish a circuit, here are some hints:
2026) </p>
2027) 
2028) <ol>
2029) <li>Are you sure Tor is running? If you're using Vidalia, you may have
2030) to click on the onion and select "Start" to launch Tor.</li>
2031) <li>Check your system clock. If it's more than a few hours off, Tor will

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

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

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

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

2039) </li>

2040) <li>Are you running programs like Norton Internet Security or SELinux
2041) that

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

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

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

2049) </ol>
2050) 
2051) <hr />
2052) 

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

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

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

2141) 
2142) <p>
2143) Vidalia interacts with the Tor software via Tor's "control port". The
2144) control port lets Vidalia receive status updates from Tor, request a new
2145) identity, configure Tor's settings, etc. Each time Vidalia starts Tor,
2146) Vidalia sets a random password for Tor's control port to prevent other
2147) applications from also connecting to the control port and potentially
2148) compromising your anonymity.
2149) </p>
2150) 
2151) <p>
2152) Usually this process of generating and setting a random control password
2153) happens in the background. There are three common situations, though,
2154) where Vidalia may prompt you for a password:
2155) </p>
2156) 
2157) <ol>
2158) <li>You're already running Vidalia and Tor. For example, this situation
2159) can happen if you installed the Vidalia bundle and now you're trying to
2160) run the Tor Browser Bundle. In that case, you'll need to close the old
2161) Vidalia and Tor before you can run this one.
2162) </li>
2163) <li>Vidalia crashed, but left Tor running with the last known random
2164) password. After you restart Vidalia, it generates a new random password,

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

2167) <br />

2168) If the dialog that prompts you for a control password has a Reset
2169) button,

2170) you can click the button and Vidalia will restart Tor with a new random
2171) control password.
2172) <br />
2173) If you do not see a Reset button, or if Vidalia is unable to restart
2174) Tor for you, you can still fix the problem manually. Simply go into your
2175) process or task manager, and terminate the Tor process. Then use Vidalia
2176) to restart Tor and all will work again.
2177) </li>
2178) <li>You had previously set Tor to run as a Windows NT service. When Tor
2179) is set to
2180) run as a service, it starts up when the system boots. If you configured
2181) Tor to start as a service through Vidalia, a random password was set
2182) and saved in Tor. When you reboot, Tor starts up and uses the random
2183) password it saved. You login and start up Vidalia. Vidalia attempts to
2184) talk to the already running Tor. Vidalia generates a random password,
2185) but it is different than the saved password in the Tor service.
2186) <br />
2187) You need to reconfigure Tor to not be a service. See the FAQ entry on

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

2189) Windows NT service</a>

2190) for more information on how to remove the Tor service.
2191) </li>
2192) </ol>
2193) 

2194)     <hr>

2195) 

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

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

2199) 

2200)     <p>

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

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

2205)     </p>
2206)     <dl>
2207)       <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>

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

2210)         </dd>
2211)       <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

2214)         </dd>
2215)       <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>

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

2217)         </dd>
2218)       <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>

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

2220)             Nodes listed in <tt>ExcludeNodes</tt> are automatically in
2221) this list.

2222)         </dd>
2223)     </dl>
2224)     <p>

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

2226)     — they are intended for testing and may disappear in future
2227) versions.

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

2231)     </p>
2232)     <p>

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

2240)     </p>
2241)     <p>

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

2243) 
2244) href="https://secure.wikimedia.org/wikipedia/en/wiki/ISO_3166-1_alpha-2"
2245) >2

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

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

2250)     </p>
2251)     <p>

2252)     If you want to access a service directly through Tor's Socks
2253) interface

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

2255)     internal mapping in your configuration file using
2256) <tt>MapAddress</tt>.

2257)     See the manual page for details.
2258)     </p>

2259) 

2260)     <hr>

2261) 

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

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

2265) 
2266) <p>
2267) If your firewall works by blocking ports, then you can tell Tor to only

2268) use the ports that your firewall permits by adding "FascistFirewall 1"
2269) to

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

2271) configuration file</a>, or by clicking "My firewall only lets me connect
2272) to certain ports" in Vidalia's Network Settings window.
2273) </p>
2274) 
2275) <p>
2276) By default, when you set this Tor assumes that your firewall allows only
2277) port 80 and port 443 (HTTP and HTTPS respectively). You can select a
2278) different set of ports with the FirewallPorts torrc option.
2279) </p>
2280) 
2281) <p>
2282) If you want to be more fine-grained with your controls, you can also
2283) use the ReachableAddresses config options, e.g.:
2284) </p>
2285) 
2286) <pre>
2287)   ReachableDirAddresses *:80
2288)   ReachableORAddresses *:443
2289) </pre>
2290) 
2291) <hr>

2292) 

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

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

2296)     <p>

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

2301)     </p>
2302)     <pre>
2303)   reject 0.0.0.0/8
2304)   reject 169.254.0.0/16
2305)   reject 127.0.0.0/8
2306)   reject 192.168.0.0/16
2307)   reject 10.0.0.0/8
2308)   reject 172.16.0.0/12
2309)   reject *:25
2310)   reject *:119
2311)   reject *:135-139
2312)   reject *:445
2313)   reject *:563
2314)   reject *:1214
2315)   reject *:4661-4666
2316)   reject *:6346-6429
2317)   reject *:6699
2318)   reject *:6881-6999
2319)   accept *:*
2320)     </pre>
2321)     <p>

2322)     A relay will block access to its own IP address, as well local network 
2323)     IP addresses. A relay always blocks itself by default. This prevents 
2324)     Tor users from accidentally accessing any of the exit operator's local 
2325)     services. 
2326)     </p>
2327) 
2328)     <hr>
2329) 

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

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

2435)     </p>
2436) 
2437)     <hr>
2438) 

2439)     <a id="RunningATorRelay"></a>
2440)     <h2><a class="anchor">Running a Tor relay:</a></h2>
2441) 

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

2475)     <a id="IDontHaveAStaticIP"></a>
2476)     <h3><a class="anchor" href="#IDontHaveAStaticIP">I don't have a static 
2477)     IP.</a></h3>
2478) 
2479)     <p>
2480)     Tor can handle relays with dynamic IP addresses just fine. Just leave 
2481)     the "Address" line in your torrc blank, and Tor will guess. 
2482)     </p>
2483) 
2484)     <hr>
2485) 
2486)     <a id="ModemKeepsCrashing"></a>
2487)     <h3><a class="anchor" href="#ModemKeepsCrashing">My cable/DSL modem 
2488)     keeps crashing. What's going on?</h3></a>
2489) 
2490)     <p>
2491)     Tor relays hold many connections open at once. This is more intensive 
2492)     use than your cable modem (or other home router) would ever get normally. 
2493)     So if there are any bugs or instabilities, they might show up now. 
2494)     </p>
2495)     <p>
2496)     If your router keeps crashing, you've got two options. First, you should 
2497)     try to upgrade its firmware. If you need tips on how to do this, ask 
2498)     Google or your cable/router provider, or try the Tor IRC channel. 
2499)     </p>
2500) 
2501)     <p>
2502)     Usually the firmware upgrade will fix it. If it doesn't, you will 
2503)     probably want to get a new (better) router. 
2504)     </p>
2505) 
2506)     <hr>
2507) 
2508)     <a id="PortscannedMore"></a>
2509)     <h3><a class="anchor" href="#PortscannedMore">Why do I get portscanned 
2510)     more often when I run a Tor relay?</a></h3>
2511) 
2512)     <p>
2513)     If you allow exit connections, some services that people connect to 
2514)     from your relay will connect back to collect more information about you. 
2515)     For example, some IRC servers connect back to your identd port to record 
2516)     which user made the connection. (This doesn't really work for them, 
2517)     because Tor doesn't know this information, but they try anyway.) Also, 
2518)     users exiting from you might attract the attention of other users on the 
2519)     IRC server, website, etc. who want to know more about the host they're 
2520)     relaying through. 
2521)     </p>
2522)     <p>
2523)     Another reason is that groups who scan for open proxies on the Internet 
2524)     have learned that sometimes Tor relays expose their socks port to the 
2525)     world. We recommend that you bind your socksport to local networks only. 
2526)     </p>
2527)     <p>
2528)     In any case, you need to keep up to date with your security. See this <a 
2529)     href="https://trac.torproject.org/projects/tor/wiki/doc/OperationalSecurity">article 
2530)     on operational security for Tor relays</a> for more suggestions. 
2531)     </p>
2532) 
2533)     <hr>
2534) 
2535)     <a id="MoreThanOneCPU"></a>
2536)     <h3><a class="anchor" href="#MoreThanOneCPU">I have more than one CPU. 
2537)     Does this help?</a></h3>
2538) 
2539)     <p>
2540)     Yes. You can set your NumCpus config option in torrc to the number of 
2541)     CPUs you have, and Tor will spawn this many cpuworkers to deal with 
2542)     public key operations in parallel. 
2543)     </p>
2544) 
2545)     <p>
2546)     This option has no effect for clients. 
2547)     </p>
2548) 
2549)     <hr>
2550) 

2551)     <a id="HighCapacityConnection"></a>    
2552)     <h3><a class="anchor" href="#HighCapacityConnection">How can I get Tor to fully 
2553)     make use of my high capacity connection?</a></h3>
2554)     
2555)     <p>
2556)     See <a href="http://archives.seul.org/or/relays/Aug-2010/msg00034.html">this 
2557)     tor-relays thread</a>.
2558)     </p>
2559)     
2560)     <hr>    
2561)     

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

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

2565) 

2566)     <p>
2567)     We aim to make setting up a Tor relay easy and convenient:
2568)     </p>

2569) 

2570)     <ul>
2571)     <li>Tor has built-in support for <a

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

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

2576) 

2577) href="#LimitTotalBandwidth">

2578) hibernation

2579)     feature</a>.
2580)     </li>

2581)     <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a>
2582) that
2583)     specifies what sort of outbound connections are allowed or refused
2584) from
2585)     that relay. If you are uncomfortable allowing people to exit from
2586) your
2587)     relay, you can set it up to only allow connections to other Tor
2588) relays.

2589)     </li>
2590)     <li>It's fine if the relay goes offline sometimes. The directories
2591)     notice this quickly and stop advertising the relay. Just try to make
2592)     sure it's not too often, since connections using the relay when it
2593)     disconnects will break.
2594)     </li>
2595)     <li>We can handle relays with dynamic IPs just fine &mdash; simply
2596)     leave the Address config option blank, and Tor will try to guess.
2597)     </li>
2598)     <li>If your relay is behind a NAT and it doesn't know its public
2599)     IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

2600)     forwarding. Forwarding TCP connections is system dependent but

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

2602)     offers some examples on how to do this.
2603)     </li>
2604)     <li>Your relay will passively estimate and advertise its recent

2605)     bandwidth capacity, so high-bandwidth relays will attract more users
2606) than
2607)     low-bandwidth ones. Therefore having low-bandwidth relays is useful
2608) too.

2609)     </li>
2610)     </ul>

2611) 

2612)     <hr>

2613)     
2614)     <a id="BandwidthShaping"></a>
2615)     <h3><a class="anchor" href="#BandwidthShaping">What bandwidth shaping 
2616)     options are available to Tor relays?</a></h3>
2617) 
2618)     <p>
2619)     There are two options you can add to your torrc file: 
2620)     </p>
2621)     <ul>
2622)     <li>
2623)     BandwidthRate is the maximum long-term bandwidth allowed (bytes per 
2624)     second). For example, you might want to choose "BandwidthRate 2 MB" 
2625)     for 2 megabytes per second (a fast connection), or "BandwidthRate 50 
2626)     KB" for 50 kilobytes per second (a medium-speed cable connection). 
2627)     The minimum BandwidthRate is 20 kilobytes per second. 
2628)     </li>
2629)     <li>
2630)     BandwidthBurst is a pool of bytes used to fulfill requests during 
2631)     short periods of traffic above BandwidthRate but still keeps the 
2632)     average over a long period to BandwidthRate. A low Rate but a high 
2633)     Burst enforces a long-term average while still allowing more traffic 
2634)     during peak times if the average hasn't been reached lately. For example, 
2635)     if you choose "BandwidthBurst 50 KB" and also use that for your 
2636)     BandwidthRate, then you will never use more than 50 kilobytes per second; 
2637)     but if you choose a higher BandwidthBurst (like 1 MB), it will allow 
2638)     more bytes through until the pool is empty.
2639)     </li>
2640)     </ul>
2641)     <p>
2642)     If you have an asymmetric connection (upload less than download) such 
2643)     as a cable modem, you should set BandwidthRate to less than your smaller 
2644)     bandwidth (Usually that's the upload bandwidth). (Otherwise, you could 
2645)     drop many packets during periods of maximum bandwidth usage -- you may 
2646)     need to experiment with which values make your connection comfortable.) 
2647)     Then set BandwidthBurst to the same as BandwidthRate. 
2648)     </p>
2649)     <p>
2650)     Linux-based Tor nodes have another option at their disposal: they can 
2651)     prioritize Tor traffic below other traffic on their machine, so that 

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

2653)     href="https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/linux-tor-prio.sh">script
2654)     to do this</a> can be found in the Tor source distribution's contrib 
2655)     directory. 
2656)     </p>
2657)     <p>
2658)     Additionally, there are hibernation options where you can tell Tor to 
2659)     only serve a certain amount of bandwidth per time period (such as 100 
2660)     GB per month). These are covered in the <a 
2661)     href="#LimitTotalBandwidth">hibernation entry</a> below. 
2662)     </p>
2663)     <p>
2664)     Note that BandwidthRate and BandwidthBurst are in <b>Bytes,</b>not Bits. 
2665)     </p>
2666) 
2667)     <hr>
2668) 
2669)     <a id="LimitTotalBandwidth"></a>
2670)     <h3><a class="anchor" href="#LimitTotalBandwidth">How can I limit the 
2671)     total amount of bandwidth used by my Tor relay?</a></h3>
2672)     <p>
2673)     The accounting options in the torrc file allow you to specify the maximum 
2674)     amount of bytes your relay uses for a time period. 
2675)     </p>
2676)     <pre>
2677)     AccountingStart day week month [day] HH:MM
2678)     </pre>
2679)     <p>
2680)     This specifies when the accounting should reset. For instance, to setup 
2681)     a total amount of bytes served for a week (that resets every Wednesday 
2682)     at 10:00am), you would use: 
2683)     </p>
2684)     <pre>
2685)     AccountingStart week 3 10:00
2686)     AccountingMax N bytes KB MB GB TB
2687)     </pre>
2688)     <p>
2689)     This specifies the maximum amount of data your relay will send during an 
2690)     accounting period, and the maximum amount of data your relay will receive 
2691)     during an account period. When the accounting period resets (from 
2692)     AccountingStart), then the counters for AccountingMax are reset to 0.
2693)     </p>
2694)     <p>
2695)     Example. Let's say you want to allow 1 GB of traffic every day in each 
2696)     direction and the accounting should reset at noon each day: 
2697)     </p>
2698)     <pre>
2699)     AccountingStart day 12:00
2700)     AccountingMax 1 GB
2701)     </pre>
2702)     <p>
2703)     Note that your relay won't wake up exactly at the beginning of each 
2704)     accounting period. It will keep track of how quickly it used its 
2705)     quota in the last period, and choose a random point in the new interval 
2706)     to wake up. This way we avoid having hundreds of relays working at the 
2707)     beginning of each month but none still up by the end. 
2708)     </p>
2709)     <p>
2710)     If you have only a small amount of bandwidth to donate compared to your 
2711)     connection speed, we recommend you use daily accounting, so you don't 
2712)     end up using your entire monthly quota in the first day. Just divide 
2713)     your monthly amount by 30. You might also consider rate limiting to 
2714)     spread your usefulness over more of the day: if you want to offer X GB 
2715)     in each direction, you could set your BandwidthRate to 20*X. For example, 
2716)     if you have 10 GB to offer each way, you might set your BandwidthRate to 
2717)     200 KB: this way your relay will always be useful for at least half of 
2718)     each day. 
2719)     </p>

2720) 
2721)     <hr>
2722) 
2723)     <a id="RelayWritesMoreThanItReads"></a>

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

2726) 
2727)     <p>You're right, for the most part a byte into your Tor relay means a 
2728)     byte out, and vice versa. But there are a few exceptions:</p>
2729) 
2730)     <p>If you open your DirPort, then Tor clients will ask you for a copy of 
2731)     the directory. The request they make (an HTTP GET) is quite small, and the 
2732)     response is sometimes quite large. This probably accounts for most of the 
2733)     difference between your "write" byte count and your "read" byte count.</p>
2734) 
2735)     <p>Another minor exception shows up when you operate as an exit node, and 
2736)     you read a few bytes from an exit connection (for example, an instant 
2737)     messaging or ssh connection) and wrap it up into an entire 512 byte cell 
2738)     for transport through the Tor network.</p>
2739) 
2740)     <hr>
2741) 
2742)     <a id="Hibernation"></a>
2743)     <h3><a class="anchor" href="#Hibernation">Why can I not browse anymore 

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

2745) 
2746)     <p>The parameters assigned in the <a 
2747)     href="#LimitTotalBandwidth">AccountingMax</a> and <a 
2748)     href="#BandwidthShaping">BandwidthRate</a> apply to both client and 
2749)     relay functions of the Tor process. Thus you may find that you are unable 
2750)     to browse as soon as your Tor goes into hibernation, signaled by this 
2751)     entry in the log:</p>
2752) 
2753)     <pre>Bandwidth soft limit reached; commencing hibernation. No new 
2754)     connections will be accepted</pre>
2755) 
2756)     <p>The solution is to run two Tor processes - one relay and one client, 
2757)     each with its own config. One way to do this (if you are starting from a 
2758)     working relay setup) is as follows:</p>
2759) 
2760)     <ul>
2761)         <li>In the relay Tor torrc file, simply set the SocksPort to 0.</li>
2762)         <li>Create a new client torrc file from the torrc.sample and ensure 
2763)         it uses a different log file from the relay. One naming convention 
2764)         may be torrc.client and torrc.relay.</li>
2765)         <li>Modify the Tor client and relay startup scripts to include 
2766)         '-f /path/to/correct/torrc'.</li>
2767)         <li>In Linux/BSD/OSX, changing the startup scripts to Tor.client 
2768)         and Tor.relay may make separation of configs easier.</li>
2769)     </ul>
2770) 

2771)     <hr>

2772) 

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

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

2776) 

2777)     <p>
2778)     Great. That's exactly why we implemented exit policies.
2779)     </p>

2780) 

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

2783)     outbound connections are allowed or refused from that relay. The
2784) exit

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

2789)     based on abuse potential and his own situation. Read the FAQ entry
2790) on
2791)     <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might
2792) encounter</a>

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

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

2795)     for running an exit node with minimal harassment</a>.
2796)     </p>

2797) 

2798)     <p>

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

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

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

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

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

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

2807)     file. If you want to avoid most if not all abuse potential, set it
2808) to
2809)     "reject *:*" (or un-check all the boxes in Vidalia). This setting
2810) means
2811)     that your relay will be used for relaying traffic inside the Tor
2812) network,

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

2815) 

2816)     <p>

2817)     If you do allow any exit connections, make sure name resolution
2818) works

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

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

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

2823)     explicitly reject them in your exit policy — otherwise Tor
2824) users

2825)     will be impacted too.
2826)     </p>

2827) 

2828)     <hr>

2829) 

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

2873)     <p>

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

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

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

2881)     </p>
2882) 
2883)     <hr>
2884) 
2885)     <a id="ServerClient"></a>

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

2905)     </p>
2906)     <pre>

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

2918)     <p>

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

2921)     </p>
2922)     <pre>
2923)   SocksListenAddress 192.168.x.x:9100 #eth0
2924)   SocksListenAddress 10.x.x.x:9100 #eth1
2925)     </pre>
2926)     <p>

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

2930)     </p>
2931)     <p>

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

2935)     <p>

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

2939)     </p>
2940) 
2941)     <hr>
2942) 

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

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

2946) 
2947)     <p>

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

2950)     </p>
2951)     <p>
2952) 30 Seconds to a Tor Relay:
2953)     </p>
2954)     <ul><li>
2955)     Configure a Nickname: 
2956)     </li></ul>
2957)     <pre>
2958) Nickname ididnteditheconfig
2959)     </pre>

2960)     <ul><li>

2961)     Configure ORPort: 

2962)     </li></ul>

2963)     <pre>
2964) ORPort 9001
2965)     </pre>

2966)     <ul><li>

2967)     Configure Contact Info: 

2968)     </li></ul>

2969) 
2970)     <pre>
2971) ContactInfo human@…

2972)     </pre>
2973)     <ul><li>

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

2977)     </li></ul>

2978) 
2979)     <hr />

2980) 

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

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

2984) 

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

2988)     listed in the public Tor directory.

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

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

2991)     </p>

2992) 

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

2995)     publicly or not.

2996)     </p>

2997) 

2998)     <p>

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

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

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

3003)     </p>

3004) 

3005)     <p>
3006)     Several countries, including China and Iran, have found ways to

3007)     detect and block connections to Tor bridges.

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

3009)     this by adding another layer of obfuscation.

3010)     </p>
3011) 

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

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

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

3020)     </p>

3021) 

3022)     <hr>

3023) 

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

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

3027) 
3028) <p>

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

3033) </p>
3034) <p>

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

3039) </p>
3040) 
3041)     <hr>
3042) 
3043) <a id="NTService"></a>

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

3046) 
3047) <p>

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

3051) </p>
3052) <p>

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

3058) </p>
3059) <p>
3060) To install Tor as a service, you can simply run:
3061) </p>
3062) <pre>
3063) tor --service install
3064) </pre>
3065) <p>

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

3072) </p>
3073) <p>

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

3078) </p>
3079) <pre>
3080) tor --service install -options -f C:\tor\torrc ControlPort 9151
3081) </pre>
3082) <p>
3083) You can also start or stop the Tor service from the command line by typing:
3084) </p>
3085) <pre>
3086)  tor --service start
3087) </pre>
3088) <p>
3089) or
3090) </p>
3091) <pre>
3092)  tor --service stop
3093) </pre>
3094) <p>
3095) To remove the Tor service, you can run the following command:
3096) </p>
3097) <pre>
3098) tor --service remove
3099) </pre>
3100) <p>

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

3105) </p>
3106) 
3107) <hr>
3108) 
3109) <a id="VirtualServer"></a>

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

3112) 
3113) <p>

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

3122) <p>

3123) <table border="1">

3124) <tr>
3125) <td>
3126) <i>resource</i>
3127) </td>
3128) <td>
3129) <i>held</i>
3130) </td>
3131) <td>
3132) <i>maxheld</i>
3133) </td>
3134) <td>
3135) <i>barrier</i>
3136) </td>
3137) <td>
3138) <i>limit</i>
3139) </td>
3140) <td>
3141) <i>failcnt</i>
3142) </td>
3143) </tr>
3144) <tr>
3145) <td>
3146) tcpsndbuf
3147) </td>
3148) <td>
3149) 46620
3150) </td>
3151) <td>
3152) 48840
3153) </td>
3154) <td>
3155) 3440640
3156) </td>
3157) <td>
3158) 5406720
3159) </td>
3160) <td>
3161) 0
3162) </td>
3163) </tr>
3164) <tr>
3165) <td>
3166) tcprcvbuf
3167) </td>
3168) <td>
3169) 0
3170) </td>
3171) <td>
3172) 2220
3173) </td>
3174) <td>
3175) 3440640
3176) </td>
3177) <td>
3178) 5406720
3179) </td>
3180) <td>
3181) 0
3182) </td>
3183) </tr>
3184) <tr>
3185) <td>
3186) othersockbuf
3187) </td>
3188) <td>
3189) 243516
3190) </td>
3191) <td>
3192) 260072
3193) </td>
3194) <td>
3195) 2252160
3196) </td>
3197) <td>
3198) 4194304
3199) </td>
3200) <td>
3201) 0
3202) </td>
3203) </tr>
3204) <tr>
3205) <td>
3206) numothersock
3207) </td>
3208) <td>
3209) 151
3210) </td>
3211) <td>
3212) 153
3213) </td>
3214) <td>
3215) 720
3216) </td>
3217) <td>
3218) 720
3219) </td>
3220) <td>
3221) 0
3222) </td>
3223) </tr>
3224) </table>
3225) <p>
3226)  Xen, Virtual Box and VMware virtual servers have no such limits normally.
3227) </p>
3228) <p>

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

3235) </p>
3236) <p>

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

3241) </p>
3242) <p>

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

3246) </p>
3247)