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)     <p>Tor has <a href="<page getinvolved/open-positions>">two open positions</a>.
31)     Please <a href="<page about/contact>">contact us</a> if you are qualified!</p>
32)     
33)     <a id="Documentation"></a>
34)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
35)     <ol>
36)     <li>Help translate the web page and documentation into other
37)     languages. See the <a href="<page getinvolved/translation>">translation
38)     guidelines</a> if you want to help out. We especially need Arabic or
39)     Farsi translations, for the many Tor users in censored areas.</li>
40)     <li>Evaluate and document
41)     <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">our
42)     list of programs</a> that can be configured to use Tor.</li>
43)     <li>We have a huge list of <a
44)     href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">potentially useful
45)     programs that interface to Tor</a>. Which ones are useful in which
46)     situations? Please help us test them out and document your results.</li>
47)     </ol>
48)     
49)     <a id="Advocacy"></a>
50)     <h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
51)     <ol>

52)     <li>Create a <a
53) href="https://trac.torproject.org/projects/tor/wiki/CommunityLogos">community
54) logo</a> under a Creative Commons license that all can use and modify.</li>
55)     <li>Create a presentation that can be used for various user group
56) meetings around the world.</li>

57)     <li>Create a video about the positive uses of Tor, what Tor is,
58)     or how to use it.  Some have already started on <a
59)     href="http://media.torproject.org/video/">Tor's Media server</a>,
60)     <a

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

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

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

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

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

67)     </ol>
68)     

69)     <a id="Projects"></a>
70)     <h2><a class="anchor" href="#Projects">Projects</a></h2>
71)     
72)     <p>
73)     Below are a list of Tor related projects we're developing and/or
74)     maintaining. Most discussions happen on IRC so if you're interested in any
75)     of these (or you have a project idea of your own), then please <a
76)     href="<page about/contact>#irc">join us in #tor-dev</a>. Project
77)     contributors are listed by their IRC nicks.
78)     </p>
79)     
80)     <table id="projects">
81)       <tr>
82)         <th>Name</th>
83)         <th>Category</th>
84)         <th>Language</th>
85)         <th>Activity</th>
86)         <th>Contributors</th>
87)       </tr>
88)       
89)       <tr>
90)         <td><a href="#project-tor">Tor</a></td>
91)         <td>Core</td>
92)         <td>C</td>
93)         <td>Heavy</td>
94)         <td>nickm, arma, etc</td>
95)       </tr>
96)       
97)       <tr class="alt">
98)         <td><a href="#project-tbb">TBB</a></td>
99)         <td>Usability</td>
100)         <td>Multiple</td>
101)         <td>Heavy</td>

102)         <td>Erinn</td>

103)       </tr>
104)       
105)       <tr>

106)         <td><a href="#project-tails">TAILS</a></td>
107)         <td>Usability</td>
108)         <td>Multiple</td>
109)         <td>Heavy</td>
110)         <td><a href="https://amnesia.boum.org/chat/">#tails</a></td>
111)       </tr>
112)       
113)       <tr class="alt">

114)         <td><a href="#project-torsocks">Torsocks</a></td>
115)         <td>Usability</td>
116)         <td>C</td>
117)         <td>Light</td>
118)         <td>mwenge</td>
119)       </tr>
120)       

121)       <tr>

122)         <td>*<a href="#project-torouter">Torouter</a></td>
123)         <td>Usability</td>
124)         <td>None</td>
125)         <td>Light</td>
126)         <td>ioerror, Runa</td>
127)       </tr>
128)       

129)       <tr class="alt">

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

137)       <tr>

138)         <td><a href="#project-arm">Arm</a></td>
139)         <td>User Interface</td>
140)         <td>Python, Curses</td>
141)         <td>Heavy</td>
142)         <td>atagar</td>
143)       </tr>
144)       

145)       <tr class="alt">

146)         <td><a href="#project-orbot">Orbot</a></td>
147)         <td>User Interface</td>
148)         <td>Java</td>
149)         <td>None</td>
150)         <td>n8fr8</td>
151)       </tr>
152)       

153)       <tr>

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

161)       <tr class="alt">

162)         <td>*<a href="#project-thandy">Thandy</a></td>
163)         <td>Updater</td>
164)         <td>Python</td>
165)         <td>Light</td>

166)         <td>Sebastian, Erinn</td>

167)       </tr>
168)       

169)       <tr>

170)         <td><a href="#project-torctl">TorCtl</a></td>
171)         <td>Library</td>
172)         <td>Python</td>
173)         <td>Light</td>
174)         <td>mikeperry</td>
175)       </tr>
176)       

177)       <tr class="alt">

178)         <td>*<a href="#project-jtor">JTor</a></td>
179)         <td>Library</td>
180)         <td>Java</td>
181)         <td>None</td>
182)         <td></td>
183)       </tr>
184)       

185)       <tr>

186)         <td><a href="#project-metrics">Metrics</a></td>
187)         <td>Client Service</td>
188)         <td>Java</td>
189)         <td>Heavy</td>
190)         <td>karsten</td>
191)       </tr>
192)       

193)       <tr class="alt">

194)         <td><a href="#project-torstatus">TorStatus</a></td>
195)         <td>Client Service</td>
196)         <td>PHP</td>
197)         <td>None</td>
198)         <td></td>
199)       </tr>
200)       

201)       <tr>

202)         <td><a href="#project-weather">Weather</a></td>
203)         <td>Client Service</td>
204)         <td>Python</td>
205)         <td>Light</td>
206)         <td>kaner</td>
207)       </tr>
208)       

209)       <tr class="alt">

210)         <td><a href="#project-gettor">GetTor</a></td>
211)         <td>Client Service</td>
212)         <td>Python</td>
213)         <td>None</td>
214)         <td></td>
215)       </tr>
216)       

217)       <tr>

