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 <a href="<page
19)     docs/bridges>">bridge</a> in less than 10 minutes with <a

20)     href="https://cloud.torproject.org/">tor cloud</a>!</li>

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

33)     

34)     <a id="Documentation"></a>
35)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
36)     <ol>
37)     <li>Help translate the web page and documentation into other
38)     languages. See the <a href="<page getinvolved/translation>">translation
39)     guidelines</a> if you want to help out. We especially need Arabic or
40)     Farsi translations, for the many Tor users in censored areas.</li>
41)     <li>Evaluate and document

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

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

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

46)     programs that interface to Tor</a>. Which ones are useful in which
47)     situations? Please help us test them out and document your results.</li>
48)     </ol>

49)     

50)     <a id="Advocacy"></a>
51)     <h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
52)     <ol>

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

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

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

58)     <a

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

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

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

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

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

65)     </ol>

66)     

67)     <a id="opw"></a>

68)     <h2><a class="anchor" href="#opw">Outreach Program for Women</a></h2>

69)     
70)     <p>
71)     Several organisations, including Tor, are taking part in the <a
72)     href="https://live.gnome.org/OutreachProgramForWomen">2013 Outreach Program
73)     for Women</a>. This is a mentoring program similar to <a
74)     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2012">Google
75)     Summer of Code</a> targeted at getting more women involved in open source.
76)     </p>
77)     
78)     <p>

79)     The program runs from January 2 through April 2, 2013. The application
80)     deadline is December 3, 2012 and it is best to start as early as possible
81)     preparing your application. Like GSoC the program involves a stipend so, if
82)     you're a woman interested in fighting surveillance and censorship around
83)     the world then let us know!

84)     </p>
85)     
86)     <p>
87)     To apply...
88)     </p>
89)     
90)     <ol>
91)       <li>Read up on the <a href="https://live.gnome.org/OutreachProgramForWomen">outreach program</a>.</li>
92)       <li>Look over our projects and task ideas below. If nothing there strikes your fancy then feel free to make one of your own.</li>
93)       <li>Join the <a href="https://www.torproject.org/about/contact.html.en#irc">#tor-dev irc channel</a> and introduce yourself!</li>
94)       <li>Contact the maintainer of the project that you're interested in contributing to, and talk with them about how to get started. Maintainers are listed in the table below. Note that you need to submit a patch or contribute in some way before you can apply to the program.</li>
95)       <li><a href="https://live.gnome.org/OutreachProgramForWomen#Send_in_an_Application">Send your application</a> to opw-list@gnome.org. Please be available and responsive throughout the application period so we can work with you on improving it.</li>
96)     </ol>
97)     

98)     <a id="Projects"></a>
99)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

100)     

101)     <p>
102)     Below are a list of Tor related projects we're developing and/or
103)     maintaining. Most discussions happen on IRC so if you're interested in any
104)     of these (or you have a project idea of your own), then please <a

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

108)     </p>

109)     

110)     <table id="projects">
111)       <tr>
112)         <th>Name</th>
113)         <th>Category</th>
114)         <th>Language</th>
115)         <th>Activity</th>
116)         <th>Contributors</th>
117)       </tr>

118)       

119)       <tr>
120)         <td><a href="#project-tor">Tor</a></td>
121)         <td>Core</td>
122)         <td>C</td>
123)         <td>Heavy</td>

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

125)       </tr>

126)       

127)       <tr class="alt">

128)         <td>*<a href="#project-jtor">JTor</a></td>
129)         <td>Core</td>
130)         <td>Java</td>
131)         <td>None</td>

132)         <td>bleidl</td>

133)       </tr>

134)       

135)       <tr>

136)         <td><a href="#project-tbb">TBB</a></td>
137)         <td>Usability</td>

138)         <td>Sys Admin</td>
139)         <td>Moderate</td>

140)         <td>Erinn</td>

141)       </tr>

142)       

143)       <tr class="alt">

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

145)         <td>Usability</td>

146)         <td>Sys Admin</td>

147)         <td>Heavy</td>

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

149)       </tr>

150)       

151)       <tr>

152)         <td><a href="#project-torsocks">Torsocks</a></td>
153)         <td>Usability</td>
154)         <td>C</td>

155)         <td>Heavy</td>
156)         <td>ioerror, nickm</td>

157)       </tr>

158)       

159)       <tr class="alt">

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

162)         <td>Sys Admin</td>

163)         <td>Light</td>

164)         <td>ioerror</td>

165)       </tr>

166)       

167)       <tr>

168)         <td><a href="#project-vidalia">Vidalia</a></td>
169)         <td>User Interface</td>
170)         <td>C++, Qt</td>
171)         <td>Light</td>
172)         <td>chiiph</td>
173)       </tr>

174)       

175)       <tr class="alt">

176)         <td><a href="#project-arm">Arm</a></td>
177)         <td>User Interface</td>
178)         <td>Python, Curses</td>

179)         <td>Light</td>

180)         <td>atagar</td>
181)       </tr>

182)       

183)       <tr>

184)         <td><a href="#project-orbot">Orbot</a></td>
185)         <td>User Interface</td>
186)         <td>Java</td>

187)         <td>Moderate</td>

188)         <td>n8fr8, ioerror</td>

189)       </tr>

190)       

191)       <tr class="alt">

192)         <td><a href="#project-torbutton">Torbutton</a></td>
193)         <td>Browser Add-on</td>
194)         <td>Javascript</td>
195)         <td>Moderate</td>
196)         <td>mikeperry</td>
197)       </tr>

198)       

199)       <tr>

200)         <td><a href="#project-torbirdy">TorBirdy</a></td>
201)         <td>Browser Add-on</td>
202)         <td>JavaScript</td>
203)         <td>Heavy</td>
204)         <td>Sukhbir (sukhe), ioerror</td>
205)       </tr>
206)       
207)       <tr class="alt">

208)         <td><a href="#project-obfsproxy">Obfsproxy</a></td>
209)         <td>Client Add-on</td>
210)         <td>C</td>
211)         <td>Moderate</td>
212)         <td>nickm, asn</td>
213)       </tr>

214)       

215)       <tr>

216)         <td>*<a href="#project-thandy">Thandy</a></td>
217)         <td>Updater</td>
218)         <td>Python</td>
219)         <td>Light</td>

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

221)       </tr>

222)       

223)       <tr class="alt">

224)         <td>*<a href="#project-ooni-probe">Ooni Probe</a></td>
225)         <td>Scanner</td>
226)         <td>Python</td>
227)         <td>Moderate</td>

228)         <td>hellais, isis, ioerror</td>

229)       </tr>

230)       

231)       <tr>

232)         <td><a href="#project-shadow">Shadow</a></td>
233)         <td>Experimentation</td>
234)         <td>C, Python</td>
235)         <td>Moderate</td>
236)         <td>robgjansen</td>
237)       </tr>

238)       

239)       <tr class="alt">

240)         <td><a href="#project-torctl">TorCtl</a></td>
241)         <td>Library</td>
242)         <td>Python</td>

243)         <td>None</td>
244)         <td>aagbsn</td>

245)       </tr>

246)       

247)       <tr>

248)         <td>*<a href="#project-stem">Stem</a></td>
249)         <td>Library</td>
250)         <td>Python</td>
251)         <td>Heavy</td>

252)         <td>atagar, neena</td>

253)       </tr>

254)       

255)       <tr class="alt">

256)         <td><a href="#project-metrics">Metrics</a></td>
257)         <td>Client Service</td>
258)         <td>Java</td>
259)         <td>Heavy</td>
260)         <td>karsten</td>
261)       </tr>

262)       

263)       <tr>

264)         <td><a href="#project-atlas">Atlas</a></td>
265)         <td>Client Service</td>
266)         <td>JavaScript</td>
267)         <td>Moderate</td>
268)         <td>hellais</td>
269)       </tr>

270)       

271)       <tr class="alt">

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

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

275)         <td>None</td>
276)         <td></td>
277)       </tr>

278)       

279)       <tr>

280)         <td><a href="#project-compass">Compass</a></td>
281)         <td>Client Service</td>
282)         <td>Python</td>
283)         <td>Heavy</td>
284)         <td>gsathya, karsten</td>
285)       </tr>
286)       

287)       <tr class="alt">

288)         <td><a href="#project-weather">Weather</a></td>
289)         <td>Client Service</td>
290)         <td>Python</td>

291)         <td>None</td>

292)         <td>kaner</td>
293)       </tr>

294)       

295)       <tr>

296)         <td><a href="#project-gettor">GetTor</a></td>
297)         <td>Client Service</td>
298)         <td>Python</td>

299)         <td>None</td>

300)         <td>kaner</td>

301)       </tr>

302)       

303)       <tr class="alt">

304)         <td><a href="#project-torcheck">TorCheck</a></td>
305)         <td>Client Service</td>
306)         <td>Python, Perl</td>
307)         <td>None</td>

308)         <td>ioerror</td>

309)       </tr>

310)       

311)       <tr>

312)         <td><a href="#project-onionoo">Onionoo</a></td>
313)         <td>Backend Service</td>

314)         <td>Java, Python</td>

315)         <td>Moderate</td>

316)         <td>karsten, gsathya</td>

317)       </tr>

318)       

319)       <tr class="alt">

320)         <td><a href="#project-bridgedb">BridgeDB</a></td>
321)         <td>Backend Service</td>
322)         <td>Python</td>

323)         <td>None</td>

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

325)       </tr>

326)       

327)       <tr>

328)         <td><a href="#project-torflow">TorFlow</a></td>
329)         <td>Backend Service</td>
330)         <td>Python</td>

331)         <td>None</td>
332)         <td>aagbsn</td>

333)       </tr>

334)       

335)       <tr class="alt">

336)         <td>*<a href="#project-torbel">TorBEL</a></td>
337)         <td>Backend Service</td>
338)         <td>Python</td>
339)         <td>None</td>
340)         <td>Sebastian</td>
341)       </tr>
342)     </table>

343)     

344)     <sub>
345)     * Project is still in an alpha state.
346)     </sub>

347)     

348)     <br /><br />

349)     

