tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 4-optional
4) 
5) #include "head.wmi" TITLE="Tor: Volunteer" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page getinvolved/volunteer>">Volunteer</a>
10)   </div>
11)   <div id="maincol"> 
12)     <!-- PUT CONTENT AFTER THIS TAG -->
13)     <h1>A few things everyone can do now:</h1>
14)     <ol>
15)     <li>Please consider <a href="<page docs/tor-doc-relay>">running
16)     a relay</a> to help the Tor network grow.</li>
17)     <li>Tell your friends! Get them to run relays. Get them to run hidden
18)     services. Get them to tell their friends.</li>
19)     <li>If you like Tor's goals, please <a href="<page donate/donate>">take a moment
20)     to donate to support further Tor development</a>. We're also looking
21)     for more sponsors &mdash; if you know any companies, NGOs, agencies,
22)     or other organizations that want anonymity / privacy / communications
23)     security, let them know about us.</li>
24)     <li>We're looking for more <a href="<page about/torusers>">good examples of Tor
25)     users and Tor use cases</a>. If you use Tor for a scenario or purpose not
26)     yet described on that page, and you're comfortable sharing it with us,
27)     we'd love to hear from you.</li>
28)     </ol>
29)     
30)     <a id="Documentation"></a>
31)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
32)     <ol>
33)     <li>Help translate the web page and documentation into other
34)     languages. See the <a href="<page getinvolved/translation>">translation
35)     guidelines</a> if you want to help out. We especially need Arabic or
36)     Farsi translations, for the many Tor users in censored areas.</li>
37)     <li>Evaluate and document

38)     <a href="<wiki>doc/TorifyHOWTO">our

39)     list of programs</a> that can be configured to use Tor.</li>
40)     <li>We have a huge list of <a

41)     href="<wiki>doc/SupportPrograms">potentially useful

42)     programs that interface to Tor</a>. Which ones are useful in which
43)     situations? Please help us test them out and document your results.</li>
44)     </ol>
45)     
46)     <a id="Advocacy"></a>
47)     <h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
48)     <ol>

49)     <li>Create a presentation that can be used for various user group
50) meetings around the world.</li>

51)     <li>Create a video about the positive uses of Tor, what Tor is,
52)     or how to use it.  Some have already started on <a

53)     href="https://media.torproject.org/video/">Tor's Media server</a>,

54)     <a

55)     href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy">Howcast</a>,

56)     and <a href="http://www.youtube.com/thetorproject">YouTube</a>.</li> 

57)     <li>Create a poster, or a set of posters, around a theme,

58)     such as "Tor for Freedom!".</li>

59)     <li>Create a t-shirt design that incorporates "Congratulations!
60)     You are using Tor!" in any language.</li>

61)     </ol>
62)     

63)     <a id="Projects"></a>
64)     <h2><a class="anchor" href="#Projects">Projects</a></h2>
65)     
66)     <p>
67)     Below are a list of Tor related projects we're developing and/or
68)     maintaining. Most discussions happen on IRC so if you're interested in any
69)     of these (or you have a project idea of your own), then please <a

70)     href="<page about/contact>#irc">join us in #tor-dev</a>. Don't be shy
71)     to ask questions, and don't hesitate to ask even if the main contributors
72)     aren't active at that moment.

73)     </p>
74)     
75)     <table id="projects">
76)       <tr>
77)         <th>Name</th>
78)         <th>Category</th>
79)         <th>Language</th>
80)         <th>Activity</th>
81)         <th>Contributors</th>
82)       </tr>
83)       
84)       <tr>
85)         <td><a href="#project-tor">Tor</a></td>
86)         <td>Core</td>
87)         <td>C</td>
88)         <td>Heavy</td>

89)         <td>nickm, arma, Sebastian</td>

90)       </tr>
91)       
92)       <tr class="alt">

93)         <td>*<a href="#project-jtor">JTor</a></td>
94)         <td>Core</td>
95)         <td>Java</td>
96)         <td>None</td>
97)         <td></td>
98)       </tr>
99)       
100)       <tr>

101)         <td><a href="#project-tbb">TBB</a></td>
102)         <td>Usability</td>

103)         <td>Sys Admin</td>
104)         <td>Moderate</td>

105)         <td>Erinn</td>

106)       </tr>
107)       

108)       <tr class="alt">

109)         <td><a href="#project-tails">Tails</a></td>

110)         <td>Usability</td>

111)         <td>Sys Admin</td>

112)         <td>Heavy</td>

113)         <td><a href="https://tails.boum.org/chat/">#tails</a></td>

114)       </tr>
115)       

116)       <tr>

117)         <td><a href="#project-torsocks">Torsocks</a></td>
118)         <td>Usability</td>
119)         <td>C</td>

120)         <td>None</td>

121)         <td>mwenge</td>
122)       </tr>
123)       

124)       <tr class="alt">

125)         <td>*<a href="#project-torouter">Torouter</a></td>
126)         <td>Usability</td>

127)         <td>Sys Admin</td>

128)         <td>Light</td>
129)         <td>ioerror, Runa</td>
130)       </tr>
131)       

132)       <tr>

133)         <td><a href="#project-vidalia">Vidalia</a></td>
134)         <td>User Interface</td>
135)         <td>C++, Qt</td>
136)         <td>Light</td>
137)         <td>chiiph</td>
138)       </tr>
139)       

140)       <tr class="alt">

141)         <td><a href="#project-arm">Arm</a></td>
142)         <td>User Interface</td>
143)         <td>Python, Curses</td>

144)         <td>Light</td>

145)         <td>atagar</td>
146)       </tr>
147)       

148)       <tr>

149)         <td><a href="#project-orbot">Orbot</a></td>
150)         <td>User Interface</td>
151)         <td>Java</td>

152)         <td>Moderate</td>

153)         <td>n8fr8</td>
154)       </tr>
155)       

156)       <tr class="alt">

157)         <td><a href="#project-torbutton">Torbutton</a></td>
158)         <td>Browser Add-on</td>
159)         <td>Javascript</td>
160)         <td>Moderate</td>
161)         <td>mikeperry</td>
162)       </tr>
163)       

164)       <tr>

165)         <td><a href="#project-obfsproxy">Obfsproxy</a></td>
166)         <td>Client Add-on</td>
167)         <td>C</td>
168)         <td>Moderate</td>
169)         <td>nickm, asn</td>
170)       </tr>
171)       
172)       <tr class="alt">

173)         <td>*<a href="#project-thandy">Thandy</a></td>
174)         <td>Updater</td>
175)         <td>Python</td>
176)         <td>Light</td>

177)         <td>chiiph, Erinn, nickm</td>

178)       </tr>
179)       

180)       <tr>

181)         <td>*<a href="#project-ooni-probe">Ooni Probe</a></td>
182)         <td>Scanner</td>
183)         <td>Python</td>
184)         <td>Moderate</td>
185)         <td>hellais, ioerror</td>
186)       </tr>
187)       
188)       <tr class="alt">

189)         <td><a href="#project-shadow">Shadow</a></td>
190)         <td>Experimentation</td>
191)         <td>C, Python</td>
192)         <td>Moderate</td>
193)         <td>robgjansen</td>
194)       </tr>
195)       
196)       <tr>

197)         <td><a href="#project-torctl">TorCtl</a></td>
198)         <td>Library</td>
199)         <td>Python</td>
200)         <td>Light</td>
201)         <td>mikeperry</td>
202)       </tr>
203)       

204)       <tr class="alt">

205)         <td>*<a href="#project-stem">Stem</a></td>
206)         <td>Library</td>
207)         <td>Python</td>
208)         <td>Heavy</td>
209)         <td>atagar</td>
210)       </tr>
211)       

212)       <tr>

213)         <td><a href="#project-metrics">Metrics</a></td>
214)         <td>Client Service</td>
215)         <td>Java</td>
216)         <td>Heavy</td>
217)         <td>karsten</td>
218)       </tr>
219)       

220)       <tr class="alt">

221)         <td><a href="#project-torstatus">TorStatus</a></td>
222)         <td>Client Service</td>

223)         <td>Python, Django</td>

224)         <td>None</td>
225)         <td></td>
226)       </tr>
227)       

228)       <tr>

229)         <td><a href="#project-weather">Weather</a></td>
230)         <td>Client Service</td>
231)         <td>Python</td>

232)         <td>None</td>

233)         <td>kaner</td>
234)       </tr>
235)       

236)       <tr class="alt">

237)         <td><a href="#project-gettor">GetTor</a></td>
238)         <td>Client Service</td>
239)         <td>Python</td>

240)         <td>None</td>

241)         <td>kaner</td>

242)       </tr>
243)       

244)       <tr>

245)         <td><a href="#project-torcheck">TorCheck</a></td>
246)         <td>Client Service</td>
247)         <td>Python, Perl</td>
248)         <td>None</td>
249)         <td></td>
250)       </tr>
251)       