218)         <td><a href="#project-torcheck">TorCheck</a></td>
219)         <td>Client Service</td>
220)         <td>Python, Perl</td>
221)         <td>None</td>
222)         <td></td>
223)       </tr>
224)       

225)       <tr class="alt">

226)         <td><a href="#project-bridgedb">BridgeDB</a></td>
227)         <td>Backend Service</td>
228)         <td>Python</td>
229)         <td>None</td>
230)         <td>kaner</td>
231)       </tr>
232)       

233)       <tr>

234)         <td><a href="#project-torflow">TorFlow</a></td>
235)         <td>Backend Service</td>
236)         <td>Python</td>
237)         <td>None</td>
238)         <td>mikeperry</td>
239)       </tr>
240)       

241)       <tr class="alt">

242)         <td>*<a href="#project-torbel">TorBEL</a></td>
243)         <td>Backend Service</td>
244)         <td>Python</td>
245)         <td>None</td>
246)         <td>Sebastian</td>
247)       </tr>
248)     </table>
249)     
250)     <sub>
251)     * Project is still in an alpha state.
252)     </sub>
253)     
254)     <br /><br />
255)     
256)     <a id="project-tor"></a>
257)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
258)     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
259)     tracker</a>)</h3>
260)     
261)     <p>
262)     Central project, providing the core software for using and participating in
263)     the Tor network. Numerous people contribute to the project to varying
264)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
265)     </p>
266)     
267)     <p>
268)     <b>Project Ideas:</b><br />
269)     <i><a href="#resistCensorship">Improving Tor's ability to resist
270)     censorship</a></i><br />
271)     <i><a href="#unitTesting">Improve our unit testing process</a></i><br />
272)     <i><a href="#simulateSlowConnections">Simulator for slow Internet connections</a></i>
273)     </p>
274)     
275)     <a id="project-tbb"></a>
276)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
277)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
278)     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
279)     tracker</a>)</h3>
280)     
281)     <p>
282)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
283)     and Firefox preconfigured to work together out of the box. This is actively
284)     being worked on by Erinn Clark.
285)     </p>
286)     
287)     <p>
288)     <b>Project Ideas:</b><br />
289)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
290)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
291)     </p>
292)     

293)     <a id="project-tails"></a>
294)     <h3><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live System</a> (<a
295)     href="http://git.immerda.ch/?p=amnesia.git;a=summary">code</a>, <a
296)     href="https://amnesia.boum.org/bugs/">bug
297)     tracker</a>)</h3>
298)     
299)     <p>
300)     The (Amnesic) Incognito Live System is a live CD/USB distribution
301)     preconfigured so that everything is safely routed through Tor and leaves no
302)     trace on the local system. This is a merger of the Amnesia and <a
303)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
304)     and still under very active development.
305)     </p>
306)     

