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>Do you have an Amazon account? Are you willing to spend up to $3 a
18)     month? Then spin up your own Tor relay in less than 10 minutes with <a
19)     href="https://cloud.torproject.org/">tor cloud</a>!</li>

20)     <li>Tell your friends! Get them to run relays. Get them to run hidden
21)     services. Get them to tell their friends.</li>
22)     <li>If you like Tor's goals, please <a href="<page donate/donate>">take a moment
23)     to donate to support further Tor development</a>. We're also looking
24)     for more sponsors &mdash; if you know any companies, NGOs, agencies,
25)     or other organizations that want anonymity / privacy / communications
26)     security, let them know about us.</li>
27)     <li>We're looking for more <a href="<page about/torusers>">good examples of Tor
28)     users and Tor use cases</a>. If you use Tor for a scenario or purpose not
29)     yet described on that page, and you're comfortable sharing it with us,
30)     we'd love to hear from you.</li>
31)     </ol>
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="<wiki>doc/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="<wiki>doc/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 presentation that can be used for various user group
53) meetings around the world.</li>

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

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

57)     <a

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

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

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

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

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

64)     </ol>
65)     

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

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

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

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

93)       </tr>
94)       
95)       <tr class="alt">

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

104)         <td><a href="#project-tbb">TBB</a></td>
105)         <td>Usability</td>

106)         <td>Sys Admin</td>
107)         <td>Moderate</td>

108)         <td>Erinn</td>

109)       </tr>
110)       

111)       <tr class="alt">

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

113)         <td>Usability</td>

114)         <td>Sys Admin</td>

115)         <td>Heavy</td>

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

117)       </tr>
118)       

119)       <tr>

120)         <td><a href="#project-torsocks">Torsocks</a></td>
121)         <td>Usability</td>
122)         <td>C</td>

123)         <td>None</td>

124)         <td>mwenge</td>
125)       </tr>
126)       

127)       <tr class="alt">

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

130)         <td>Sys Admin</td>

131)         <td>Light</td>
132)         <td>ioerror, Runa</td>
133)       </tr>
134)       

135)       <tr>

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

143)       <tr class="alt">

144)         <td><a href="#project-arm">Arm</a></td>
145)         <td>User Interface</td>
146)         <td>Python, Curses</td>

147)         <td>Light</td>

148)         <td>atagar</td>
149)       </tr>
150)       

151)       <tr>

152)         <td><a href="#project-orbot">Orbot</a></td>
153)         <td>User Interface</td>
154)         <td>Java</td>

155)         <td>Moderate</td>

156)         <td>n8fr8</td>
157)       </tr>
158)       

159)       <tr class="alt">

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

167)       <tr>

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

176)         <td>*<a href="#project-thandy">Thandy</a></td>
177)         <td>Updater</td>
178)         <td>Python</td>
179)         <td>Light</td>

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

181)       </tr>
182)       

183)       <tr>

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

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

200)         <td><a href="#project-torctl">TorCtl</a></td>
201)         <td>Library</td>
202)         <td>Python</td>
203)         <td>Light</td>
204)         <td>mikeperry</td>
205)       </tr>
206)       

207)       <tr class="alt">

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

215)       <tr>

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

223)       <tr class="alt">

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

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

227)         <td>None</td>
228)         <td></td>
229)       </tr>
230)       

231)       <tr>

232)         <td><a href="#project-weather">Weather</a></td>
233)         <td>Client Service</td>
234)         <td>Python</td>

235)         <td>None</td>

236)         <td>kaner</td>
237)       </tr>
238)       

239)       <tr class="alt">

240)         <td><a href="#project-gettor">GetTor</a></td>
241)         <td>Client Service</td>
242)         <td>Python</td>

243)         <td>None</td>

244)         <td>kaner</td>

245)       </tr>
246)       

247)       <tr>

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

255)       <tr class="alt">

256)         <td><a href="#project-bridgedb">BridgeDB</a></td>
257)         <td>Backend Service</td>
258)         <td>Python</td>

259)         <td>None</td>

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

261)       </tr>
262)       

263)       <tr>

264)         <td><a href="#project-torflow">TorFlow</a></td>
265)         <td>Backend Service</td>
266)         <td>Python</td>

267)         <td>Moderate</td>

268)         <td>mikeperry</td>
269)       </tr>
270)       

271)       <tr class="alt">

