link to the wiki gsoc blurb. plus add another pony.
Roger Dingledine

Roger Dingledine commited on 2007-03-15 12:54:42
Zeige 1 geänderte Dateien mit 14 Einfügungen und 7 Löschungen.

... ...
@@ -103,16 +103,18 @@ SSL <a href="<page documentation>#Developers">SVN repository?</a></li>
103 103
 
104 104
 <a id="Coding"></a>
105 105
 <h2><a class="anchor" href="#Coding">Coding and Design</a></h2>
106
-<p>Want to spend your Google Summer of Code working on Tor? Great. More
107
-details coming soon. In the mean time, see if any of these ideas catch
106
+<p>Want to spend your <a href="http://code.google.com/soc/">Google Summer
107
+of Code</a> working on Tor? Great.
108
+<a href="http://wiki.noreply.org/noreply/TheOnionRouter/SummerOfCode">Read
109
+more about Tor and GSoC</a>, and see if any of the below ideas catch
108 110
 your eye.</p>
109 111
 <ol>
110 112
 <li>Tor servers don't work well on Windows XP. On
111
-Windows, Tor uses the standard <tt>select</tt> system
113
+Windows, Tor uses the standard <tt>select()</tt> system
112 114
 call, which uses space in the non-page pool. This means
113 115
 that a medium sized Tor server will empty the non-page pool, <a
114 116
 href="http://wiki.noreply.org/noreply/TheOnionRouter/WindowsBufferProblems">causing
115
-havoc and crashes</a>. We should probably be using overlapped IO
117
+havoc and system crashes</a>. We should probably be using overlapped IO
116 118
 instead. One solution would be to teach libevent how to use overlapped IO
117 119
 rather than select() on Windows, and then adapt Tor to the new libevent
118 120
 interface.</li>
... ...
@@ -144,11 +146,14 @@ and well-documented USB image for Tor and supporting applications. A
144 146
 lot of the hard part here is deciding what configurations are secure,
145 147
 documentating these decisions, and making something that is easy to
146 148
 maintain going forward.</li>
149
+<li>Our preferred graphical front-end for Tor, named
150
+<a href="http://vidalia-project.net/">Vidalia</a>, needs all sorts
151
+of development work.</li>
147 152
 <li>We need to actually start building our <a href="<page
148 153
 documentation>#DesignDoc">blocking-resistance design</a>. This involves
149
-fleshing out the design, modifying many different pieces of Tor, working
150
-on a <a href="http://vidalia-project.net/">GUI</a> that's intuitive,
151
-and planning for deployment.</li>
154
+fleshing out the design, modifying many different pieces of Tor, adapting
155
+<a href="http://vidalia-project.net/">Vidalia</a> so it supports the
156
+new features, and planning for deployment.</li>
152 157
 <li>We need a flexible simulator framework for studying end-to-end
153 158
 traffic confirmation attacks. Many researchers have whipped up ad hoc
154 159
 simulators to support their intuition either that the attacks work
... ...
@@ -208,6 +213,8 @@ UDP</a> &mdash; please let us know what's wrong with it.</li>
208 213
 <li>We're not that far from having IPv6 support for destination addresses
209 214
 (at exit nodes). If you care strongly about IPv6, that's probably the
210 215
 first place to start.</li>
216
+<li><i>Don't see your idea here? We probably need it anyway! Contact
217
+us and find out.</i></li>
211 218
 </ol>
212 219
 
213 220
 <a id="Research"></a>
214 221