307)     <a id="project-torsocks"></a>
308)     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
309)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
310)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
311)     tracker</a>)</h3>
312)     
313)     <p>
314)     Utility for adapting other applications to work with Tor. Development has
315)     slowed and compatibility issues remain with some platforms, but it's
316)     otherwise feature complete.
317)     </p>
318)     
319)     <p>
320)     <b>Project Ideas:</b><br />
321)     <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
322)     </p>
323)     
324)     <a id="project-torouter"></a>
325)     <h3><a
326)     href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/Torouter">Torouter</a> (<a
327)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
328)     tracker</a>)</h3>
329)     
330)     <p>
331)     Project to provide an easy-to-use, embedded Tor instance for routers. This
332)     had a couple months of high activity, but has since been rather quiet.
333)     </p>
334)     
335)     <a id="project-vidalia"></a>
336)     <h3><a href="<page projects/vidalia>">Vidalia</a> (<a
337)     href="https://svn.torproject.org/vidalia/vidalia/trunk/">code</a>, <a
338)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority">bug
339)     tracker</a>)</h3>
340)     
341)     <p>
342)     The most commonly used user interface for Tor. Matt Edman started the
343)     project in 2006 and brought it to its current stable state. Development
344)     slowed for several years, though Tomás Touceda has since taken a lead with
345)     pushing the project forward.
346)     </p>
347)     
348)     <p>
349)     <b>Project Ideas:</b><br />
350)     <i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i><br />
351)     <i><a href="#vidaliaNetworkMap">An Improved and More Usable Network Map in Vidalia</a></i>
352)     </p>
353)     
354)     <a id="project-arm"></a>
355)     <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a
356)     href="https://svn.torproject.org/svn/arm/trunk/">code</a>, <a
357)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=arm&order=priority">bug
358)     tracker</a>)</h3>
359)     
360)     <p>
361)     Command-line monitor for Tor. This has been under very active development
362)     by its author, Damian Johnson, since early 2009 to make it a better
363)     general-purpose controller for *nix environments.
364)     </p>
365)     
366)     <p>
367)     <b>Project Ideas:</b><br />
368)     <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i>
369)     </p>
370)     
371)     <a id="project-orbot"></a>
372)     <h3><a href="https://guardianproject.info/apps/orbot/">Orbot</a> (<a
373)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/">code</a>, <a
374)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Orbot&order=priority">bug
375)     tracker</a>)</h3>
376)     
377)     <p>
378)     Provides Tor on the Android platform. This was under very active
379)     development up through Fall 2010, after which things have been quiet.
380)     </p>
381)     
382)     <p>
383)     <b>Project Ideas:</b><br />
384)     <i><a href="#orbotDevelopment">More on Orbot & Android OS-specific development</a></i>
385)     </p>
386)     
387)     <a id="project-torbutton"></a>
388)     <h3><a href="<page torbutton/index>">Torbutton</a> (<a
389)     href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
390)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug
391)     tracker</a>)</h3>
392)     
393)     <p>
394)     Firefox addon that addresses many of the client-side threats to browsing
395)     the Internet anonymously. Mike has since continued to adapt it to new
396)     threats, updated versions of Firefox, and possibly <a
397)     href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">Chrome
398)     as well</a>.
399)     </p>
400)     
401)     <p>
402)     <b>Project Ideas:</b><br />
403)     <i><a href="#torbuttonForThunderbird">Torbutton equivalent for Thunderbird</a></i>
404)     </p>
405)     
406)     <a id="project-thandy"></a>
407)     <h3>Thandy (<a
408)     href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>
409)     
410)     <p>
411)     Updater for Tor. The project began in the Summer of 2008 but wasn't
412)     completed. Recently interest in it has been rekindled and many aspects of
413)     its design (including the language it'll be in) are currently in flux.
414)     </p>
415)     
416)     <a id="project-torctl"></a>
417)     <h3>TorCtl (<a
418)     href="https://gitweb.torproject.org/pytorctl.git">code</a>, <a
419)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority">bug
420)     tracker</a>)</h3>
421)     
422)     <p>
423)     Python bindings and utilities for using the Tor control port. It has been
424)     stable for several years, with only minor revisions.
425)     </p>
426)     
427)     <a id="project-jtor"></a>
428)     <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a
429)     href="https://github.com/brl/JTor">code</a>, <a
430)     href="https://github.com/brl/JTor/issues">bug
431)     tracker</a>)</h3>
432)     
433)     <p>
434)     Java implementation of Tor. This project isn't yet complete, and has been
435)     inactive since Fall 2010.
436)     </p>
437)     
438)     <a id="project-metrics"></a>
439)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
440)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
441)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
442)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
443)     href="https://gitweb.torproject.org/metrics.git">general</a>, <a
444)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
445)     tracker</a>)</h3>
446)     
447)     <p>
448)     Processing and analytics of consensus data, provided to users via the
449)     metrics portal. This has been under active development for several years by
450)     Karsten Loesing.
451)     </p>
452)     
453)     <p>
454)     <b>Project Ideas:</b><br />
455)     <i><a href="#trackNetworkStatus">Help track the overall Tor Network status</a></i>
456)     </p>
457)     
458)     <a id="project-torstatus"></a>
459)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorStatus">TorStatus</a> (<a
460)     href="https://svn.torproject.org/svn/torstatus/trunk/">code</a>)</h3>
461)     
462)     <p>
463)     Portal providing an overview of the Tor network, and details on any of its
464)     current relays. Though very actively used, this project has been
465)     unmaintained for a long while.
466)     </p>
467)     
468)     <a id="project-weather"></a>
469)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/Weather">Weather</a> (<a
470)     href="https://gitweb.torproject.org/weather.git">code</a>, <a
471)     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
472)     tracker</a>)</h3>
473)     
474)     <p>
475)     Provides automatic notification to subscribed relay operators when their
476)     relay's unreachable. This underwent a rewrite by the <a
477)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
478)     in early 2011.
479)     </p>
480)     
481)     <a id="project-gettor"></a>
482)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/EmailAutoResponder">GetTor</a> (<a
483)     href="https://svn.torproject.org/svn/projects/gettor/">code</a>, <a
484)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=GetTor&order=priority">bug
485)     tracker</a>)</h3>
486)     
487)     <p>
488)     E-mail autoresponder providing Tor's packages over SMTP. This has been
489)     relatively unchanged for quite a while.
490)     </p>
491)     
492)     <a id="project-torcheck"></a>
493)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorCheck">TorCheck</a> (<a
494)     href="https://svn.torproject.org/svn/check/trunk/">code</a>, <a
495)     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
496)     tracker</a>)</h3>
497)     
498)     <p>
499)     Provides a simple site for determining if the visitor is using Tor or not.
500)     This has been relatively unchanged for quite a while.
501)     </p>
502)     
503)     <a id="project-bridgedb"></a>
504)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/BridgeDB">BridgeDB</a> (<a
505)     href="https://gitweb.torproject.org/bridgedb.git">code</a>, <a
506)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=BridgeDB&order=priority">bug
507)     tracker</a>)</h3>
508)     
509)     <p>
510)     Backend bridge distributor, handling the various pools they're distributed
511)     in. This was actively developed until Fall of 2010.
512)     </p>
513)     
514)     <a id="project-torflow"></a>
515)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorFlow">TorFlow</a> (<a
516)     href="https://gitweb.torproject.org/torflow.git">code</a>, <a
517)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torflow&order=priority">bug
518)     tracker</a>)</h3>
519)     
520)     <p>
521)     Library and collection of services for actively monitoring the Tor network.
522)     These include the Bandwidth Scanners (measuring throughput of relays) and
523)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
524)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
525)     months later. Both have been under active use since then, but development
526)     has stopped.
527)     </p>
528)     
529)     <a id="project-torbel"></a>
530)     <h3><a
531)     href="https://trac.torproject.org/projects/tor/wiki/projects/TorBulkExitlist">TorBEL</a> (<a
532)     href="https://gitweb.torproject.org/tordnsel.git">code</a>, <a
533)     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
534)     tracker</a>)</h3>
535)     
536)     <p>
537)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
538)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
539)     (though unmaintained) Haskell application for this purpose. The initial
540)     version of TorBEL was started in GSOC 2010 but since then the project has
541)     been inactive.
542)     </p>
543)     
544)     <!--
545)     Copy and fill out the following for new projects:
546)     
547)     <a id="project-"></a>
548)     <h3><a href=""></a> (<a
549)     href="">code</a>, <a
550)     href="">bug
551)     tracker</a>)</h3>
552)     
553)     <p>
554)     </p>
555)     
556)     -->
557)     

558)     <a id="Coding"></a>
559)     <a id="Summer"></a>

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

561)     
562)     <p>
563)     You may find some of these projects to be good <a href="<page

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

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

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