252)       <tr class="alt">

253)         <td><a href="#project-bridgedb">BridgeDB</a></td>
254)         <td>Backend Service</td>
255)         <td>Python</td>

256)         <td>None</td>

257)         <td>kaner, nickm</td>

258)       </tr>
259)       

260)       <tr>

261)         <td><a href="#project-torflow">TorFlow</a></td>
262)         <td>Backend Service</td>
263)         <td>Python</td>

264)         <td>Moderate</td>

265)         <td>mikeperry</td>
266)       </tr>
267)       

268)       <tr class="alt">

269)         <td>*<a href="#project-torbel">TorBEL</a></td>
270)         <td>Backend Service</td>
271)         <td>Python</td>
272)         <td>None</td>
273)         <td>Sebastian</td>
274)       </tr>
275)     </table>
276)     
277)     <sub>
278)     * Project is still in an alpha state.
279)     </sub>
280)     
281)     <br /><br />
282)     
283)     <a id="project-tor"></a>
284)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
285)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Client&component=Tor+Relay&component=vidalia&order=priority">bug
286)     tracker</a>)</h3>
287)     
288)     <p>
289)     Central project, providing the core software for using and participating in
290)     the Tor network. Numerous people contribute to the project to varying
291)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
292)     </p>
293)     
294)     <p>
295)     <b>Project Ideas:</b><br />
296)     <i><a href="#resistCensorship">Improving Tor's ability to resist
297)     censorship</a></i><br />

298)     <i><a href="#unitTesting">Improve our unit testing process</a></i><br />
299)     <i><a href="#simulateSlowConnections">Simulator for slow Internet connections</a></i>

300)     </p>
301)     

302)     <a id="project-jtor"></a>
303)     <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a
304)     href="https://github.com/brl/JTor">code</a>, <a
305)     href="https://github.com/brl/JTor/issues">bug
306)     tracker</a>)</h3>
307)     
308)     <p>
309)     Java implementation of Tor and successor to <a
310)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
311)     isn't yet complete, and has been inactive since Fall 2010.
312)     </p>
313)     

314)     <a id="project-tbb"></a>
315)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
316)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
317)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+bundles/installation&order=priority">bug
318)     tracker</a>)</h3>
319)     
320)     <p>
321)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
322)     and Firefox preconfigured to work together out of the box. This is actively
323)     being worked on by Erinn Clark.
324)     </p>
325)     
326)     <p>
327)     <b>Project Ideas:</b><br />
328)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
329)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
330)     </p>
331)     

332)     <a id="project-tails"></a>

333)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

334)     href="http://git.immerda.ch/?p=amnesia.git;a=summary">code</a>, <a

335)     href="https://tails.boum.org/bugs/">bug

336)     tracker</a>)</h3>
337)     
338)     <p>

339)     The Amnesic Incognito Live System is a live CD/USB distribution

340)     preconfigured so that everything is safely routed through Tor and leaves no
341)     trace on the local system. This is a merger of the Amnesia and <a
342)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
343)     and still under very active development.
344)     </p>
345)     

346)     <p>
347)     <b>Project Ideas:</b><br />
348)     <i><a href="#tailsStartMenu">Custom GDM3 startup menu, aka.
349)     tails-greeter</a></i><br />
350)     <i><a href="#tailsMetadataAnonymizing">Meta-data anonymizing toolkit for
351)     file publication</a></i><br />
352)     <i><a href="#tailsDebianLive">Improve Debian Live support for
353)     persistence</a></i>
354)     </p>
355)     

356)     <a id="project-torsocks"></a>
357)     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
358)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
359)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
360)     tracker</a>)</h3>
361)     
362)     <p>
363)     Utility for adapting other applications to work with Tor. Development has
364)     slowed and compatibility issues remain with some platforms, but it's
365)     otherwise feature complete.
366)     </p>
367)     
368)     <p>
369)     <b>Project Ideas:</b><br />
370)     <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
371)     </p>
372)     
373)     <a id="project-torouter"></a>
374)     <h3><a

375)     href="<wiki>doc/Torouter">Torouter</a> (<a

376)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
377)     tracker</a>)</h3>
378)     
379)     <p>
380)     Project to provide an easy-to-use, embedded Tor instance for routers. This

381)     had high activity in late 2010, but has since been rather quiet.

382)     </p>
383)     
384)     <a id="project-vidalia"></a>
385)     <h3><a href="<page projects/vidalia>">Vidalia</a> (<a

386)     href="https://gitweb.torproject.org/vidalia.git">code</a>, <a

387)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority">bug
388)     tracker</a>)</h3>
389)     
390)     <p>
391)     The most commonly used user interface for Tor. Matt Edman started the
392)     project in 2006 and brought it to its current stable state. Development
393)     slowed for several years, though Tomás Touceda has since taken a lead with
394)     pushing the project forward.
395)     </p>
396)     
397)     <p>
398)     <b>Project Ideas:</b><br />

399)     <i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i>

400)     </p>
401)     
402)     <a id="project-arm"></a>
403)     <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a

404)     href="https://gitweb.torproject.org/arm.git">code</a>, <a

405)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=arm&order=priority">bug
406)     tracker</a>)</h3>
407)     
408)     <p>
409)     Command-line monitor for Tor. This has been under very active development
410)     by its author, Damian Johnson, since early 2009 to make it a better
411)     general-purpose controller for *nix environments.
412)     </p>
413)     

414)     <!--

415)     <p>
416)     <b>Project Ideas:</b><br />

417)     <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i><br />
418)     <i><a href="#armGui">GUI for Arm</a></i>

419)     </p>

420)     -->

421)     
422)     <a id="project-orbot"></a>
423)     <h3><a href="https://guardianproject.info/apps/orbot/">Orbot</a> (<a

424)     href="https://gitweb.torproject.org/orbot.git">code</a>, <a

425)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Orbot&order=priority">bug
426)     tracker</a>)</h3>
427)     
428)     <p>
429)     Provides Tor on the Android platform. This was under very active
430)     development up through Fall 2010, after which things have been quiet.
431)     </p>
432)     
433)     <p>
434)     <b>Project Ideas:</b><br />

435)     <i><a href="#orbot-torbutton">TorButton for Mobile Firefox 4 or Custom Browser on Android</a></i><br />
436)     <i><a href="#orbot-userInterface">Build a better user interface for Orbot</a></i><br />
437)     <i><a href="#orbot-optimisation">Core Tor mobile optimisation</a></i><br />
438)     <i><a href="#orbot-orlibAndOutreach">Orbot integration library and community outreach</a></i>

439)     </p>
440)     
441)     <a id="project-torbutton"></a>
442)     <h3><a href="<page torbutton/index>">Torbutton</a> (<a
443)     href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
444)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug
445)     tracker</a>)</h3>
446)     
447)     <p>
448)     Firefox addon that addresses many of the client-side threats to browsing
449)     the Internet anonymously. Mike has since continued to adapt it to new
450)     threats, updated versions of Firefox, and possibly <a
451)     href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">Chrome
452)     as well</a>.
453)     </p>
454)     
455)     <p>
456)     <b>Project Ideas:</b><br />
457)     <i><a href="#torbuttonForThunderbird">Torbutton equivalent for Thunderbird</a></i>
458)     </p>
459)     

460)     <a id="project-obfsproxy"></a>
461)     <h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc">Obfsproxy</a> (<a
462)     href="https://gitweb.torproject.org/obfsproxy.git">code</a>, <a
463)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Pluggable+transport&order=priority">bug
464)     tracker</a>)</h3>
465)     
466)     <p>
467)     A proxy that shapes Tor traffic, making it harder for censors to detect and
468)     block Tor.
469)     </p>
470)     

471)     <p>
472)     <b>Project Ideas:</b><br />
473)     <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
474)     <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
475)     <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
476)     </p>
477)     

478)     <a id="project-thandy"></a>
479)     <h3>Thandy (<a
480)     href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>
481)     
482)     <p>
483)     Updater for Tor. The project began in the Summer of 2008 but wasn't
484)     completed. Recently interest in it has been rekindled and many aspects of
485)     its design (including the language it'll be in) are currently in flux.
486)     </p>
487)     

488)     <a id="project-ooni-probe"></a>
489)     <h3>Ooni Probe (<a
490)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
491)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
492)     tracker</a>)</h3>
493)     
494)     <p>
495)     Censorship scanner, checking your local connection for blocked or modified
496)     content.
497)     </p>
498)     

499)     <a id="project-shadow"></a>
500)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
501)     href="https://github.com/shadow">code</a>, <a
502)     href="https://github.com/shadow/shadow/issues">bug
503)     tracker</a>)</h3>
504)     
505)     <p>
506)     Shadow is a discrete-event network simulator that runs the real
507)     Tor software as a plug-in. Shadow is open-source software that enables
508)     accurate, efficient, controlled, and repeatable Tor experimentation.
509)     </p>
510)     