350)     <a id="project-tor"></a>
351)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
352)     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
353)     tracker</a>)</h3>

354)     

355)     <p>
356)     Central project, providing the core software for using and participating in
357)     the Tor network. Numerous people contribute to the project to varying
358)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
359)     </p>

360)     

361)     <p>
362)     <b>Project Ideas:</b><br />

363)     <i><a href="#limitCapabilities">Run With Limited Capabilities</a></i><br />
364)     <i><a href="#torCleanup">Tor Codebase Cleanup</a></i><br />
365)     <i><a href="#httpsImersonation">HTTPS Server Impersonation</a></i><br />
366)     <i><a href="#chutneyExpansion">Make Chutney Do More, More Reliably</a></i>

367)     </p>

368)     

369)     <a id="project-jtor"></a>
370)     <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a
371)     href="https://github.com/brl/JTor">code</a>, <a
372)     href="https://github.com/brl/JTor/issues">bug
373)     tracker</a>)</h3>

374)     

375)     <p>
376)     Java implementation of Tor and successor to <a
377)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
378)     isn't yet complete, and has been inactive since Fall 2010.
379)     </p>

380)     

381)     <a id="project-tbb"></a>
382)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
383)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
384)     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
385)     tracker</a>)</h3>

386)     

387)     <p>
388)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
389)     and Firefox preconfigured to work together out of the box. This is actively
390)     being worked on by Erinn Clark.
391)     </p>

392)     

393)     <!--

394)     <p>
395)     <b>Project Ideas:</b><br />
396)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
397)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
398)     </p>

399)     -->

400)     

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

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

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

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

405)     tracker</a>)</h3>

406)     

407)     <p>

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

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

414)     

415)     <!--

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

418)     <i><a href="#tailsHiddenServicePetnames">Petname system for Tor hidden
419)     services</a></i><br />
420)     <i><a href="#tailsServer">Tails server: Self-hosted services behind
421)     Tails-powered Tor hidden services</a></i>

422)     </p>

423)     -->

424)     

425)     <a id="project-torsocks"></a>
426)     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
427)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
428)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
429)     tracker</a>)</h3>

430)     

431)     <p>
432)     Utility for adapting other applications to work with Tor. Development has
433)     slowed and compatibility issues remain with some platforms, but it's
434)     otherwise feature complete.
435)     </p>

436)     

437)     <!--

438)     <p>
439)     <b>Project Ideas:</b><br />
440)     <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
441)     </p>

442)     -->

443)     

444)     <a id="project-torouter"></a>
445)     <h3><a

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

447)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
448)     tracker</a>)</h3>

449)     

450)     <p>
451)     Project to provide an easy-to-use, embedded Tor instance for routers. This

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

453)     </p>

454)     

455)     <a id="project-vidalia"></a>
456)     <h3><a href="<page projects/vidalia>">Vidalia</a> (<a

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

458)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority">bug
459)     tracker</a>)</h3>

460)     

461)     <p>
462)     The most commonly used user interface for Tor. Matt Edman started the
463)     project in 2006 and brought it to its current stable state. Development
464)     slowed for several years, though Tomás Touceda has since taken a lead with
465)     pushing the project forward.
466)     </p>

467)     

468)     <!--

469)     <p>
470)     <b>Project Ideas:</b><br />

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

473)     </p>

474)     -->

475)     

476)     <a id="project-arm"></a>
477)     <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a

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

479)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=arm&order=priority">bug
480)     tracker</a>)</h3>

481)     

482)     <p>
483)     Command-line monitor for Tor. This has been under very active development
484)     by its author, Damian Johnson, since early 2009 to make it a better
485)     general-purpose controller for *nix environments.
486)     </p>

487)     

488)     <!--

489)     <p>
490)     <b>Project Ideas:</b><br />

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

493)     </p>

494)     -->

495)     

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

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

499)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Orbot&order=priority">bug
500)     tracker</a>)</h3>

501)     

502)     <p>
503)     Provides Tor on the Android platform. This was under very active
504)     development up through Fall 2010, after which things have been quiet.
505)     </p>

506)     

507)     <!--

508)     <p>
509)     <b>Project Ideas:</b><br />

510)     <i><a href="#orbot-torbutton">TorButton for Mobile Firefox 4 or Custom Browser on Android</a></i><br />
511)     <i><a href="#orbot-userInterface">Build a better user interface for Orbot</a></i><br />

512)     <i><a href="#orbot-optimisation">Core Tor mobile optimisation</a></i>

513)     </p>

514)     -->

515)     

516)     <a id="project-torbutton"></a>
517)     <h3><a href="<page torbutton/index>">Torbutton</a> (<a
518)     href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
519)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug
520)     tracker</a>)</h3>

521)     

522)     <p>
523)     Firefox addon that addresses many of the client-side threats to browsing
524)     the Internet anonymously. Mike has since continued to adapt it to new
525)     threats, updated versions of Firefox, and possibly <a
526)     href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">Chrome
527)     as well</a>.
528)     </p>

529)     

530)     <a id="project-torbirdy"></a>
531)     <h3>TorBirdy (<a
532)     href="https://github.com/ioerror/torbirdy">code</a>, <a
533)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
534)     tracker</a>)</h3>
535)     
536)     <p>
537)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
538)     </p>
539)     
540)     <p>
541)     <b>Project Ideas:</b><br />
542)     <i><a href="#improveTorbirdy">Improving TorBirdy</a></i><br />
543)     </p>
544)     

545)     <a id="project-obfsproxy"></a>
546)     <h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc">Obfsproxy</a> (<a
547)     href="https://gitweb.torproject.org/obfsproxy.git">code</a>, <a
548)     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
549)     tracker</a>)</h3>

550)     

551)     <p>
552)     A proxy that shapes Tor traffic, making it harder for censors to detect and
553)     block Tor.
554)     </p>

555)     

556)     <!--

557)     <p>
558)     <b>Project Ideas:</b><br />
559)     <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
560)     <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
561)     <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
562)     </p>

563)     -->

564)     

565)     <a id="project-thandy"></a>
566)     <h3>Thandy (<a
567)     href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>

568)     

569)     <p>
570)     Updater for Tor. The project began in the Summer of 2008 but wasn't
571)     completed. Recently interest in it has been rekindled and many aspects of
572)     its design (including the language it'll be in) are currently in flux.
573)     </p>

574)     

575)     <a id="project-ooni-probe"></a>
576)     <h3>Ooni Probe (<a
577)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
578)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
579)     tracker</a>)</h3>

580)     

581)     <p>
582)     Censorship scanner, checking your local connection for blocked or modified
583)     content.
584)     </p>

585)     

586)     <a id="project-shadow"></a>
587)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
588)     href="https://github.com/shadow">code</a>, <a
589)     href="https://github.com/shadow/shadow/issues">bug
590)     tracker</a>)</h3>

591)     

592)     <p>
593)     Shadow is a discrete-event network simulator that runs the real
594)     Tor software as a plug-in. Shadow is open-source software that enables
595)     accurate, efficient, controlled, and repeatable Tor experimentation.
596)     </p>

597)     

598)     <a id="project-torctl"></a>
599)     <h3>TorCtl (<a
600)     href="https://gitweb.torproject.org/pytorctl.git">code</a>, <a
601)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority">bug
602)     tracker</a>)</h3>

603)     

604)     <p>
605)     Python bindings and utilities for using the Tor control port. It has been
606)     stable for several years, with only minor revisions.
607)     </p>

608)     

609)     <a id="project-stem"></a>

610)     <h3><a href="https://stem.readthedocs.org/en/latest/index.html">Stem</a> (<a

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

612)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">bug

613)     tracker</a>)</h3>

614)     

615)     <p>
616)     Python controller library with a similar scope to TorCtl, but with better
617)     testing, documentation, and API. This project is not yet feature complete.
618)     </p>

619)     

620)     <p>
621)     <b>Project Ideas:</b><br />

622)     <i><a href="#stemUsability">Stem Usability Improvements</a></i>

623)     </p>

624)     

625)     <a id="project-metrics"></a>
626)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
627)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
628)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
629)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
630)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
631)     tracker</a>)</h3>

632)     

633)     <p>
634)     Processing and analytics of consensus data, provided to users via the
635)     metrics portal. This has been under active development for several years by
636)     Karsten Loesing.
637)     </p>

638)     

639)     <p>
640)     <b>Project Ideas:</b><br />
641)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
642)     </p>

643)     

644)     <a id="project-atlas"></a>
645)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
646)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

647)     

648)     <p>
649)     Atlas is a web application to discover Tor relays and bridges. It provides
650)     useful information on how relays are configured along with graphics about
651)     their past usage. This is the third evolution of the TorStatus application.
652)     </p>

653)     

654)     <a id="project-torstatus"></a>

655)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorStatus">TorStatus</a> (<a

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

657)     

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

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

665)     </p>

666)     

667)     <a id="project-compass"></a>
668)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
669)     href="https://gitweb.torproject.org/compass.git">code</a>, <a
670)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Compass&order=priority">bug
671)     tracker</a>)</h3>
672)     
673)     <p>
674)     Compass is a web and command line application that filters and
675)     aggregates the Tor relays based on various attributes.
676)     </p>
677)     

678)     <p>
679)     <b>Project Ideas:</b><br />
680)     <i><a href="#compassRefactoring">Compass Refactoring</a></i>
681)     </p>
682)     

683)     <a id="project-weather"></a>

684)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Weather">Weather</a> (<a

685)     href="https://gitweb.torproject.org/weather.git">code</a>, <a
686)     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
687)     tracker</a>)</h3>

688)     

689)     <p>
690)     Provides automatic notification to subscribed relay operators when their
691)     relay's unreachable. This underwent a rewrite by the <a
692)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
693)     in early 2011.
694)     </p>

695)     

696)     <a id="project-gettor"></a>

697)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/GetTor">GetTor</a> (<a

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

699)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=GetTor&order=priority">bug
700)     tracker</a>)</h3>

701)     

702)     <p>
703)     E-mail autoresponder providing Tor's packages over SMTP. This has been
704)     relatively unchanged for quite a while.
705)     </p>