569)     If one or more of these ideas looks promising to you, please <a
570)     href="<page about/contact>">contact us</a> to discuss your plans rather than
571)     sending blind applications. You may also want to propose your own project
572)     idea &mdash; which often results in the best applications.
573)     </p>
574)     
575)     <ol>
576)     

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

578)     <li>

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

580)     <br>

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

582)     <br>

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

584)     <br>

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

586)     <br>

587)     Likely Mentors: <i>Steven, Erinn, Jacob, Andrew</i>

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

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

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

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

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

602)     </li>
603)     

604)     <a id="trackNetworkStatus"></a>

605)     <li>
606)     <b>Help track the overall Tor Network status</b>

607)     <br>

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

609)     <br>

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

611)     <br>

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

613)     <br>

614)     Likely Mentors: <i>Karsten, Roger</i>

615)     <p>It would be great to set up an automated system for tracking network

616)     health over time, graphing it, etc. Part of this project would involve
617)     inventing better metrics for assessing network health and growth. Is the
618)     average uptime of the network increasing? How many relays are qualifying
619)     for Guard status this month compared to last month? What's the turnover
620)     in terms of new relays showing up and relays shutting off? Periodically
621)     people collect brief snapshots, but where it gets really interesting is

622)     when we start tracking data points over time.</p>
623)     <p>Data could be collected from the Tor Network Scanners in <a

624)     href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from
625)     the server descriptors that each relay publishes, and from other
626)     sources. Results over time could be integrated into one of the <a
627)     href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
628)     kept separate. Speaking of the Tor Status pages, take a look at Roger's
629)     <a href="http://archives.seul.org/or/talk/Jan-2008/msg00300.html">Tor

630)     Status wish list</a>.</p>

631)     </li>
632)     

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

634)     <li>
635)     <b>Improving Tor's ability to resist censorship</b>

636)     <br>

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

638)     <br>

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

640)     <br>

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

642)     <br>

643)     Likely Mentors: <i>Roger, Nick, Steven, Jake</i>

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

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

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

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

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

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

656)     blog post on the topic</a> as an overview, and then look at <a
657)     href="http://archives.seul.org/or/dev/Dec-2009/msg00000.html">Roger's
658)     or-dev post</a> from December for more recent thoughts &mdash; lots of

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

661)     we should address is that current Tors can only listen on a single
662)     address/port combination at a time. There's
663)     <a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
664)     proposal to address this limitation</a> and allow clients to connect
665)     to any given Tor on multiple addresses and ports, but it needs more

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

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

670)     then trading off censorship resistance with usability and
671)     robustness.</p>

672)     </li>
673)     

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

675)     <li>
676)     <b>Client Mode Use Cases for Arm</b>
677)     <br>
678)     Priority: <i>Medium</i>
679)     <br>
680)     Effort Level: <i>High</i>
681)     <br>
682)     Skill Level: <i>Medium</i>
683)     <br>
684)     Likely Mentors: <i>Damian</i>
685)     <p><a href="<page projects/arm>">Arm</a> is a Tor command line status
686)     monitor on *nix environments (Linux, Mac, and BSD). It functions much like
687)     top does, giving a CLI overlay of Tor's bandwidth usage, connections,
688)     configuration, log, etc. Thus far its design has been geared for Tor relay
689)     operators. However, this doesn't need to be the case. This project would be
690)     to expand and simplify arm to make it useful for Tor's client users
691)     too.</p>
692)     
693)     <p>This would include UI design, experimenting, and a lot of python
694)     hacking. Here's some ideas for client functionality arm could provide:</p>
695)     
696)     <ul>
697)       <li>A panel for client connections, showing each hop of the user's
698)       circuits with the ISP, country, and jurisdiction where those relays
699)       reside. Other interesting information would be the circuit's latency, how
700)       long its been around, and its possible exit ports. Some of this will be
701)       pretty tricky and require some experimentation to figure out what
702)       information can be fetched safely (for instance, scraping rdns and whois
703)       lookups could give hints about a relay's ISP, but we'd need to do it on
704)       all Tor relays to avoid leaking our connections to the resolver).</li>
705)       
706)       <li>Options to let the user request new circuits (the &quot;New
707)       Identity&quot; feature in Vidalia), select the exit country, etc.</li>
708)       
709)       <li>A panel showing Internet application and if their connections are
710)       being routed through Tor or not (giving a warning if there's leaks).</li>
711)       
712)       <li>The status of the bridges we're configured to use (ie, are they up?).
713)       This would include adding control port functionality to Tor for <a
714)       href="https://trac.torproject.org/projects/tor/ticket/2068">ticket
715)       2068</a>.</li>
716)       
717)       <li>A one click option to set Tor to be a client, relay, or bridge. The
718)       goal would be to make it trivial for users to voluntarily contribute to
719)       the Tor network.</li>
720)       
721)       <li>Menus as an alternative to hotkeys to make the interface more
722)       intuitive and usable for beginners (<a
723)       href="http://gnosis.cx/publish/programming/charming_python_6.html">example</a>).</li>
724)       
725)       <li>Look at Vidalia and TorK for ideas and solicit input from the Tor community.</li>
726)       
727)       <li>Make it easier for users to install arm by <a
728)       href="https://secure.wikimedia.org/wikipedia/en/wiki/Opkg">packaging for
729)       OpenWrt</a> (as a UI for the <a
730)       href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/Torouter">Torouter
731)       project</a>) and Macs.</li>
732)     </ul>
733)     
734)     <p>For more project ideas see arm's <a
735)     href="https://svn.torproject.org/svn/arm/trunk/TODO">TODO</a>.</p>
736)     </li>
737)     

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

739)     <li>
740)     <b>Improve our unit testing process</b>

741)     <br>

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

743)     <br>

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

745)     <br>

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

747)     <br>

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

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

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

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

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

763)     </li>
764)     

