Roger Dingledine commited on 2010-03-18 10:06:10
Zeige 1 geänderte Dateien mit 7 Einfügungen und 3 Löschungen.
... | ... |
@@ -170,7 +170,7 @@ can guess for you whether your browser is configured to point to Tor. |
170 | 170 |
<br /> |
171 | 171 |
This project would make use of <a |
172 | 172 |
href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, |
173 |
-a set of Python scripts to interact with Tor; the project would be |
|
173 |
+a set of Python scripts to interact with Tor, |
|
174 | 174 |
to figure out how our Tor Exit Checker should actually work, and then |
175 | 175 |
build it — probably in Python since Torflow is in Python. The main |
176 | 176 |
goal is to reduce false positives as much as possible, by making sure |
... | ... |
@@ -179,8 +179,12 @@ the testing phase concludes quickly, and making sure the answers get |
179 | 179 |
passed to the Check script quickly. As a bonus, we should standardize |
180 | 180 |
(specify) the format of the exitAddresses file, and rewrite the <a |
181 | 181 |
href="https://svn.torproject.org/svn/check/trunk/cgi-bin/TorBulkExitList.py">Tor |
182 |
-Bulk Exit List</a> script to use that file rather than its current |
|
183 |
-horrible DNS hacks. |
|
182 |
+Bulk Exit List</a> script to use that file rather than its current <a |
|
183 |
+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=1019">horrible |
|
184 |
+DNS hacks</a>. As an extra bonus, we should work with Freenode, OFTC, |
|
185 |
+and/or other IRC networks to make sure that the scripts we offer are |
|
186 |
+actually the scripts they want, in terms of accurately identifying which |
|
187 |
+of their users are coming from the Tor network. |
|
184 | 188 |
<br /> |
185 | 189 |
You can fetch the <a href="git://git.torproject.org/git/tordnsel">latest |
186 | 190 |
tordnsel</a> via git. |
187 | 191 |