511)     <a id="project-torctl"></a>
512)     <h3>TorCtl (<a
513)     href="https://gitweb.torproject.org/pytorctl.git">code</a>, <a
514)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority">bug
515)     tracker</a>)</h3>
516)     
517)     <p>
518)     Python bindings and utilities for using the Tor control port. It has been
519)     stable for several years, with only minor revisions.
520)     </p>
521)     

522)     <a id="project-stem"></a>
523)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> (<a
524)     href="https://gitweb.torproject.org/stem.git">code</a>, <a
525)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Stem&order=priority">bug
526)     tracker</a>)</h3>
527)     
528)     <p>
529)     Python controller library with a similar scope to TorCtl, but with better
530)     testing, documentation, and API. This project is not yet feature complete.
531)     </p>
532)     

533)     <p>
534)     <b>Project Ideas:</b><br />
535)     <i><a href="#stemPathsupport">Stem PathSupport Capabilities</a></i>
536)     </p>
537)     

538)     <a id="project-metrics"></a>
539)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
540)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
541)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
542)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
543)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
544)     tracker</a>)</h3>
545)     
546)     <p>
547)     Processing and analytics of consensus data, provided to users via the
548)     metrics portal. This has been under active development for several years by
549)     Karsten Loesing.
550)     </p>
551)     

552)     <p>
553)     <b>Project Ideas:</b><br />
554)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
555)     </p>
556)     

557)     <a id="project-torstatus"></a>
558)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorStatus">TorStatus</a> (<a

559)     href="https://gitweb.torproject.org/torstatus.git">code</a>)</h3>

560)     
561)     <p>
562)     Portal providing an overview of the Tor network, and details on any of its
563)     current relays. Though very actively used, this project has been

564)     unmaintained for a long while. The <a
565)     href="https://svn.torproject.org/svn/torstatus/trunk/">original
566)     codebase</a> was written in PHP, and students from Wesleyan wrote the new
567)     Django counterpart.

568)     </p>
569)     
570)     <a id="project-weather"></a>
571)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/Weather">Weather</a> (<a
572)     href="https://gitweb.torproject.org/weather.git">code</a>, <a
573)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Weather&order=priority">bug
574)     tracker</a>)</h3>
575)     
576)     <p>
577)     Provides automatic notification to subscribed relay operators when their
578)     relay's unreachable. This underwent a rewrite by the <a
579)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
580)     in early 2011.
581)     </p>
582)     
583)     <a id="project-gettor"></a>
584)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/EmailAutoResponder">GetTor</a> (<a

585)     href="https://gitweb.torproject.org/gettor.git">code</a>, <a

586)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=GetTor&order=priority">bug
587)     tracker</a>)</h3>
588)     
589)     <p>
590)     E-mail autoresponder providing Tor's packages over SMTP. This has been
591)     relatively unchanged for quite a while.
592)     </p>
593)     
594)     <a id="project-torcheck"></a>
595)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorCheck">TorCheck</a> (<a
596)     href="https://svn.torproject.org/svn/check/trunk/">code</a>, <a
597)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Check&order=priority">bug
598)     tracker</a>)</h3>
599)     
600)     <p>
601)     Provides a simple site for determining if the visitor is using Tor or not.
602)     This has been relatively unchanged for quite a while.
603)     </p>
604)     
605)     <a id="project-bridgedb"></a>
606)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/BridgeDB">BridgeDB</a> (<a
607)     href="https://gitweb.torproject.org/bridgedb.git">code</a>, <a
608)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=BridgeDB&order=priority">bug
609)     tracker</a>)</h3>
610)     
611)     <p>
612)     Backend bridge distributor, handling the various pools they're distributed
613)     in. This was actively developed until Fall of 2010.
614)     </p>
615)     
616)     <a id="project-torflow"></a>
617)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorFlow">TorFlow</a> (<a
618)     href="https://gitweb.torproject.org/torflow.git">code</a>, <a
619)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torflow&order=priority">bug
620)     tracker</a>)</h3>
621)     
622)     <p>
623)     Library and collection of services for actively monitoring the Tor network.
624)     These include the Bandwidth Scanners (measuring throughput of relays) and
625)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
626)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
627)     months later. Both have been under active use since then, but development
628)     has stopped.
629)     </p>
630)     
631)     <a id="project-torbel"></a>
632)     <h3><a
633)     href="https://trac.torproject.org/projects/tor/wiki/projects/TorBulkExitlist">TorBEL</a> (<a
634)     href="https://gitweb.torproject.org/tordnsel.git">code</a>, <a
635)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=TorDNSEL/TorBEL&order=priority">bug
636)     tracker</a>)</h3>
637)     
638)     <p>
639)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
640)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
641)     (though unmaintained) Haskell application for this purpose. The initial
642)     version of TorBEL was started in GSOC 2010 but since then the project has
643)     been inactive.
644)     </p>
645)     

646)     <a id="Coding"></a>
647)     <a id="Summer"></a>

648)     <h2><a class="anchor" href="#Coding">Project Ideas</a></h2>

649)     
650)     <p>
651)     You may find some of these projects to be good <a href="<page

652)     about/gsoc>">Google Summer of Code 2011</a> ideas. We have labelled each idea

653)     with how useful it would be to the overall Tor project (priority), how
654)     much work we expect it would be (effort level), how much clue you should
655)     start with (skill level), and which of our <a href="<page

656)     about/corepeople>">core developers</a> would be good mentors.

657)     If one or more of these ideas looks promising to you, please <a
658)     href="<page about/contact>">contact us</a> to discuss your plans rather than
659)     sending blind applications. You may also want to propose your own project
660)     idea &mdash; which often results in the best applications.
661)     </p>
662)     
663)     <ol>
664)     

665)     <a id="auditTBB"></a>

666)     <li>

667)     <b>Audit Tor Browser Bundles for data leaks</b>

668)     <br>

669)     Priority: <i>High</i>

670)     <br>

671)     Effort Level: <i>High</i>

672)     <br>

673)     Skill Level: <i>Medium</i>

674)     <br>

675)     Likely Mentors: <i>Erinn and Jacob</i>

676)     <p>The Tor Browser Bundle incorporates Tor, Firefox, Polipo, and the Vidalia

677)     user interface (and optionally the <a href="http://pidgin.im/">Pidgin</a>
678)     Instant Messaging client). Components are pre-configured to operate in a
679)     secure way, and it has very few dependencies on the installed operating
680)     system. It has therefore become one of the most easy to use, and popular,

681)     ways to use Tor on Windows.</p>
682)     <p>This project is to identify all of the traces left behind by
683)     using a Tor Browser Bundle on Windows, Mac OS X, or Linux.  Developing
684)     ways to stop, counter, or remove these traces is a final step.</p>
685)     <p>Students should be familiar with operating system analysis,

686)     application development on one or preferably all of Windows, Linux,

687)     and Mac OS X, and be comfortable with C/C++ and shell scripting.</p>
688)     <p>If you would like to help extend or do security auditing for
689)     TBB, please contact Erinn.</p>

690)     </li>
691)     

692)     <a id="firewallProbeTool"></a>
693)     <li>
694)     <b>Develop a fully automatic firewall-probing system</b>
695)     <br>
696)     Priority: <i>High</i>
697)     <br>
698)     Effort Level: <i>Medium to High</i>
699)     <br>
700)     Skill Level: <i>High</i>
701)     <br>
702)     Likely Mentors: <i>Robert Ransom, Nick, Jacob</i>
703)     <p>We would like to have a fully automatic firewall-probing system for
704)     blocking systems with no long-term state (i.e. firewalls that can
705)     examine each connection, but do not change their behaviour for future
706)     connections based on the traffic they have seen).</p>
707)     <p>Ideally, volunteers would only need to set up one or more test servers,
708)     and run the probe client program on a publicly accessible computer
709)     behind the firewall.</p>
710)     <p>The test tool should:</p>
711)     <ul>
712)     <li>generate packet captures on both ends (and send them out to the
713)         extent possible),</li>
714)     <li>cycle through all the SSL configurations we might want to test
715)         through a censorship device, and</li>
716)     <li>also test some other protocols to see whether they are allowed
717)         through the firewall (IMAP and other mail protocols, BitTorrent,
718)         DTLS, etc.).</li>
719)     </ul>
720)     </li>
721)     

722)     <a id="tailsStartMenu"></a>
723)     <li>
724)     <b>Custom GDM3 startup menu, aka. tails-greeter</b>
725)     <br>
726)     Priority: <i>High</i>
727)     <br>
728)     Effort Level: <i>Medium</i>
729)     <br>
730)     Skill Level: <i>Medium to High</i>
731)     <br>
732)     Likely Mentors: <i>intrigeri, anonym</i>

733)     <p>Several major upcoming Tails features need to gather user input at

734)     startup time: bridges support, persistence, MAC address anonymization,
735)     etc.</p>
736)     <p>Existing boot menus lack the graphical widgets and generally

