2008-03-22 19:53:09 +01:00
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<title>This is a Tor Exit Router</title>
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
|
2008-05-15 09:26:05 +02:00
|
|
|
This notice is intended to be placed on a virtual host for a domain that
|
2008-03-22 19:53:09 +01:00
|
|
|
your Tor exit node IP reverse resolves to so that people who may be about
|
2008-05-15 09:26:05 +02:00
|
|
|
to file an abuse complaint would check it first before bothering you or
|
2008-03-22 19:53:09 +01:00
|
|
|
your ISP. Ex:
|
|
|
|
|
http://tor-exit.yourdomain.org or http://tor-readme.yourdomain.org.
|
|
|
|
|
|
2008-05-15 09:26:05 +02:00
|
|
|
This type of setup has proven very effective at reducing abuse complaints
|
2008-03-22 19:53:09 +01:00
|
|
|
for exit node operators.
|
|
|
|
|
|
|
|
|
|
There are a few places in this document that you may want to customize.
|
2008-05-15 09:26:05 +02:00
|
|
|
They are marked with FIXME.
|
2008-03-22 19:53:09 +01:00
|
|
|
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
</head>
|
|
|
|
|
<body bgcolor=white text=black>
|
|
|
|
|
|
|
|
|
|
<center><h1>This is a Tor Exit Router</h1></center>
|
|
|
|
|
|
|
|
|
|
<p>Most likely you are accessing this website because you had some issue with
|
|
|
|
|
the traffic coming from this IP. This router is part of the <a
|
2008-05-15 09:32:11 +02:00
|
|
|
href="https://www.torproject.org/">Tor Anonymity Network</a>, which is
|
2008-03-22 19:53:09 +01:00
|
|
|
dedicated to providing people with anonymity who need it most: average
|
|
|
|
|
computer users. This router IP should be generating no other traffic, unless
|
|
|
|
|
it has been compromised.
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
While Tor is not designed for malicious computer users, it is inevitable that
|
|
|
|
|
some may use the network for malicious ends. In the mind of this operator,
|
|
|
|
|
the social need for easily accessible censorship-resistant anonymous
|
|
|
|
|
communication trumps the risk. Tor sees use by many important segments of the
|
|
|
|
|
population, including whistle blowers, journalists, Chinese dissidents
|
|
|
|
|
skirting the Great Firewall and oppressive censorship, abuse victims,
|
|
|
|
|
stalker targets, the US military, and law enforcement, just to name a few.
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
2008-06-19 19:17:42 +02:00
|
|
|
<!-- FIXME: you should probably grab your own copy of how_tor_works_thumb.png
|
2008-03-22 19:53:09 +01:00
|
|
|
and serve it locally -->
|
2008-06-19 19:17:42 +02:00
|
|
|
<center><a href="https://www.torproject.org/overview.html">
|
|
|
|
|
<img src="http://www.torproject.org/images/how_tor_works_thumb.png"></a></center>
|
2008-03-22 19:53:09 +01:00
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
In terms of applicable law, the best way to understand Tor is to consider it a
|
|
|
|
|
network of routers operating as common carriers, much like the Internet
|
|
|
|
|
backbone. However, unlike the Internet backbone routers, Tor routers
|
|
|
|
|
explicitly do not contain identifiable routing information about the source of
|
|
|
|
|
a packet.
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
As such, there is little the operator of this router can do to help you track
|
|
|
|
|
the connection further. This router maintains no logs of any of the Tor
|
|
|
|
|
traffic, so there is little that can be done to trace either legitimate or
|
|
|
|
|
illegitimate traffic (or to filter one from the other). Attempts to
|
|
|
|
|
seize this router will accomplish nothing.
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
<!--- FIXME: US-Only section. Remove if you are a non-US operator -->
|
|
|
|
|
|
|
|
|
|
Furthermore, this machine also serves as a carrier of email, which means that
|
|
|
|
|
its contents are further protected under the ECPA. <a
|
|
|
|
|
href="http://www4.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002707----000-.html">18
|
|
|
|
|
USC 2707</a> explicitly allows for civil remedies ($1000/account
|
|
|
|
|
<i><b><u>plus</u></b></i> legal fees)
|
|
|
|
|
in the event of a seizure executed without good faith or probable cause (it
|
|
|
|
|
should be clear at this point that traffic with an originating IP address of
|
|
|
|
|
FIXME_DNS_NAME should not constitute probable cause to seize the
|
|
|
|
|
machine). Similar considerations exist for 1st amendment content on this
|
|
|
|
|
machine.
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
2008-05-15 09:26:05 +02:00
|
|
|
<!-- FIXME: May or may not be US-only. Some non-US tor nodes have in
|
2008-03-22 19:53:09 +01:00
|
|
|
fact reported DMCA harassment... -->
|
|
|
|
|
|
|
|
|
|
If you are a representative of a company who feels that this router is being
|
|
|
|
|
used to violate the DMCA, please be aware that this machine does not host or
|
|
|
|
|
contain any illegal content. Also be aware that network infrastructure
|
|
|
|
|
maintainers are not liable for the type of content that passes over their
|
|
|
|
|
equipment, in accordance with <a
|
|
|
|
|
href="http://www4.law.cornell.edu/uscode/html/uscode17/usc_sec_17_00000512----000-.html">DMCA
|
|
|
|
|
"safe harbor" provisions</a>. In other words, you will have just as much luck
|
|
|
|
|
sending a takedown notice to the Internet backbone providers. Please consult
|
2008-05-15 09:26:05 +02:00
|
|
|
<a href="https://www.torproject.org/eff/tor-dmca-response.html">EFF's prepared
|
2008-03-22 19:53:09 +01:00
|
|
|
response</a> for more information on this matter.
|
|
|
|
|
|
|
|
|
|
<p>For more information, please consult the following documentation:
|
|
|
|
|
|
|
|
|
|
<ol>
|
2008-05-15 09:26:05 +02:00
|
|
|
<li><a href="https://www.torproject.org/overview.html">Tor Overview</a></li>
|
|
|
|
|
<li><a href="https://www.torproject.org/faq-abuse.html">Tor Abuse FAQ</a></li>
|
|
|
|
|
<li><a href="https://www.torproject.org//eff/tor-legal-faq.html">Tor Legal FAQ</a></li>
|
2008-03-22 19:53:09 +01:00
|
|
|
</ol>
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
That being said, if you still have a complaint about the router, you may
|
|
|
|
|
email the <a href="mailto:FIXME_YOUR_EMAIL_ADDRESS">maintainer</a>. If
|
|
|
|
|
complaints are related to a particular service that is being abused, I will
|
|
|
|
|
consider removing that service from my exit policy, which would prevent my
|
2008-05-15 09:32:11 +02:00
|
|
|
router from allowing that traffic to exit through it. I can only do this on an
|
|
|
|
|
IP+destination port basis, however. Common P2P ports are
|
2008-03-22 19:53:09 +01:00
|
|
|
already blocked.
|
|
|
|
|
|
2008-05-15 09:32:11 +02:00
|
|
|
<p>You also have the option of blocking this IP address and others on
|
|
|
|
|
the Tor network if you so desire. The Tor project provides a <a
|
2008-05-15 09:26:05 +02:00
|
|
|
href="https://www.torproject.org/cvs/tor/contrib/exitlist">python script</a> to
|
2008-03-22 19:53:09 +01:00
|
|
|
extract all IP addresses of Tor exit nodes, and an official <a
|
2008-05-15 09:26:05 +02:00
|
|
|
href="http://exitlist.torproject.org/">DNSRBL</a> is also available to
|
2008-05-15 09:32:11 +02:00
|
|
|
determine if a given IP address is actually a Tor exit server. Please
|
|
|
|
|
be considerate
|
2008-03-22 19:53:09 +01:00
|
|
|
when using these options. It would be unfortunate to deny all Tor users access
|
2008-05-15 09:26:05 +02:00
|
|
|
to your site indefinitely simply because of a few bad apples.
|
2008-03-22 19:53:09 +01:00
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
2008-05-15 09:26:05 +02:00
|
|
|
|
