Remove some completed or in-progress items from the volunteer.wml page
Nick Mathewson

Nick Mathewson commited on 2006-11-05 18:59:48
Zeige 1 geänderte Dateien mit 7 Einfügungen und 27 Löschungen.

... ...
@@ -10,9 +10,6 @@
10 10
 <ol>
11 11
 <li>Please consider <a href="<page docs/tor-doc-server>">running
12 12
 a server</a> to help the Tor network grow.</li>
13
-<li>Take a look at the <a href="<page gui/index>">Tor GUI Competition</a>, and
14
-contribute to making Tor's interface
15
-and usability better. Free Tor T-shirt for each submission!</li>
16 13
 <li>Tell your friends! Get them to run servers. Get them to run hidden
17 14
 services. Get them to tell their friends.</li>
18 15
 <li>We are looking for funding and sponsors. If you like Tor's goals, please
... ...
@@ -64,7 +61,9 @@ of cron, or perhaps it would sleep until appropriate times and then do
64 61
 its tweak (that's probably more portable). Can somebody write one for us
65 62
 and we'll put it into <a href="<svnsandbox>contrib/">contrib/</a>?
66 63
 This is a good entry for the <a href="<page gui/index>">Tor GUI
67
-competition</a>.</li>
64
+competition</a>.
65
+  <!-- We have a good script to adjust stuff now, right? -NM -->
66
+</li>
68 67
 <li>Tor can <a
69 68
 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ChooseEntryExit">exit
70 69
 the Tor network from a particular exit node</a>, but we should be able
... ...
@@ -91,13 +90,15 @@ it easier for users to manage this risk? What is the risk exactly?</li>
91 90
 functionality for Firefox 1.5+? We hear Tor is much faster when you take
92 91
 Privoxy out of the loop.</li>
93 92
 <li>Please help Matt Edman with the documentation and how-tos for his
94
-<a href="http://vidalia-project.net/">Tor Controller</a>.</li>
93
+Tor controller,
94
+<a href="http://vidalia-project.net/">Vidalia</a>.</li>
95 95
 <li>Evaluate and document
96 96
 <a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">our
97 97
 list of programs</a> that can be configured to use Tor.</li>
98 98
 <li>We need better documentation for dynamically intercepting
99 99
 connections and sending them through Tor. tsocks (Linux), dsocks (BSD),
100
-and freecap (Windows) seem to be good candidates.</li>
100
+and freecap (Windows) seem to be good candidates, as would better
101
+use of our new TransPort feature.</li>
101 102
 <li>We have a huge list of <a href="http://wiki.noreply.org/noreply/TheOnionRouter/SupportPrograms">potentially useful
102 103
 programs that interface to Tor</a>. Which ones are useful in which
103 104
 situations? Please help us test them out and document your results.</li>
... ...
@@ -126,20 +127,6 @@ and signature on a hidden service descriptor so they can't be tricked
126 127
 into giving out fake ones. Second, any reliable distributed storage
127 128
 system will do, as long as it allows authenticated updates, but as far
128 129
 as we know no implemented DHT code supports authenticated updates.</li>
129
-<li>Tor exit servers need to do many DNS resolves in parallel. But
130
-gethostbyname() is poorly designed --- it blocks until it has finished
131
-resolving a query --- so it requires its own thread or process. So Tor
132
-is forced to spawn many separate DNS "worker" threads. There are some
133
-asynchronous DNS libraries out there, but historically they are buggy and
134
-abandoned. Are any of them stable, fast, clean, and free software? (Remember,
135
-Tor uses OpenSSL, and OpenSSL is (probably) not compatible with the GPL, so
136
-any GPL libraries are out of the running.) If so
137
-(or if we can make that so), we should integrate them into Tor. See <a
138
-href="http://archives.seul.org/or/talk/Sep-2005/msg00001.html">Agl's
139
-post</a> for one potential approach. Also see
140
-<a href="http://daniel.haxx.se/projects/c-ares/">c-ares</a> and
141
-<a href="http://www.monkey.org/~provos/libdnsres/">libdnsres</a>.
142
-</li>
143 130
 <li>Tor 0.1.1.x includes support for hardware crypto accelerators via
144 131
 OpenSSL. Nobody has ever tested it, though. Does somebody want to get
145 132
 a card and let us know how it goes?</li>
... ...
@@ -149,17 +136,10 @@ just for buffers. We need better heuristics for when to shrink/expand
149 136
 buffers. Maybe this should be modelled after the Linux kernel buffer
150 137
 design, where you have many smaller buffers that link to each other,
151 138
 rather than monolithic buffers?</li>
152
-<li>Implement reverse DNS requests inside Tor (already specified in
153
-Section 5.4 of <a href="<svnsandbox>doc/tor-spec.txt">tor-spec.txt</a>).</li>
154 139
 <li>Perform a security analysis of Tor with <a
155 140
 href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
156 141
 if there are good fuzzing libraries out there for what we want. Win fame by
157 142
 getting credit when we put out a new release because of you!</li>
158
-<li>How hard is it to patch bind or a
159
-DNS proxy to redirect requests to Tor via our <a
160
-href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#CompatibleApplications">tor-resolve
161
-socks extension</a>? dsocks already does this on BSD. What about to
162
-convert UDP DNS requests to TCP requests and send them through Tor?</li>
163 143
 <li>Tor uses TCP for transport and TLS for link
164 144
 encryption. This is nice and simple, but it means all cells
165 145
 on a link are delayed when a single packet gets dropped, and
166 146