737)     user-friendliness needed. Hence it was decided to implement Tails startup

738)     menu in GDM3: GDM3's default login/password prompt needs to be replaced
739)     with a custom GTK+ application hereby named tails-greeter that allows the
740)     user to provide any input necessary.</p>
741)     <p>Anyone undertaking this project should be familiar with GNU/Linux and
742)     application development; no other skill is required, apart of the ability
743)     to quickly find practical answers in APIs and documentation for many
744)     technologies she knows nothing about: this challenging coding project will
745)     indeed involve getting familiar with some modern GNU/Linux Desktop
746)     technologies such as D-Bus, GNOME and GConf. Python/GTK+ is probably the
747)     best suited language for the task.</p>

748)     <p>For more information see <a href="https://tails.boum.org/todo/boot_menu/">https://tails.boum.org/todo/boot_menu/</a></p>

749)     </li>
750) 

751)     <a id="orbot-torbutton"></a>
752)     <li>
753)     <b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>
754)     <br>
755)     Priority: <i>High</i>
756)     <br>
757)     Effort Level: <i>High</i>
758)     <br>
759)     Skill Level: <i>High</i>
760)     <br>
761)     Likely Mentors: <i>Nathan (n8fr8), Jake, Mike Perry</i>
762)     <p>Initial work has been done on implementing a proxy-setting add-on for
763)     Firefox on Android (see <a
764)     href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a
765)     full port of TorButton needs to be done (dependent upon Firefox 4 port of
766)     TorButton). The other approach is to implement a custom &quot;Tor
767)     Browser&quot; based on Firefox or Webkit browser. See <a
768)     href="http://code.google.com/p/torora/wiki/Android">Torora</a> for progress
769)     on this so far.</p>
770)     </li>
771)     

772)     <a id="obfsproxy-new-transports"></a>
773)     <li>
774)     <b>New and innovative pluggable transports</b>
775)     <br>
776)     Priority: <i>High</i>
777)     <br>
778)     Effort Level: <i>High</i>
779)     <br>
780)     Skill Level: <i>High</i>
781)     <br>
782)     Likely Mentors: <i>asn</i>
783)     <p>Not-very-smart transports like ROT13 and base64 are nice but not super
784)     interesting. Other ideas like bittorrent transports might be relevant,
785)     but you will have to provide security proofs on why they are harder to
786)     detect and block than other less-sophisticated transports.</p>
787)     
788)     <p>The whole point of this project, though, is to come up with new
789)     transports that we haven't already thought of. Be creative.</p>
790)     
791)     <p>Bonus points if your idea is interesting and still implementable
792)     through the summer period.</p>
793)     
794)     <p>More bonus points if it's implemented on top of obfsproxy, or if your
795)     implementation has a pluggable transport interface on top of it (as
796)     specified <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt">here</a>).</p>
797)     </li>
798)     
799)     <a id="obfsproxy-scanning-measures"></a>
800)     <li>
801)     <b>Defensive bridge active scanning measures</b>
802)     <br>
803)     Priority: <i>High</i>
804)     <br>
805)     Effort Level: <i>High</i>
806)     <br>
807)     Skill Level: <i>High</i>
808)     <br>
809)     Likely Mentors: <i>asn</i>
810)     <p>Involves providing good answers to <a
811)     href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html">this
812)     thread</a> as well as concrete implementation plans for it.</p>
813)     
814)     <p>This also involves implementing proposals <a
815)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a>
816)     and <a
817)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p>
818)     </li>
819)     

820)     <a id="orbot-userInterface"></a>
821)     <li>
822)     <b>Build a better user interface for Orbot</b>
823)     <br>
824)     Priority: <i>High</i>
825)     <br>
826)     Effort Level: <i>Medium</i>
827)     <br>
828)     Skill Level: <i>Medium</i>
829)     <br>
830)     Likely Mentors: <i>Nathan (n8fr8), Jake</i>
831)     <p>Improved home screen to show confirmation of connection (via a TorCheck
832)     API call), better statistics about data transferred (up/down), number of
833)     circuits connected, quality of connection and so on. The &quot;Tether
834)     Wifi&quot; Android application is a good model to follow in how it shows a
835)     realtime count of bytes transferred as well as notifications when wifi
836)     clients connect. In addition, better handling of Tor system and error
837)     messages would also be very helpful, include use of standard Android
838)     operating systems notifications. The addition of a wizard or tutorial
839)     walkthrough for novice users to explain to them exactly what is and what is
840)     not anonymized or protected would greatly improve the likelihood they will
841)     use Orbot correctly. All of this should work on the range of screens and
842)     device types now offered for Android, from 2&quot; phone to 10&quot;
843)     Tablet.</p>
844)     </li>
845)     

846)     <a id="resistCensorship"></a>

847)     <li>
848)     <b>Improving Tor's ability to resist censorship</b>

849)     <br>

850)     Priority: <i>Medium to High</i>

851)     <br>

852)     Effort Level: <i>Medium to High</i>

853)     <br>

854)     Skill Level: <i>High</i>

855)     <br>

856)     Likely Mentors: <i>Roger, Nick, Jake, Thomas</i>

857)     <p>The Tor 0.2.1.x series makes <a

858)     href="<svnprojects>design-paper/blocking.html">significant
859)     improvements</a> in resisting national and organizational censorship.
860)     But Tor still needs better mechanisms for some parts of its

861)     anti-censorship design.</p>
862)     <p>One huge category of work is adding features to our <a

863)     href="https://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a>

864)     service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge
865)     relay addresses</a> to users that can't reach the Tor network
866)     directly, but there's an arms race between algorithms for distributing
867)     addresses and algorithms for gathering and blocking them. See <a

868)     href="<blog>bridge-distribution-strategies">our

869)     blog post on the topic</a> as an overview, and then look at <a

870)     href="https://lists.torproject.org/pipermail/tor-dev/2009-December/000666.html">Roger's
871)     or-dev post</a> from December 2009 for more recent thoughts &mdash; lots of

872)     design work remains.</p>
873)     <p>If you want to get more into the guts of Tor itself (C), a more minor problem

874)     we should address is that current Tors can only listen on a single
875)     address/port combination at a time. There's

876)     <a href="<specblob>proposals/118-multiple-orports.txt">a

877)     proposal to address this limitation</a> and allow clients to connect
878)     to any given Tor on multiple addresses and ports, but it needs more

879)     work.</p>
880)     <p>This project could involve a lot of research and design. One of the big

881)     challenges will be identifying and crafting approaches that can still
882)     resist an adversary even after the adversary knows the design, and

883)     then trading off censorship resistance with usability and
884)     robustness.</p>

885)     </li>
886)     

887)     <a id="stemPathsupport"></a>
888)     <li>
889)     <b>Stem PathSupport Capabilities</b>
890)     <br>
891)     Priority: <i>Medium</i>
892)     <br>
893)     Effort Level: <i>High</i>
894)     <br>
895)     Skill Level: <i>Medium</i>
896)     <br>
897)     Likely Mentors: <i>Damian (atagar)</i>
898)     <p><a
899)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a
900)     python controller library for tor. Like it's predecessor, <a
901)     href="#project-torctl">TorCtl</a>, it uses tor's <a
902)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control
903)     protocol</a> to help developers program against the tor process, enabling
904)     them to build things similar to <a href="#project-vidalia">Vidalia</a> and
905)     <a href="#project-arm">arm</a>.</p>
906)     
907)     <p>While TorCtl provided a fine first draft for this sort of functionality,
908)     it has not proved to be extensible nor maintainable. Stem is a rewrite of
909)     TorCtl with a heavy focus on testing, documentation, and providing a
910)     developer friendly API.</p>
911)     
912)     <p>At the moment stem is still very much incomplete, missing several pieces
913)     of functionality that TorCtl provides. This is a project to fix that by
914)     porting TorCtl's <a
915)     href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport
916)     module</a> to stem, writing tests for it, and migrate a couple clients to
917)     use it.</p>
918)     
919)     <p>PathSupport provides applications with programmatic control over how
920)     tor's circuits are built, for instance letting you exit from particular
921)     relays. This is used by projects like <a href="#project-torbel">TorBEL</a>,
922)     <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>.</p>
923)     
924)     <p>This project can be broken into three parts...</p>
925)     
926)     <ol style="list-style-type: decimal">
927)       <li><p>Look at PathSupport's clients to figure out how it is used and
928)       come up with the API that we will use for stem. Note that the goal if
929)       this project is <b>not</b> to simply copy PathSupport, but to make it
930)       better. This task would ideally be done as part of writing the GSoC
931)       application.</p></li>
932)       <li><p>Implement the PathSupport counterpart for stem. This should be
933)       done in an incremental fashion, writing the feature, tests, and going
934)       through a code review before moving on. I'll be pretty anal about making
935)       it as good as we can during these code reviews so plan for this to take a
936)       while. ;)</p></li>
937)       <li><p>The real test of the API that you've developed will come when we
938)       use it in some real applications. Try to migrate a TorCtl client or two
939)       to stem, filling in functionality that we're missing and improving our
940)       API as we discover issues. A particularly good client to start with would
941)       be TorBEL.</p></li>
942)     </ol>
943)     

