tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 3-low
4) 
5) #include "head.wmi" TITLE="Tor Project: Abuse 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-abuse>">Abuse FAQ</a>
11)   </div>
12)   <div id="maincol"> 
13)     <!-- PUT CONTENT AFTER THIS TAG -->
14)     <h1>Abuse FAQ</h1>

15)     <hr>

16)     #<!-- BEGIN SIDEBAR -->
17)     #<div class="sidebar-left">
18)     #<h3>Questions</h3>
19)     #<ul>
20)     #<li><a href="<page docs/faq-abuse>#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></li>
21)     #<li><a href="<page docs/faq-abuse>#DDoS">What about distributed denial of service attacks?</a></li>
22)     #<li><a href="<page docs/faq-abuse>#WhatAboutSpammers">What about spammers?</a></li>
23)     #<li><a href="<page docs/faq-abuse>#HowMuchAbuse">Does Tor get much abuse?</a></li>
24)     #<li><a href="<page docs/faq-abuse>#TypicalAbuses">So what should I expect if I run an exit relay?</a></li>
25)     #<li><a href="<page docs/faq-abuse>#IrcBans">Tor is banned from the IRC network I want to use.</a></li>
26)     #<li><a href="<page docs/faq-abuse>#SMTPBans">Your nodes are banned from the mail server I want to use.</a></li>
27)     #<li><a href="<page docs/faq-abuse>#Bans">I want to ban the Tor network from my service.</a></li>
28)     #<li><a href="<page docs/faq-abuse>#TracingUsers">I have a compelling reason to trace a Tor user. Can you help?</a></li>
29)     #<li><a href="<page docs/faq-abuse>#RemoveContent">I want some content removed from a .onion address.</a></li>
30)     #<li><a href="<page docs/faq-abuse>#LegalQuestions">I have legal questions about Tor abuse.</a></li>
31)     #</ul>
32)     #</div>
33)     #<!-- END SIDEBAR -->

34)     <h3>Questions</h3>
35)     <ul>
36)     <li><a href="#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></li>
37)     <li><a href="#DDoS">What about distributed denial of service attacks?</a></li>
38)     <li><a href="#WhatAboutSpammers">What about spammers?</a></li>
39)     <li><a href="#HowMuchAbuse">Does Tor get much abuse?</a></li>
40)     <li><a href="#TypicalAbuses">So what should I expect if I run an exit relay?</a></li>
41)     <li><a href="#IrcBans">Tor is banned from the IRC network I want to use.</a></li>
42)     <li><a href="#SMTPBans">Your nodes are banned from the mail server I want to use.</a></li>
43)     <li><a href="#Bans">I want to ban the Tor network from my service.</a></li>
44)     <li><a href="#TracingUsers">I have a compelling reason to trace a Tor user. Can you help?</a></li>
45)     <li><a href="#RemoveContent">I want some content removed from a .onion address.</a></li>
46)     <li><a href="#LegalQuestions">I have legal questions about Tor abuse.</a></li>
47)     </ul>
48)     <hr>

49)     
50)     <a id="WhatAboutCriminals"></a>
51)     <h3><a class="anchor" href="#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></h3>
52)     
53)     <p>Criminals can already do bad things. Since they're willing to
54)     break laws, they already have lots of options available that provide
55)     <em>better</em> privacy than Tor provides. They can steal cell phones,
56)     use them, and throw them in a ditch; they can crack into computers
57)     in Korea or Brazil and use them to launch abusive activities; they
58)     can use spyware, viruses, and other techniques to take control of
59)     literally millions of Windows machines around the world. </p>
60)     
61)     <p>Tor aims to provide protection for ordinary people who want to follow
62)     the law. Only criminals have privacy right now, and we need to fix that. </p>
63)     
64)     <p>Some advocates of anonymity explain that it's just a tradeoff &mdash;
65)     accepting the bad uses for the good ones &mdash; but there's more to it
66)     than that.
67)     Criminals and other bad people have the motivation to learn how to
68)     get good anonymity, and many have the motivation to pay well to achieve
69)     it. Being able to steal and reuse the identities of innocent victims
70)     (identify theft) makes it even easier. Normal people, on the other hand,
71)     don't have the time or money to spend figuring out how to get
72)     privacy online. This is the worst of all possible worlds. </p>
73)     
74)     <p>So yes, criminals could in theory use Tor, but they already have
75)     better options, and it seems unlikely that taking Tor away from the
76)     world will stop them from doing their bad things. At the same time, Tor
77)     and other privacy measures can <em>fight</em> identity theft, physical
78)     crimes like stalking, and so on. </p>
79)     