706)     

707)     <a id="project-torcheck"></a>

708)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorCheck">TorCheck</a> (<a

709)     href="https://svn.torproject.org/svn/check/trunk/">code</a>, <a
710)     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
711)     tracker</a>)</h3>

712)     

713)     <p>
714)     Provides a simple site for determining if the visitor is using Tor or not.
715)     This has been relatively unchanged for quite a while.
716)     </p>

717)     

718)     <a id="project-onionoo"></a>
719)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a

720)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
721)     href="https://gitweb.torproject.org/pyonionoo.git">python
722)     codebase</a>)</h3>

723)     

724)     <p>
725)     Onionoo is a JSON based protocol to learn information about currently
726)     running Tor relays and bridges.
727)     </p>

728)     

729)     <a id="project-bridgedb"></a>

730)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/BridgeDB">BridgeDB</a> (<a

731)     href="https://gitweb.torproject.org/bridgedb.git">code</a>, <a
732)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=BridgeDB&order=priority">bug
733)     tracker</a>)</h3>

734)     

735)     <p>
736)     Backend bridge distributor, handling the various pools they're distributed
737)     in. This was actively developed until Fall of 2010.
738)     </p>

739)     

740)     <a id="project-torflow"></a>

741)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorFlow">TorFlow</a> (<a

742)     href="https://gitweb.torproject.org/torflow.git">code</a>, <a
743)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torflow&order=priority">bug
744)     tracker</a>)</h3>

745)     

746)     <p>
747)     Library and collection of services for actively monitoring the Tor network.
748)     These include the Bandwidth Scanners (measuring throughput of relays) and
749)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
750)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
751)     months later. Both have been under active use since then, but development
752)     has stopped.
753)     </p>

754)     

755)     <a id="project-torbel"></a>
756)     <h3><a

757)     href="https://blog.torproject.org/blog/torbel-tor-bulk-exit-list-tools">TorBEL</a> (<a
758)     href="https://gitweb.torproject.org/torbel.git">code</a>, <a

759)     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
760)     tracker</a>)</h3>

761)     

762)     <p>
763)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
764)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
765)     (though unmaintained) Haskell application for this purpose. The initial
766)     version of TorBEL was started in GSOC 2010 but since then the project has
767)     been inactive.
768)     </p>

769)     

770)     <a id="Coding"></a>
771)     <a id="Summer"></a>

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

773)     

774)     <p>

775)     You may find some of these projects to be good ideas for <a href="<page
776)     about/gsoc>">Google Summer of Code</a> and the <a
777)     href="https://live.gnome.org/OutreachProgramForWomen">Outreach Program for
778)     Women</a>. We have labelled each idea with how useful it would be to the
779)     overall Tor project (priority), how much work we expect it would be (effort
780)     level), how much clue you should start with (skill level), and which of our
781)     <a href="<page about/corepeople>">core developers</a> would be good
782)     mentors. If one or more of these ideas looks promising to you, please <a

783)     href="<page about/contact>">contact us</a> to discuss your plans rather than
784)     sending blind applications. You may also want to propose your own project
785)     idea &mdash; which often results in the best applications.
786)     </p>

787)     

788)     <ol>

789)     

790)     <a id="improveTorbirdy"></a>
791)     <li>
792)     <b>Improving TorBirdy</b>
793)     <br>
794)     Priority: <i>High</i>
795)     <br>
796)     Effort Level: <i>High</i>
797)     <br>
798)     Skill Level: <i>Medium to High</i>
799)     <br>
800)     Likely Mentors: <i>Sukhbir, Jacob</i>
801)     <p>
802)     TorBirdy is Torbutton for Thunderbird, Icedove and related Mozilla mail
803)     clients.
804)     </p>
805)     <p>
806)     TorBirdy is under active development and is available from <a
807)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy">our wiki</a>
808)     and <a
809)     href="https://addons.mozilla.org/en-US/thunderbird/addon/torbirdy/">mozilla's
810)     addons site</a>.
811)     </p>
812)     
813)     <p>
814)     The goal of this project is to improve TorBirdy by:
815)     </p>
816)     
817)     <ul>
818)       <li>
819)         Writing a Thunderbird patch to plug known leaks. We have already <a
820)         href="https://bugzilla.mozilla.org/show_bug.cgi?id=776397">submitted a
821)         patch to Thunderbird</a> but we anticipate there will be much more work
822)         required before it is accepted, possibly involving rewriting the entire
823)         patch; this appears trivial, but it is not, as we are proposing a
824)         completely new privacy-safe message-ID header generation algorithm for
825)         Thunderbird.
826)       </li>
827)       <li>
828)         Implementing a JavaScript HTTP proxy (see the <a
829)         href="https://trac.torproject.org/projects/tor/ticket/6958">ticket</a>)
830)       </li>
831)       <li>
832)         Auditing TorBirdy for leaks and for use with other add-ons (as an
833)         example see its <a
834)         href="https://trac.torproject.org/projects/tor/ticket/6319">ticket</a>)
835)       </li>
836)     </ul>
837)     
838)     <p>
839)     A student undertaking this project should have some C++ and JavaScript
840)     development experience. Previous experience with Firefox/Thunderbird
841)     extension development is a plus, but not required.
842)     </p>
843)     </li>
844)     
845)     <!--

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

847)     <li>

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

849)     <br>

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

851)     <br>

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

853)     <br>

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

855)     <br>

856)     Likely Mentors: <i>Jacob</i>

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

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

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

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

868)     and Mac OS X, and be comfortable with C/C++ and shell scripting.</p>

869)     <p>Since the core of this project is researching and auditing TBB this is
870)     not likely to be a good GSoC project.</p>

871)     </li>

872)     -->

873)     

874)     <!--

875)     <a id="firewallProbeTool"></a>
876)     <li>
877)     <b>Develop a fully automatic firewall-probing system</b>
878)     <br>
879)     Priority: <i>High</i>
880)     <br>
881)     Effort Level: <i>Medium to High</i>
882)     <br>
883)     Skill Level: <i>High</i>
884)     <br>

885)     Likely Mentors: <i>Robert Ransom, Jacob</i>

886)     <p>We would like to have a fully automatic firewall-probing system for
887)     blocking systems with no long-term state (i.e. firewalls that can
888)     examine each connection, but do not change their behaviour for future
889)     connections based on the traffic they have seen).</p>
890)     <p>Ideally, volunteers would only need to set up one or more test servers,
891)     and run the probe client program on a publicly accessible computer
892)     behind the firewall.</p>
893)     <p>The test tool should:</p>
894)     <ul>
895)     <li>generate packet captures on both ends (and send them out to the
896)         extent possible),</li>
897)     <li>cycle through all the SSL configurations we might want to test
898)         through a censorship device, and</li>
899)     <li>also test some other protocols to see whether they are allowed
900)         through the firewall (IMAP and other mail protocols, BitTorrent,
901)         DTLS, etc.).</li>
902)     </ul>
903)     </li>

904)     -->

905)     

906)     <!--

907)     <a id="orbot-torbutton"></a>
908)     <li>
909)     <b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>
910)     <br>
911)     Priority: <i>High</i>
912)     <br>
913)     Effort Level: <i>High</i>
914)     <br>
915)     Skill Level: <i>High</i>
916)     <br>

917)     Likely Mentors: <i>Jake</i>

918)     <p>Initial work has been done on implementing a proxy-setting add-on for
919)     Firefox on Android (see <a
920)     href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a
921)     full port of TorButton needs to be done (dependent upon Firefox 4 port of
922)     TorButton). The other approach is to implement a custom &quot;Tor
923)     Browser&quot; based on Firefox or Webkit browser. See <a
924)     href="http://code.google.com/p/torora/wiki/Android">Torora</a> for progress
925)     on this so far.</p>
926)     </li>

927)     -->

928)     

929)     <!--

930)     <a id="obfsproxy-new-transports"></a>
931)     <li>
932)     <b>New and innovative pluggable transports</b>
933)     <br>
934)     Priority: <i>High</i>
935)     <br>
936)     Effort Level: <i>High</i>
937)     <br>
938)     Skill Level: <i>High</i>
939)     <br>

940)     Likely Mentors: <i>asn, Steven</i>

941)     <p>Not-very-smart transports like ROT13 and base64 are nice but not super
942)     interesting. Other ideas like bittorrent transports might be relevant,
943)     but you will have to provide security proofs on why they are harder to
944)     detect and block than other less-sophisticated transports.</p>

945)     

946)     <p>The whole point of this project, though, is to come up with new
947)     transports that we haven't already thought of. Be creative.</p>

948)     

949)     <p>Bonus points if your idea is interesting and still implementable
950)     through the summer period.</p>

951)     

952)     <p>More bonus points if it's implemented on top of obfsproxy, or if your
953)     implementation has a pluggable transport interface on top of it (as
954)     specified <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt">here</a>).</p>
955)     </li>

956)     -->

957)     

958)     <!--

959)     <a id="obfsproxy-scanning-measures"></a>
960)     <li>
961)     <b>Defensive bridge active scanning measures</b>
962)     <br>
963)     Priority: <i>High</i>
964)     <br>
965)     Effort Level: <i>High</i>
966)     <br>
967)     Skill Level: <i>High</i>
968)     <br>
969)     Likely Mentors: <i>asn</i>
970)     <p>Involves providing good answers to <a
971)     href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html">this
972)     thread</a> as well as concrete implementation plans for it.</p>

973)     

974)     <p>This also involves implementing proposals <a
975)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a>
976)     and <a
977)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p>
978)     </li>

979)     -->

980)     