944)     <a id="geoIPUpgrade"></a>
945)     <li>
946)     <b>Improve our GeoIP file format</b>
947)     <br>
948)     Priority: <i>Medium</i>
949)     <br>
950)     Effort Level: <i>Medium</i>
951)     <br>
952)     Skill Level: <i>Medium to High</i>
953)     <br>
954)     Likely Mentors: <i>Robert Ransom</i>

955)     <p>Currently, Tor bridges and relays read an entire IP-&gt;country database

956)     into memory from a text file during startup.  We would like to
957)     distribute this database and store it on disk in a much more compact

958)     form, and perform IP->country lookups on it in its on-disk format if

959)     possible.</p>

960)     <p>We have <a href='https://trac.torproject.org/projects/tor/ticket/2506'>a
961)     sketch of a design</a> for a moderately optimized format for IPv4 GeoIP
962)     data; this project will involve both implementing the IPv4 format and
963)     designing and implementing a format for IPv6 GeoIP data.</p>

964)     <p>Since the core of this project is researching IPv6 GeoIP data and

965)     designing the IPv6 format, this is not likely to be a good GSoC

966)     project.</p>

967)     </li>
968)     

969)     <!--

970)     <a id="armClientMode"></a>

971)     <li>
972)     <b>Client Mode Use Cases for Arm</b>
973)     <br>
974)     Priority: <i>Medium</i>
975)     <br>
976)     Effort Level: <i>High</i>
977)     <br>
978)     Skill Level: <i>Medium</i>
979)     <br>

980)     Likely Mentors: <i>Damian (atagar)</i>

981)     <p><a href="<page projects/arm>">Arm</a> is a Tor command line status
982)     monitor on *nix environments (Linux, Mac, and BSD). It functions much like
983)     top does, giving a CLI overlay of Tor's bandwidth usage, connections,
984)     configuration, log, etc. Thus far its design has been geared for Tor relay
985)     operators. However, this doesn't need to be the case. This project would be
986)     to expand and simplify arm to make it useful for Tor's client users
987)     too.</p>
988)     
989)     <p>This would include UI design, experimenting, and a lot of python
990)     hacking. Here's some ideas for client functionality arm could provide:</p>
991)     
992)     <ul>
993)       <li>A panel for client connections, showing each hop of the user's
994)       circuits with the ISP, country, and jurisdiction where those relays
995)       reside. Other interesting information would be the circuit's latency, how
996)       long its been around, and its possible exit ports. Some of this will be
997)       pretty tricky and require some experimentation to figure out what
998)       information can be fetched safely (for instance, scraping rdns and whois
999)       lookups could give hints about a relay's ISP, but we'd need to do it on
1000)       all Tor relays to avoid leaking our connections to the resolver).</li>
1001)       
1002)       <li>Options to let the user request new circuits (the &quot;New
1003)       Identity&quot; feature in Vidalia), select the exit country, etc.</li>
1004)       
1005)       <li>A panel showing Internet application and if their connections are
1006)       being routed through Tor or not (giving a warning if there's leaks).</li>
1007)       
1008)       <li>The status of the bridges we're configured to use (ie, are they up?).
1009)       This would include adding control port functionality to Tor for <a
1010)       href="https://trac.torproject.org/projects/tor/ticket/2068">ticket
1011)       2068</a>.</li>
1012)       
1013)       <li>A one click option to set Tor to be a client, relay, or bridge. The
1014)       goal would be to make it trivial for users to voluntarily contribute to
1015)       the Tor network.</li>
1016)       
1017)       <li>Menus as an alternative to hotkeys to make the interface more
1018)       intuitive and usable for beginners (<a
1019)       href="http://gnosis.cx/publish/programming/charming_python_6.html">example</a>).</li>
1020)       
1021)       <li>Look at Vidalia and TorK for ideas and solicit input from the Tor community.</li>
1022)     </ul>
1023)     

1024)     <p>
1025)     More information is available in the following sections of arm's dev notes: <a href="https://trac.torproject.org/projects/tor/wiki/projects/arm#ConnectionListingExpansion">Connection Listing Expansion</a>, <a href="https://trac.torproject.org/projects/tor/wiki/projects/arm#CircuitDetails">Circuit Details</a>, and <a href="https://trac.torproject.org/projects/tor/wiki/projects/arm#ClientModeUseCases">Client Mode Use Cases</a>
1026)     </p>

1027)     </li>

1028)     -->

1029)     

1030)     <a id="metricsSearch"></a>
1031)     <li>
1032)     <b>Searchable Tor descriptor and Metrics data archive</b>
1033)     <br>
1034)     Priority: <i>Medium</i>
1035)     <br>
1036)     Effort Level: <i>Medium</i>
1037)     <br>
1038)     Skill Level: <i>Medium</i>
1039)     <br>
1040)     Likely Mentors: <i>Karsten</i>
1041)     <p>The <a href="https://metrics.torproject.org/data.html">Metrics data archive</a> of Tor relay descriptors and other Tor-related network data has grown to over 100G in size, bz2-compressed.  We have developed two search interfaces: the <a href="https://metrics.torproject.org/relay-search.html">relay search</a> finds relays by nickname, fingerprint, or IP address in a given month; <a href="https://metrics.torproject.org/exonerator-beta.html">ExoneraTor</a> finds whether a given IP address was a relay on a given day.</p>
1042)     
1043)     <p>We'd like to have a more general search application for Tor descriptors and metrics data.  There are more <a href="https://metrics.torproject.org/formats.html">descriptor types</a> that we'd like to include in the search.  The search application should handle most of them and understand some semantics like what's a timestamp, what's an IP address, and what's a link to another descriptor.  Users should then be able to search for arbitrary strings or limit their search to given time periods or IP address ranges.  Descriptors that reference other descriptors should contain links, and descriptors should be able to say from where they are linked.  The goal is to make the archive easily browsable.</p>
1044)     
1045)     <p>The search application shall be separate from the metrics website and shouldn't rely on the metrics website codebase.  The search application will contain hourly updated descriptor data from the metrics website via rsync.  Programming language and database system are not specified yet, though there's a slight preference for Python/Django and Postgres for maintenance reasons.  If there are good reasons to pick something else, e.g, some NoSQL variant or some search application framework, that's fine, too.  Further requirements are that lookups should be really fast and that changes to the search application can be implemented in reasonable time.</p>
1046)     
1047)     <p>Applications for this project should come with a design of the proposed search application, ideally with a proof-of-concept based on a subset of the available data to show that it will be able to handle the 100G+ of data.</p>
1048)     

1049)     <a id="unitTesting"></a>

1050)     <li>
1051)     <b>Improve our unit testing process</b>

1052)     <br>

1053)     Priority: <i>Medium</i>

1054)     <br>

1055)     Effort Level: <i>Medium</i>

1056)     <br>

1057)     Skill Level: <i>Medium</i>

1058)     <br>

1059)     Likely Mentors: <i>Nick, Erinn</i>

1060)     <p>Tor needs to be tested far more thoroughly. This is a
1061)     multi-part effort. To start with, our unit test coverage should
1062)     rise substantially, especially in the areas outside the utility
1063)     functions. This will require significant refactoring of some parts
1064)     of Tor, in order to dissociate as much logic as possible from
1065)     globals.</p>

1066)     <p>Additionally, we need to automate our performance testing. We've got

1067)     buildbot to automate our regular integration and compile testing already
1068)     (though we need somebody to set it up on Windows),
1069)     but we need to get our network simulation tests (as built in <a
1070)     href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
1071)     updated for more recent versions of Tor, and designed to launch a test
1072)     network either on a single machine, or across several, so we can test

1073)     changes in performance on machines in different roles automatically.</p>

1074)     </li>
1075)     

1076)     <a id="simulateSlowConnections"></a>

1077)     <li>
1078)     <b>Simulator for slow Internet connections</b>

1079)     <br>

1080)     Priority: <i>Medium</i>

1081)     <br>

1082)     Effort Level: <i>Medium</i>

1083)     <br>

1084)     Skill Level: <i>Medium</i>

1085)     <br>

1086)     Likely Mentors: <i>Nick</i>

1087)     <p>

1088)     Many users of Tor have poor-quality Internet connections, giving low
1089)     bandwidth, high latency, and high packet loss/re-ordering. User
1090)     experience is that Tor reacts badly to these conditions, but it is
1091)     difficult to improve the situation without being able to repeat the
1092)     problems in the lab.

1093)     </p>
1094)     
1095)     <p>

1096)     This project would be to build a simulation environment which
1097)     replicates the poor connectivity so that the effect on Tor performance
1098)     can be measured. Other components would be a testing utility to
1099)     establish what are the properties of connections available, and to
1100)     measure the effect of performance-improving modifications to Tor.

