Browse code
Fix #9736
Sebastian Hahn authored on 19/10/2014 15:09:26
Showing 1 changed files
| ... | ... |
@@ -6,9 +6,9 @@ for Tor exit nodes. The implementation is available at |
| 6 | 6 |
|
| 7 | 7 |
https://www.torproject.org/tordnsel/dist/ |
| 8 | 8 |
|
| 9 |
-The design and its rationale are described in the Tor sources at |
|
| 9 |
+The design and its rationale were described in the Tor sources, see |
|
| 10 | 10 |
|
| 11 |
- /doc/contrib/torel-design.txt |
|
| 11 |
+ https://gitweb.torproject.org/tordnsel.git/blob/HEAD:/doc/torel-design.txt |
|
| 12 | 12 |
|
| 13 | 13 |
This document is an attempt to make sense of the exit list format that |
| 14 | 14 |
TorDNSEL publishes without the original TorDNSEL author being around. |
Browse code
Add the exitlist file to the website so that it doesn't get automatically removed anymore.
Sebastian Hahn authored on 01/05/2011 12:23:27
Showing 1 changed files
| 1 | 1 |
new file mode 100644 |
| ... | ... |
@@ -0,0 +1,46 @@ |
| 1 |
+ |
|
| 2 |
+ TorDNSEL Exit List Format |
|
| 3 |
+ |
|
| 4 |
+TorDNSEL is an implementation of the active testing, DNS-based exit list |
|
| 5 |
+for Tor exit nodes. The implementation is available at |
|
| 6 |
+ |
|
| 7 |
+ https://www.torproject.org/tordnsel/dist/ |
|
| 8 |
+ |
|
| 9 |
+The design and its rationale are described in the Tor sources at |
|
| 10 |
+ |
|
| 11 |
+ /doc/contrib/torel-design.txt |
|
| 12 |
+ |
|
| 13 |
+This document is an attempt to make sense of the exit list format that |
|
| 14 |
+TorDNSEL publishes without the original TorDNSEL author being around. |
|
| 15 |
+ |
|
| 16 |
+ |
|
| 17 |
+TorDNSEL publishes its exit test results in a single document with entries |
|
| 18 |
+using the following format. The document consists of an arbitrary number |
|
| 19 |
+of entries each consisting of four or more lines: (ExitNode | Published | |
|
| 20 |
+LastStatus | ExitAddress*)*. In the format below, keywords are written in |
|
| 21 |
+double quotes and spaces and newlines are explicitly marked as SP and NL: |
|
| 22 |
+ |
|
| 23 |
+ "ExitNode" SP fingerprint NL |
|
| 24 |
+ |
|
| 25 |
+ The identity of the relay in upper-case hex characters. This |
|
| 26 |
+ fingerprint corresponds to the fingerprint in v2 and v3 network status |
|
| 27 |
+ documents as specified in /doc/spec/dir-spec.txt in the Tor sources. |
|
| 28 |
+ |
|
| 29 |
+ "Published" SP YYYY-MM-DD SP HH:MM:SS NL |
|
| 30 |
+ |
|
| 31 |
+ The publication time, in UTC, of the most recent relay descriptor that |
|
| 32 |
+ was known when the test was initiated. No further test is initiated |
|
| 33 |
+ until the relay publishes a new descriptor. |
|
| 34 |
+ |
|
| 35 |
+ "LastStatus" SP YYYY-MM-DD SP HH:MM:SS NL |
|
| 36 |
+ |
|
| 37 |
+ The last time, in UTC, when the relay was seen in a v2 network status |
|
| 38 |
+ document. A relay is discarded from the list if it was not seen in a |
|
| 39 |
+ network status for at least 48 hours. |
|
| 40 |
+ |
|
| 41 |
+ "ExitAddress" SP address SP YYYY-MM-DD SP HH:MM:SS NL |
|
| 42 |
+ |
|
| 43 |
+ One or more test results for this relay consisting of the found exit |
|
| 44 |
+ address and the time, in UTC, when the test was performed. A test is |
|
| 45 |
+ discarded from the list if it is older than 48 hours. |
|
| 46 |
+ |