981)     <a id="limitCapabilities"></a>
982)     <li>
983)     <b>Run With Limited Capabilities</b>
984)     <br>
985)     Priority: <i>Medium to High</i>
986)     <br>
987)     Effort Level: <i>Medium to High</i>
988)     <br>
989)     Skill Level: <i>High</i>
990)     <br>
991)     Likely Mentors: <i>Nick (nickm)</i>
992)     <p>
993)     Many modern operating systems give a running program the ability to drop
994)     capabilities that it no longer needs, and other ways for a program to run
995)     pieces of itself in a sandbox with diminished privileges.
996)     </p>
997)     
998)     <p>
999)     We'd like to do this with Tor, to improve its resistance to attacks.  The
1000)     easiest areas to address would be on systems like <a
1001)     href="https://lwn.net/Articles/475361/">recent Linux kernels</a> that make
1002)     it easy to drop or restrict the set of syscalls that a program can invoke.
1003)     That's a great project, but probably not big enough for an internship just
1004)     on its own.  For that, we'd want to make progress on at least multiple
1005)     platforms, or look into refactoring Tor into pieces that need more
1006)     privileges and pieces that don't with an eye towards sandboxing them
1007)     differently.
1008)     </p>
1009)     
1010)     <p>
1011)     See tickets <a href="https://trac.torproject.org/7005">#7005</a> and <a
1012)     href="https://trac.torproject.org/5219">#5219</a>, and their descendants,
1013)     for more information.
1014)     </p>
1015)     </li>
1016)     

1017)     <a id="docUpdate"></a>
1018)     <li>
1019)     <b>Website and video documentation update</b>
1020)     <br>
1021)     Priority: <i>High</i>
1022)     <br>
1023)     Effort Level: <i>Medium</i>
1024)     <br>
1025)     Skill Level: <i>Medium</i>
1026)     <br>
1027)     Likely Mentors: <i>Runa, Karen</i>
1028)     <p>
1029)     Identify outdated and/or weak pages on torproject.org and re-write the
1030)     documentation to appeal to a less technical, more goal-oriented
1031)     audience. Create a number of 3-5 minute videos with graphically
1032)     portray the written documentation. See
1033)     <a href="https://trac.torproject.org/projects/tor/query?component=Website&status=new">the
1034)     website tickets</a> for more information and a starting point.
1035)     </p>
1036)     </li>
1037)     

1038)     <a id="torCleanup"></a>
1039)     <li>
1040)     <b>Tor Codebase Cleanup</b>
1041)     <br>
1042)     Priority: <i>Medium to High</i>
1043)     <br>
1044)     Effort Level: <i>Low to High, depending on subproject chosen</i>
1045)     <br>
1046)     Skill Level: <i>Medium to High</i>
1047)     <br>
1048)     Likely Mentors: <i>Nick (nickm)</i>
1049)     <p>
1050)     The Tor code is almost 10 years old in places, and we haven't always had
1051)     enough time or wisdom to write things as well as we could have.  Our unit
1052)     test coverage is shamefully low, and the dependency graph of our modules is
1053)     shamefully convoluted . We could use refactoring and unit tests!  Please
1054)     look through the Tor source code and look for ugly or tricky code or
1055)     dependencies -- the uglier and trickier the better -- and think about how
1056)     you could make the code look better, read better, and (subject to testing)
1057)     work better.
1058)     </p>
1059)     
1060)     <p>
1061)     If this is for a fun side-project, it would be great for you to work on
1062)     anything that can be made better and more tested.  For an internship-level
1063)     position, we'd hope that you could find a number of particularly tricky or
1064)     knotty piece of the code to clean up, and aim for resolving the ugliest
1065)     problems, not necessarily the easiest.
1066)     </p>
1067)     
1068)     <p>
1069)     For a big project here, it would be great to pick one of the major
1070)     "submodules" of Tor -- path selection, node discovery, directory authority
1071)     operations, directory service -- and refactor its interface completely, to
1072)     minify and codify its points of contact with the rest of Tor.
1073)     </p>
1074)     </li>
1075)     
1076)     <a id="httpsImersonation"></a>
1077)     <li>
1078)     <b>HTTPS Server Impersonation</b>
1079)     <br>
1080)     Priority: <i>Medium</i>
1081)     <br>
1082)     Effort Level: <i>Medium to High</i>
1083)     <br>
1084)     Skill Level: <i>Medium to High</i>
1085)     <br>
1086)     Likely Mentors: <i>Nick (nickm)</i>
1087)     <p>
1088)     We have an open proposal for a way to make Tor bridges avoid censorship by
1089)     impersonating an HTTPS server.  Specifically, we need to hack some popular
1090)     SSL "reverse proxy" (your choice) so that it relays regular web connections
1091)     to an HTTP server, but certain connections to a local Tor process.  <a
1092)     href="https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/203-https-frontend.txt">Proposal
1093)     203</a> has a general design sketch.
1094)     </p>
1095)     </li>
1096)     
1097)     <a id="chutneyExpansion"></a>
1098)     <li>
1099)     <b>Make Chutney Do More, More Reliably</b>
1100)     <br>
1101)     Priority: <i>Medium</i>
1102)     <br>
1103)     Effort Level: <i>Medium to High, depending on scope of project</i>
1104)     <br>
1105)     Skill Level: <i>Medium</i>
1106)     <br>
1107)     Likely Mentors: <i>Nick (nickm)</i>
1108)     <p>
1109)     We have a little Python tool called <a
1110)     href="https://gitweb.torproject.org/nickm/chutney.git">Chutney</a> for
1111)     making small local test networks.  It's small, not widely used, and not as
1112)     automated as it could be.
1113)     </p>
1114)     
1115)     <p>
1116)     It would be great to see chutney extended and a set of supporting tests
1117)     built to the point where we could use Chutney to exercise various Tor
1118)     features as an automated integration test.
1119)     </p>
1120)     </li>
1121)     

1122)     <a id="stemUsability"></a>
1123)     <li>
1124)     <b>Stem Usability Improvements</b>
1125)     <br>
1126)     Priority: <i>Medium</i>
1127)     <br>
1128)     Effort Level: <i>Medium</i>
1129)     <br>
1130)     Skill Level: <i>Medium</i>
1131)     <br>
1132)     Likely Mentors: <i>Damian (atagar)</i>
1133)     <p>
1134)     <a href="https://stem.readthedocs.org/en/latest/index.html">Stem</a> is a
1135)     python controller library for tor. Like it's predecessor, <a
1136)     href="#project-torctl">TorCtl</a>, it uses tor's <a
1137)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control
1138)     protocol</a> to help developers program against the tor process, enabling
1139)     them to build things similar to <a href="#project-vidalia">Vidalia</a> and
1140)     <a href="#project-arm">arm</a>.
1141)     </p>
1142)     
1143)     <p>
1144)     While TorCtl provided a fine first draft for this sort of functionality,
1145)     it has not proved to be extensible nor maintainable. Stem is a rewrite of
1146)     TorCtl with a heavy focus on testing, documentation, and providing a
1147)     developer friendly API.
1148)     </p>
1149)     
1150)     <p>
1151)     Stem is very nearly feature complete but presently has no users. We
1152)     want to change that prior to making our first release for a couple
1153)     reasons...
1154)     </p>
1155)     
1156)     <ul>
1157)       <li>Make sure that we have a reasonably good API, and improve the rough
1158)       edges that hurt its usability.</li>
1159)       <li>Provide examples for how stem can be used.</li>
1160)     </ul>
1161)     
1162)     <p>
1163)     This project involves several tasks...
1164)     </p>
1165)     
1166)     <ol>
1167)       <li>Move stem's site to Tor's website (<a href="https://trac.torproject.org/projects/tor/ticket/7324">ticket</a>)</li>
1168)       <li>Set up Piwik for our site (<a href="https://trac.torproject.org/projects/tor/ticket/7424">ticket</a>)</li>
1169)       <li>Come up with a better, more developer friendly "Module Overview" for our documentation (<a href="https://stem.readthedocs.org/en/latest/api/control.html">example page</a>). For instance, it would be nice to provide interlinking between the overview and the classes/methods that it lists. This will probably involve asking for help from the <a href="http://sphinx-doc.org/">Sphinx user list</a>.</li>
1170)       <li>Finally get your hands dirty using stem. We want to expand stem's <a href="https://stem.readthedocs.org/en/latest/tutorial.html">tutorial page</a> with more examples. To do this you'll want to both brainstorm some of your own and contact the <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">tor-dev@ email list</a> to solicit ideas. This last step is pretty open ended, so go nuts with whatever you think will improve stem's usability!</li>
1171)     </ol>
1172)     </li>
1173)     

1174)     <a id="compassRefactoring"></a>
1175)     <li>
1176)     <b>Compass Refactoring</b>
1177)     <br>
1178)     Priority: <i>Medium</i>
1179)     <br>
1180)     Effort Level: <i>Medium</i>
1181)     <br>
1182)     Skill Level: <i>Medium</i>
1183)     <br>
1184)     Likely Mentors: <i>gsathya, karsten</i>
1185)     <p>
1186)     Compass was first designed to be a cli app and then hacked into a web app.
1187)     The codebase needs to be refactored such that the main processing code is
1188)     separated from the display functions(probably into separate files) and made
1189)     modular so that adding more features (<a
1190)     href="https://trac.torproject.org/6612">#6612</a>) is easy. For example, the
1191)     main processing logic could be in compass.py, whereas print_groups() and other
1192)     display related functions could be part of a separate cli.py; web.py would also
1193)     have to modified to make use of this new modular code. Bonus points for adding
1194)     features to compass(<a href="https://trac.torproject.org/6619">#6619</a>, <a
1195)     href="https://trac.torproject.org/6612">#6612</a>, <a
1196)     href="https://trac.torproject.org/6728">#6728</a>).
1197)     </p>
1198)     </li>
1199)     

1200)     <!--

1201)     <a id="stemPathsupport"></a>
1202)     <li>
1203)     <b>Stem PathSupport Capabilities</b>
1204)     <br>
1205)     Priority: <i>High</i>
1206)     <br>
1207)     Effort Level: <i>High</i>
1208)     <br>
1209)     Skill Level: <i>Medium</i>
1210)     <br>
1211)     Likely Mentors: <i>Damian (atagar)</i>
1212)     <p><a
1213)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a
1214)     python controller library for tor. Like it's predecessor, <a
1215)     href="#project-torctl">TorCtl</a>, it uses tor's <a
1216)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control
1217)     protocol</a> to help developers program against the tor process, enabling
1218)     them to build things similar to <a href="#project-vidalia">Vidalia</a> and
1219)     <a href="#project-arm">arm</a>.</p>