1101)     </p>
1102)     
1103)     <p>

1104)     The tools used would be up to the student, but dummynet (for FreeBSD)
1105)     and nistnet (for Linux) are two potential components on which this
1106)     project could be built. Students should be experienced with network
1107)     programming/debugging and TCP/IP, and preferably familiar with C and a
1108)     scripting language.

1109)     </p>

1110)     </li>
1111)     

1112)     <a id="torbuttonForThunderbird"></a>

1113)     <li>
1114)     <b>Torbutton equivalent for Thunderbird</b>

1115)     <br>

1116)     Priority: <i>Medium</i>

1117)     <br>

1118)     Effort Level: <i>High</i>

1119)     <br>

1120)     Skill Level: <i>High</i>

1121)     <br>

1122)     Likely Mentors: <i>Mike</i>

1123)     <p>

1124)     We're hearing from an increasing number of users that they want to use
1125)     Thunderbird with Tor. However, there are plenty of application-level
1126)     concerns, for example, by default Thunderbird will put your hostname in
1127)     the outgoing mail that it sends. At some point we should start a new
1128)     push to build a Thunderbird extension similar to Torbutton.

1129)     </p>

1130)     </li>
1131)     

1132)     <a id="usabilityTesting"></a>

1133)     <li>
1134)     <b>Usability testing of Tor</b>

1135)     <br>

1136)     Priority: <i>Medium</i>

1137)     <br>

1138)     Effort Level: <i>Medium</i>

1139)     <br>

1140)     Skill Level: <i>Low to Medium</i>

1141)     <br>

1142)     Likely Mentors: <i>Andrew</i>

1143)     <p>

1144)     Especially the browser bundle, ideally amongst our target demographic.
1145)     That would help a lot in knowing what needs to be done in terms of bug
1146)     fixes or new features. We get this informally at the moment, but a more
1147)     structured process would be better.

1148)     </p>

1149)     
1150)     <p>
1151)     Please note that since this isn't a coding project, it isn't suitable for
1152)     Google Summer of Code.
1153)     </p>

1154)     </li>

1155)     

1156)     <a id="tailsMetadataAnonymizing"></a>
1157)     <li>
1158)     <b>Meta-data anonymizing toolkit for file publication</b>
1159)     <br>
1160)     Priority: <i>Medium</i>
1161)     <br>
1162)     Effort Level: <i>Low to Medium</i>
1163)     <br>
1164)     Skill Level: <i>Low to Medium</i>
1165)     <br>
1166)     Likely Mentors: <i>intrigeri, anonym</i>

1167)     <p>Tor helps greatly in publishing files anonymously. However, much personal
1168)     information can be enclosed *inside* such published files' meta-data: GPS
1169)     coordinates, author's name and so on. Anyone who wants to anonymously

1170)     publish a file can thus far too easily de-anonymize herself.</p>

1171)     <p>A set of tools allowing users to easily inspect and clean up meta-data in files

1172)     would benefit Tor users, and would e.g. be shipped in Tails.</p>

1173)     <p>A graphical user interface is a must, but library and command-line
1174)     interfaces are most welcome so that future work can add support for

1175)     cleaning published files to various publishing tools, such as desktop

1176)     social networking clients and Web content management systems.</p>

1177)     <p>This project mostly consists of writing glue between the many existing
1178)     tools and libraries that provide read/write access to files' meta-data. An

1179)     extensible program design would probably be the best bet, so that support
1180)     for other kinds of files can easily be added later.</p>
1181)     <p>The meta-data cleaning toolkit would run at least on GNU/Linux;
1182)     additional Windows and/or Mac OS X support would be welcome. The tools used
1183)     would be up to the students. The detailed specification is ready and will
1184)     be published soon.</p>

1185)     </li>   
1186)  

1187)     <a id="tailsDebianLive"></a>
1188)     <li>
1189)     <b>Improve Debian Live support for persistence</b>
1190)     <br>
1191)     Priority: <i>Medium</i>
1192)     <br>
1193)     Effort Level: <i>Medium</i>
1194)     <br>
1195)     Skill Level: <i>Low to Medium</i>
1196)     <br>
1197)     Likely Mentors: <i>intrigeri, anonym</i>
1198)     <p>Data persistence is a somewhat tricky topic in a Live system context,

1199)     especially one such as Tails, which is explicitly designed to avoid

1200)     leaving any trace of its use.</p>
1201)     <p>Some real-life use cases, however, require some kind of data

1202)     persistence. To start with, Tails should (carefully) support persistence of

1203)     application-specific configurations (e.g. GnuPG keyring) and of a user

1204)     arbitrary data store. Note that persistence in Tails will always be opt-in

1205)     and require encrypted storage.</p>

1206)     <p>The backend work consists of improving Debian Live's existing

1207)     persistence features to make them suit the specific context of Tails. A trust

1208)     relationship is already established with upstream who is happy to merge our
1209)     changes. The codebase is not that small and much refactoring is needed, so
1210)     this really is a programming project rather than a fire'n'forget shell
1211)     script hack contest.</p>
1212)     <p>Anyone undertaking this project must be familiar with GNU/Linux, and
1213)     preferably with Debian. Being able to (quickly learn to) write clean and
1214)     safe programs in shell is also needed.</p>

1215)     <p>For more information, see <a href="https://tails.boum.org/todo/persistence/">https://tails.boum.org/todo/persistence/</a>.</p>

1216)     </li>

1217)     

1218)     <a id="torsocksForOSX"></a>

1219)     <li>
1220)     <b>Make torsocks/dsocks work on OS X</b>

1221)     <br>

1222)     Priority: <i>Medium</i>

1223)     <br>

1224)     Effort Level: <i>Medium</i>

1225)     <br>

1226)     Skill Level: <i>Medium</i>

1227)     <br>

1228)     Likely Mentors: <i>Robert Hogan</i>

1229)     <p>

1230)     <a href="https://code.google.com/p/torsocks/">Torsocks</a> and <a
1231)     href="https://code.google.com/p/dsocks/">dsocks</a> are wrappers that will

1232)     run applications, intercept their outgoing network connections, and push
1233)     those connections through Tor. The goal is to handle applications that
1234)     don't support proxies (or don't supporting them well). To get it right,
1235)     they need to intercept many system calls. The syscalls you need to
1236)     intercept on Linux differ dramatically from those on BSD. So Torsocks
1237)     works fine on Linux, dsocks works ok on BSD (though it may be less
1238)     maintained and thus might miss more syscalls), and nothing works well
1239)     on both. First, we should patch dsocks to use Tor's <i>mapaddress</i>
1240)     commands from the controller interface, so we don't waste a whole
1241)     round-trip inside Tor doing the resolve before connecting. Second,
1242)     we should make our <i>torify</i> script detect which of torsocks or
1243)     dsocks is installed, and call them appropriately. This probably means
1244)     unifying their interfaces, and might involve sharing code between them
1245)     or discarding one entirely.

1246)     </p>
1247)     </li>
1248)     

1249)     <a id="vidaliaStatusEventInterface"></a>

1250)     <li>
1251)     <b>Tor Controller Status Event Interface for Vidalia</b>
1252)     <br>
1253)     Priority: <i>Medium</i>
1254)     <br>
1255)     Effort Level: <i>Medium</i>
1256)     <br>
1257)     Skill Level: <i>Low to Medium</i>
1258)     <br>

1259)     Likely Mentors: <i>Tomás</i>

1260)     <p>There are a number of status changes inside Tor of which the user may need
1261)     to be informed. For example, if the user is trying to set up his Tor as a
1262)     relay and Tor decides that its ports are not reachable from outside
1263)     the user's network, we should alert the user. Currently, all the user
1264)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1265)     likely never see since they don't receive a notification that something
1266)     has gone wrong. Even if the user does actually look at the message log,
1267)     most of the messages make little sense to the novice user.</p>
1268)     <p>Tor has the ability to inform Vidalia of many such status
1269)     changes, and we recently implemented support for a couple of these
1270)     events. Still, there are many more status events which the user should
1271)     be informed of, and we need a better UI for actually displaying them
1272)     to the user.</p>
1273)     <p>The goal of this project then is to design and implement a UI for
1274)     displaying Tor status events to the user. For example, we might put a
1275)     little badge on Vidalia's tray icon that alerts the user to new status
1276)     events they should look at. Double-clicking the icon could bring up a
1277)     dialog that summarizes recent status events in simple terms and maybe
1278)     suggests a remedy for any negative events if they can be corrected by
1279)     the user. Of course, this is just an example and one is free to
1280)     suggest another approach.</p>
1281)     <p>A person undertaking this project should have good UI design and layout
1282)     skills and some C++ development experience. Previous experience with Qt and
1283)     Qt's Designer will be very helpful, but are not required. Some
1284)     English writing ability will also be useful, since this project will
1285)     likely involve writing small amounts of help documentation that should
1286)     be understandable by non-technical users. Bonus points for some graphic
1287)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1288)     </li>
1289)     