80)     #<a id="Pervasive"></a>
81)     #<h3><a class="anchor" href="#Pervasive">If the whole world starts using
82)     #Tor, won't civilization collapse?</a></h3>

83)     
84)     <a id="DDoS"></a>
85)     <h3><a class="anchor" href="#DDoS">What about distributed denial of service attacks?</a></h3>
86)     
87)     <p>Distributed denial of service (DDoS) attacks typically rely on having a group
88)     of thousands of computers all sending floods of traffic to a victim. Since
89)     the goal is to overpower the bandwidth of the victim, they typically send
90)     UDP packets since those don't require handshakes or coordination. </p>
91)     
92)     <p>But because Tor only transports correctly formed TCP streams, not
93)     all IP packets, you cannot send UDP packets over Tor. (You can't do
94)     specialized forms of this attack like SYN flooding either.) So ordinary
95)     DDoS attacks are not possible over Tor. Tor also doesn't allow bandwidth
96)     amplification attacks against external sites: you need to send in a byte
97)     for every byte that the Tor network will send to your destination. So
98)     in general, attackers who control enough bandwidth to launch an effective
99)     DDoS attack can do it just fine without Tor. </p>
100)     
101)     <a id="WhatAboutSpammers"></a>
102)     <h3><a class="anchor" href="#WhatAboutSpammers">What about spammers?</a></h3>
103)     
104)     <p>First of all, the default Tor exit policy rejects all outgoing
105)     port 25 (SMTP) traffic. So sending spam mail through Tor isn't going to
106)     work by default. It's possible that some relay operators will enable
107)     port 25 on their particular exit node, in which case that computer will
108)     allow outgoing mails; but that individual could just set up an open mail
109)     relay too, independent of Tor. In short, Tor isn't useful for spamming,
110)     because nearly all Tor relays refuse to deliver the mail. </p>
111)     
112)     <p>Of course, it's not all about delivering the mail. Spammers can use
113)     Tor to connect to open HTTP proxies (and from there to SMTP servers); to
114)     connect to badly written mail-sending CGI scripts; and to control their
115)     botnets &mdash; that is, to covertly communicate with armies of
116)     compromised computers that deliver the spam.
117)     </p>
118)     
119)     <p>
120)     This is a shame, but notice that spammers are already doing great
121)     without Tor. Also, remember that many of their more subtle communication
122)     mechanisms (like spoofed UDP packets) can't be used over Tor, because
123)     it only transports correctly-formed TCP connections.
124)     </p>
125)     
126)     <a id="ExitPolicies"></a>
127)     <h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3>
128)     
129)     <p>

130)     <a href="<page docs/faq>#ExitPolicies">See the main FAQ</a>

131)     </p>
132)     
133)     <a id="HowMuchAbuse"></a>
134)     <h3><a class="anchor" href="#HowMuchAbuse">Does Tor get much abuse?</a></h3>
135)     

136)     <p>Not much, in the grand scheme of things. The network has been running

137)     since October 2003, and it's only generated a handful of complaints. Of

138)     course, like all privacy-oriented networks on the net, it attracts its

139)     share of jerks. Tor's exit policies help separate the role of "willing
140)     to donate resources to the network" from the role of "willing to deal
141)     with exit abuse complaints," so we hope our network is more sustainable
142)     than past attempts at anonymity networks. </p>
143)     
144)     <p>Since Tor has

145)     <a href="<page about/torusers>">many good uses as