272)         <td>*<a href="#project-torbel">TorBEL</a></td>
273)         <td>Backend Service</td>
274)         <td>Python</td>
275)         <td>None</td>
276)         <td>Sebastian</td>
277)       </tr>
278)     </table>
279)     
280)     <sub>
281)     * Project is still in an alpha state.
282)     </sub>
283)     
284)     <br /><br />
285)     
286)     <a id="project-tor"></a>
287)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
288)     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
289)     tracker</a>)</h3>
290)     
291)     <p>
292)     Central project, providing the core software for using and participating in
293)     the Tor network. Numerous people contribute to the project to varying
294)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
295)     </p>
296)     
297)     <p>
298)     <b>Project Ideas:</b><br />
299)     <i><a href="#resistCensorship">Improving Tor's ability to resist
300)     censorship</a></i><br />

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

303)     </p>
304)     

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

317)     <a id="project-tbb"></a>
318)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
319)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
320)     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
321)     tracker</a>)</h3>
322)     
323)     <p>
324)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
325)     and Firefox preconfigured to work together out of the box. This is actively
326)     being worked on by Erinn Clark.
327)     </p>
328)     
329)     <p>
330)     <b>Project Ideas:</b><br />
331)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
332)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
333)     </p>
334)     

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

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

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

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

339)     tracker</a>)</h3>
340)     
341)     <p>

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

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

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

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

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

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

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

385)     </p>
386)     
387)     <a id="project-vidalia"></a>
388)     <h3><a href="<page projects/vidalia>">Vidalia</a> (<a

389)     href="https://gitweb.torproject.org/vidalia.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=Vidalia&order=priority">bug
391)     tracker</a>)</h3>
392)     
393)     <p>
394)     The most commonly used user interface for Tor. Matt Edman started the
395)     project in 2006 and brought it to its current stable state. Development
396)     slowed for several years, though Tomás Touceda has since taken a lead with
397)     pushing the project forward.
398)     </p>
399)     
400)     <p>
401)     <b>Project Ideas:</b><br />

402)     <i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i><br />
403)     <i><a href="#vidalia-hidden-service-panel">Torrc plugin and improved hidden service configuration panel</a></i>

404)     </p>
405)     
406)     <a id="project-arm"></a>
407)     <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a

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

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

418)     <!--

419)     <p>
420)     <b>Project Ideas:</b><br />

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

423)     </p>

424)     -->

425)     
426)     <a id="project-orbot"></a>
427)     <h3><a href="https://guardianproject.info/apps/orbot/">Orbot</a> (<a

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

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

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

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

464)     <a id="project-obfsproxy"></a>
465)     <h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc">Obfsproxy</a> (<a
466)     href="https://gitweb.torproject.org/obfsproxy.git">code</a>, <a
467)     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
468)     tracker</a>)</h3>
469)     
470)     <p>
471)     A proxy that shapes Tor traffic, making it harder for censors to detect and
472)     block Tor.
473)     </p>
474)     

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

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

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

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

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

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

537)     <p>
538)     <b>Project Ideas:</b><br />
539)     <i><a href="#stemPathsupport">Stem PathSupport Capabilities</a></i>
540)     </p>
541)     

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

556)     <p>
557)     <b>Project Ideas:</b><br />
558)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
559)     </p>
560)     

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

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

564)     
565)     <p>
566)     Portal providing an overview of the Tor network, and details on any of its
567)     current relays. Though very actively used, this project has been

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

572)     </p>
573)     
574)     <a id="project-weather"></a>
575)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/Weather">Weather</a> (<a
576)     href="https://gitweb.torproject.org/weather.git">code</a>, <a
577)     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
578)     tracker</a>)</h3>
579)     
580)     <p>
581)     Provides automatic notification to subscribed relay operators when their
582)     relay's unreachable. This underwent a rewrite by the <a
583)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
584)     in early 2011.
585)     </p>
586)     
587)     <a id="project-gettor"></a>
588)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/EmailAutoResponder">GetTor</a> (<a

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

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

650)     <a id="Coding"></a>
651)     <a id="Summer"></a>

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

653)     
654)     <p>
655)     You may find some of these projects to be good <a href="<page

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

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

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

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

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

670)     <li>

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

672)     <br>

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

674)     <br>

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

676)     <br>

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

678)     <br>

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

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

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

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

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

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

694)     </li>
695)     

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

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

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

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

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

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

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

753)     </li>
754) 

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

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

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

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

851)     <li>
852)     <b>Improving Tor's ability to resist censorship</b>

853)     <br>

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

855)     <br>

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

857)     <br>

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

859)     <br>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

887)     then trading off censorship resistance with usability and
888)     robustness.</p>

889)     </li>
890)     

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

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

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

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

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

