Roger Dingledine commited on 2005-06-08 02:56:49
Zeige 1 geänderte Dateien mit 22 Einfügungen und 15 Löschungen.
... | ... |
@@ -94,7 +94,7 @@ all IP packets, you cannot send UDP packets over Tor. (You can't do |
94 | 94 |
specialized forms of this attack like SYN flooding either.) So ordinary |
95 | 95 |
DDoS attacks are not possible over Tor. Tor also doesn't allow bandwidth |
96 | 96 |
amplification attacks against external sites: you need to send in a byte |
97 |
-for every byte which the Tor network will send to your destination. So |
|
97 |
+for every byte that the Tor network will send to your destination. So |
|
98 | 98 |
in general, attackers who control enough bandwidth to launch an effective |
99 | 99 |
DDoS attack can do it just fine without Tor. </p> |
100 | 100 |
|
... | ... |
@@ -107,13 +107,14 @@ if you're still worried. </p> |
107 | 107 |
|
108 | 108 |
<p>The simple answer: The default Tor exit policy rejects all outgoing |
109 | 109 |
port 25 (SMTP) traffic. So sending spam mail through Tor isn't going to |
110 |
-work. It's possible that some server operators will enable port 25 on |
|
111 |
-their particular exit node, in which case only that computer will allow |
|
112 |
-outgoing mails; but that individual could just set up an open mail relay |
|
113 |
-too, independent of Tor. In short, Tor isn't useful for spammers, because |
|
114 |
-nearly all Tor servers refuse to deliver it. </p> |
|
115 |
- |
|
116 |
-<p>The complex answer: Spammers are already doing great without Tor. They |
|
110 |
+work by default. It's possible that some server operators will enable |
|
111 |
+port 25 on their particular exit node, in which case that computer will |
|
112 |
+allow outgoing mails; but that individual could just set up an open mail |
|
113 |
+relay too, independent of Tor. In short, Tor isn't useful for spammers, |
|
114 |
+because nearly all Tor servers refuse to deliver their mail. </p> |
|
115 |
+ |
|
116 |
+<p>The complex answer: Even if the above were not true, spammers are |
|
117 |
+already doing great without Tor. They |
|
117 | 118 |
have armies of compromised computers that do their spamming. The added |
118 | 119 |
complexity of getting new software installed and configured, and doing |
119 | 120 |
Tor's public key operations, etc, makes it not economically worthwhile |
... | ... |
@@ -159,7 +160,7 @@ main ones so far have taken the following form: </p> |
159 | 160 |
FBI sends you a polite email, you explain that you run a Tor server, |
160 | 161 |
and they say 'oh well' and leave you alone. [Port 80]</li> |
161 | 162 |
<li>Somebody tries to get you shut down by using Tor to connect to google |
162 |
-groups and posting spam to usenet, and then sending an angry mail to |
|
163 |
+groups and post spam to usenet, and then sending an angry mail to |
|
163 | 164 |
your ISP about how you're destroying the world. [Port 80]</li> |
164 | 165 |
<li>Somebody connects to an irc network and makes a nuisance of |
165 | 166 |
himself. Your ISP gets polite mail about how your computer has been |
... | ... |
@@ -237,13 +238,14 @@ Tor at all, or they may not be aware that the hostnames they're klining |
237 | 238 |
are Tor exit nodes. If you explain the problem, and they conclude that |
238 | 239 |
Tor ought to be blocked, you may want to consider moving to a network that |
239 | 240 |
is more open to free speech. Maybe inviting them to #tor on irc.oftc.net |
240 |
-helps them show that we are not all evil people. </p> |
|
241 |
+will help show them that we are not all evil people. </p> |
|
241 | 242 |
|
242 |
-<p>Finally, if you become aware of an IRC network which seems to be |
|
243 |
+<p>Finally, if you become aware of an IRC network that seems to be |
|
243 | 244 |
blocking Tor, or a single Tor exit node, please put that information on <a |
244 |
-href="http://wiki.noreply.org/wiki/TheOnionRouter/BlockingIrc">BlockingIrc</a> |
|
245 |
+href="http://wiki.noreply.org/wiki/TheOnionRouter/BlockingIrc">The Tor |
|
246 |
+IRC block tracker</a> |
|
245 | 247 |
so that others can share. At least one IRC network consults that page |
246 |
-to unblock exit nodes which have been blocked inadvertently. </p> |
|
248 |
+to unblock exit nodes that have been blocked inadvertently. </p> |
|
247 | 249 |
|
248 | 250 |
<a name="SMTPBans"></a> |
249 | 251 |
<h3>Your nodes are banned from the mail server I want to use.</h3> |
... | ... |
@@ -273,9 +275,14 @@ to your service right now to carry on normal activities. You need to |
273 | 275 |
decide whether banning the Tor network is worth losing the contributions |
274 | 276 |
of these users, as well as potential future such users. </p> |
275 | 277 |
|
278 |
+<p>At this point, you should also ask yourself what you do about other |
|
279 |
+services that aggregate many users behind a few IP addresses. Tor is |
|
280 |
+not so different from AOL in this respect.</p> |
|
281 |
+ |
|
276 | 282 |
<p>Lastly, please remember that Tor servers have individual exit |
277 | 283 |
policies. Many Tor servers do not allow exiting connections at |
278 |
-all. Many of those that do, probably already disallow connections to |
|
284 |
+all. Many of those that do allow some exit connections probably already |
|
285 |
+disallow connections to |
|
279 | 286 |
your service. When you go about banning nodes, you should parse the |
280 | 287 |
exit policies and only block the ones that allow these connections; |
281 | 288 |
and you should keep in mind that exit policies can change (as well as |
... | ... |
@@ -293,7 +300,7 @@ we're not the ones to talk to about legal questions or concerns. </p> |
293 | 300 |
|
294 | 301 |
<p>Please take a look at the <a |
295 | 302 |
href="http://tor.eff.org//eff/tor-legal-faq.html">Tor Legal FAQ</a>, |
296 |
-and contact EFF directly if you have any further questions. </p> |
|
303 |
+and contact EFF directly if you have any further legal questions. </p> |
|
297 | 304 |
|
298 | 305 |
</div><!-- #main --> |
299 | 306 |
</div> |
300 | 307 |