146)     well</a>, we feel that we're doing pretty well at striking a balance
147)     currently. </p>
148)     
149)     <a id="TypicalAbuses"></a>
150)     <h3><a class="anchor" href="#TypicalAbuses">So what should I expect if I run an exit relay?</a></h3>
151)     
152)     <p>If you run a Tor relay that allows exit connections (such as the
153)     default exit policy), it's probably safe to say that you will eventually
154)     hear from somebody. Abuse
155)     complaints may come in a variety of forms. For example: </p>
156)     <ul>
157)     <li>Somebody connects to Hotmail, and sends a ransom note to a
158)     company. The
159)     FBI sends you a polite email, you explain that you run a Tor relay,
160)     and they say "oh well" and leave you alone. [Port 80]</li>
161)     <li>Somebody tries to get you shut down by using Tor to connect to Google
162)     groups and post spam to Usenet, and then sends an angry mail to
163)     your ISP about how you're destroying the world. [Port 80]</li>
164)     <li>Somebody connects to an IRC network and makes a nuisance of
165)     himself. Your ISP gets polite mail about how your computer has been
166)     compromised; and/or your computer gets DDoSed. [Port 6667]</li>
167)     <li>Somebody uses Tor to download a Vin Diesel movie, and
168)     your ISP gets a DMCA takedown notice. See EFF's
169)     <a href="<page eff/tor-dmca-response>">Tor DMCA Response
170)     Template</a>, which explains why your ISP can probably ignore
171)     the notice without any liability. [Arbitrary ports]</li>
172)     </ul>

173) 
174)     <p>For a complete set of template responses to different abuse complaint
175)     types, see <a

176)     href="<wiki>doc/TorAbuseTemplates">the collection of templates

177)     on the Tor wiki</a>. You can also proactively reduce the amount of abuse you
178)     get by following <a href="<blog>tips-running-exit-node-minimal-harassment">these tips

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

180)     
181)     <p>You might also find that your Tor relay's IP is blocked from accessing
182)     some Internet sites/services. This might happen regardless of your exit
183)     policy, because some groups don't seem to know or care that Tor has
184)     exit policies. (If you have a spare IP not used for other activities,
185)     you might consider running your Tor relay on it.) For example, </p>
186)     
187)     <ul>
188)     <li>Because of a few cases of anonymous jerks messing with its web
189)     pages, Wikipedia is currently blocking many Tor relay IPs from writing
190)     (reading still works). We're talking to Wikipedia about how they might
191)     control abuse while still providing access to anonymous contributors,
192)     who often have hot news or inside info on a topic but don't want to risk
193)     revealing their identities when publishing it (or don't want to reveal
194)     to local observers that they're accessing Wikipedia). Slashdot is also
195)     in the same boat.</li>
196)     
197)     <li>SORBS is putting some Tor relay IPs on their email
198)     blacklist as well. They do this because they passively detect whether your
199)     relay connects to certain IRC networks, and they conclude from this that
200)     your relay is capable of spamming. We tried to work with
201)     them to teach them that not all software works this way,
202)     but we have given up. We recommend you avoid them, and <a
203)     href="http://paulgraham.com/spamhausblacklist.html">teach your friends
204)     (if they use them) to avoid abusive blacklists too</a>.</li>
205)     
206)     </ul>
207)     
208)     <a id="IrcBans"></a>
209)     <h3><a class="anchor" href="#IrcBans">Tor is banned from the IRC network I want to use.</a></h3>
210)     
211)     <p>Sometimes jerks make use of Tor to troll IRC channels. This abuse
212)     results in IP-specific temporary bans ("klines" in IRC lingo), as the
213)     network operators try to keep the troll off of their network. </p>
214)     
215)     <p>This response underscores a fundamental flaw in IRC's security model:
216)     they assume that IP addresses equate to humans, and by banning the
217)     IP address they can ban the human. In reality this is not the case &mdash;
218)     many such trolls routinely make use of the literally millions of open
219)     proxies and compromised computers around the Internet. The IRC networks
220)     are fighting a losing battle of trying to block all these nodes,
221)     and an entire cottage industry of blacklists and counter-trolls has
222)     sprung up based on this flawed security model (not unlike the antivirus
223)     industry). The Tor network is just a drop in the bucket here. </p>
224)     
225)     <p>On the other hand, from the viewpoint of IRC server operators, security
226)     is not an all-or-nothing thing.  By responding quickly to trolls or
227)     any other social attack, it may be possible to make the attack scenario
228)     less attractive to the attacker.  And most individual IP addresses do
229)     equate to individual humans, on any given IRC network at any given time.
230)     The exceptions include NAT gateways which may be allocated access as
231)     special cases. While it's a losing battle to try to stop the use of open
232)     proxies, it's not generally a losing battle to keep klining a single
233)     ill-behaved IRC user until that user gets bored and goes away. </p>
234)     
235)     <p>But the real answer is to implement application-level auth systems,
236)     to let in well-behaving users and keep out badly-behaving users. This
237)     needs to be based on some property of the human (such as a password he
238)     knows), not some property of the way his packets are transported. </p>
239)     
240)     <p>Of course, not all IRC networks are trying to ban Tor nodes. After
241)     all, quite a few people use Tor to IRC in privacy in order to carry
242)     on legitimate communications without tying them to their real-world
243)     identity. Each IRC network needs to decide for itself if blocking a few
244)     more of the millions of IPs that bad people can use is worth losing the
245)     contributions from the well-behaved Tor users. </p>
246)     
247)     <p>If you're being blocked, have a discussion with the network operators
248)     and explain the issues to them. They may not be aware of the existence of
249)     Tor at all, or they may not be aware that the hostnames they're klining
250)     are Tor exit nodes.  If you explain the problem, and they conclude that
251)     Tor ought to be blocked, you may want to consider moving to a network that
252)     is more open to free speech.  Maybe inviting them to #tor on irc.oftc.net
253)     will help show them that we are not all evil people. </p>
254)     
255)     <p>Finally, if you become aware of an IRC network that seems to be
256)     blocking Tor, or a single Tor exit node, please put that information on <a

