Roger Dingledine commited on 2009-06-24 07:43:47
Zeige 1 geänderte Dateien mit 23 Einfügungen und 27 Löschungen.
... | ... |
@@ -118,10 +118,13 @@ and make sure it's owned by the user that will be running tor. --> |
118 | 118 |
|
119 | 119 |
</ul></li> |
120 | 120 |
|
121 |
-<li> If you are using a firewall, open a hole in your firewall so |
|
122 |
-incoming connections can reach the ports you configured (ORPort, plus |
|
123 |
-DirPort if you enabled it). Make sure you allow all outgoing connections, |
|
124 |
-so your relay can reach the other Tor relays. |
|
121 |
+<li>If you are using a firewall, open a hole in your firewall |
|
122 |
+so incoming connections can reach the ports you configured |
|
123 |
+(ORPort, plus DirPort if you enabled it). If you have a |
|
124 |
+hardware firewall (Linksys box, cablemodem, etc) you might like <a |
|
125 |
+href="http://portforward.com/">portforward.com</a>. Also, make sure you |
|
126 |
+allow all <em>outgoing</em> connections, so your relay can reach the |
|
127 |
+other Tor relays. |
|
125 | 128 |
</li> |
126 | 129 |
|
127 | 130 |
<li>Restart your relay. If it <a |
... | ... |
@@ -133,18 +136,10 @@ any warnings</a>, address them. |
133 | 136 |
href="http://archives.seul.org/or/announce/">or-announce</a> |
134 | 137 |
mailing list. It is very low volume, and it will keep you informed |
135 | 138 |
of new stable releases. You might also consider subscribing to <a |
136 |
-href="http://archives.seul.org/or/talk/">or-talk</a> (higher volume), |
|
137 |
-where new development releases are announced. |
|
139 |
+href="<page documentation>#MailingLists">the higher-volume Tor lists</a> |
|
140 |
+too. |
|
138 | 141 |
</li> |
139 | 142 |
|
140 |
-<li> |
|
141 |
-Have a look at the manual. |
|
142 |
-The <a href="<page tor-manual>">manual</a> for the |
|
143 |
-latest stable version provides a list of all the possible configuration |
|
144 |
-options for both clients and relays. |
|
145 |
-If you are running the development version of Tor, the manual is available |
|
146 |
-<a href="<page tor-manual-dev>">here</a>. |
|
147 |
-</li> |
|
148 | 143 |
</ol> |
149 | 144 |
|
150 | 145 |
<hr /> |
... | ... |
@@ -154,7 +149,8 @@ If you are running the development version of Tor, the manual is available |
154 | 149 |
|
155 | 150 |
<p>As soon as your relay manages to connect to the network, it will |
156 | 151 |
try to determine whether the ports you configured are reachable from |
157 |
-the outside. This may take up to 20 minutes. Look for a |
|
152 |
+the outside. This step is usually fast, but may take up to 20 |
|
153 |
+minutes. Look for a |
|
158 | 154 |
<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">log |
159 | 155 |
entry</a> like |
160 | 156 |
<tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt> |
... | ... |
@@ -164,7 +160,7 @@ testing the IP and port you think it should be testing, etc. |
164 | 160 |
</p> |
165 | 161 |
|
166 | 162 |
<p>When it decides that it's reachable, it will upload a "server |
167 |
-descriptor" to the directories. This will let clients know |
|
163 |
+descriptor" to the directories, to let clients know |
|
168 | 164 |
what address, ports, keys, etc your relay is using. You can <a |
169 | 165 |
href="http://moria.seul.org:9032/tor/status/authority">load one of |
170 | 166 |
the network statuses manually</a> and |
... | ... |
@@ -182,19 +178,19 @@ We recommend the following steps as well: |
182 | 178 |
</p> |
183 | 179 |
|
184 | 180 |
<p> |
185 |
-8. Read |
|
186 |
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">this document</a> |
|
181 |
+6. Read |
|
182 |
+<a href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">about operational security</a> |
|
187 | 183 |
to get ideas how you can increase the security of your relay. |
188 | 184 |
</p> |
189 | 185 |
|
190 | 186 |
<p> |
191 |
-9. If you want to run more than one relay that's great, but please set <a |
|
187 |
+7. If you want to run more than one relay that's great, but please set <a |
|
192 | 188 |
href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">the |
193 | 189 |
MyFamily option</a> in all your relays' configuration files. |
194 | 190 |
</p> |
195 | 191 |
|
196 | 192 |
<p> |
197 |
-10. Decide about rate limiting. Cable modem, DSL, and other users |
|
193 |
+8. Decide about rate limiting. Cable modem, DSL, and other users |
|
198 | 194 |
who have asymmetric bandwidth (e.g. more down than up) should |
199 | 195 |
rate limit to their slower bandwidth, to avoid congestion. See the <a |
200 | 196 |
href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate |
... | ... |
@@ -202,7 +198,7 @@ limiting FAQ entry</a> for details. |
202 | 198 |
</p> |
203 | 199 |
|
204 | 200 |
<p> |
205 |
-11. Back up your Tor relay's private key (stored in "keys/secret_id_key" |
|
201 |
+9. Back up your Tor relay's private key (stored in "keys/secret_id_key" |
|
206 | 202 |
in your DataDirectory). This is your relay's "identity," and |
207 | 203 |
you need to keep it safe so nobody can read the traffic that goes |
208 | 204 |
through your relay. This is the critical file to keep if you need to <a |
... | ... |
@@ -212,7 +208,7 @@ or restore your Tor relay</a> if something goes wrong. |
212 | 208 |
|
213 | 209 |
<p> |
214 | 210 |
|
215 |
-12. If you control the name servers for your domain, consider setting your |
|
211 |
+10. If you control the name servers for your domain, consider setting your |
|
216 | 212 |
reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when |
217 | 213 |
other people see the address in their web logs, they will more quickly |
218 | 214 |
understand what's going on. Adding the <a |
... | ... |
@@ -223,7 +219,7 @@ complaints to you and your ISP if you are running an exit node. |
223 | 219 |
</p> |
224 | 220 |
|
225 | 221 |
<p> |
226 |
-13. If your computer isn't running a webserver, please consider |
|
222 |
+11. If your computer isn't running a webserver, please consider |
|
227 | 223 |
changing your ORPort to 443 and your DirPort to 80. Many Tor |
228 | 224 |
users are stuck behind firewalls that only let them browse the |
229 | 225 |
web, and this change will let them reach your Tor relay. Win32 |
... | ... |
@@ -238,7 +234,7 @@ ports are 22, 110, and 143. |
238 | 234 |
</p> |
239 | 235 |
|
240 | 236 |
<p> |
241 |
-14. If your Tor relay provides other services on the same IP address |
|
237 |
+12. If your Tor relay provides other services on the same IP address |
|
242 | 238 |
— such as a public webserver — make sure that connections to the |
243 | 239 |
webserver are allowed from the local host too. You need to allow these |
244 | 240 |
connections because Tor clients will detect that your Tor relay is the <a |
... | ... |
@@ -249,7 +245,7 @@ explicitly reject them in your exit policy. |
249 | 245 |
</p> |
250 | 246 |
|
251 | 247 |
<p> |
252 |
-15. (Unix only). Make a separate user to run the relay. If you |
|
248 |
+13. (Unix only). Make a separate user to run the relay. If you |
|
253 | 249 |
installed the OS X package or the deb or the rpm, this is already |
254 | 250 |
done. Otherwise, you can do it by hand. (The Tor relay doesn't need to |
255 | 251 |
be run as root, so it's good practice to not run it as root. Running |
... | ... |
@@ -260,7 +256,7 @@ into a chroot jail</a>.) |
260 | 256 |
</p> |
261 | 257 |
|
262 | 258 |
<p> |
263 |
-16. (Unix only.) Your operating system probably limits the number |
|
259 |
+14. (Unix only.) Your operating system probably limits the number |
|
264 | 260 |
of open file descriptors per process to 1024 (or even less). If you |
265 | 261 |
plan to be running a fast exit node, this is probably not enough. On |
266 | 262 |
Linux, you should add a line like "toruser hard nofile 8192" to your |
... | ... |
@@ -270,7 +266,7 @@ out and log back in if you run it yourself). |
270 | 266 |
</p> |
271 | 267 |
|
272 | 268 |
<p> |
273 |
-17. If you installed Tor via some package or installer, it probably starts |
|
269 |
+15. If you installed Tor via some package or installer, it probably starts |
|
274 | 270 |
Tor for you automatically on boot. But if you installed from source, |
275 | 271 |
you may find the initscripts in contrib/tor.sh or contrib/torctl useful. |
276 | 272 |
</p> |
277 | 273 |