963)     possible.</p>

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

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

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

970)     project.</p>

971)     </li>
972)     

973)     <!--

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

975)     <li>
976)     <b>Client Mode Use Cases for Arm</b>
977)     <br>
978)     Priority: <i>Medium</i>
979)     <br>
980)     Effort Level: <i>High</i>
981)     <br>
982)     Skill Level: <i>Medium</i>
983)     <br>

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

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

1028)     <p>
1029)     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>
1030)     </p>

1031)     </li>

1032)     -->

1033)     

1034)     <a id="vidalia-hidden-service-panel"></a>
1035)     <li>
1036)     <b>Torrc plugin and improved hidden service configuration panel</b>
1037)     <br>
1038)     Priority: <i>Medium</i>
1039)     <br>
1040)     Effort Level: <i>Medium</i>
1041)     <br>
1042)     Skill Level: <i>Medium</i>
1043)     <br>
1044)     Likely Mentors: <i>Tomás</i>
1045)     <p>Vidalia's configuration handling has changed in the alpha branch. Now
1046)     every Tor option is saved in the torrc file. With that change, the
1047)     Hidden Service configuration panel was removed due to its specificity
1048)     and its multiple bugs.</p>
1049)     
1050)     <p>The idea would be to provide the new Torrc class' functionality to the
1051)     Plugin Engine and with that, create a better Hidden Service
1052)     configuration panel as a plugin.</p>
1053)     
1054)     <p>A person undertaking this project should have good UI design, layout
1055)     skills and some C++ development experience. Previous experience with Qt
1056)     and Qt's Designer will be very helpful, but are not required. Javascript
1057)     knowledge is a plus, but it shouldn't be a problem if the person
1058)     complies with the previous requirements.</p>
1059)     </li>
1060)     

1061)     <a id="metricsSearch"></a>
1062)     <li>
1063)     <b>Searchable Tor descriptor and Metrics data archive</b>
1064)     <br>
1065)     Priority: <i>Medium</i>
1066)     <br>
1067)     Effort Level: <i>Medium</i>
1068)     <br>
1069)     Skill Level: <i>Medium</i>
1070)     <br>
1071)     Likely Mentors: <i>Karsten</i>
1072)     <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>
1073)     
1074)     <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>
1075)     
1076)     <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>
1077)     
1078)     <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>
1079)     

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

1081)     <li>
1082)     <b>Improve our unit testing process</b>

1083)     <br>

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

1085)     <br>

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

1087)     <br>

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

1089)     <br>

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

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

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

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

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

1105)     </li>
1106)     

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

1108)     <li>
1109)     <b>Simulator for slow Internet connections</b>

1110)     <br>

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

1112)     <br>

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

1114)     <br>

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

1116)     <br>

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

1118)     <p>

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

1124)     </p>
1125)     
1126)     <p>

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

1132)     </p>
1133)     
1134)     <p>

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

1140)     </p>

1141)     </li>
1142)     

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

1144)     <li>
1145)     <b>Torbutton equivalent for Thunderbird</b>

1146)     <br>

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

1148)     <br>

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

1150)     <br>

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

1152)     <br>

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

1154)     <p>

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

1160)     </p>

1161)     </li>
1162)     

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

1164)     <li>
1165)     <b>Usability testing of Tor</b>

1166)     <br>

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

1168)     <br>

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

1170)     <br>

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

1172)     <br>

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

1174)     <p>

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

1179)     </p>

1180)     
1181)     <p>
1182)     Please note that since this isn't a coding project, it isn't suitable for
1183)     Google Summer of Code.
1184)     </p>

1185)     </li>

1186)     

1187)     <a id="tailsMetadataAnonymizing"></a>
1188)     <li>
1189)     <b>Meta-data anonymizing toolkit for file publication</b>
1190)     <br>
1191)     Priority: <i>Medium</i>
1192)     <br>
1193)     Effort Level: <i>Low to Medium</i>
1194)     <br>
1195)     Skill Level: <i>Low to Medium</i>
1196)     <br>
1197)     Likely Mentors: <i>intrigeri, anonym</i>

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

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

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

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

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

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

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

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

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

1216)     </li>   
1217)  

1218)     <a id="tailsDebianLive"></a>
1219)     <li>
1220)     <b>Improve Debian Live support for persistence</b>
1221)     <br>
1222)     Priority: <i>Medium</i>
1223)     <br>
1224)     Effort Level: <i>Medium</i>
1225)     <br>
1226)     Skill Level: <i>Low to Medium</i>
1227)     <br>
1228)     Likely Mentors: <i>intrigeri, anonym</i>
1229)     <p>Data persistence is a somewhat tricky topic in a Live system context,

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

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

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

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

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

