tor-exit-notice.html 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141
  1. <?xml version="1.0"?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  3. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  4. <html xmlns="http://www.w3.org/1999/xhtml">
  5. <head>
  6. <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
  7. <title>This is a Tor Exit Router</title>
  8. <!--
  9. This notice is intended to be placed on a virtual host for a domain that
  10. your Tor exit node IP reverse resolves to so that people who may be about
  11. to file an abuse complaint would check it first before bothering you or
  12. your ISP. Ex:
  13. http://tor-exit.yourdomain.org or http://tor-readme.yourdomain.org.
  14. This type of setup has proven very effective at reducing abuse complaints
  15. for exit node operators.
  16. There are a few places in this document that you may want to customize.
  17. They are marked with FIXME.
  18. -->
  19. </head>
  20. <body>
  21. <p style="text-align:center; font-size:xx-large; font-weight:bold">This is a Tor Exit Router</p>
  22. <p>
  23. the traffic coming from this IP. This router is part of the <a
  24. href="https://www.torproject.org/">Tor Anonymity Network</a>, which is
  25. dedicated to <a href="https://www.torproject.org/overview.html">providing
  26. privacy</a> to people who need it most: average computer users. This
  27. router IP should be generating no other traffic, unless it has been
  28. compromised.</p>
  29. <!-- FIXME: you should probably grab your own copy of how_tor_works_thumb.png
  30. and serve it locally -->
  31. <p style="text-align:center">
  32. <a href="https://www.torproject.org/overview.html">
  33. <img src="https://www.torproject.org/images/how_tor_works_thumb.png" alt="How Tor works" style="border-style:none"/>
  34. </a></p>
  35. <p>
  36. Tor sees use by <a href="https://www.torproject.org/torusers.html">many
  37. important segments of the population</a>, including whistle blowers,
  38. journalists, Chinese dissidents skirting the Great Firewall and oppressive
  39. censorship, abuse victims, stalker targets, the US military, and law
  40. enforcement, just to name a few. While Tor is not designed for malicious
  41. computer users, it is true that they can use the network for malicious ends.
  42. In reality however, the actual amount of <a
  43. href="https://www.torproject.org/faq-abuse.html">abuse</a> is quite low. This
  44. is largely because criminals and hackers have significantly better access to
  45. privacy and anonymity than do the regular users whom they prey upon. Criminals
  46. can and do <a
  47. href="http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html">build,
  48. sell, and trade</a> far larger and <a
  49. href="http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_distributing_your.html">more
  50. powerful networks</a> than Tor on a daily basis. Thus, in the mind of this
  51. operator, the social need for easily accessible censorship-resistant private,
  52. anonymous communication trumps the risk of unskilled bad actors, who are
  53. almost always more easily uncovered by traditional police work than by
  54. extensive monitoring and surveillance anyway.</p>
  55. <p>
  56. In terms of applicable law, the best way to understand Tor is to consider it a
  57. network of routers operating as common carriers, much like the Internet
  58. backbone. However, unlike the Internet backbone routers, Tor routers
  59. explicitly do not contain identifiable routing information about the source of
  60. a packet, and no single Tor node can determine both the origin and destination
  61. of a given transmission.</p>
  62. <p>
  63. As such, there is little the operator of this router can do to help you track
  64. the connection further. This router maintains no logs of any of the Tor
  65. traffic, so there is little that can be done to trace either legitimate or
  66. illegitimate traffic (or to filter one from the other). Attempts to
  67. seize this router will accomplish nothing.</p>
  68. <!-- FIXME: US-Only section. Remove if you are a non-US operator -->
  69. <p>
  70. Furthermore, this machine also serves as a carrier of email, which means that
  71. its contents are further protected under the ECPA. <a
  72. href="http://www4.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002707----000-.html">18
  73. USC 2707</a> explicitly allows for civil remedies ($1000/account
  74. <i><b>plus</b></i> legal fees)
  75. in the event of a seizure executed without good faith or probable cause (it
  76. should be clear at this point that traffic with an originating IP address of
  77. FIXME_DNS_NAME should not constitute probable cause to seize the
  78. machine). Similar considerations exist for 1st amendment content on this
  79. machine.</p>
  80. <!-- FIXME: May or may not be US-only. Some non-US tor nodes have in
  81. fact reported DMCA harassment... -->
  82. <p>
  83. If you are a representative of a company who feels that this router is being
  84. used to violate the DMCA, please be aware that this machine does not host or
  85. contain any illegal content. Also be aware that network infrastructure
  86. maintainers are not liable for the type of content that passes over their
  87. equipment, in accordance with <a
  88. href="http://www4.law.cornell.edu/uscode/html/uscode17/usc_sec_17_00000512----000-.html">DMCA
  89. "safe harbor" provisions</a>. In other words, you will have just as much luck
  90. sending a takedown notice to the Internet backbone providers. Please consult
  91. <a href="https://www.torproject.org/eff/tor-dmca-response.html">EFF's prepared
  92. response</a> for more information on this matter.</p>
  93. <p>For more information, please consult the following documentation:</p>
  94. <ol>
  95. <li><a href="https://www.torproject.org/overview.html">Tor Overview</a></li>
  96. <li><a href="https://www.torproject.org/faq-abuse.html">Tor Abuse FAQ</a></li>
  97. <li><a href="https://www.torproject.org/eff/tor-legal-faq.html">Tor Legal FAQ</a></li>
  98. </ol>
  99. <p>
  100. That being said, if you still have a complaint about the router, you may
  101. email the <a href="mailto:FIXME_YOUR_EMAIL_ADDRESS">maintainer</a>. If
  102. complaints are related to a particular service that is being abused, I will
  103. consider removing that service from my exit policy, which would prevent my
  104. router from allowing that traffic to exit through it. I can only do this on an
  105. IP+destination port basis, however. Common P2P ports are
  106. already blocked.</p>
  107. <p>
  108. You also have the option of blocking this IP address and others on
  109. the Tor network if you so desire. The Tor project provides a <a
  110. href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">python script</a> to
  111. extract all IP addresses of Tor exit nodes, and an official <a
  112. href="https://www.torproject.org/tordnsel/">DNSRBL</a> is also available to
  113. determine if a given IP address is actually a Tor exit server. Please
  114. be considerate
  115. when using these options. It would be unfortunate to deny all Tor users access
  116. to your site indefinitely simply because of a few bad apples.</p>
  117. </body>
  118. </html>