1290)     <a id="orbot-optimisation"></a>
1291)     <li>
1292)     <b>Core Tor mobile optimisation</b>
1293)     <br>
1294)     Priority: <i>Medium</i>
1295)     <br>
1296)     Effort Level: <i>Medium</i>
1297)     <br>
1298)     Skill Level: <i>High</i>
1299)     <br>
1300)     Likely Mentors: <i>Nathan (n8fr8), Jake</i>
1301)     <p>
1302)     The existing port of Tor to Android is basically a straight
1303)     cross-compile to Linux ARM. There has been no work done in looking at
1304)     possible optimizations of Tor within a mobile hardware environment or on
1305)     mobile networks. In addition, a number of additional Android OS APIs are
1306)     available (such as wireless network status) that could be taken
1307)     advantage of.
1308)     </p>
1309)     
1310)     <p>
1311)     It should be noted, that even without optimisation, Tor is handling the
1312)     mobile network environment very well, automatically detecting change in
1313)     IP addresses, opening circuits, etc, as the device switches from no
1314)     coverage to 2G, 3G or Wifi constantly as it changes position. However,
1315)     this observation of &quot;very well&quot;, is just based on user
1316)     experience, and not any detailed study of what exactly is happening, and
1317)     what threats might exist because of this constantly changing network state.
1318)     </p>
1319)     
1320)     <p>
1321)     Finally, the build process needs to be moved to the Android NDK from the
1322)     custom GCC toolchain we are now using, and compatibility with Android
1323)     2.3 and 3.x Honeycomb OS need to be verified.
1324)     </p>
1325)     
1326)     <p>
1327)     For more information see the <a
1328)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD">Orbot
1329)     build documentation</a>.
1330)     </p>
1331)     </li>
1332)     
1333)     <a id="orbot-orlibAndOutreach"></a>
1334)     <li>
1335)     <b>Orbot integration library and community outreach</b>
1336)     <br>
1337)     Priority: <i>Medium</i>
1338)     <br>
1339)     Effort Level: <i>Low</i>
1340)     <br>
1341)     Skill Level: <i>Medium</i>
1342)     <br>
1343)     Likely Mentors: <i>Nathan (n8fr8)</i>
1344)     <p>
1345)     We need additional work on <a
1346)     href="https://github.com/guardianproject/orlib">ORLib</a>, our library for
1347)     use with third-party application to easily enable them to support
1348)     &quot;Torification&quot; on non-rooted devices (i.e. w/o transparent
1349)     proxying). This library includes a SOCKS client, a wrapper for the Apache
1350)     HTTPClient library, a utility class for detecting the state of Orbot
1351)     connectivity, and other relevant/useful things an Android app might need to
1352)     anonymize itself. This work would includes direct development of the
1353)     library, documentation, and sample code. Outreach or effort to implement
1354)     the library within other open-source apps is also needed.
1355)     </p>
1356)     </li>
1357)     

1358)     <!--

1359)     <a id="vidaliaNetworkMap"></a>

1360)     <li>
1361)     <b>An Improved and More Usable Network Map in Vidalia</b>
1362)     <br>
1363)     Priority: <i>Low to Medium</i>
1364)     <br>
1365)     Effort Level: <i>Medium</i>
1366)     <br>
1367)     Skill Level: <i>Medium</i>
1368)     <br>

1369)     Likely Mentors: <i>Tomás</i>

1370)     <p>
1371)     One of Vidalia's existing features is a network map that shows the user
1372)     the approximate geographic location of relays in the Tor network and
1373)     plots the paths the user's traffic takes as it is tunneled through the
1374)     Tor network. The map is currently not very interactive and has rather
1375)     poor graphics. Instead, we implemented KDE's Marble widget such
1376)     that it gives us a better quality map and enables improved interactivity,
1377)     such as allowing the user to click on individual relays or circuits to
1378)     display additional information. We want to add the ability
1379)     for users to click on a particular relay or a country containing one or
1380)     more Tor exit relays and say, "I want my connections to exit
1381)     from here."
1382)     </p>
1383)     
1384)     <p>
1385)     This project will first involve getting familiar with Vidalia
1386)     and the Marble widget's API. One will then integrate the widget
1387)     into Vidalia and customize Marble to be better suited for our application,
1388)     such as making circuits clickable, storing cached map data in Vidalia's
1389)     own data directory, and customizing some of the widget's dialogs.
1390)     </p>
1391)     
1392)     <p>
1393)     A person undertaking this project should have good C++ development
1394)     experience. Previous experience with Qt and CMake is helpful, but not
1395)     required.
1396)     </p>

1397)     </li>

1398)     -->

1399)     

1400)     <a id="obfsproxy-fuzzer"></a>
1401)     <li>
1402)     <b>Fuzzer for the Tor protocol</b>
1403)     <br>
1404)     Priority: <i>Low to Medium</i>
1405)     <br>
1406)     Effort Level: <i>Medium to High</i>
1407)     <br>
1408)     Skill Level: <i>High</i>
1409)     <br>
1410)     Likely Mentors: <i>asn</i>
1411)     <p>Involves researching good and smart ways to fuzz stateful network
1412)     protocols, and also implementing the fuzzer.</p>
1413)     
1414)     <p>We are mostly looking for a fuzzer that fuzzes the Tor protocol
1415)     itself, and not the Tor directory protocol.</p>
1416)     
1417)     <p>Bonus points if it's extremely modular. Relevant research:</p>
1418)     
1419)     <ul>
1420)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1421)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1422)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1423)       Testing and Machine Learning</li>
1424)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1425)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1426)       <li>Also look at the concepts of &quot;model checking&quot; and
1427)       &quot;symbolic execution&quot; to get inspired.</li>
1428)     </ul>
1429)     </li>
1430)     

1431)     <!--

1432)     <a id="armGui"></a>
1433)     <li>
1434)     <b>GUI for Arm</b>
1435)     <br>
1436)     Priority: <i>Low</i>
1437)     <br>
1438)     Effort Level: <i>High</i>
1439)     <br>
1440)     Skill Level: <i>Medium</i>
1441)     <br>

1442)     Likely Mentors: <i>Damian (atagar)</i>

1443)     <p>
1444)     Arm has several unique features, some of the most interesting being its
1445)     connection listing (correlating netstat results against the Tor consensus)
1446)     and configuration editor (a quick method for editing Tor's config, with
1447)     information pulled from the control port and man page). However, since arm
1448)     is a command line controller it's of limited appeal to certain sets of
1449)     users. This project would be to build a GTK or Qt frontend for the
1450)     controller, providing similar features set but with a windowed interface.
1451)     </p>
1452)     
1453)     <p>
1454)     The vast majority of arm's more interesting functionality lies in its

1455)     backend <a href="https://gitweb.torproject.org/arm.git/tree/HEAD:/src/util">utilities</a>, so

1456)     there should be little to no work decoupling the CLI from its backend.
1457)     Instead, this project would mostly be UI hacking and experimentation,
1458)     trying different interfaces to find something that's elegant and simple,
1459)     but matches the information found in the current terminal application.
1460)     </p>
1461)     </li>

1462)     -->

1463)     

1464)     <li>
1465)     <b>Bring up new ideas!</b>

1466)     <br>

1467)     Don't like any of these? Look at the <a

1468)     href="/press/presskit/2008-12-19-roadmap-full.pdf">Tor development

1469)     roadmap</a> for more ideas, or just try out Tor, Vidalia, and Torbutton,
1470)     and find out what you think needs fixing.

1471)     Some of the <a href="<spectree>proposals">current proposals</a>

1472)     might also be short on developers.
1473)     </li>
1474)     
1475)     </ol>
1476)     
1477)     <a id="OtherCoding"></a>
1478)     <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
1479)     <ol>
1480)     <li>Tor relays don't work well on Windows XP. On
1481)     Windows, Tor uses the standard <tt>select()</tt> system
1482)     call, which uses space in the non-page pool. This means
1483)     that a medium sized Tor relay will empty the non-page pool, <a

1484)     href="<wiki>doc/WindowsBufferProblems">causing

1485)     havoc and system crashes</a>. We should probably be using overlapped IO
1486)     instead. One solution would be to teach <a
1487)     href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
1488)     overlapped IO rather than select() on Windows, and then adapt Tor to
1489)     the new libevent interface. Christian King made a
1490)     <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
1491)     start</a> on this in the summer of 2007.</li>
1492)     
1493)     <li>We need to actually start building our <a href="<page
1494)     docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
1495)     fleshing out the design, modifying many different pieces of Tor, adapting
1496)     <a href="<page projects/vidalia>">Vidalia</a> so it supports the
1497)     new features, and planning for deployment.</li>
1498)     
1499)     <li>We need a flexible simulator framework for studying end-to-end
1500)     traffic confirmation attacks. Many researchers have whipped up ad hoc
1501)     simulators to support their intuition either that the attacks work
1502)     really well or that some defense works great. Can we build a simulator
1503)     that's clearly documented and open enough that everybody knows it's
1504)     giving a reasonable answer? This will spur a lot of new research.
1505)     See the entry <a href="#Research">below</a> on confirmation attacks for
1506)     details on the research side of this task &mdash; who knows, when it's
1507)     done maybe you can help write a paper or three also.</li>
1508)     