1236)     and require encrypted storage.</p>

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

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

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

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

1247)     </li>

1248)     

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

1250)     <li>
1251)     <b>Make torsocks/dsocks work on OS X</b>

1252)     <br>

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

1254)     <br>

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

1256)     <br>

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

1258)     <br>

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

1260)     <p>

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

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

1277)     </p>
1278)     </li>
1279)     

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

1281)     <li>
1282)     <b>Tor Controller Status Event Interface for Vidalia</b>
1283)     <br>
1284)     Priority: <i>Medium</i>
1285)     <br>
1286)     Effort Level: <i>Medium</i>
1287)     <br>
1288)     Skill Level: <i>Low to Medium</i>
1289)     <br>

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

1291)     <p>There are a number of status changes inside Tor of which the user may need
1292)     to be informed. For example, if the user is trying to set up his Tor as a
1293)     relay and Tor decides that its ports are not reachable from outside
1294)     the user's network, we should alert the user. Currently, all the user
1295)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1296)     likely never see since they don't receive a notification that something
1297)     has gone wrong. Even if the user does actually look at the message log,
1298)     most of the messages make little sense to the novice user.</p>
1299)     <p>Tor has the ability to inform Vidalia of many such status
1300)     changes, and we recently implemented support for a couple of these
1301)     events. Still, there are many more status events which the user should
1302)     be informed of, and we need a better UI for actually displaying them
1303)     to the user.</p>
1304)     <p>The goal of this project then is to design and implement a UI for
1305)     displaying Tor status events to the user. For example, we might put a
1306)     little badge on Vidalia's tray icon that alerts the user to new status
1307)     events they should look at. Double-clicking the icon could bring up a
1308)     dialog that summarizes recent status events in simple terms and maybe
1309)     suggests a remedy for any negative events if they can be corrected by
1310)     the user. Of course, this is just an example and one is free to
1311)     suggest another approach.</p>
1312)     <p>A person undertaking this project should have good UI design and layout
1313)     skills and some C++ development experience. Previous experience with Qt and
1314)     Qt's Designer will be very helpful, but are not required. Some
1315)     English writing ability will also be useful, since this project will
1316)     likely involve writing small amounts of help documentation that should
1317)     be understandable by non-technical users. Bonus points for some graphic
1318)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1319)     </li>
1320)     

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

1389)     <!--

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

1391)     <li>
1392)     <b>An Improved and More Usable Network Map in Vidalia</b>
1393)     <br>
1394)     Priority: <i>Low to Medium</i>
1395)     <br>
1396)     Effort Level: <i>Medium</i>
1397)     <br>
1398)     Skill Level: <i>Medium</i>
1399)     <br>

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

1401)     <p>
1402)     One of Vidalia's existing features is a network map that shows the user
1403)     the approximate geographic location of relays in the Tor network and
1404)     plots the paths the user's traffic takes as it is tunneled through the
1405)     Tor network. The map is currently not very interactive and has rather
1406)     poor graphics. Instead, we implemented KDE's Marble widget such
1407)     that it gives us a better quality map and enables improved interactivity,
1408)     such as allowing the user to click on individual relays or circuits to
1409)     display additional information. We want to add the ability
1410)     for users to click on a particular relay or a country containing one or
1411)     more Tor exit relays and say, "I want my connections to exit
1412)     from here."
1413)     </p>
1414)     
1415)     <p>
1416)     This project will first involve getting familiar with Vidalia
1417)     and the Marble widget's API. One will then integrate the widget
1418)     into Vidalia and customize Marble to be better suited for our application,
1419)     such as making circuits clickable, storing cached map data in Vidalia's
1420)     own data directory, and customizing some of the widget's dialogs.
1421)     </p>
1422)     
1423)     <p>
1424)     A person undertaking this project should have good C++ development
1425)     experience. Previous experience with Qt and CMake is helpful, but not
1426)     required.
1427)     </p>

1428)     </li>

1429)     -->

1430)     