765)     <a id="orbotDevelopment"></a>

766)     <li>
767)     <b>More on Orbot &amp; Android OS-specific development</b>
768)     <br/>

769)     <br>

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

771)     <br>

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

773)     <br>

774)     Skill Level: <i>Medium to High</i>

775)     <br>

776)     Likely Mentors: <i>Nathan, Jake</i>

777)     <p><b>Android Java UI work:</b> Improved home screen to show better
778)     statistics about data transferred (up/down), number of circuits
779)     connected, quality of connection and so on. The "Tether Wifi"
780)     Android application is a good model to follow in how it shows
781)     a realtime count of bytes transferred as well as notifications

782)     when wifi clients connect. In addition, better display/handling

783)     of Tor system/error messages would also be very helpful. Finally,
784)     the addition of a wizard or tutorial walkthrough for novice

785)     users to explain to them exactly what is and what is not anonymized

786)     or protected would greatly improve the likelihood they will use
787)     Orbot correctly.</p>
788)     
789)     <p><b>Android Java OS/Core app work:</b> Better system-wide

790)     indication, either via the notification bar, "Toast" pop-up dialogs
791)     or some other indicator, that an application's traffic is indeed

792)     moving through Orbot/Tor. For instance, right now you need to
793)     first go to a torcheck web service to ensure your browser is
794)     routing via Tor. Orbot should be able to notify you that circuits
795)     are being opened, used, etc. The aforementioned data transfer
796)     tracker might provide this type of awareness as well.</p>
797)     
798)     <p><b>Android Java Library/Community Outreach work:</b> We need
799)     to package a simple library for use with third-party application

800)     to easily enable them to support "Torification" on non-rooted
801)     devices (i.e. w/o transparent proxying). This library should

802)     include a wrapper for the Apache HTTPClient library, a utility
803)     class for detecting the state of Orbot connectivity, and other
804)     relevant/useful things an Android app might need to anonymize
805)     itself. This work would include the creation of the library,
806)     documentation, and sample code. Outreach or effort to implement
807)     the library within other open-source apps would follow.</p>
808)     
809)     <p><b>Android OS/C/Linux work:</b> The port of Tor to Android
810)     is basically a straight cross-compile to Linux ARM. There has
811)     been no work done in looking the optimization of Tor within a
812)     mobile hardware environment, on the ARM processor or other
813)     Android hardware, or on mobile networks. It should be noted,
814)     that even without optimization, Tor is handling the mobile
815)     network environment very well, automatically detecting change

816)     in IP addresses, reconnecting circuits, etc. across switching

817)     from 2G to 3G to Wifi, and so forth.</p>

818)     </li>
819)     

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

821)     <li>
822)     <b>Simulator for slow Internet connections</b>

823)     <br>

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

825)     <br>

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

827)     <br>

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

829)     <br>

830)     Likely Mentors: <i>Steven</i>

831)     <p>

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

837)     </p>
838)     
839)     <p>

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

845)     </p>
846)     
847)     <p>

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

853)     </p>

854)     </li>
855)     

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

857)     <li>
858)     <b>Torbutton equivalent for Thunderbird</b>

859)     <br>

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

861)     <br>

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

863)     <br>

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

865)     <br>

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

867)     <p>

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

873)     </p>

874)     </li>
875)     

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

877)     <li>
878)     <b>Usability testing of Tor</b>

879)     <br>

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

881)     <br>

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

883)     <br>

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

885)     <br>

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

887)     <p>

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

892)     </p>

893)     
894)     <p>
895)     Please note that since this isn't a coding project, it isn't suitable for
896)     Google Summer of Code.
897)     </p>

898)     </li>

899)     

900)     <a id="authenticatingIrcProxy"></a>

901)     <li>
902)     <b>An authenticating IRC proxy</b>

903)     <br>

904)     Priority: <i>Low</i>

905)     <br>

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

907)     <br>

908)     Skill Level: <i>Medium to High</i>

909)     <br>

910)     Likely Mentors: <i>Sebastian, Peter, Roger</i>
911)     <p>

912)     The world needs an authenticating irc proxy. As we're periodically
913)     reminded from the Penny Arcade web comic, "Internet user + anonymity =
914)     jerk". With respect to websites we're actually doing ok, since websites
915)     can make their users log in and use other application-level authentication
916)     approaches. But IRC servers are much worse off, because most IRC server
917)     code is poorly written: hard to maintain, and harder to modify. Many
918)     IRC networks now block connections from Tor, and we're basically down to
919)     two holdouts (OFTC and Freenode). This state of affairs means that a lot
920)     of people around the world are thinking "I told you so" about anonymity
921)     online, when in fact the problem is simply lack of technology to make the
922)     problem manageable. We need some way to let the IRC networks distinguish
923)     which users have developed a reputation as not being jerks, so they can
924)     treat the two groups separately. There are some really cool research
925)     designs like <a href="http://www.cs.dartmouth.edu/~nymble/">Nymble</a>,
926)     which aim to let websites blacklist users without needing to learn who
927)     they are.  But Nymble is designed around web interactions. We need to
928)     build the glue around the IRC protocol that would let us plug in a project
929)     like Nymble (or a simpler one to start, as a proof-of-concept). One way
930)     to do that would be to build an IRC proxy that knows how to hear from
931)     IRC clients, knows how to talk to IRC servers, and has an additional
932)     layer that requires the users to authenticate.  Some work on this has
933)     begun by other volunteers, see their progress at <a

934)     href="https://github.com/anonirc/orc">https://github.com/anonirc/orc</a>.

935)     </p>

936)     </li>
937)     

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

939)     <li>
940)     <b>Make torsocks/dsocks work on OS X</b>

941)     <br>

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

943)     <br>

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

945)     <br>

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

947)     <br>

948)     Likely Mentors: <i>?</i>

949)     <p>

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

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