1220)     

1221)     <p>While TorCtl provided a fine first draft for this sort of functionality,
1222)     it has not proved to be extensible nor maintainable. Stem is a rewrite of
1223)     TorCtl with a heavy focus on testing, documentation, and providing a
1224)     developer friendly API.</p>

1225)     

1226)     <p>At the moment stem is still very much incomplete, missing several pieces
1227)     of functionality that TorCtl provides. This is a project to fix that by
1228)     porting TorCtl's <a
1229)     href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport
1230)     module</a> to stem, writing tests for it, and migrate a couple clients to
1231)     use it.</p>

1232)     

1233)     <p>PathSupport provides applications with programmatic control over how
1234)     tor's circuits are built, for instance letting you exit from particular
1235)     relays. This is used by projects like <a href="#project-torbel">TorBEL</a>,
1236)     <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>.</p>

1237)     

1238)     <p>This project can be broken into three parts...</p>

1239)     

1240)     <ol style="list-style-type: decimal">
1241)       <li><p>Look at PathSupport's clients to figure out how it is used and
1242)       come up with the API that we will use for stem. Note that the goal if
1243)       this project is <b>not</b> to simply copy PathSupport, but to make it
1244)       better. This task would ideally be done as part of writing the GSoC
1245)       application.</p></li>
1246)       <li><p>Implement the PathSupport counterpart for stem. This should be
1247)       done in an incremental fashion, writing the feature, tests, and going
1248)       through a code review before moving on. I'll be pretty anal about making
1249)       it as good as we can during these code reviews so plan for this to take a
1250)       while. ;)</p></li>
1251)       <li><p>The real test of the API that you've developed will come when we
1252)       use it in some real applications. Try to migrate a TorCtl client or two
1253)       to stem, filling in functionality that we're missing and improving our
1254)       API as we discover issues. A particularly good client to start with would
1255)       be TorBEL.</p></li>
1256)     </ol>

1257)     

1258)     <p><b>
1259)     Upon reflection this is not an especially good project for this year's GSoC. You are still perfectly wecome to apply for this project, but <a href="https://trac.torproject.org/projects/tor/wiki/doc/stem">other stem related tasks</a> such as implementing a general controller, descriptor fetching, and client migrations would be better. For the discussion that lead to this see <a href="http://archives.seul.org/or/dev/Apr-2012/msg00006.html">this thread</a>.
1260)     </b></p>
1261)     </li>

1262)     -->

1263)     

1264)     <!--

1265)     <a id="orbot-userInterface"></a>
1266)     <li>
1267)     <b>Build a better user interface for Orbot</b>
1268)     <br>
1269)     Priority: <i>High</i>
1270)     <br>
1271)     Effort Level: <i>Medium</i>
1272)     <br>
1273)     Skill Level: <i>Medium</i>
1274)     <br>

1275)     Likely Mentors: <i>Jake</i>

1276)     <p>Improved home screen to show confirmation of connection (via a TorCheck
1277)     API call), better statistics about data transferred (up/down), number of
1278)     circuits connected, quality of connection and so on. The &quot;Tether
1279)     Wifi&quot; Android application is a good model to follow in how it shows a
1280)     realtime count of bytes transferred as well as notifications when wifi
1281)     clients connect. In addition, better handling of Tor system and error
1282)     messages would also be very helpful, include use of standard Android
1283)     operating systems notifications. The addition of a wizard or tutorial
1284)     walkthrough for novice users to explain to them exactly what is and what is
1285)     not anonymized or protected would greatly improve the likelihood they will
1286)     use Orbot correctly. All of this should work on the range of screens and
1287)     device types now offered for Android, from 2&quot; phone to 10&quot;
1288)     Tablet.</p>
1289)     </li>

1290)     -->

1291)     

1292)     <!--

1293)     <a id="user-space-transport"></a>
1294)     <li>
1295)     <b>Integrating Tor with user-space transport protocol libraries</b>
1296)     <br>
1297)     Priority: <i>Medium to High</i>
1298)     <br>
1299)     Effort Level: <i>High</i>
1300)     <br>
1301)     Skill Level: <i>High</i>
1302)     <br>
1303)     Likely Mentors: <i>Steven</i>
1304)     <p>Tor currently sends data over TCP links between nodes. <a
1305)     href="http://static.usenix.org/events/sec09/tech/full_papers/reardon.pdf">Prior
1306)     research</a> has indicated that this may not be optimal, and instead the
1307)     role that TCP plays (congestion control and reliability) should be moved
1308)     into Tor itself. This would allow a number of desirable changes, such as
1309)     preventing errors on one circuit delaying another, and giving Tor control
1310)     and visibility of congestion control.</p>
1311)     <p>There are <a
1312)     href="http://www.cl.cam.ac.uk/~sjm217/papers/tor11datagramcomparison.pdf">many
1313)     ways to do this</a>, each with their own tradeoffs and difficulty of
1314)     implementation. This project will be to select one (or more) option and
1315)     implement it in Tor. The primary goal will be to test this modified version
1316)     of Tor in simulation, but if it turns out to work well, it could be
1317)     deployed in the live Tor network.</p>
1318)     <p>Excellent C programming skills are needed, and knowledge of Tor
1319)     internals are highly desirable.</p>
1320)     </li>

1321)     -->

1322)     

1323)     <!--

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

1325)     <li>
1326)     <b>Improving Tor's ability to resist censorship</b>

1327)     <br>

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

1329)     <br>

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

1331)     <br>

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

1333)     <br>

1334)     Likely Mentors: <i>Jake, Thomas</i>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1361)     then trading off censorship resistance with usability and
1362)     robustness.</p>

1363)     </li>

1364)     -->

1365)     

1366)     <!--

1367)     <a id="tailsHiddenServicePetnames"></a>
1368)     <li>
1369)     <b>Petname system for Tor hidden services</b>
1370)     <br>
1371)     Priority: <i>Medium</i>
1372)     <br>
1373)     Effort Level: <i>High</i>
1374)     <br>
1375)     Skill Level: <i>High</i>
1376)     <br>
1377)     Likely Mentors: <i>ague</i>
1378)     <p>Tor provides hidden services. These services are only reachable through
1379)     Tor itself, and provide greater anonymity both for the providers of the
1380)     service and for its users.</p>
1381)     <p>One current downside of Tor hidden services is that they are addressed
1382)     using 80-bit base32-encoded addresses such as "v2cbb2l4lsnpio4q.onion".
1383)     These addresses are hard to remember; this makes them hard to use
1384)     within amnesic environment like Tails.</p>
1385)     <p>The project is to implement a petname system for Tor hidden services:
1386)     a way for users or providers of Tor hidden services to add a simple
1387)     'nickname' to a central database. Users could then query this central
1388)     database to retrieve a full hidden service address by giving
1389)     a nickname.</p>
1390)     <p>Adding petnames to the database could be done using a web interface or
1391)     automated fetch like those described in the <a
1392)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/ideas/xxx-onion-nyms.txt">&quot;.onion
1393)     nym system&quot; proposal</a>.</p>
1394)     <p>Querying the database could be done using a web interface, a REST API and
1395)     a DNS interface.</p>
1396)     <p>In order not to grow indefinitely, the software should make regular tests to
1397)     see if hidden services are still reachable and, depending on the last time
1398)     a nickname was accessed, cleanup the database as necessary.</p>
1399)     <p>The software should allow a distributed, fault-tolerant setup.
1400)     All nodes should have a synchronized copy of the database, should be
1401)     ready to answer queries and should coordinate the tests for hidden
1402)     service availability.</p>
1403)     <p>The resulting codebase must be easy to deploy: it should not be hard to
1404)     setup new databases.</p>
1405)     <p>It is expected that the volunteer will be using Behaviour Driven
1406)     Development methods. Either in Ruby using Cucumber and RSpec, or in
1407)     Python using similar tools.</p>
1408)     </li>

1409)     -->

1410)     

1411)     <!--

1412)     <a id="tailsServer"></a>
1413)     <li>
1414)     <b>Tails server: Self-hosted services behind Tails-powered Tor hidden services</b>
1415)     <br>
1416)     Priority: <i>Medium</i>
1417)     <br>
1418)     Effort Level: <i>High</i>
1419)     <br>
1420)     Skill Level: <i>Medium, but wide-scoped</i>
1421)     <br>
1422)     Likely Mentors: <i>intrigeri, anonym</i>
1423)     <p>Let's talk about group collaboration, communication and data sharing
1424)     infrastructure, such as chat servers, wikis, or file repositories.</p>
1425)     <p>Hosting such data and infrastructure <b>in the cloud</b> generally
1426)     implies to trust the service providers not to disclose content, usage or
1427)     users location information to third-parties. Hence, there are many threat
1428)     models in which cloud hosting is not suitable.</p>
1429)     <p>Tor partly answers the <b>users location</b> part; this is great, but
1430)     <b>content</b> is left unprotected.</p>
1431)     <p>There are two main ways to protect such content: either to encrypt it
1432)     client-side (<b>security by design</b>), or to avoid putting it into
1433)     untrusted hands in the first place.</p>
1434)     <p>Cloud solutions that offer security by design are rare and generally
1435)     not mature yet. The <b>Tails server</b> project is about exploring the
1436)     other side of the alternative: avoiding to put private data into
1437)     untrusted hands in the first place.</p>
1438)     <p>This is made possible thanks to Tor hidden services, that allow users
1439)     to offer location-hidden services, and make self-hosting possible in
1440)     many threat models. Self-hosting has its own lot of problems, however,
1441)     particularly in contexts where the physical security of the hosting
1442)     place is not assured. Combining Tor hidden services with Tails'
1443)     amnesia property and limited support for persistent encrypted data
1444)     allows to protect content, to a great degree, even in such contexts.</p>
1445)     <p>In short, setting up a new Tails server would be done by:</p>

1446)     