1431)     <a id="obfsproxy-fuzzer"></a>
1432)     <li>
1433)     <b>Fuzzer for the Tor protocol</b>
1434)     <br>
1435)     Priority: <i>Low to Medium</i>
1436)     <br>
1437)     Effort Level: <i>Medium to High</i>
1438)     <br>
1439)     Skill Level: <i>High</i>
1440)     <br>
1441)     Likely Mentors: <i>asn</i>
1442)     <p>Involves researching good and smart ways to fuzz stateful network
1443)     protocols, and also implementing the fuzzer.</p>
1444)     
1445)     <p>We are mostly looking for a fuzzer that fuzzes the Tor protocol
1446)     itself, and not the Tor directory protocol.</p>
1447)     
1448)     <p>Bonus points if it's extremely modular. Relevant research:</p>
1449)     
1450)     <ul>
1451)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1452)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1453)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1454)       Testing and Machine Learning</li>
1455)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1456)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1457)       <li>Also look at the concepts of &quot;model checking&quot; and
1458)       &quot;symbolic execution&quot; to get inspired.</li>
1459)     </ul>
1460)     </li>
1461)     

1462)     <!--

1463)     <a id="armGui"></a>
1464)     <li>
1465)     <b>GUI for Arm</b>
1466)     <br>
1467)     Priority: <i>Low</i>
1468)     <br>
1469)     Effort Level: <i>High</i>
1470)     <br>
1471)     Skill Level: <i>Medium</i>
1472)     <br>

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

1474)     <p>
1475)     Arm has several unique features, some of the most interesting being its
1476)     connection listing (correlating netstat results against the Tor consensus)
1477)     and configuration editor (a quick method for editing Tor's config, with
1478)     information pulled from the control port and man page). However, since arm
1479)     is a command line controller it's of limited appeal to certain sets of
1480)     users. This project would be to build a GTK or Qt frontend for the
1481)     controller, providing similar features set but with a windowed interface.
1482)     </p>
1483)     
1484)     <p>
1485)     The vast majority of arm's more interesting functionality lies in its

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

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

1493)     -->

1494)     

1495)     <li>
1496)     <b>Bring up new ideas!</b>

1497)     <br>

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

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

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

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

1503)     might also be short on developers.
1504)     </li>
1505)     
1506)     </ol>
1507)     
1508)     <a id="OtherCoding"></a>
1509)     <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
1510)     <ol>
1511)     <li>Tor relays don't work well on Windows XP. On
1512)     Windows, Tor uses the standard <tt>select()</tt> system
1513)     call, which uses space in the non-page pool. This means
1514)     that a medium sized Tor relay will empty the non-page pool, <a

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

1516)     havoc and system crashes</a>. We should probably be using overlapped IO
1517)     instead. One solution would be to teach <a
1518)     href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
1519)     overlapped IO rather than select() on Windows, and then adapt Tor to
1520)     the new libevent interface. Christian King made a
1521)     <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
1522)     start</a> on this in the summer of 2007.</li>
1523)     
1524)     <li>We need to actually start building our <a href="<page
1525)     docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
1526)     fleshing out the design, modifying many different pieces of Tor, adapting
1527)     <a href="<page projects/vidalia>">Vidalia</a> so it supports the
1528)     new features, and planning for deployment.</li>
1529)     
1530)     <li>We need a flexible simulator framework for studying end-to-end
1531)     traffic confirmation attacks. Many researchers have whipped up ad hoc
1532)     simulators to support their intuition either that the attacks work
1533)     really well or that some defense works great. Can we build a simulator
1534)     that's clearly documented and open enough that everybody knows it's
1535)     giving a reasonable answer? This will spur a lot of new research.
1536)     See the entry <a href="#Research">below</a> on confirmation attacks for
1537)     details on the research side of this task &mdash; who knows, when it's
1538)     done maybe you can help write a paper or three also.</li>
1539)     

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

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

1544)     Tor if needed.</li>

1545)     
1546)     <li>Perform a security analysis of Tor with <a

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

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

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

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

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

1559)     for Tor and
1560)     UDP</a> &mdash; please let us know what's wrong with it.</li>
1561)     
1562)     <li>We're not that far from having IPv6 support for destination addresses
1563)     (at exit nodes). If you care strongly about IPv6, that's probably the
1564)     first place to start.</li>
1565)     
1566)     <li>We need a way to generate the website diagrams (for example, the "How
1567)     Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
1568)     from source, so we can translate them as UTF-8 text rather than edit
1569)     them by hand with Gimp. We might want to
1570)     integrate this as an wml file so translations are easy and images are
1571)     generated in multiple languages whenever we build the website.</li>
1572)     
1573)     <li>How can we make the various LiveCD/USB systems easier
1574)     to maintain, improve, and document?  One example is <a

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

1576)     System</a>.
1577)     </li>
1578)     
1579)     <li>
1580)     Another anti-censorship project is to try to make Tor
1581)     more scanning-resistant.  Right now, an adversary can identify <a

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

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

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