966)     </p>
967)     </li>
968)     

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

970)     <li>
971)     <b>Tor Controller Status Event Interface for Vidalia</b>
972)     <br>
973)     Priority: <i>Medium</i>
974)     <br>
975)     Effort Level: <i>Medium</i>
976)     <br>
977)     Skill Level: <i>Low to Medium</i>
978)     <br>
979)     Likely Mentors: <i>Tomás?</i>
980)     <p>There are a number of status changes inside Tor of which the user may need
981)     to be informed. For example, if the user is trying to set up his Tor as a
982)     relay and Tor decides that its ports are not reachable from outside
983)     the user's network, we should alert the user. Currently, all the user
984)     gets is a couple of log messages in Vidalia's 'message log' window, which they
985)     likely never see since they don't receive a notification that something
986)     has gone wrong. Even if the user does actually look at the message log,
987)     most of the messages make little sense to the novice user.</p>
988)     <p>Tor has the ability to inform Vidalia of many such status
989)     changes, and we recently implemented support for a couple of these
990)     events. Still, there are many more status events which the user should
991)     be informed of, and we need a better UI for actually displaying them
992)     to the user.</p>
993)     <p>The goal of this project then is to design and implement a UI for
994)     displaying Tor status events to the user. For example, we might put a
995)     little badge on Vidalia's tray icon that alerts the user to new status
996)     events they should look at. Double-clicking the icon could bring up a
997)     dialog that summarizes recent status events in simple terms and maybe
998)     suggests a remedy for any negative events if they can be corrected by
999)     the user. Of course, this is just an example and one is free to
1000)     suggest another approach.</p>
1001)     <p>A person undertaking this project should have good UI design and layout
1002)     skills and some C++ development experience. Previous experience with Qt and
1003)     Qt's Designer will be very helpful, but are not required. Some
1004)     English writing ability will also be useful, since this project will
1005)     likely involve writing small amounts of help documentation that should
1006)     be understandable by non-technical users. Bonus points for some graphic
1007)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1008)     </li>
1009)     

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

1011)     <li>
1012)     <b>An Improved and More Usable Network Map in Vidalia</b>
1013)     <br>
1014)     Priority: <i>Low to Medium</i>
1015)     <br>
1016)     Effort Level: <i>Medium</i>
1017)     <br>
1018)     Skill Level: <i>Medium</i>
1019)     <br>
1020)     Likely Mentors: <i>Tomás?</i>
1021)     <p>
1022)     One of Vidalia's existing features is a network map that shows the user
1023)     the approximate geographic location of relays in the Tor network and
1024)     plots the paths the user's traffic takes as it is tunneled through the
1025)     Tor network. The map is currently not very interactive and has rather
1026)     poor graphics. Instead, we implemented KDE's Marble widget such
1027)     that it gives us a better quality map and enables improved interactivity,
1028)     such as allowing the user to click on individual relays or circuits to
1029)     display additional information. We want to add the ability
1030)     for users to click on a particular relay or a country containing one or
1031)     more Tor exit relays and say, "I want my connections to exit
1032)     from here."
1033)     </p>
1034)     
1035)     <p>
1036)     This project will first involve getting familiar with Vidalia
1037)     and the Marble widget's API. One will then integrate the widget
1038)     into Vidalia and customize Marble to be better suited for our application,
1039)     such as making circuits clickable, storing cached map data in Vidalia's
1040)     own data directory, and customizing some of the widget's dialogs.
1041)     </p>
1042)     
1043)     <p>
1044)     A person undertaking this project should have good C++ development
1045)     experience. Previous experience with Qt and CMake is helpful, but not
1046)     required.
1047)     </p>

1048)     </li>
1049)     

1050)     <!--
1051)     <li>
1052)     <b>Help with independent Tor client implementations</b>
1053)     <br>
1054)     Priority: <i>Medium</i>
1055)     <br>
1056)     Effort Level: <i>High</i>
1057)     <br>
1058)     Skill Level: <i>Medium to High</i>
1059)     <br>
1060)     Likely Mentors: <i>Bruce, Nathan</i>
1061)     <p>Others are currently working on Tor clients for Java, Android, and Maemo
1062)     environments.  The first step is to get a handle on the current state of
1063)     the project in which you are interested in helping; <a

1064)     href="https://github.com/brl/JTor">Tor for Java</a>,

1065)     <a href="https://svn.torproject.org/svn/projects/android/trunk/">Android/Orbot</a>,
1066)      or <a href="<page docs/N900>">Tor for Maemo</a>. Check out the
1067)     repository and familiarize yourself
1068)     with the source code.  Further, support for requesting or even providing
1069)     Tor hidden services would be neat, but not required.</p>
1070)     <p>A prospective developer should be able to understand and write new Java
1071)     code, including a Java cryptography API. Being able to read C code would be helpful,
1072)     too. One should be willing to read the existing documentation,
1073)     implement code based on it, and refine the documentation
1074)     when things are underdocumented. This project is mostly about coding and
1075)     to a small degree about design.</p>
1076)     </li>
1077)     -->
1078) 

