Chris Palmer commited on 2004-12-23 22:46:09
Zeige 1 geänderte Dateien mit 188 Einfügungen und 0 Löschungen.
... | ... |
@@ -0,0 +1,188 @@ |
1 |
+<html> |
|
2 |
+ |
|
3 |
+<head> |
|
4 |
+<title>Legal FAQ for Tor Server Operators</title> |
|
5 |
+</head> |
|
6 |
+ |
|
7 |
+<body> |
|
8 |
+ |
|
9 |
+<h1>Legal FAQ for Tor Server Operators</h1> |
|
10 |
+ |
|
11 |
+<p><strong>by <a href="http://www.eff.org/">The Electronic Frontier |
|
12 |
+Foundation (EFF)</a>. Last updated 23 Dec 2004.</strong></p> |
|
13 |
+ |
|
14 |
+<p><strong>NOTE:</strong> This FAQ is for informational purposes only |
|
15 |
+and does not constitute legal advice. EFF has not analyzed any |
|
16 |
+particular factual situation or laws in drafting this FAQ, but rather |
|
17 |
+has tried to give a general description of the legal issues surrounding |
|
18 |
+Tor for a general audience. Different factual situations and different |
|
19 |
+legal jurisdictions will result in different answers. Therefore, please |
|
20 |
+do not act on this information alone; instead seek a complete review of |
|
21 |
+your situation with a lawyer licensed to practice in your jurisdiction |
|
22 |
+if you have any specific issues or questions.</p> |
|
23 |
+ |
|
24 |
+<p>Also, if you received this document from anywhere besides <a |
|
25 |
+href="http://tor.eff.org/eff/legal-faq.html">http://tor.eff.org/eff/legal-faq.html</a>, |
|
26 |
+it may be out of date. Follow the link to get the latest version.</p> |
|
27 |
+ |
|
28 |
+<h2>Has anyone ever been sued for running Tor?</h2> |
|
29 |
+ |
|
30 |
+<p><strong>No.</strong> Further, we believe that running a Tor node is |
|
31 |
+lawful under U.S. law.</p> |
|
32 |
+ |
|
33 |
+ |
|
34 |
+<h2>Should I use Tor, or encourage the use of Tor, for illegal purposes |
|
35 |
+such as spamming, harassment, distribution of child porn, or copyright |
|
36 |
+infringement?</h2> |
|
37 |
+ |
|
38 |
+<p><strong>No.</strong> Tor has been developed to be a tool for free |
|
39 |
+speech, privacy and human rights. It is not a tool designed or intended |
|
40 |
+to be used to break the law, either by Tor users or Tor server |
|
41 |
+operators.</p> |
|
42 |
+ |
|
43 |
+<p>We further recommend that you not keep any potentially illegal files |
|
44 |
+on the same machine you use for Tor, nor use that machine for any |
|
45 |
+illegal purpose. Although no Tor server has ever been seized or |
|
46 |
+subpoenaed, the future possibility cannot be ruled out and if that |
|
47 |
+happens, you will want your machine to be clean.</p> |
|
48 |
+ |
|
49 |
+ |
|
50 |
+<h2>Can EFF promise that I won’t get in trouble for running a Tor |
|
51 |
+server?</h2> |
|
52 |
+ |
|
53 |
+<p><strong>No.</strong> All new technologies create legal uncertainties, |
|
54 |
+and Tor is no different. Presently, no court has ever considered any |
|
55 |
+case involving the Tor technology, and we therefore cannot guarantee |
|
56 |
+that you will never face any legal liability as a result of running a |
|
57 |
+Tor server.</p> |
|
58 |
+ |
|
59 |
+ |
|
60 |
+<h2>Will EFF represent me if I get in trouble for running a Tor |
|
61 |
+server?</h2> |
|
62 |
+ |
|
63 |
+<p><strong>Maybe.</strong> While EFF cannot promise legal representation |
|
64 |
+of all Tor server operators, it will assist server operators in |
|
65 |
+assessing the situation and will try to locate qualified legal counsel |
|
66 |
+when necessary. Inquiries to EFF for the purpose of securing legal |
|
67 |
+representation or referrals should be directed to staff attorney Kevin |
|
68 |
+Bankston (US +1 (415) 436-9333 x 126) such inquiries will be kept |
|
69 |
+confidential subject to the limits of the attorney/client privilege. |
|
70 |
+Note that although EFF cannot practice law outside of the U.S., it will |
|
71 |
+still try to assist non-U.S. server operators in finding local |
|
72 |
+representation.</p> |
|
73 |
+ |
|
74 |
+ |
|
75 |
+<h2>Should I contact the Tor developers when I have legal questions |
|
76 |
+about Tor or to inform them if I suspect Tor is being used for illegal |
|
77 |
+purposes?</h2> |
|
78 |
+ |
|
79 |
+<p><strong>No.</strong> Tor’s core developers, Roger Dingledine |
|
80 |
+and Nick Mathewson, are available to answer technical questions, but |
|
81 |
+they are not lawyers and cannot give legal advice. Nor do they have any |
|
82 |
+ability to prevent illegal activity that may occur through Tor servers. |
|
83 |
+Furthermore, your communications with Tor’s core developers are |
|
84 |
+not protected by any legal privilege, so law enforcement or civil |
|
85 |
+litigants could subpoena and obtain any information you give to |
|
86 |
+them.</p> |
|
87 |
+ |
|
88 |
+ |
|
89 |
+<h2>If I receive a request from law enforcement or anyone else for my |
|
90 |
+Tor server’s logs, what should I do?</h2> |
|
91 |
+ |
|
92 |
+<p><strong>Educate them about Tor.</strong> In most instances, properly |
|
93 |
+configured Tor servers will have no useful data for inquiring parties, |
|
94 |
+and you should feel free to educate them on this point. To the extent |
|
95 |
+you do maintain logs, however, you should not disclose them to any third |
|
96 |
+party without first consulting a lawyer. In the U.S., such a disclosure |
|
97 |
+may violate the Electronic Communications Privacy Act, and server |
|
98 |
+operators outside of the U.S. may be subject to similar data protection |
|
99 |
+laws.</p> |
|
100 |
+ |
|
101 |
+<p>You may receive legal inquiries where you are prohibited by law from |
|
102 |
+telling anyone about the request. We believe that, at least in the |
|
103 |
+U.S., such gag orders do not prevent you from talking to a lawyer, |
|
104 |
+including calling a lawyer to find representation. Inquiries to EFF for |
|
105 |
+the purpose of securing legal representation should be directed to staff |
|
106 |
+attorney Kevin Bankston ((US +1 (415) 436-9333 x126). Such inquiries |
|
107 |
+will be kept confidential subject to the limits of the attorney/client |
|
108 |
+privilege.</p> |
|
109 |
+ |
|
110 |
+<p>EFF is currently working on informational materials to help you |
|
111 |
+respond to the most likely types of legal requests or notices, so watch |
|
112 |
+this space.</p> |
|
113 |
+ |
|
114 |
+ |
|
115 |
+<h2>Should I snoop on the plaintext that exits through my Tor |
|
116 |
+server?</h2> |
|
117 |
+ |
|
118 |
+<p><strong>No.</strong> You are technically capable of monitoring or |
|
119 |
+logging plaintext that exits your node, if you modify the Tor source |
|
120 |
+code or install additional software to enable such snooping. However, |
|
121 |
+Tor server operators in the U.S. can create legal and possibly even |
|
122 |
+criminal liability for themselves under state or federal wiretap laws if |
|
123 |
+they affirmatively monitor, log, or disclose Tor users’ |
|
124 |
+communications, while non-U.S. operators may be subject to similar laws. |
|
125 |
+Do not examine the contents of anyone’s communications without |
|
126 |
+first talking to a lawyer.</p> |
|
127 |
+ |
|
128 |
+ |
|
129 |
+<h2>Do Tor’s core developers make any promises about the |
|
130 |
+trustworthiness or reliability of Tor servers that are listed in their |
|
131 |
+directory?</h2> |
|
132 |
+ |
|
133 |
+<p><strong>No.</strong> Although the developers attempt to verify that |
|
134 |
+Tor servers listed in the directory the core developers maintain are |
|
135 |
+stable and have adequate bandwidth, neither they nor EFF can guarantee |
|
136 |
+the personal trustworthiness or reliability of the individuals who run |
|
137 |
+those servers. Tor’s core developers further reserve the right to |
|
138 |
+refuse a Tor server operator’s request to be listed in their |
|
139 |
+directory or to remove any server from their directory for any |
|
140 |
+reason.</p> |
|
141 |
+ |
|
142 |
+ |
|
143 |
+<h2>Is the Tor software subject to any license terms?</h2> |
|
144 |
+ |
|
145 |
+<p><strong>Yes.</strong> The Tor license is included in the software |
|
146 |
+download and reproduced below:</p> |
|
147 |
+ |
|
148 |
+<blockquote> |
|
149 |
+ |
|
150 |
+<p>Copyright (c) 2001-2004, Roger Dingledine<br /> |
|
151 |
+Copyright (c) 2004, Roger Dingledine, Nick Mathewson</p> |
|
152 |
+ |
|
153 |
+<p>Redistribution and use in source and binary forms, with or without |
|
154 |
+modification, are permitted provided that the following conditions are |
|
155 |
+met:</p> |
|
156 |
+ |
|
157 |
+<ul> |
|
158 |
+ |
|
159 |
+<li>Redistributions of source code must retain the above copyright |
|
160 |
+notice, this list of conditions and the following disclaimer.</li> |
|
161 |
+ |
|
162 |
+<li>Redistributions in binary form must reproduce the above copyright |
|
163 |
+notice, this list of conditions and the following disclaimer in the |
|
164 |
+documentation and/or other materials provided with the |
|
165 |
+distribution.</li> |
|
166 |
+ |
|
167 |
+<li>Neither the names of the copyright owners nor the names of its |
|
168 |
+contributors may be used to endorse or promote products derived from |
|
169 |
+this software without specific prior written permission.</li> |
|
170 |
+ |
|
171 |
+<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS |
|
172 |
+“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, |
|
173 |
+BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND |
|
174 |
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE |
|
175 |
+COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, |
|
176 |
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT |
|
177 |
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF |
|
178 |
+USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON |
|
179 |
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
|
180 |
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF |
|
181 |
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p> |
|
182 |
+ |
|
183 |
+</blockquote> |
|
184 |
+ |
|
185 |
+</body> |
|
186 |
+ |
|
187 |
+</html> |
|
188 |
+ |
|
0 | 189 |