1447)     <ol style="list-style-type: decimal">
1448)       <li>Alice plugs a USB stick into a running desktop Tails system.</li>
1449)       <li>Alice uses a GUI to easily configure the needed services.</li>
1450)       <li>Alice unplugs the USB stick, that now contains encrypted services
1451)       configuration and data storage space.</li>
1452)       <li>Alice plugs that USB stick (and possibly a Tails Live CD) into the
1453)       old laptop that was dedicated to run Tails server.</li>
1454)       <li>Once booted, Alice enters the encryption passphrase either
1455)       directly using the keyboard or through a web interface listening on the
1456)       local network.</li>
1457)       <li>Then, Bob can use the configured services once he gets a hold on
1458)       the hidden service address. (The <b>petname system for Tor hidden
1459)       services</b> project would be very complementary to this one, by the
1460)       way.)</li>
1461)     </ol>

1462)     

1463)     <p>Tails server should content itself with hardware that is a bit old
1464)     (such as a PIII-450 laptop with 256MB of RAM) and/or half broken (e.g.
1465)     non-functional hard-disk, screen or keyboard).</p>
1466)     <p>The challenges behind this project are:</p>

1467)     

1468)     <ul>
1469)       <li>Design and write the services configuration GUI [keywords: edit
1470)       configuration files, upgrade between major Debian versions,
1471)       debconf].</li>
1472)       <li>How to create the hidden service key? [keywords: Vidalia, control
1473)       protocol].</li>
1474)       <li>Adapt the Tails boot process to allow switching to &quot;server
1475)       mode&quot; when appropriate.</li>
1476)       <li>Add support, to the Tails persistence setup process, for asking an
1477)       encryption passphrase without X, and possibly with a broken keyboard
1478)       and/or screen [keywords: local network, SSL/TLS?, certificate?].</li>
1479)     </ul>

1480)     

1481)     <p>This project can easily grow quite large, so the first task would
1482)     probably be to clarify what it would need to get an initial (minimal
1483)     but working) implementation ready to be shipped to users.</p>
1484)     <p>This project does not require to be an expert in one specific field,
1485)     but it requires to be experienced and at ease with a large scope of
1486)     software development tools, processes, and operating system knowledge.</p>
1487)     <p>Undertaking this project requires in-depth knowledge of Debian-like
1488)     systems (self-test: do the "dpkg conffile" and "debconf preseeding"
1489)     words sound new to your ear?); the Debian Live persistence system
1490)     being written in shell, being at ease with robust shell scripting is
1491)     a must; to end with, at least two pieces of software need to be
1492)     written from scratch (a GUI and a webapp): the preferred languages for
1493)     these tasks would be Python and Perl. Using Behaviour Driven
1494)     Development methods to convey expectations and acceptance criteria
1495)     would be most welcome.</p>
1496)     <p>For more information see https://tails.boum.org/todo/server_edition/</p>
1497)     </li>

1498)     -->

1499)     

1500)     <!--

1501)     <a id="geoIPUpgrade"></a>
1502)     <li>
1503)     <b>Improve our GeoIP file format</b>
1504)     <br>
1505)     Priority: <i>Medium</i>
1506)     <br>
1507)     Effort Level: <i>Medium</i>
1508)     <br>
1509)     Skill Level: <i>Medium to High</i>
1510)     <br>
1511)     Likely Mentors: <i>Robert Ransom</i>

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

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

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

1516)     possible.</p>

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

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

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

1523)     project.</p>

1524)     </li>

1525)     -->

1526)     

1527)     <!--

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

1529)     <li>
1530)     <b>Client Mode Use Cases for Arm</b>
1531)     <br>
1532)     Priority: <i>Medium</i>
1533)     <br>
1534)     Effort Level: <i>High</i>
1535)     <br>
1536)     Skill Level: <i>Medium</i>
1537)     <br>

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

1539)     <p><a href="<page projects/arm>">Arm</a> is a Tor command line status
1540)     monitor on *nix environments (Linux, Mac, and BSD). It functions much like
1541)     top does, giving a CLI overlay of Tor's bandwidth usage, connections,
1542)     configuration, log, etc. Thus far its design has been geared for Tor relay
1543)     operators. However, this doesn't need to be the case. This project would be
1544)     to expand and simplify arm to make it useful for Tor's client users
1545)     too.</p>

1546)     

1547)     <p>This would include UI design, experimenting, and a lot of python
1548)     hacking. Here's some ideas for client functionality arm could provide:</p>

1549)     

1550)     <ul>
1551)       <li>A panel for client connections, showing each hop of the user's
1552)       circuits with the ISP, country, and jurisdiction where those relays
1553)       reside. Other interesting information would be the circuit's latency, how
1554)       long its been around, and its possible exit ports. Some of this will be
1555)       pretty tricky and require some experimentation to figure out what
1556)       information can be fetched safely (for instance, scraping rdns and whois
1557)       lookups could give hints about a relay's ISP, but we'd need to do it on
1558)       all Tor relays to avoid leaking our connections to the resolver).</li>

1559)       

1560)       <li>Options to let the user request new circuits (the &quot;New
1561)       Identity&quot; feature in Vidalia), select the exit country, etc.</li>

1562)       

1563)       <li>A panel showing Internet application and if their connections are
1564)       being routed through Tor or not (giving a warning if there's leaks).</li>

1565)       

1566)       <li>The status of the bridges we're configured to use (ie, are they up?).
1567)       This would include adding control port functionality to Tor for <a
1568)       href="https://trac.torproject.org/projects/tor/ticket/2068">ticket
1569)       2068</a>.</li>

1570)       

1571)       <li>A one click option to set Tor to be a client, relay, or bridge. The
1572)       goal would be to make it trivial for users to voluntarily contribute to
1573)       the Tor network.</li>

1574)       

1575)       <li>Menus as an alternative to hotkeys to make the interface more
1576)       intuitive and usable for beginners (<a
1577)       href="http://gnosis.cx/publish/programming/charming_python_6.html">example</a>).</li>

1578)       

1579)       <li>Look at Vidalia and TorK for ideas and solicit input from the Tor community.</li>
1580)     </ul>

1581)     

1582)     <p>

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

1584)     </p>

1585)     </li>

1586)     -->

1587)     

1588)     <!--

1589)     <a id="vidalia-hidden-service-panel"></a>
1590)     <li>
1591)     <b>Torrc plugin and improved hidden service configuration panel</b>
1592)     <br>
1593)     Priority: <i>Medium</i>
1594)     <br>
1595)     Effort Level: <i>Medium</i>
1596)     <br>
1597)     Skill Level: <i>Medium</i>
1598)     <br>
1599)     Likely Mentors: <i>Tomás</i>
1600)     <p>Vidalia's configuration handling has changed in the alpha branch. Now
1601)     every Tor option is saved in the torrc file. With that change, the
1602)     Hidden Service configuration panel was removed due to its specificity
1603)     and its multiple bugs.</p>

1604)     

1605)     <p>The idea would be to provide the new Torrc class' functionality to the
1606)     Plugin Engine and with that, create a better Hidden Service
1607)     configuration panel as a plugin.</p>

1608)     

1609)     <p>A person undertaking this project should have good UI design, layout
1610)     skills and some C++ development experience. Previous experience with Qt
1611)     and Qt's Designer will be very helpful, but are not required. Javascript
1612)     knowledge is a plus, but it shouldn't be a problem if the person
1613)     complies with the previous requirements.</p>
1614)     </li>

1615)     -->

1616)     

1617)     <a id="metricsSearch"></a>
1618)     <li>
1619)     <b>Searchable Tor descriptor and Metrics data archive</b>
1620)     <br>
1621)     Priority: <i>Medium</i>
1622)     <br>
1623)     Effort Level: <i>Medium</i>
1624)     <br>
1625)     Skill Level: <i>Medium</i>
1626)     <br>
1627)     Likely Mentors: <i>Karsten</i>

1628)     <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.html">ExoneraTor</a> finds whether a given IP address was a relay on a given day.</p>

1629)     

1630)     <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>

1631)     

1632)     <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>

1633)     

1634)     <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>

1635)     

1636)     <!--

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

1638)     <li>
1639)     <b>Improve our unit testing process</b>

1640)     <br>

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

1642)     <br>

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

1644)     <br>

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

1646)     <br>

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

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

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

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

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

1662)     </li>

1663)     -->

1664)     

1665)     <!--

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

1667)     <li>
1668)     <b>Simulator for slow Internet connections</b>

1669)     <br>

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

1671)     <br>

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

1673)     <br>

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

1675)     <br>

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

1677)     <p>

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

1683)     </p>

1684)     

1685)     <p>

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

1691)     </p>

1692)     

1693)     <p>

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

1699)     </p>

1700)     </li>

1701)     -->

1702)     

1703)     <!--

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

1705)     <li>
1706)     <b>Usability testing of Tor</b>

1707)     <br>

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

1709)     <br>

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

1711)     <br>

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

1713)     <br>

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

1715)     <p>

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

1720)     </p>

1721)     

1722)     <p>
1723)     Please note that since this isn't a coding project, it isn't suitable for
1724)     Google Summer of Code.
1725)     </p>

1726)     </li>

1727)     -->

1728)     

1729)     <!--

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

1731)     <li>
1732)     <b>Make torsocks/dsocks work on OS X</b>

1733)     <br>

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

1735)     <br>

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

1737)     <br>

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

1739)     <br>

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

1741)     <p>

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

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

1758)     </p>
1759)     </li>

1760)     -->

1761)     

1762)     <!--

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

1764)     <li>
1765)     <b>Tor Controller Status Event Interface for Vidalia</b>
1766)     <br>
1767)     Priority: <i>Medium</i>
1768)     <br>
1769)     Effort Level: <i>Medium</i>
1770)     <br>
1771)     Skill Level: <i>Low to Medium</i>
1772)     <br>

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