1079)     <!--
1080)     <li>
1081)     <b>Improvements for Tor+Vidalia interaction on Linux/Unix platforms</b>
1082)     <br>
1083)     Priority: <i>Medium</i>
1084)     <br>
1085)     Effort Level: <i>Medium</i>
1086)     <br>
1087)     Skill Level: <i>Medium</i>
1088)     <br>
1089)     Likely Mentors: <i>Erinn, Peter</i>
1090)     <p>
1091)     Vidalia currently doesn't play nicely with Tor on Linux and Unix platforms.
1092)     Currently, on Debian and Ubuntu, there is a configuration mechanism which
1093)     allows Vidalia to override Tor's ability to start on boot (by sourcing
1094)     <code>/etc/default/tor.vidalia</code> which sets <code>RUN_DAEMON=no</code> at the user's
1095)     request), but full implementation of <a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> 
1096)     communication is still required.
1097)     </p>
1098)     
1099)     <p>
1100)     A better solution on Linux and Unix platforms would be to use Tor's
1101)     ControlSocket, which allows Vidalia to talk to Tor via a Unix domain socket,
1102)     and could possibly be enabled by default in Tor's distribution packages.
1103)     Vidalia can then authenticate to Tor using filesystem-based (cookie)
1104)     authentication if the user running Vidalia is also in the distribution-specific
1105)     tor group.
1106)     </p>
1107)     
1108)     <p>
1109)     This project will first involve adding support for Tor's ControlSocket to
1110)     Vidalia. The student will then develop and test this support on various
1111)     distributions to make sure it behaves in a predictable and consistent manner on
1112)     all of them.
1113)     </p>
1114)     
1115)     <p>
1116)     The next challenge would be to find an intuitive and usable way for Vidalia to be
1117)     able to change Tor's configuration (torrc) even though it is located in
1118)     <code>/etc/tor/torrc</code> and thus immutable. In Debian and Ubuntu we handle
1119)     this with the aforementioned <code>/etc/default/tor.vidalia</code> but this
1120)     functionality could (or should) be less distribution-specific.
1121)     </p>
1122)     
1123)     <p>
1124)     The best idea we've come up with so far is to feed Tor a new configuration via
1125)     the ControlSocket when Vidalia starts, but that's bad because if the user is not
1126)     using the latest Debian/Ubuntu packages, they may not have disabled Tor's
1127)     ability to run on boot and will end up with a configuration that is different
1128)     from what they want. The second best idea we've come up with is for Vidalia to
1129)     write out a temporary torrc file and ask the user to manually move it to
1130)     <code>/etc/tor/torrc</code>, but that's bad because users shouldn't have to
1131)     mess with files directly.
1132)     </p>
1133)     
1134)     <p>
1135)     A person undertaking this project should have prior knowledge of various Linux
1136)     distributions and their packaging mechanisms as well as some C++ development
1137)     experience. Previous experience with Qt is helpful, but not required.
1138)     </p>
1139)     </li>
1140)     -->
1141)     

1142)     <li>
1143)     <b>Bring up new ideas!</b>

1144)     <br>

1145)     Don't like any of these? Look at the <a
1146)     href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
1147)     roadmap</a> for more ideas, or just try out Tor, Vidalia, and Torbutton,
1148)     and find out what you think needs fixing.
1149)     Some of the <a href="<gittree>doc/spec/proposals">current proposals</a>
1150)     might also be short on developers.
1151)     </li>
1152)     
1153)     </ol>
1154)     
1155)     <a id="OtherCoding"></a>
1156)     <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
1157)     <ol>
1158)     <li>Tor relays don't work well on Windows XP. On
1159)     Windows, Tor uses the standard <tt>select()</tt> system
1160)     call, which uses space in the non-page pool. This means
1161)     that a medium sized Tor relay will empty the non-page pool, <a
1162)     href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/WindowsBufferProblems">causing
1163)     havoc and system crashes</a>. We should probably be using overlapped IO
1164)     instead. One solution would be to teach <a
1165)     href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
1166)     overlapped IO rather than select() on Windows, and then adapt Tor to
1167)     the new libevent interface. Christian King made a
1168)     <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
1169)     start</a> on this in the summer of 2007.</li>
1170)     
1171)     <li>We need to actually start building our <a href="<page
1172)     docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
1173)     fleshing out the design, modifying many different pieces of Tor, adapting
1174)     <a href="<page projects/vidalia>">Vidalia</a> so it supports the
1175)     new features, and planning for deployment.</li>
1176)     
1177)     <li>We need a flexible simulator framework for studying end-to-end
1178)     traffic confirmation attacks. Many researchers have whipped up ad hoc
1179)     simulators to support their intuition either that the attacks work
1180)     really well or that some defense works great. Can we build a simulator
1181)     that's clearly documented and open enough that everybody knows it's
1182)     giving a reasonable answer? This will spur a lot of new research.
1183)     See the entry <a href="#Research">below</a> on confirmation attacks for
1184)     details on the research side of this task &mdash; who knows, when it's
1185)     done maybe you can help write a paper or three also.</li>
1186)     

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

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

1191)     Tor if needed.</li>

1192)     
1193)     <li>Perform a security analysis of Tor with <a

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

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

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