1509)     <li>Tor 0.1.1.x and later include support for hardware crypto
1510)     accelerators via OpenSSL. It has been lightly tested and is
1511)     possibly very buggy.  We're looking for more rigorous testing,

1512)     performance analysis, and optimally, code fixes to OpenSSL and

1513)     Tor if needed.</li>

1514)     
1515)     <li>Perform a security analysis of Tor with <a

1516)     href="https://secure.wikimedia.org/wikipedia/en/wiki/Fuzz_testing">"fuzz"</a>. Determine

1517)     if there are good fuzzing libraries out there for what we want. Win fame by
1518)     getting credit when we put out a new release because of you!</li>
1519)     
1520)     <li>Tor uses TCP for transport and TLS for link
1521)     encryption. This is nice and simple, but it means all cells
1522)     on a link are delayed when a single packet gets dropped, and
1523)     it means we can only reasonably support TCP streams. We have a <a

1524)     href="<page docs/faq>#TransportIPnotTCP">list

1525)     of reasons why we haven't shifted to UDP transport</a>, but it would
1526)     be great to see that list get shorter. We also have a proposed <a

1527)     href="<specblob>proposals/100-tor-spec-udp.txt">specification

1528)     for Tor and
1529)     UDP</a> &mdash; please let us know what's wrong with it.</li>
1530)     
1531)     <li>We're not that far from having IPv6 support for destination addresses
1532)     (at exit nodes). If you care strongly about IPv6, that's probably the
1533)     first place to start.</li>
1534)     
1535)     <li>We need a way to generate the website diagrams (for example, the "How
1536)     Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
1537)     from source, so we can translate them as UTF-8 text rather than edit
1538)     them by hand with Gimp. We might want to
1539)     integrate this as an wml file so translations are easy and images are
1540)     generated in multiple languages whenever we build the website.</li>
1541)     
1542)     <li>How can we make the various LiveCD/USB systems easier
1543)     to maintain, improve, and document?  One example is <a

1544)     href="https://tails.boum.org/">The Amnesic Incognito Live

1545)     System</a>.
1546)     </li>
1547)     
1548)     <li>
1549)     Another anti-censorship project is to try to make Tor
1550)     more scanning-resistant.  Right now, an adversary can identify <a

1551)     href="<specblob>proposals/125-bridges.txt">Tor bridges</a>

1552)     just by trying to connect to them, following the Tor protocol,
1553)     and seeing if they respond.  To solve this, bridges could <a
1554)     href="<svnprojects>design-paper/blocking.html#tth_sEc9.3">act like
1555)     webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
1556)     and not act like bridges until the user provides a bridge-specific key.
1557)     To start, check out Shane Pope's <a
1558)     href="http://dl.dropbox.com/u/37735/index.html">thesis and prototype</a>.
1559)     </li>
1560)     
1561)     </ol>
1562)     
1563)     <a id="Research"></a>
1564)     <h2><a class="anchor" href="#Research">Research</a></h2>
1565)     <ol>
1566)     <li>The "end-to-end traffic confirmation attack":
1567)     by watching traffic at Alice and at Bob, we can <a
1568)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1569)     traffic signatures and become convinced that we're watching the same
1570)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1571)     attack is trivial in all cases. First of all, is that actually true? How
1572)     much traffic of what sort of distribution is needed before the adversary
1573)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1574)     that slow down the attack? Do some traffic padding or traffic shaping
1575)     schemes work better than others?</li>
1576)     <li>A related question is: Does running a relay/bridge provide additional
1577)     protection against these timing attacks? Can an external adversary that can't
1578)     see inside TLS links still recognize individual streams reliably?
1579)     Does the amount of traffic carried degrade this ability any? What if the
1580)     client-relay deliberately delayed upstream relayed traffic to create a queue
1581)     that could be used to mimic timings of client downstream traffic to make it
1582)     look like it was also relayed? This same queue could also be used for masking
1583)     timings in client upstream traffic with the techniques from <a
1584)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1585)     but without the need for additional traffic. Would such an interleaving of
1586)     client upstream traffic obscure timings for external adversaries? Would the
1587)     strategies need to be adjusted for asymmetric links? For example, on
1588)     asymmetric links, is it actually possible to differentiate client traffic from
1589)     natural bursts due to their asymmetric capacity? Or is it easier than
1590)     symmetric links for some other reason?</li>
1591)     <li>Repeat Murdoch and Danezis's <a
1592)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1593)     Oakland 05</a> on the current Tor network. See if you can learn why it
1594)     works well on some nodes and not well on others. (My theory is that the
1595)     fast nodes with spare capacity resist the attack better.) If that's true,
1596)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1597)     options to run a relay that is used as a client while relaying the
1598)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1599)     attack get harder? What's the right ratio of RelayBandwidthRate to
1600)     actually capacity? Or is it a ratio at all? While we're at it, does a
1601)     much larger set of candidate relays increase the false positive rate
1602)     or other complexity for the attack? (The Tor network is now almost two
1603)     orders of magnitude larger than it was when they wrote their paper.) Be
1604)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1605)     Clog the Queue</a> too.</li>
1606)     <li>The "routing zones attack": most of the literature thinks of
1607)     the network path between Alice and her entry node (and between the
1608)     exit node and Bob) as a single link on some graph. In practice,
1609)     though, the path traverses many autonomous systems (ASes), and <a
1610)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1611)     that the same AS appears on both the entry path and the exit path</a>.
1612)     Unfortunately, to accurately predict whether a given Alice, entry,
1613)     exit, Bob quad will be dangerous, we need to download an entire Internet
1614)     routing zone and perform expensive operations on it. Are there practical
1615)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1616)     <li>Other research questions regarding geographic diversity consider
1617)     the tradeoff between choosing an efficient circuit and choosing a random
1618)     circuit. Look at Stephen Rollyson's <a
1619)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1620)     paper</a> on how to discard particularly slow choices without hurting
1621)     anonymity "too much". This line of reasoning needs more work and more
1622)     thinking, but it looks very promising.</li>
1623)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1624)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1625)     each hop, if the incoming bytes are arriving just fine and the outgoing
1626)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1627)     don't really transmit this information back to the incoming streams.
1628)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1629)     and rate-limit incoming streams to regulate this itself? I can imagine
1630)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1631)     slowly increase it until we get lost packets, back off, repeat. We
1632)     need somebody who's good with networks to simulate this and help design
1633)     solutions; and/or we need to understand the extent of the performance
1634)     degradation, and use this as motivation to reconsider UDP transport.</li>
1635)     <li>A related topic is congestion control. Is our
1636)     current design sufficient once we have heavy use? Maybe
1637)     we should experiment with variable-sized windows rather
1638)     than fixed-size windows? That seemed to go well in an <a
1639)     href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">ssh
1640)     throughput experiment</a>. We'll need to measure and tweak, and maybe
1641)     overhaul if the results are good.</li>
1642)     <li>Our censorship-resistance goals include preventing
1643)     an attacker who's looking at Tor traffic on the wire from <a
1644)     href="<svnprojects>design-paper/blocking.html#sec:network-fingerprint">distinguishing
1645)     it from normal SSL traffic</a>. Obviously we can't achieve perfect
1646)     steganography and still remain usable, but for a first step we'd like to
1647)     block any attacks that can win by observing only a few packets. One of
1648)     the remaining attacks we haven't examined much is that Tor cells are 512
1649)     bytes, so the traffic on the wire may well be a multiple of 512 bytes.
1650)     How much does the batching and overhead in TLS records blur this on the
1651)     wire? Do different buffer flushing strategies in Tor affect this? Could
1652)     a bit of padding help a lot, or is this an attack we must accept?</li>
1653)     <li>Tor circuits are built one hop at a time, so in theory we have the
1654)     ability to make some streams exit from the second hop, some from the
1655)     third, and so on. This seems nice because it breaks up the set of exiting
1656)     streams that a given relay can see. But if we want each stream to be safe,
1657)     the "shortest" path should be at least 3 hops long by our current logic, so
1658)     the rest will be even longer. We need to examine this performance / security
1659)     tradeoff.</li>
1660)     <li>It's not that hard to DoS Tor relays or directory authorities. Are client
1661)     puzzles the right answer? What other practical approaches are there? Bonus
1662)     if they're backward-compatible with the current Tor protocol.</li>
1663)     <li>Programs like <a

1664)     href="<page torbutton/index>">Torbutton</a> aim to hide