257)     href="<wiki>doc/BlockingIrc">The Tor

258)     IRC block tracker</a>
259)     so that others can share.  At least one IRC network consults that page
260)     to unblock exit nodes that have been blocked inadvertently. </p>
261)     
262)     <a id="SMTPBans"></a>
263)     <h3><a class="anchor" href="#SMTPBans">Your nodes are banned from the mail server I want to use.</a></h3>
264)     
265)     <p>Even though <a href="#WhatAboutSpammers">Tor isn't useful for
266)     spamming</a>, some over-zealous blacklisters seem to think that all
267)     open networks like Tor are evil &mdash; they attempt to strong-arm network
268)     administrators on policy, service, and routing issues, and then extract
269)     ransoms from victims. </p>
270)     
271)     <p>If your server administrators decide to make use of these
272)     blacklists to refuse incoming mail, you should have a conversation with
273)     them and explain about Tor and Tor's exit policies. </p>
274)     
275)     <a id="Bans"></a>
276)     <h3><a class="anchor" href="#Bans">I want to ban the Tor network from my service.</a></h3>
277)     
278)     <p>We're sorry to hear that. There are some situations where it makes
279)     sense to block anonymous users for an Internet service. But in many
280)     cases, there are easier solutions that can solve your problem while
281)     still allowing users to access your website securely.</p>
282)     
283)     <p>First, ask yourself if there's a way to do application-level decisions
284)     to separate the legitimate users from the jerks. For example, you might
285)     have certain areas of the site, or certain privileges like posting,
286)     available only to people who are registered. It's easy to build an
287)     up-to-date list of Tor IP addresses that allow connections to your
288)     service, so you could set up this distinction only for Tor users. This
289)     way you can have multi-tiered access and not have to ban every aspect
290)     of your service. </p>
291)     
292)     <p>For example, the <a
293)     href="http://freenode.net/policy.shtml#tor">Freenode IRC network</a>
294)     had a problem with a coordinated group of abusers joining channels and
295)     subtly taking over the conversation; but when they labelled all users
296)     coming from Tor nodes as "anonymous users," removing the ability of the
297)     abusers to blend in, the abusers moved back to using their open proxies
298)     and bot networks. </p>
299)     
300)     <p>Second, consider that hundreds of thousands of
301)     people use Tor every day simply for
302)     good data hygiene &mdash; for example, to protect against data-gathering
303)     advertising companies while going about their normal activities. Others
304)     use Tor because it's their only way to get past restrictive local
305)     firewalls. Some Tor users may be legitimately connecting
306)     to your service right now to carry on normal activities. You need to
307)     decide whether banning the Tor network is worth losing the contributions
308)     of these users, as well as potential future legitimate users. (Often
309)     people don't have a good measure of how many polite Tor users are
310)     connecting to their service &mdash; you never notice them until there's
311)     an impolite one.)</p>
312)     
313)     <p>At this point, you should also ask yourself what you do about other
314)     services that aggregate many users behind a few IP addresses. Tor is
315)     not so different from AOL in this respect.</p>
316)     
317)     <p>Lastly, please remember that Tor relays have <a