1203)     of reasons why we haven't shifted to UDP transport</a>, but it would
1204)     be great to see that list get shorter. We also have a proposed <a
1205)     href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
1206)     for Tor and
1207)     UDP</a> &mdash; please let us know what's wrong with it.</li>
1208)     
1209)     <li>We're not that far from having IPv6 support for destination addresses
1210)     (at exit nodes). If you care strongly about IPv6, that's probably the
1211)     first place to start.</li>
1212)     
1213)     <li>We need a way to generate the website diagrams (for example, the "How
1214)     Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
1215)     from source, so we can translate them as UTF-8 text rather than edit
1216)     them by hand with Gimp. We might want to
1217)     integrate this as an wml file so translations are easy and images are
1218)     generated in multiple languages whenever we build the website.</li>
1219)     
1220)     <li>How can we make the various LiveCD/USB systems easier
1221)     to maintain, improve, and document?  One example is <a
1222)     href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
1223)     System</a>.
1224)     </li>
1225)     
1226)     <li>
1227)     Another anti-censorship project is to try to make Tor
1228)     more scanning-resistant.  Right now, an adversary can identify <a
1229)     href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
1230)     just by trying to connect to them, following the Tor protocol,
1231)     and seeing if they respond.  To solve this, bridges could <a
1232)     href="<svnprojects>design-paper/blocking.html#tth_sEc9.3">act like
1233)     webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
1234)     and not act like bridges until the user provides a bridge-specific key.
1235)     To start, check out Shane Pope's <a
1236)     href="http://dl.dropbox.com/u/37735/index.html">thesis and prototype</a>.
1237)     </li>
1238)     
1239)     </ol>
1240)     
1241)     <a id="Research"></a>
1242)     <h2><a class="anchor" href="#Research">Research</a></h2>
1243)     <ol>
1244)     <li>The "end-to-end traffic confirmation attack":
1245)     by watching traffic at Alice and at Bob, we can <a
1246)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1247)     traffic signatures and become convinced that we're watching the same
1248)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1249)     attack is trivial in all cases. First of all, is that actually true? How
1250)     much traffic of what sort of distribution is needed before the adversary
1251)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1252)     that slow down the attack? Do some traffic padding or traffic shaping
1253)     schemes work better than others?</li>
1254)     <li>A related question is: Does running a relay/bridge provide additional
1255)     protection against these timing attacks? Can an external adversary that can't
1256)     see inside TLS links still recognize individual streams reliably?
1257)     Does the amount of traffic carried degrade this ability any? What if the
1258)     client-relay deliberately delayed upstream relayed traffic to create a queue
1259)     that could be used to mimic timings of client downstream traffic to make it
1260)     look like it was also relayed? This same queue could also be used for masking
1261)     timings in client upstream traffic with the techniques from <a
1262)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1263)     but without the need for additional traffic. Would such an interleaving of
1264)     client upstream traffic obscure timings for external adversaries? Would the
1265)     strategies need to be adjusted for asymmetric links? For example, on
1266)     asymmetric links, is it actually possible to differentiate client traffic from
1267)     natural bursts due to their asymmetric capacity? Or is it easier than
1268)     symmetric links for some other reason?</li>
1269)     <li>Repeat Murdoch and Danezis's <a
1270)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1271)     Oakland 05</a> on the current Tor network. See if you can learn why it
1272)     works well on some nodes and not well on others. (My theory is that the
1273)     fast nodes with spare capacity resist the attack better.) If that's true,
1274)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1275)     options to run a relay that is used as a client while relaying the
1276)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1277)     attack get harder? What's the right ratio of RelayBandwidthRate to
1278)     actually capacity? Or is it a ratio at all? While we're at it, does a
1279)     much larger set of candidate relays increase the false positive rate
1280)     or other complexity for the attack? (The Tor network is now almost two
1281)     orders of magnitude larger than it was when they wrote their paper.) Be
1282)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1283)     Clog the Queue</a> too.</li>
1284)     <li>The "routing zones attack": most of the literature thinks of
1285)     the network path between Alice and her entry node (and between the
1286)     exit node and Bob) as a single link on some graph. In practice,
1287)     though, the path traverses many autonomous systems (ASes), and <a
1288)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1289)     that the same AS appears on both the entry path and the exit path</a>.
1290)     Unfortunately, to accurately predict whether a given Alice, entry,
1291)     exit, Bob quad will be dangerous, we need to download an entire Internet
1292)     routing zone and perform expensive operations on it. Are there practical
1293)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1294)     <li>Other research questions regarding geographic diversity consider
1295)     the tradeoff between choosing an efficient circuit and choosing a random
1296)     circuit. Look at Stephen Rollyson's <a
1297)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1298)     paper</a> on how to discard particularly slow choices without hurting
1299)     anonymity "too much". This line of reasoning needs more work and more
1300)     thinking, but it looks very promising.</li>
1301)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1302)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1303)     each hop, if the incoming bytes are arriving just fine and the outgoing
1304)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1305)     don't really transmit this information back to the incoming streams.
1306)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1307)     and rate-limit incoming streams to regulate this itself? I can imagine
1308)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1309)     slowly increase it until we get lost packets, back off, repeat. We
1310)     need somebody who's good with networks to simulate this and help design
1311)     solutions; and/or we need to understand the extent of the performance
1312)     degradation, and use this as motivation to reconsider UDP transport.</li>
1313)     <li>A related topic is congestion control. Is our
1314)     current design sufficient once we have heavy use? Maybe
1315)     we should experiment with variable-sized windows rather
1316)     than fixed-size windows? That seemed to go well in an <a
1317)     href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">ssh
1318)     throughput experiment</a>. We'll need to measure and tweak, and maybe
1319)     overhaul if the results are good.</li>
1320)     <li>Our censorship-resistance goals include preventing
1321)     an attacker who's looking at Tor traffic on the wire from <a
1322)     href="<svnprojects>design-paper/blocking.html#sec:network-fingerprint">distinguishing
1323)     it from normal SSL traffic</a>. Obviously we can't achieve perfect
1324)     steganography and still remain usable, but for a first step we'd like to
1325)     block any attacks that can win by observing only a few packets. One of
1326)     the remaining attacks we haven't examined much is that Tor cells are 512
1327)     bytes, so the traffic on the wire may well be a multiple of 512 bytes.
1328)     How much does the batching and overhead in TLS records blur this on the
1329)     wire? Do different buffer flushing strategies in Tor affect this? Could
1330)     a bit of padding help a lot, or is this an attack we must accept?</li>
1331)     <li>Tor circuits are built one hop at a time, so in theory we have the
1332)     ability to make some streams exit from the second hop, some from the
1333)     third, and so on. This seems nice because it breaks up the set of exiting
1334)     streams that a given relay can see. But if we want each stream to be safe,
1335)     the "shortest" path should be at least 3 hops long by our current logic, so
1336)     the rest will be even longer. We need to examine this performance / security
1337)     tradeoff.</li>
1338)     <li>It's not that hard to DoS Tor relays or directory authorities. Are client
1339)     puzzles the right answer? What other practical approaches are there? Bonus
1340)     if they're backward-compatible with the current Tor protocol.</li>
1341)     <li>Programs like <a

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