Roger Dingledine commited on 2008-09-10 05:22:54
Zeige 1 geänderte Dateien mit 4 Einfügungen und 8 Löschungen.
... | ... |
@@ -288,20 +288,16 @@ and you should keep in mind that exit policies can change (as well as |
288 | 288 |
the overall list of nodes in the network).</p> |
289 | 289 |
|
290 | 290 |
<p>If you really want to do this, we provide a |
291 |
-<a href="<svnsandbox>contrib/exitlist">Python script to parse the Tor |
|
292 |
-directory</a>. Note that this script won't give you a perfect list |
|
293 |
-of IP addresses that might connect to you using Tor, since some Tor |
|
294 |
-relays might exit from other addresses than the one they publish. |
|
295 |
-For a more accurate approach (with perhaps an easier interface for |
|
296 |
-you), consider the <a href="http://exitlist.torproject.org/">TorDNSEL |
|
297 |
-service</a>. |
|
291 |
+<a href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">Tor |
|
292 |
+exit relay list</a> or a |
|
293 |
+<a href="<page tordnsel/index>">DNS-based list you can query</a>. |
|
298 | 294 |
</p> |
299 | 295 |
|
300 | 296 |
<p> |
301 | 297 |
(Some system administrators block ranges of IP addresses because of |
302 | 298 |
official policy or some abuse pattern, but some have also asked about |
303 | 299 |
whitelisting Tor exit relays because they want to permit access to their |
304 |
-systems using Tor. These scripts are usable for whitelisting as well.) |
|
300 |
+systems only using Tor. These scripts are usable for whitelisting as well.) |
|
305 | 301 |
</p> |
306 | 302 |
|
307 | 303 |
<a id="TracingUsers"></a> |
308 | 304 |