1774)     <p>There are a number of status changes inside Tor of which the user may need
1775)     to be informed. For example, if the user is trying to set up his Tor as a
1776)     relay and Tor decides that its ports are not reachable from outside
1777)     the user's network, we should alert the user. Currently, all the user
1778)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1779)     likely never see since they don't receive a notification that something
1780)     has gone wrong. Even if the user does actually look at the message log,
1781)     most of the messages make little sense to the novice user.</p>
1782)     <p>Tor has the ability to inform Vidalia of many such status
1783)     changes, and we recently implemented support for a couple of these
1784)     events. Still, there are many more status events which the user should
1785)     be informed of, and we need a better UI for actually displaying them
1786)     to the user.</p>
1787)     <p>The goal of this project then is to design and implement a UI for
1788)     displaying Tor status events to the user. For example, we might put a
1789)     little badge on Vidalia's tray icon that alerts the user to new status
1790)     events they should look at. Double-clicking the icon could bring up a
1791)     dialog that summarizes recent status events in simple terms and maybe
1792)     suggests a remedy for any negative events if they can be corrected by
1793)     the user. Of course, this is just an example and one is free to
1794)     suggest another approach.</p>
1795)     <p>A person undertaking this project should have good UI design and layout
1796)     skills and some C++ development experience. Previous experience with Qt and
1797)     Qt's Designer will be very helpful, but are not required. Some
1798)     English writing ability will also be useful, since this project will
1799)     likely involve writing small amounts of help documentation that should
1800)     be understandable by non-technical users. Bonus points for some graphic
1801)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1802)     </li>

1803)     -->

1804)     

1805)     <!--

1806)     <a id="orbot-optimisation"></a>
1807)     <li>
1808)     <b>Core Tor mobile optimisation</b>
1809)     <br>
1810)     Priority: <i>Medium</i>
1811)     <br>
1812)     Effort Level: <i>Medium</i>
1813)     <br>
1814)     Skill Level: <i>High</i>
1815)     <br>

1816)     Likely Mentors: <i>Jake</i>

1817)     <p>
1818)     The existing port of Tor to Android is basically a straight
1819)     cross-compile to Linux ARM. There has been no work done in looking at
1820)     possible optimizations of Tor within a mobile hardware environment or on
1821)     mobile networks. In addition, a number of additional Android OS APIs are
1822)     available (such as wireless network status) that could be taken
1823)     advantage of.
1824)     </p>

1825)     

1826)     <p>
1827)     It should be noted, that even without optimisation, Tor is handling the
1828)     mobile network environment very well, automatically detecting change in
1829)     IP addresses, opening circuits, etc, as the device switches from no
1830)     coverage to 2G, 3G or Wifi constantly as it changes position. However,
1831)     this observation of &quot;very well&quot;, is just based on user
1832)     experience, and not any detailed study of what exactly is happening, and
1833)     what threats might exist because of this constantly changing network state.
1834)     </p>

1835)     

1836)     <p>
1837)     Finally, the build process needs to be moved to the Android NDK from the
1838)     custom GCC toolchain we are now using, and compatibility with Android
1839)     2.3 and 3.x Honeycomb OS need to be verified.
1840)     </p>

1841)     

1842)     <p>
1843)     For more information see the <a
1844)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD">Orbot
1845)     build documentation</a>.
1846)     </p>
1847)     </li>

1848)     -->

1849)     

1850)     <!--

1851)     <a id="orbot-orlibAndOutreach"></a>
1852)     <li>
1853)     <b>Orbot integration library and community outreach</b>
1854)     <br>
1855)     Priority: <i>Medium</i>
1856)     <br>
1857)     Effort Level: <i>Low</i>
1858)     <br>
1859)     Skill Level: <i>Medium</i>
1860)     <br>
1861)     Likely Mentors: <i>Nathan (n8fr8)</i>
1862)     <p>
1863)     We need additional work on <a
1864)     href="https://github.com/guardianproject/orlib">ORLib</a>, our library for
1865)     use with third-party application to easily enable them to support
1866)     &quot;Torification&quot; on non-rooted devices (i.e. w/o transparent
1867)     proxying). This library includes a SOCKS client, a wrapper for the Apache
1868)     HTTPClient library, a utility class for detecting the state of Orbot
1869)     connectivity, and other relevant/useful things an Android app might need to
1870)     anonymize itself. This work would includes direct development of the
1871)     library, documentation, and sample code. Outreach or effort to implement
1872)     the library within other open-source apps is also needed.
1873)     </p>
1874)     </li>

1875)     -->

1876)     

1877)     <!--

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

1879)     <li>
1880)     <b>An Improved and More Usable Network Map in Vidalia</b>
1881)     <br>
1882)     Priority: <i>Low to Medium</i>
1883)     <br>
1884)     Effort Level: <i>Medium</i>
1885)     <br>
1886)     Skill Level: <i>Medium</i>
1887)     <br>

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

1889)     <p>
1890)     One of Vidalia's existing features is a network map that shows the user
1891)     the approximate geographic location of relays in the Tor network and
1892)     plots the paths the user's traffic takes as it is tunneled through the
1893)     Tor network. The map is currently not very interactive and has rather
1894)     poor graphics. Instead, we implemented KDE's Marble widget such
1895)     that it gives us a better quality map and enables improved interactivity,
1896)     such as allowing the user to click on individual relays or circuits to
1897)     display additional information. We want to add the ability
1898)     for users to click on a particular relay or a country containing one or
1899)     more Tor exit relays and say, "I want my connections to exit
1900)     from here."
1901)     </p>

1902)     

1903)     <p>
1904)     This project will first involve getting familiar with Vidalia
1905)     and the Marble widget's API. One will then integrate the widget
1906)     into Vidalia and customize Marble to be better suited for our application,
1907)     such as making circuits clickable, storing cached map data in Vidalia's
1908)     own data directory, and customizing some of the widget's dialogs.
1909)     </p>

1910)     

1911)     <p>
1912)     A person undertaking this project should have good C++ development
1913)     experience. Previous experience with Qt and CMake is helpful, but not
1914)     required.
1915)     </p>

1916)     </li>

1917)     -->

1918)     

1919)     <!--

1920)     <a id="obfsproxy-fuzzer"></a>
1921)     <li>
1922)     <b>Fuzzer for the Tor protocol</b>
1923)     <br>
1924)     Priority: <i>Low to Medium</i>
1925)     <br>
1926)     Effort Level: <i>Medium to High</i>
1927)     <br>
1928)     Skill Level: <i>High</i>
1929)     <br>
1930)     Likely Mentors: <i>asn</i>
1931)     <p>Involves researching good and smart ways to fuzz stateful network
1932)     protocols, and also implementing the fuzzer.</p>

1933)     

1934)     <p>We are mostly looking for a fuzzer that fuzzes the Tor protocol
1935)     itself, and not the Tor directory protocol.</p>

1936)     

1937)     <p>Bonus points if it's extremely modular. Relevant research:</p>

1938)     

1939)     <ul>
1940)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1941)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1942)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1943)       Testing and Machine Learning</li>
1944)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1945)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1946)       <li>Also look at the concepts of &quot;model checking&quot; and
1947)       &quot;symbolic execution&quot; to get inspired.</li>
1948)     </ul>
1949)     </li>

1950)     -->

1951)     

1952)     <!--

1953)     <a id="armGui"></a>
1954)     <li>
1955)     <b>GUI for Arm</b>
1956)     <br>
1957)     Priority: <i>Low</i>
1958)     <br>
1959)     Effort Level: <i>High</i>
1960)     <br>
1961)     Skill Level: <i>Medium</i>
1962)     <br>

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

1964)     <p>
1965)     Arm has several unique features, some of the most interesting being its
1966)     connection listing (correlating netstat results against the Tor consensus)
1967)     and configuration editor (a quick method for editing Tor's config, with
1968)     information pulled from the control port and man page). However, since arm
1969)     is a command line controller it's of limited appeal to certain sets of
1970)     users. This project would be to build a GTK or Qt frontend for the
1971)     controller, providing similar features set but with a windowed interface.
1972)     </p>

1973)     

1974)     <p>
1975)     The vast majority of arm's more interesting functionality lies in its

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

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

1983)     -->

1984)     

1985)     <!--

1986)     <a id="APAF"></a>
1987)     <li>
1988)     <b>APAF: Anonymous Python Application Framework</b>
1989)     <br>
1990)     Priority: <i>Medium</i>
1991)     <br>
1992)     Effort Level: <i>Medium</i>
1993)     <br>
1994)     Skill Level: <i>Medium</i>
1995)     <br>
1996)     Likely Mentors: <i>Arturo (hellais)</i>
1997)     <p>

1998)     The goal of APAF is to create a build framework for creating a binary
1999)     package for multiple platforms (.app/dmg, .exe, .deb, etc.) that includes
2000)     the python interpreter (cpython), the Tor binary and all the UI necessary
2001)     to make users be able to easily run the bundled Tor Hidden Service.

2002)     </p>

2003)     

2004)     <p>

2005)     For GSoC the student is expected to create the build system capable of
2006)     building a simple web application that serves static files. It should also
2007)     include a web UI for a wizard setup, checking the status of the HS and
2008)     configuring it.

2009)     </p>

2010)     

2011)     <p>

2012)     For more details on this: check out <a
2013)     href="https://pad.riseup.net/p/1zA8FI4nrYlq">https://pad.riseup.net/p/1zA8FI4nrYlq</a>

2014)     </p>
2015)     </li>

2016)     -->

2017)     

2018)     <li>
2019)     <b>Bring up new ideas!</b>

2020)     <br>

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

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

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

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

2026)     might also be short on developers.
2027)     </li>

2028)     

2029)     </ol>

2030)     

2031)     <a id="OtherCoding"></a>
2032)     <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
2033)     <ol>
2034)     <li>Tor relays don't work well on Windows XP. On
2035)     Windows, Tor uses the standard <tt>select()</tt> system
2036)     call, which uses space in the non-page pool. This means
2037)     that a medium sized Tor relay will empty the non-page pool, <a

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

2039)     havoc and system crashes</a>. We should probably be using overlapped IO
2040)     instead. One solution would be to teach <a
2041)     href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
2042)     overlapped IO rather than select() on Windows, and then adapt Tor to
2043)     the new libevent interface. Christian King made a
2044)     <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
2045)     start</a> on this in the summer of 2007.</li>

2046)     

2047)     <li>We need to actually start building our <a href="<page
2048)     docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
2049)     fleshing out the design, modifying many different pieces of Tor, adapting
2050)     <a href="<page projects/vidalia>">Vidalia</a> so it supports the
2051)     new features, and planning for deployment.</li>

