mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-20 10:12:15 +01:00
Code Issues Projects Releases Wiki Activity

Add Tor exit node notice page to contrib.

Browse Source 
svn:r14155
This commit is contained in:
Mike Perry 2008-03-22 18:53:09 +00:00
parent f5215002e2
commit 0b88a1c579
1 changed files with 123 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

123
contrib/tor-exit-notice.html Normal file
View File

@ -0,0 +1,123 @@
<html>
<head>
<title>This is a Tor Exit Router</title>
<!--
This notice is intended to be placed on a virtual host for a domain that
your Tor exit node IP reverse resolves to so that people who may be about
to file an abuse complaint would check it first before bothering you or
your ISP. Ex:
http://tor-exit.yourdomain.org or http://tor-readme.yourdomain.org.
This type of setup has proven very effective at reducing abuse complaints
for exit node operators.
There are a few places in this document that you may want to customize.
They are marked with FIXME.
-->
</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
href="http://tor.eff.org/index.html">Tor Anonymous Network</a>, which is
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>
<!-- FIXME: you should probably grab your own copy of tor-route.png
and serve it locally -->
<center><a href="http://tor.eff.org/overview.html.en">
<img src="http://tor-exit.fscked.org/tor-route.png"></a></center>
<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>
<!-- FIXME: May or may not be US-only. Some non-US tor nodes have in
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
<a href="http://tor.eff.org/eff/tor-dmca-response.html">EFF's prepared
response</a> for more information on this matter.
<p>For more information, please consult the following documentation:
<ol>
<li><a href="http://tor.eff.org/overview.html">Tor Overview</a></li>
<li><a href="http://tor.eff.org/faq-abuse.html">Tor Abuse FAQ</a></li>
<li><a href="http://tor.eff.org//eff/tor-legal-faq.html">Tor Legal FAQ</a></li>
</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
router from allowing that traffic to exit through it. I can only do this on a
IP+destination port basis, however. Common P2P and IRC ports are
already blocked.
<p>You also have the option of blocking this IP and others on the Tor network
if you so desire. The Tor project provides a <a
href="http://tor.eff.org/cvs/tor/contrib/exitlist">python script</a> to
extract all IP addresses of Tor exit nodes, and an official <a
href="http://exitlist.torproject.org">DNSRBL</a> is also available to
determine if a given IP is actually a Tor exit server. Please be considerate
when using these options. It would be unfortunate to deny all Tor users access
to your site indefinitely simply because of a few bad apples.
</body>
</html>