318)     href="<page docs/faq>#ExitPolicies">individual exit policies</a>. Many
319)     Tor relays do

320)     not allow exiting connections at all. Many of those that do allow some
321)     exit connections might already disallow connections to
322)     your service. When you go about banning nodes, you should parse the
323)     exit policies and only block the ones that allow these connections;
324)     and you should keep in mind that exit policies can change (as well as
325)     the overall list of nodes in the network).</p>
326)     
327)     <p>If you really want to do this, we provide a
328)     <a href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">Tor
329)     exit relay list</a> or a
330)     <a href="<page projects/tordnsel>">DNS-based list you can query</a>.
331)     </p>
332)     
333)     <p>
334)     (Some system administrators block ranges of IP addresses because of
335)     official policy or some abuse pattern, but some have also asked about
336)     whitelisting Tor exit relays because they want to permit access to their
337)     systems only using Tor. These scripts are usable for whitelisting as well.)
338)     </p>
339)     
340)     <a id="TracingUsers"></a>
341)     <h3><a class="anchor" href="#TracingUsers">I have a compelling reason to trace a Tor user. Can you help?</a></h3>
342)     
343)     <p>
344)     There is nothing the Tor developers can do to trace Tor users. The same
345)     protections that keep bad people from breaking Tor's anonymity also
346)     prevent us from figuring out what's going on.
347)     </p>
348)     
349)     <p>
350)     Some fans have suggested that we redesign Tor to include a <a

351)     href="<page docs/faq>#Backdoor">backdoor</a>.

352)     There are two problems with this idea. First, it technically weakens the
353)     system too far. Having a central way to link users to their activities
354)     is a gaping hole for all sorts of attackers; and the policy mechanisms
355)     needed to ensure correct handling of this responsibility are enormous
356)     and unsolved. Second, the bad people <a href="#WhatAboutCriminals">aren't
357)     going to get caught by this anyway</a>, since they will use other means
358)     to ensure their anonymity (identity theft, compromising computers and
359)     using them as bounce points, etc).
360)     </p>

361) 
362)     <p>
363)     This ultimately means that it is the responsibility of site owners to protect
364)     themselves against compromise and security issues that can come from
365)     anywhere. This is just part of signing up for the benefits of the
366)     Internet. You must be prepared to secure yourself against the bad elements,
367)     wherever they may come from. Tracking and increased surveillance are not
368)     the answer to preventing abuse.
369)     </p>
370) 

371)     <p>
372)     But remember that this doesn't mean that Tor is invulnerable. Traditional
373)     police techniques can still be very effective against Tor, such as

374)     investigating means, motive, and opportunity, interviewing suspects,
375)     writing style analysis, technical analysis of the content itself, sting operations,
376)     keyboard taps, and other physical investigations. The Tor Project is also happy to work with everyone
377)     including law enforcement groups to train them how to use the Tor software to safely conduct
378)     investigations or anonymized activities online.

379)     </p>

380) 
381) 

382)     <a id="RemoveContent"></a>
383)     <h3><a class="anchor" href="#RemoveContent">I want some content removed from a .onion address.</a></h3>
384)     <p>The Tor Project does not host, control, nor have the ability to
385)     discover the owner or location of a .onion address.  The .onion address is
386)     an address from <a href="<page docs/hidden-services>">a hidden
387)     service</a>.  The name you see ending in .onion is a hidden service descriptor.
388)     It's an automatically generated name which can be located on any Tor
389)     relay or client anywhere on the Internet.  Hidden services are designed
390)     to protect both the user and service provider from discovering who they
391)     are and where they are from.  The design of hidden services means the
392)     owner and location of the .onion site is hidden even from us.</p>
393)     <p>But remember that this doesn't mean that hidden services are
394)     invulnerable. Traditional police techniques can still be very effective

395)     against them, such as interviewing suspects, writing style analysis,
396)     technical analysis of the content itself, sting operations, keyboard taps,
397)     and other physical investigations.</p>
398) 

399)     <p>If you have a complaint about child abuse materials, you may wish to report

400)     it to the National Center for Missing and Exploited Children, which serves
401)     as a national coordination point for investigation of child pornography:
402)     <a href="http://www.missingkids.com/">http://www.missingkids.com/</a>.
403)     We do not view links you report.</p>

404)