2052)     

2053)     <li>We need a flexible simulator framework for studying end-to-end
2054)     traffic confirmation attacks. Many researchers have whipped up ad hoc
2055)     simulators to support their intuition either that the attacks work
2056)     really well or that some defense works great. Can we build a simulator
2057)     that's clearly documented and open enough that everybody knows it's
2058)     giving a reasonable answer? This will spur a lot of new research.
2059)     See the entry <a href="#Research">below</a> on confirmation attacks for
2060)     details on the research side of this task &mdash; who knows, when it's
2061)     done maybe you can help write a paper or three also.</li>

2062)     

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

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

2067)     Tor if needed.</li>

2068)     

2069)     <li>Perform a security analysis of Tor with <a

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

2071)     if there are good fuzzing libraries out there for what we want. Win fame by
2072)     getting credit when we put out a new release because of you!</li>

2073)     

2074)     <li>Tor uses TCP for transport and TLS for link
2075)     encryption. This is nice and simple, but it means all cells
2076)     on a link are delayed when a single packet gets dropped, and
2077)     it means we can only reasonably support TCP streams. We have a <a

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

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

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

2082)     for Tor and
2083)     UDP</a> &mdash; please let us know what's wrong with it.</li>

2084)     

2085)     <li>We're not that far from having IPv6 support for destination addresses
2086)     (at exit nodes). If you care strongly about IPv6, that's probably the
2087)     first place to start.</li>

2088)     

2089)     <li>We need a way to generate the website diagrams (for example, the "How
2090)     Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
2091)     from source, so we can translate them as UTF-8 text rather than edit
2092)     them by hand with Gimp. We might want to
2093)     integrate this as an wml file so translations are easy and images are
2094)     generated in multiple languages whenever we build the website.</li>

2095)     

2096)     <li>How can we make the various LiveCD/USB systems easier
2097)     to maintain, improve, and document?  One example is <a

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

2099)     System</a>.
2100)     </li>

2101)     

2102)     <li>
2103)     Another anti-censorship project is to try to make Tor
2104)     more scanning-resistant.  Right now, an adversary can identify <a

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

2106)     just by trying to connect to them, following the Tor protocol,
2107)     and seeing if they respond.  To solve this, bridges could <a
2108)     href="<svnprojects>design-paper/blocking.html#tth_sEc9.3">act like
2109)     webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
2110)     and not act like bridges until the user provides a bridge-specific key.
2111)     To start, check out Shane Pope's <a
2112)     href="http://dl.dropbox.com/u/37735/index.html">thesis and prototype</a>.
2113)     </li>

2114)     

2115)     </ol>

2116)     

2117)     <a id="Research"></a>
2118)     <h2><a class="anchor" href="#Research">Research</a></h2>
2119)     <ol>
2120)     <li>The "end-to-end traffic confirmation attack":
2121)     by watching traffic at Alice and at Bob, we can <a
2122)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
2123)     traffic signatures and become convinced that we're watching the same
2124)     stream</a>. So far Tor accepts this as a fact of life and assumes this
2125)     attack is trivial in all cases. First of all, is that actually true? How
2126)     much traffic of what sort of distribution is needed before the adversary
2127)     is confident he has won? Are there scenarios (e.g. not transmitting much)
2128)     that slow down the attack? Do some traffic padding or traffic shaping
2129)     schemes work better than others?</li>
2130)     <li>A related question is: Does running a relay/bridge provide additional
2131)     protection against these timing attacks? Can an external adversary that can't
2132)     see inside TLS links still recognize individual streams reliably?
2133)     Does the amount of traffic carried degrade this ability any? What if the
2134)     client-relay deliberately delayed upstream relayed traffic to create a queue
2135)     that could be used to mimic timings of client downstream traffic to make it
2136)     look like it was also relayed? This same queue could also be used for masking
2137)     timings in client upstream traffic with the techniques from <a
2138)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
2139)     but without the need for additional traffic. Would such an interleaving of
2140)     client upstream traffic obscure timings for external adversaries? Would the
2141)     strategies need to be adjusted for asymmetric links? For example, on
2142)     asymmetric links, is it actually possible to differentiate client traffic from
2143)     natural bursts due to their asymmetric capacity? Or is it easier than
2144)     symmetric links for some other reason?</li>
2145)     <li>Repeat Murdoch and Danezis's <a
2146)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
2147)     Oakland 05</a> on the current Tor network. See if you can learn why it
2148)     works well on some nodes and not well on others. (My theory is that the
2149)     fast nodes with spare capacity resist the attack better.) If that's true,
2150)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
2151)     options to run a relay that is used as a client while relaying the
2152)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
2153)     attack get harder? What's the right ratio of RelayBandwidthRate to
2154)     actually capacity? Or is it a ratio at all? While we're at it, does a
2155)     much larger set of candidate relays increase the false positive rate
2156)     or other complexity for the attack? (The Tor network is now almost two
2157)     orders of magnitude larger than it was when they wrote their paper.) Be
2158)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
2159)     Clog the Queue</a> too.</li>
2160)     <li>The "routing zones attack": most of the literature thinks of
2161)     the network path between Alice and her entry node (and between the
2162)     exit node and Bob) as a single link on some graph. In practice,
2163)     though, the path traverses many autonomous systems (ASes), and <a
2164)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
2165)     that the same AS appears on both the entry path and the exit path</a>.
2166)     Unfortunately, to accurately predict whether a given Alice, entry,
2167)     exit, Bob quad will be dangerous, we need to download an entire Internet
2168)     routing zone and perform expensive operations on it. Are there practical
2169)     approximations, such as avoiding IP addresses in the same /8 network?</li>
2170)     <li>Other research questions regarding geographic diversity consider
2171)     the tradeoff between choosing an efficient circuit and choosing a random
2172)     circuit. Look at Stephen Rollyson's <a
2173)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
2174)     paper</a> on how to discard particularly slow choices without hurting
2175)     anonymity "too much". This line of reasoning needs more work and more
2176)     thinking, but it looks very promising.</li>
2177)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
2178)     (e.g. cable or DSL). Because Tor has separate TCP connections between
2179)     each hop, if the incoming bytes are arriving just fine and the outgoing
2180)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
2181)     don't really transmit this information back to the incoming streams.
2182)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
2183)     and rate-limit incoming streams to regulate this itself? I can imagine
2184)     a build-up and drop-off scheme where we pick a conservative rate-limit,
2185)     slowly increase it until we get lost packets, back off, repeat. We
2186)     need somebody who's good with networks to simulate this and help design
2187)     solutions; and/or we need to understand the extent of the performance
2188)     degradation, and use this as motivation to reconsider UDP transport.</li>
2189)     <li>A related topic is congestion control. Is our
2190)     current design sufficient once we have heavy use? Maybe
2191)     we should experiment with variable-sized windows rather
2192)     than fixed-size windows? That seemed to go well in an <a

2193)     href="http://www.psc.edu/index.php/hpn-ssh/638">ssh

2194)     throughput experiment</a>. We'll need to measure and tweak, and maybe
2195)     overhaul if the results are good.</li>
2196)     <li>Our censorship-resistance goals include preventing
2197)     an attacker who's looking at Tor traffic on the wire from <a
2198)     href="<svnprojects>design-paper/blocking.html#sec:network-fingerprint">distinguishing
2199)     it from normal SSL traffic</a>. Obviously we can't achieve perfect
2200)     steganography and still remain usable, but for a first step we'd like to
2201)     block any attacks that can win by observing only a few packets. One of
2202)     the remaining attacks we haven't examined much is that Tor cells are 512
2203)     bytes, so the traffic on the wire may well be a multiple of 512 bytes.
2204)     How much does the batching and overhead in TLS records blur this on the
2205)     wire? Do different buffer flushing strategies in Tor affect this? Could
2206)     a bit of padding help a lot, or is this an attack we must accept?</li>
2207)     <li>Tor circuits are built one hop at a time, so in theory we have the
2208)     ability to make some streams exit from the second hop, some from the
2209)     third, and so on. This seems nice because it breaks up the set of exiting
2210)     streams that a given relay can see. But if we want each stream to be safe,
2211)     the "shortest" path should be at least 3 hops long by our current logic, so
2212)     the rest will be even longer. We need to examine this performance / security
2213)     tradeoff.</li>
2214)     <li>It's not that hard to DoS Tor relays or directory authorities. Are client
2215)     puzzles the right answer? What other practical approaches are there? Bonus
2216)     if they're backward-compatible with the current Tor protocol.</li>
2217)     <li>Programs like <a

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

2219)     your browser's UserAgent string by replacing it with a uniform answer for
2220)     every Tor user. That way the attacker can't splinter Tor's anonymity set
2221)     by looking at that header. It tries to pick a string that is commonly used
2222)     by non-Tor users too, so it doesn't stand out. Question one: how badly
2223)     do we hurt ourselves by periodically updating the version of Firefox
2224)     that Torbutton claims to be? If we update it too often, we splinter the
2225)     anonymity sets ourselves. If we don't update it often enough, then all the
2226)     Tor users stand out because they claim to be running a quite old version
2227)     of Firefox. The answer here probably depends on the Firefox versions seen
2228)     in the wild. Question two: periodically people ask us to cycle through N
2229)     UserAgent strings rather than stick with one. Does this approach help,
2230)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
2231)     by their rotating UserAgents; malicious websites who only attack certain
2232)     browsers; and whether the answers to question one impact this answer.
2233)     </li>
2234)     <li>How many bridge relays do you need to know to maintain
2235)     reachability? We should measure the churn in our bridges. If there is
2236)     lots of churn, are there ways to keep bridge users more likely to stay
2237)     connected?
2238)     </li>
2239)     </ol>

2240)     

2241)     <p>
2242)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
2243)     of these!
2244)     </p>
2245)   </div>
2246)   <!-- END MAINCOL -->
2247)   <div id = "sidecol">
2248) #include "side.wmi"
2249) #include "info.wmi"
2250)   </div>
2251)   <!-- END SIDECOL -->
2252) </div>
2253) <!-- END CONTENT -->