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
38) <!-- web page and -->
39)     documentation into other

40)     languages. See the <a href="<page getinvolved/translation>">translation
41)     guidelines</a> if you want to help out. We especially need Arabic or
42)     Farsi translations, for the many Tor users in censored areas.</li>
43)     <li>Evaluate and document

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

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

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

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

51) 

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

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

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

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

60)     <a

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

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

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

64)     such as "Tor for Freedom!"</li>
65)     <li>Create a t-shirt design that incorporates "<a
66)     href="https://check.torproject.org/">Congratulations! You are using
67)     Tor!</a>" in any language.</li>

68)     </ol>

69) 

70) <!--

71)     <a id="gsoc"></a>
72)     <h2><a class="anchor" href="#gsoc">Google Summer of Code</a></h2>
73) 
74)     <p>
75)     Tor is also taking part in this year's <a
76)     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">Google
77)     Summer of Code</a>! The criteria for this is a little different - either
78)     gender can apply but you need to be either <a
79)     href="https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#2._Whos_eligible_to_participate_as_a">a
80)     present student or just graduated</a>.
81)     </p>
82) 
83)     <p>
84)     As mentioned above if you're eligible for either program then please apply
85)     for both! Google Summer of Code is a far, far larger program for us than
86)     OPW so your chances of being applied that way are considerably better.
87)     </p>
88) 
89)     <p>
90)     <b>See our page for <a href="<page about/gsoc>">Google Summer of Code</a>
91)     for more information.</b>
92)     </p>

93) -->

94) 

95)     <a id="Projects"></a>
96)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

97) 

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

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

105)     </p>

106) 

107)     <p>
108)     For a presentation summarizing many of these projects see...
109)     </p>
110) 
111)     <div id="ecosystem_presentation">
112)       <a href="https://media.torproject.org/video/2013-11-t3am-damian-johnson.mp4">Tor Ecosystem</a> (<a href="https://svn.torproject.org/svn/projects/presentations/2013-11-t3am-tor-ecosystem.pdf">slides</a>)
113)     </div>
114) 
115)     <br /></br />
116) 

117)     <table id="projects">
118)       <tr>
119)         <th>Name</th>
120)         <th>Category</th>
121)         <th>Language</th>
122)         <th>Activity</th>
123)         <th>Contributors</th>
124)       </tr>

125) 

126)       <tr>
127)         <td><a href="#project-tor">Tor</a></td>
128)         <td>Core</td>
129)         <td>C</td>
130)         <td>Heavy</td>

131)         <td>nickm, athena, arma</td>

132)       </tr>

133) 

134)       <tr>

135)         <td>*<a href="#project-orchid">Orchid</a></td>

136)         <td>Core</td>
137)         <td>Java</td>

138)         <td>Moderate</td>

139)         <td>bleidl</td>
140)       </tr>
141) 
142)       <tr>

143)         <td><a href="#project-torbrowser">Tor Browser</a></td>

144)         <td>Bundle</td>

145)         <td>C, Scripting</td>

146)         <td>Moderate</td>

147)         <td>mikeperry, Erinn</td>

148)       </tr>

149) 

150)       <tr>

151)         <td><a href="#project-torbutton">Torbutton</a></td>
152)         <td>Browser Add-on</td>
153)         <td>Javascript</td>
154)         <td>Moderate</td>
155)         <td>mikeperry</td>

156)       </tr>

157) 

158)       <tr>

159)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
160)         <td>Browser Add-on</td>
161)         <td>Javascript</td>

162)         <td>Heavy</td>

163)         <td>pde, mikeperry</td>

164)       </tr>

165) 

166)       <tr>

167)         <td><a href="#project-vidalia">Vidalia</a></td>
168)         <td>User Interface</td>
169)         <td>C++, Qt</td>

170)         <td>None</td>

171)         <td>chiiph</td>
172)       </tr>

173) 

174)       <tr>

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

178)         <td>Light</td>

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

181) 

182)       <tr>

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

186)         <td>Light</td>

187)         <td>n8fr8</td>

188)       </tr>

189) 

190)       <tr>

191)         <td><a href="#project-tails">Tails</a></td>
192)         <td>OS image</td>
193)         <td>Sys Admin</td>
194)         <td>Heavy</td>
195)         <td><a href="https://tails.boum.org/">#tails</a></td>

196)       </tr>

197) 

198)       <tr>

199)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
200)         <td>OS image</td>
201)         <td>Sys Admin</td>

202)         <td>None</td>

203)         <td>blueness</td>
204)       </tr>
205) 

206)       <tr>

207)         <td>*<a href="#project-torouter">Torouter</a></td>
208)         <td>OS image</td>
209)         <td>Sys Admin</td>

210)         <td>None</td>

211)         <td>ioerror</td>
212)       </tr>
213) 

214)       <tr>

215)         <td><a href="#project-torsocks">Torsocks</a></td>
216)         <td>Usability</td>
217)         <td>C</td>

218)         <td>Light</td>

219)         <td>ioerror, nickm</td>
220)       </tr>
221) 

222)       <tr>

223)         <td><a href="#project-torbirdy">TorBirdy</a></td>
224)         <td>Browser Add-on</td>
225)         <td>JavaScript</td>
226)         <td>Heavy</td>

227)         <td>Sukhbir (sukhe)</td>

228)       </tr>

229) 

230)       <tr>

231)         <td><a href="#project-obfsproxy">Obfsproxy</a></td>
232)         <td>Client Add-on</td>

233)         <td>Python</td>

234)         <td>Moderate</td>

235)         <td>asn</td>

236)       </tr>
237) 

238)       <tr>

239)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
240)         <td>Client Add-on</td>
241)         <td>Python, JavaScript, Go</td>

242)         <td>Heavy</td>

243)         <td>dcf, infinity0, aallai, jct</td>

244)       </tr>

245) 

246)       <tr>

247)         <td><a href="#project-shadow">Shadow</a></td>

248)         <td>Simulator</td>

249)         <td>C, Python</td>

250)         <td>Heavy</td>

251)         <td>robgjansen</td>
252)       </tr>

253) 

254)       <tr>

255)         <td><a href="#project-stem">Stem</a></td>

256)         <td>Library</td>
257)         <td>Python</td>
258)         <td>Heavy</td>

259)         <td>atagar</td>

260)       </tr>

261) 

262)       <tr>

263)         <td><a href="#project-txtorcon">Txtorcon</a></td>
264)         <td>Library</td>
265)         <td>Python, Twisted</td>

266)         <td>Moderate</td>

267)         <td>meejah</td>
268)       </tr>

269) 

270)       <tr>

271)         <td><a href="#project-tlsdate">Tlsdate</a></td>
272)         <td>Utility</td>
273)         <td>C</td>

274)         <td>Moderate</td>

275)         <td>ioerror</td>
276)       </tr>

277) 

278)       <tr>

279)         <td><a href="#project-metrics">Metrics</a></td>
280)         <td>Client Service</td>
281)         <td>Java</td>

282)         <td>Moderate</td>

283)         <td>karsten</td>
284)       </tr>

285) 

286)       <tr>

287)         <td><a href="#project-atlas">Atlas</a></td>
288)         <td>Client Service</td>
289)         <td>JavaScript</td>

290)         <td>Light</td>

291)         <td>hellais, karsten</td>

292)       </tr>

293) 

294)       <tr>
295)         <td><a href="#project-globe">Globe</a></td>
296)         <td>Client Service</td>
297)         <td>JavaScript</td>
298)         <td>Heavy</td>
299)         <td>Christian</td>
300)       </tr>
301) 

302)       <tr>

303)         <td><a href="#project-compass">Compass</a></td>
304)         <td>Client Service</td>
305)         <td>Python</td>

306)         <td>Light</td>

307)         <td>gsathya, karsten, cwacek</td>

308)       </tr>

309) 

310)       <tr>

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

314)         <td>Moderate</td>

315)         <td>karsten, gsathya</td>
316)       </tr>
317) 

318)       <tr>
319)         <td><a href="#project-doctor">DocTor</a></td>
320)         <td>Backend Service</td>
321)         <td>Python</td>
322)         <td>Light</td>
323)         <td>atagar</td>
324)       </tr>
325) 

326)       <tr>

327)         <td><a href="#project-weather">Weather</a></td>
328)         <td>Client Service</td>
329)         <td>Python</td>

330)         <td>None</td>

331)         <td>kaner</td>
332)       </tr>

333) 

334)       <tr>

335)         <td><a href="#project-gettor">GetTor</a></td>
336)         <td>Client Service</td>
337)         <td>Python</td>

338)         <td>None</td>

339)         <td>kaner</td>

340)       </tr>

341) 

342)       <tr>

343)         <td><a href="#project-torcheck">TorCheck</a></td>
344)         <td>Client Service</td>

345)         <td>Go</td>
346)         <td>Moderate</td>
347)         <td>Arlo</td>

348)       </tr>

349) 

350)       <tr>

351)         <td><a href="#project-bridgedb">BridgeDB</a></td>
352)         <td>Backend Service</td>
353)         <td>Python</td>

354)         <td>Light</td>

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

356)       </tr>

357) 

358)       <tr>

359)         <td><a href="#project-ooni-probe">Ooni Probe</a></td>

360)         <td>Scanner</td>
361)         <td>Python</td>

362)         <td>Moderate</td>

363)         <td>hellais, isis, ioerror</td>
364)       </tr>
365) 

366)       <tr>
367)         <td><a href="#project-torps">TorPS</a></td>
368)         <td>Backend Service</td>
369)         <td>Python</td>
370)         <td>Light</td>
371)         <td>Aaron Johnson</td>
372)       </tr>
373) 

374)       <tr>

375)         <td><a href="#project-torflow">TorFlow</a></td>
376)         <td>Backend Service</td>
377)         <td>Python</td>

378)         <td>None</td>

379)         <td>aagbsn, mikeperry</td>

380)       </tr>

381) 

382)       <tr>

383)         <td>*<a href="#project-torbel">TorBEL</a></td>
384)         <td>Backend Service</td>
385)         <td>Python</td>
386)         <td>None</td>
387)         <td>Sebastian</td>
388)       </tr>

389) 

390)       <tr>

391)         <td><a href="#project-tor2web">Tor2web</a></td>
392)         <td>Client Service</td>

393)         <td>Python</td>

394)         <td>Moderate</td>

395)         <td>evilaliv3, hellais</td>

396)       </tr>

397) 

398)       <tr>

399)         <td><a href="#project-anonbib">Anonbib</a></td>
400)         <td>Website</td>

401)         <td>Python</td>

402)         <td>Light</td>
403)         <td>arma, nickm</td>
404)       </tr>
405) 

406)     </table>

407) 

408)     <sub>
409)     * Project is still in an alpha state.
410)     </sub>

411) 

412)     <br /><br />

413) 

414)     <a id="project-tor"></a>
415)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a

416)     href="https://trac.torproject.org/projects/tor/report/12">bug

417)     tracker</a>)</h3>

418) 

419)     <p>
420)     Central project, providing the core software for using and participating in
421)     the Tor network. Numerous people contribute to the project to varying
422)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
423)     </p>

424) 

425)     <p>
426)     <b>Project Ideas:</b><br />

427)     <i><a href="#torCleanup">Tor Codebase Cleanup</a></i><br />

428)     <i><a href="#improveTorTestCoverage">Improve test coverage in Tor</a></i><br />
429)     <i><a href="#useMoreCores">Have the Tor daemon use more cores</a></i><br />
430)     <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br />
431)     <i><a href="#consensusDiffs">Implement consensus diffs</a></i><br />
432)     <i><a href="#improvedDnsSupport">Improved DNS support for Tor</a></i><br />
433)     <i><a href="#torSandboxing">Help improve Tor sandboxing</a></i>

434)     </p>

435) 

436)     <a id="project-orchid"></a>
437)     <h3><a href="https://github.com/subgraph/Orchid">Orchid</a> (<a
438)     href="https://github.com/subgraph/Orchid">code</a>, <a
439)     href="https://github.com/subgraph/Orchid/issues">bug

440)     tracker</a>)</h3>

441) 

442)     <p>

443)     Java implementation of Tor and successor to <a href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>.

444)     </p>

445) 

446)     <a id="project-torbrowser"></a>

447)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
448)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
449)     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

450)     tracker</a>, <a href="https://www.torproject.org/projects/torbrowser/design/">design doc</a>)</h3>
451) 

452)     <p>
453)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,

454)     Torbutton, and a Firefox fork preconfigured to work together out of

455)     the box. It contains a modified copy of Firefox that aims to resolve the
456)     privacy and security issues in mainline version.

457)     </p>

458) 

459)     <p>
460)     <b>Project Ideas:</b><br />
461)     <i><a href="#panopticlick">Panopticlick</a></i><br />
462)     </p>
463) 

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

468)     tracker</a>)</h3>

469) 

470)     <p>

471)     Firefox addon that addresses many of the client-side threats to browsing
472)     the Internet anonymously. Mike has since continued to adapt it to new
473)     threats, updated versions of Firefox, and possibly <a
474)     href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">Chrome
475)     as well</a>.

476)     </p>

477) 
478)     <a id="project-httpseverywhere"></a>
479)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
480)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
481)     href="https://trac.torproject.org/projects/tor/report/19">bug

482)     tracker</a>)</h3>

483) 

484)     <p>

485)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
486)     your communications with many major websites, making your browsing
487)     more secure.

488)     </p>

489) 

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

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

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

495) 

496)     <p>
497)     The most commonly used user interface for Tor. Matt Edman started the
498)     project in 2006 and brought it to its current stable state. Development

499)     slowed for several years, though Tomás Touceda has since taken the
500)     lead with pushing the project forward.

501)     </p>

502) 

503)     <a id="project-arm"></a>

504)     <h3><a href="https://www.atagar.com/arm/">Arm</a> (<a

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

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

508) 

509)     <p>

510)     The anonymizing relay monitor (arm) is a terminal status monitor for Tor,
511)     intended for command-line aficionados, ssh connections, and anyone with a
512)     tty terminal. This works much like top does for system usage, providing
513)     real time statistics for bandwidth, resource usage, connections, and quite
514)     a bit more.

515)     </p>

516) 

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

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

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

522) 
523)     <p>

524)     Provides Tor on the Android platform. The project is under active 
525)     development, updates to latest Tor releases, and working to stay up to 
526)     date with all changes in Android and mobile threats.

527)     </p>
528) 

529)     <p>
530)     <b>Project Ideas:</b><br />
531)     <i><a href="#orbotVPN">Orbot Android VPN</a></i><br />
532)     <i><a href="#orfox">Orfox - Firefox/Gecko-based Android Browser for Tor</a></i>
533)     </p>
534) 

535)     <a id="project-tails"></a>
536)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

537)     href="https://git-tails.immerda.ch/tails/">code</a>, <a
538)     href="https://labs.riseup.net/code/projects/tails">bug

539)     tracker</a>)</h3>
540) 
541)     <p>
542)     The Amnesic Incognito Live System is a live CD/USB distribution
543)     preconfigured so that everything is safely routed through Tor and leaves no
544)     trace on the local system. This is a merger of the Amnesia and <a
545)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
546)     and still under very active development.
547)     </p>
548) 

549)     <a id="project-torramdisk"></a>
550)     <h3><a href="http://opensource.dyc.edu/tor-ramdisk">Tor-ramdisk</a> (<a

551)     href="https://gitweb.torproject.org/tor-ramdisk.git">code</a>, <a

552)     href="http://opensource.dyc.edu/tor-ramdisk-documentation">documentation</a>)</h3>

553) 
554)     <p>

555)     Tor-ramdisk is a uClibc-based micro Linux distribution whose sole
556)     purpose is to securely host a Tor server purely in RAM.

557)     </p>
558) 

559)     <a id="project-torouter"></a>
560)     <h3><a
561)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

563)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
564)     tracker</a>)</h3>
565) 
566)     <p>
567)     Project to provide an easy-to-use, embedded Tor instance for routers. This
568)     had high activity in late 2010, but has since been rather quiet.
569)     </p>
570) 
571)     <a id="project-torsocks"></a>

572)     <h3>Torsocks (<a

573)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
574)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
575)     tracker</a>)</h3>
576) 

577)     <p>

578)     Utility for adapting other applications to work with Tor. Development has
579)     slowed and compatibility issues remain with some platforms, but it's
580)     otherwise feature complete.

581)     </p>

582) 

583)     <a id="project-torbirdy"></a>
584)     <h3>TorBirdy (<a
585)     href="https://github.com/ioerror/torbirdy">code</a>, <a
586)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
587)     tracker</a>)</h3>

588) 

589)     <p>
590)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
591)     </p>

592) 

593)     <p>
594)     <b>Project Ideas:</b><br />
595)     <i><a href="#makeTorbirdyBetter">Make TorBirdy Better</a></i>
596)     </p>
597) 

598)     <a id="project-obfsproxy"></a>

599)     <h3><a href="<page projects/obfsproxy>">Obfsproxy</a> (<a

600)     href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git">code</a>,
601)     <a 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

602)     tracker</a>)</h3>

603) 

604)     <p>
605)     A proxy that shapes Tor traffic, making it harder for censors to detect and

606)     block Tor. This has both a C and python implementation.

607)     </p>

608) 

609)     <p>
610)     <b>Project Ideas:</b><br />
611)     <i><a href="#betterPluggableTransports">Build Better Pluggable Transports</a></i>
612)     </p>
613) 

614)     <a id="project-flash-proxy"></a>
615)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
616)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
617)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Flashproxy">bug
618)     tracker</a>)</h3>

619) 

620)     <p>
621)     Pluggable transport using proxies running in web browsers to defeat
622)     address-based blocking.
623)     </p>

624) 

625)     <a id="project-shadow"></a>
626)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
627)     href="https://github.com/shadow">code</a>, <a
628)     href="https://github.com/shadow/shadow/issues">bug
629)     tracker</a>)</h3>

630) 

631)     <p>
632)     Shadow is a discrete-event network simulator that runs the real
633)     Tor software as a plug-in. Shadow is open-source software that enables
634)     accurate, efficient, controlled, and repeatable Tor experimentation.

635)     For another simulator, see <a
636)     href="http://crysp.uwaterloo.ca/software/exptor/">ExperimenTor</a>.

637)     </p>

638) 

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

640)     <h3><a href="https://stem.torproject.org/">Stem</a> (<a

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

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

643)     tracker</a>)</h3>

644) 

645)     <p>

646)     Python controller library for scripts and controller applications using
647)     Tor.

648)     </p>

649) 

650)     <p>
651)     <b>Project Ideas:</b><br />

652)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i><br />

653)     <i><a href="#relayWebPanel">Relay Web Status Panel</a></i><br />

654)     </p>

655) 

656)     <a id="project-txtorcon"></a>

657)     <h3><a href="https://txtorcon.readthedocs.org">Txtorcon</a> (<a

658)     href="https://github.com/meejah/txtorcon">code</a>, <a

659)     href="https://github.com/meejah/txtorcon/issues">bug tracker</a>)</h3>

660) 

661)     <p>
662)     Twisted-based asynchronous Tor control protocol implementation. Includes
663)     unit-tests, examples, state-tracking code and configuration abstraction.
664)     Used by OONI and APAF.
665)     </p>

666) 

667)     <p>
668)     <b>Project Ideas:</b><br />
669)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
670)     </p>
671) 

672)     <a id="project-tlsdate"></a>
673)     <h3>Tlsdate (<a href="https://github.com/ioerror/tlsdate">code</a>)</h3>

674) 

675)     <p>
676)     tlsdate: secure parasitic rdate replacement
677)     </p>

678) 

679)     <p>
680)     tlsdate sets the local clock by securely connecting with TLS to remote
681)     servers and extracting the remote time out of the secure handshake. Unlike
682)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
683)     enabled service, and provides some protection against adversaries that try
684)     to feed you malicious time information.
685)     </p>

686) 

687)     <a id="project-metrics"></a>
688)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
689)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
690)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a

691)     href="https://gitweb.torproject.org/metrics-web.git">web</a>)</h3>

692) 

693)     <p>
694)     Processing and analytics of consensus data, provided to users via the
695)     metrics portal. This has been under active development for several years by

696)     Karsten Loesing. See also <a
697)     href="https://gitweb.torproject.org/torperf.git">TorPerf</a>.

698)     </p>

699) 

700)     <a id="project-atlas"></a>
701)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
702)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

703) 

704)     <p>
705)     Atlas is a web application to discover Tor relays and bridges. It provides
706)     useful information on how relays are configured along with graphics about

707)     their past usage.

708)     </p>

709) 

710)     <p>

711)     This is the spiritual successor to <a
712)     href="https://gitweb.torproject.org/torstatus.git">TorStatus</a>, the <a

713)     href="https://svn.torproject.org/svn/torstatus/trunk/">original

714)     codebase</a> for which was written in PHP, and rewritten by students from
715)     Wesleyan as Django.

716)     </p>

717) 

718)     <a id="project-globe"></a>
719)     <h3><a href="http://globe.rndm.de/">Globe</a> (<a
720)     href="https://github.com/makepanic/globe">code</a>, <a
721)     href="https://github.com/makepanic/globe/issues">bug tracker</a>)</h3>
722) 
723)     <p>
724)     Globe is a web application that allows you to search for Tor relays and
725)     bridges. It gives you a detailed overview of properties and configurations
726)     of a relay or bridge.
727)     </p>
728) 

729)     <a id="project-compass"></a>
730)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
731)     href="https://gitweb.torproject.org/compass.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=Compass&order=priority">bug
733)     tracker</a>)</h3>

734) 

735)     <p>
736)     Compass is a web and command line application that filters and
737)     aggregates the Tor relays based on various attributes.
738)     </p>

739) 
740)     <a id="project-onionoo"></a>
741)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a
742)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
743)     href="https://gitweb.torproject.org/pyonionoo.git">python

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

745) 
746)     <p>
747)     Onionoo is a JSON based protocol to learn information about currently
748)     running Tor relays and bridges.
749)     </p>
750) 

751)     <a id="project-doctor"></a>
752)     <h3>DocTor (<a
753)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a
754)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=DocTor&order=priority">bug
755)     tracker</a>)</h3>
756) 
757)     <p>
758)     DocTor is a notification service that monitors newly published descriptor
759)     information for issues. This is primarily a service to help the tor
760)     directory authority operators, but it also checks for a handful of other
761)     issues like sybil attacks.
762)     </p>
763) 

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

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

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

769) 

770)     <p>
771)     Provides automatic notification to subscribed relay operators when their
772)     relay's unreachable. This underwent a rewrite by the <a
773)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
774)     in early 2011.
775)     </p>

776) 

777)     <p>
778)     <b>Project Ideas:</b><br />
779)     <i><a href="#rewriteWeather">Rewrite Tor Weather</a></i><br />
780)     </p>
781) 

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

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

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

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

787) 

788)     <p>
789)     E-mail autoresponder providing Tor's packages over SMTP. This has been
790)     relatively unchanged for quite a while.
791)     </p>

792) 

793)     <p>
794)     <b>Project Ideas:</b><br />
795)     <i><a href="#revamp_gettor">Revamp GetTor</a></i>
796)     </p>
797) 

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

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

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

801)     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
802)     tracker</a>)</h3>

803) 

804)     <p>

805)     Site for determining if the visitor is using Tor or not.

806)     </p>

807) 

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

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

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

813) 

814)     <p>
815)     Backend bridge distributor, handling the various pools they're distributed
816)     in. This was actively developed until Fall of 2010.
817)     </p>

818) 
819)     <a id="project-ooni-probe"></a>

820)     <h3><a href="https://ooni.torproject.org/">Ooni Probe</a> (<a

821)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
822)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
823)     tracker</a>)</h3>
824) 
825)     <p>
826)     Censorship scanner, checking your local connection for blocked or modified
827)     content.
828)     </p>
829) 

830)     <p>
831)     <b>Project Ideas:</b><br />

832)     <i><a href="#censorshipAnalyzer">Develop a Censorship Analyzer</a></i><br />
833)     <i><a href="#ooniprobePcapsSupport">Add Support for Reporting Pcaps to OoniBackend and OoniProbe</a></i>

834)     </p>
835) 

836)     <a id="project-torps"></a>
837)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
838) 
839)     <p>
840)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
841)     path selection in Tor. It chooses circuits and assigns user streams to
842)     those circuits in the same way that Tor does. TorPS is fast enough to
843)     perform thousands of simulations over periods of months.
844)     </p>
845) 

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

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

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

851) 

852)     <p>
853)     Library and collection of services for actively monitoring the Tor network.
854)     These include the Bandwidth Scanners (measuring throughput of relays) and
855)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
856)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
857)     months later. Both have been under active use since then, but development
858)     has stopped.
859)     </p>

860) 

861)     <a id="project-torbel"></a>
862)     <h3><a

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

865)     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
866)     tracker</a>)</h3>

867) 

868)     <p>
869)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
870)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
871)     (though unmaintained) Haskell application for this purpose. The initial
872)     version of TorBEL was started in GSOC 2010 but since then the project has
873)     been inactive.
874)     </p>

875) 
876)     <a id="project-tor2web"></a>
877)     <h3><a
878)     href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a
879)     href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3>
880) 
881)     <p>
882)     Tor2web allows Internet users to browse websites running in <a
883)     href="<page docs/hidden-services>">Tor hidden services</a>. It trades
884)     user anonymity for usability by allowing anonymous content to be
885)     distributed to non-anonymous users.
886)     </p>
887) 

888)     <a id="project-anonbib"></a>
889)     <h3><a
890)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
891)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
892) 
893)     <p>

894)     Anonbib is a list of important papers in the field of anonymity. It's
895)     also a set of scripts to generate the website from Latex (bibtex). If
896)     we're missing any important papers, please let us know!

897)     </p>
898) 

899)     <a id="Coding"></a>
900)     <a id="Summer"></a>

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

902) 

903)     <p>

904)     You may find some of these projects to be good ideas for <a href="<page
905)     about/gsoc>">Google Summer of Code</a> and the <a
906)     href="https://live.gnome.org/OutreachProgramForWomen">Outreach Program for

907)     Women</a>. We have labelled each idea with how much work we expect it would
908)     be (effort level), how much clue you should start with (skill level),
909)     and which of our <a href="<page about/corepeople>">core developers</a>
910)     would be good mentors. If one or more of these ideas looks promising to
911)     you, please <a href="<page about/contact>">contact us</a> to discuss your
912)     plans rather than sending blind applications. You may also want to propose
913)     your own project idea &mdash; which often results in the best applications.

914)     </p>

915) 

916)     <ol>

917) 

918)     <a id="txtorcon-stemIntegration"></a>
919)     <li>
920)     <b>Txtorcon/Stem Integration</b>
921)     <br>
922)     Effort Level: <i>Medium</i>
923)     <br>
924)     Skill Level: <i>Medium</i>
925)     <br>
926)     Likely Mentors: <i>meejah, Damian (atagar)</i>
927)     <p>Txtorcon is a Twisted-based Python controller library, and Stem is a
928)     synchronous (threaded) one, also in Python. There is no need to have
929)     two implementations of (at least) the protocol parsing code. This
930)     project would entail eliminating duplication by leveraging Stem's
931)     parsing in txtorcon while keeping txtorcon's API the same (or at least
932)     close).</p>

933)     <p>Besides this you should identify some additional tasks to improve our
934)     controller space across these two libraries. Some ideas are...</p>
935)     <ul>
936)       <li>Write a tutorial for <a
937)       href="https://stem.torproject.org/tutorials.html">stem's tutorial
938)       page</a> demonstrating cross txtorcon/stem usage.</li>
939)       <li>Expand the txtorcon API to include functionality of <a
940)       href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's
941)       controller</a> that would be of interest to twisted users. All additions
942)       should include tests!</li>
943)       <li>Come up with some ideas of your own! We'd love to discuss them with
944)       you.</li>
945)     </ul>

946)     <p>This would very likely involve changes to both libraries, although
947)     most would be expected to be in txtorcon. meejah is available to
948)     mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>
949)     <p>It would help if you're already familiar with event-based programming,
950)     bonus points if it's Twisted.</p>
951)     </li>
952) 

953)     <a id="relayWebPanel"></a>
954)     <li>

955)     <b>Relay Web Status Dashboard</b>

956)     <br>
957)     Effort Level: <i>Medium</i>
958)     <br>
959)     Skill Level: <i>Medium</i>
960)     <br>
961)     Likely Mentors: <i>Damian (atagar)</i>
962)     <p>
963)     Relay operators presently have a couple options for monitoring the status
964)     of their relay: <a
965)     href="https://www.torproject.org/getinvolved/volunteer.html.en#project-vidalia">Vidalia</a>
966)     which is a gui and <a href="https://www.atagar.com/arm/">arm</a> which uses
967)     curses. This project would be to make a new kind of monitor specifically
968)     for relay operators that provides a status dashboard site on localhost.
969)     </p>
970)     <p>
971)     The interface will likely <a
972)     href="https://www.atagar.com/arm/screenshots.php">borrow heavily from
973)     arm</a>, except of course in areas where we can improve upon it. Two
974)     important design constraints is that a localhost controller provides a
975)     bigger attack surface than guis or curses, so we should be a little more
976)     wary of what it does. This should be a read-only controller (ie, you can't
977)     *do* anything to the relay) and by default not surface any sensitive
978)     information (such as arm's connection panel).
979)     </p>
980)     <p>
981)     This project will likely include two parts: an AJAX site and a localhost
982)     daemon to fulfill those requests. <a
983)     href="https://stem.torproject.org/">Stem</a> is the backend of arm, and can
984)     be used to get everything you see in arm's interface (making it a natural
985)     choice for the daemon). That said, this project might entail some Stem
986)     improvements if we run across any gaps.
987)     </p>
988)     <p>

989)     This project has the potential for numerous users, one of which is an
990)     interface for <a
991)     href="https://www.torproject.org/getinvolved/volunteer.html.en#project-torouter">Torouter</a>.
992)     We should check if Torouter has any special use cases or constraints we
993)     should take into consideration.
994)     </p>
995)     <p>

996)     Applicants should be familiar with Python, JavaScript, and learn about
997)     <a href="https://stem.torproject.org/">Stem</a>. <b>As part of your
998)     application for this project please make both mockups of the interface and
999)     a proof of concept demo application using JS to surface something with
1000)     Stem. <a
1001)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">Involvement
1002)     with Stem development</a> during the application process is also a big
1003)     plus.</b>
1004)     </p>
1005)     </li>
1006) 

1007)     <a id="torCleanup"></a>

1008)     <li>

1009)     <b>Tor Codebase Cleanup</b>

1010)     <br>

1011)     Effort Level: <i>Low to High, depending on subproject chosen</i>

1012)     <br>

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

1014)     <br>

1015)     Likely Mentors: <i>Nick (nickm)</i>

1016)     <p>

1017)     The Tor code is almost 10 years old in places, and we haven't always had
1018)     enough time or wisdom to write things as well as we could have.  Our unit
1019)     test coverage is shamefully low, and the dependency graph of our modules is
1020)     shamefully convoluted . We could use refactoring and unit tests!  Please
1021)     look through the Tor source code and look for ugly or tricky code or
1022)     dependencies -- the uglier and trickier the better -- and think about how
1023)     you could make the code look better, read better, and (subject to testing)
1024)     work better.

1025)     </p>

1026) 

1027)     <p>

1028)     If this is for a fun side-project, it would be great for you to work on
1029)     anything that can be made better and more tested.  For an internship-level
1030)     position, we'd hope that you could find a number of particularly tricky or
1031)     knotty piece of the code to clean up, and aim for resolving the ugliest
1032)     problems, not necessarily the easiest.

1033)     </p>

1034) 

1035)     <p>

1036)     For a big project here, it would be great to pick one of the major
1037)     "submodules" of Tor -- path selection, node discovery, directory authority
1038)     operations, directory service -- and refactor its interface completely, to
1039)     minify and codify its points of contact with the rest of Tor.

1040)     </p>

1041) 
1042)     <p>
1043)     <b>As part of your application for this project please identify one of the
1044)     thorniest Tor functions and submit a patch refactoring it to be better. If
1045)     you find this to be difficult then this likely isn't the project for
1046)     you.</b>
1047)     </p>

1048)     </li>

1049) 

1050)     <a id="betterPluggableTransports"></a>
1051)     <li>
1052)     <b>Build Better Pluggable Transports</b>
1053)     <br>
1054)     Effort Level: <i>Medium to High</i>
1055)     <br>
1056)     Skill Level: <i>Medium</i>
1057)     <br>

1058)     Likely Mentors: <i>Steven (sjmurdoch), Ximin (infinity0), George (asn)</i>

1059)     <p>

1060)     For Tor users in censored countries, we have a <a
1061)     href="https://www.torproject.org/docs/pluggable-transports.html.en">
1062)     pluggable transports</a> framework that uses external programs to bypass
1063)     censorship in different ways. Each of these have their own strengths and
1064)     weaknesses.

1065)     </p>
1066) 
1067)     <p>

1068)     We have deployed <a
1069)     href="https://www.torproject.org/projects/obfsproxy.html.en">obfsproxy</a>
1070)     and <a href="http://crypto.stanford.edu/flashproxy/">flashproxy</a> bridges
1071)     for a while, accessible using separately-installed pluggable transport
1072)     clients. Recently, we added this client support to the main Tor Browser
1073)     Bundle, and are adding more transports such as scramblesuit and fteproxy.
1074)     </p>
1075) 
1076)     <p>
1077)     There are several possible directions for this project. Ideas include:
1078)       <ol>
1079)         <li>Address gaps or weaknesses in our existing pluggable transports
1080)           <ul>
1081)             <li>Flashproxy: Add WebRTC support to traverse NATs.</li>
1082)             <li>Flashproxy: Improve the facilitator's resistance against DoS
1083)             and poisoning attacks.</li>
1084)           </ul>
1085)         </li>
1086)         <li>Build our pluggable transport combiner, that chains several
1087)         transports together to take advantage of orthogonal types of blocking
1088)         resistance.</li>
1089)         <li>Improve the UX for selecting the appropriate pluggable transport in
1090)         the new Tor Browser Bundle, whilst maintaining user security.</li>
1091)         <li>Implement a new pluggable transport that resists blocking in a
1092)         novel way.
1093)         <ul>
1094)           <li>Impersonate a voice-over-IP protocol</li>
1095)           <li>Impersonate HTTP <a
1096)           href="http://www.cs.utexas.edu/~amir/papers/parrot.pdf">sufficiently
1097)           well</a> that traffic will go through a HTTP-only proxy</li>
1098)           <li>Implement <a
1099)           href="http://cacr.uwaterloo.ca/techreports/2011/cacr2011-21.pdf">scanning
1100)           resistance</a></li>
1101)         </ul>
1102)         </li>
1103)       </ol>
1104)     </p>
1105) 
1106)     <p>
1107)     Applicants should be familiar with asynchronous/reactive programming, in
1108)     particular the <a href="https://twistedmatrix.com/">Twisted framework</a>
1109)     or something related. Most of the existing code is written in Python, with
1110)     some parts in JavaScript and Go, so you should know at least one of these.
1111)     You are invited to talk to us and ask questions, via our mailing lists
1112)     or IRC. <b>As part of your application, please contribute a patch that
1113)     implements a small feature or fixes a bug related to this area, e.g. <a
1114)     href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Pluggable+transport">1</a>,
1115)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Obfsproxy">2</a>,
1116)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Flashproxy">3</a>.
1117)     </b>

1118)     </p>
1119) 

1120)     <a id="hsSearchEngine"></a>
1121)     <li>
1122)     <b>Search Engine for Hidden Services</b>
1123)     <br>
1124)     Effort Level: <i>Medium</i>
1125)     <br>
1126)     Skill Level: <i>Medium</i>
1127)     <br>
1128)     Likely Mentors: <i>George (asn)</i>
1129)     <p>
1130)     This project involves researching and developing a search engine for
1131)     Hidden Services.
1132)     </p>
1133) 
1134)     <p>
1135)     The student is expected to develop a search engine that can index
1136)     hidden services and reply to search queries. The student should also
1137)     develop a crawler that can search both "clear web" and hidden service
1138)     websites to find more addresses. The student is expected to use and
1139)     improve already existing search engine frameworks (e.g. YaCy), and not
1140)     reinvent the wheel when it's possible.
1141)     </p>
1142) 
1143)     <p>
1144)     The student should have a decent understanding of how search engines
1145)     work, what algorithms they use, and of any related open source tools
1146)     that are currently available.
1147)     </p>
1148) 

1149)     <a id="profileUDPTransport"></a>
1150)     <li>
1151)     <b>Profile UDP transport protocols</b>
1152)     <br>
1153)     Effort Level: <i>Medium to High</i>
1154)     <br>
1155)     Skill Level: <i>High</i>
1156)     <br>
1157)     Likely Mentors: <i>Steven (sjmurdoch)</i>
1158)     <p>
1159)     There are <a
1160)     href="https://research.torproject.org/techreports/datagram-comparison-2011-11-07.pdf">lots
1161)     of options</a> as to how Tor could send its data over UDP rather than TCP,
1162)     and some will likely perform significantly better than others. This project
1163)     will evaluate these options, so as to decide which should be used in future
1164)     versions of Tor. A first step will be to benchmark the various transport
1165)     protocols being considered, in terms of performance and also code quality,
1166)     including userspace TCP, <a
1167)     href="https://github.com/bittorrent/libutp">&mu;TP</a>, <a
1168)     href="http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol">SCTP</a>
1169)     and <a href="http://curvecp.org/">CurveCP</a>. Initially these transport
1170)     protocols will be examined in isolation, but if the project progresses well
1171)     one or more could be integrated in Tor.
1172)     </p>
1173)     </li>
1174) 

1175)     <a id="httpsEverywhereRulesetTesting"></a>
1176)     <li>
1177)     <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>
1178)     <br>
1179)     Effort Level: <i>Medium</i>
1180)     <br>
1181)     Skill Level: <i>Medium</i>
1182)     <br>

1183)     Likely Mentors: <i>Peter Eckersley (pde), Micah Lee</i>

1184)     <p>
1185) Ondrej Mikle has implemented a codebase for testing HTTPS Everywhere rulesets
1186) by crawling pages that are affected by the ruleset (<a href="https://github.com/hiviah/https-everywhere-checker">repository</a>).
1187)     </p>
1188) 
1189)     <p>
1190) This codebase still has some rough edges that need to be smoothed over, but
1191) once those are done it should be incorporated into the HTTPS Everywhere build
1192) process, in order to improve the quality of our releases.
1193)     </p>
1194)     </li>
1195) 

1196)     <a id="censorshipAnalyzer"></a>
1197)     <li>
1198)     <b>Develop a Censorship Analyzer</b>
1199)     <br>
1200)     Effort Level: <i>Medium</i>
1201)     <br>
1202)     Skill Level: <i>Medium to High (depends on the implemented tests)</i>
1203)     <br>
1204)     Likely Mentors: <i>Philipp (phw)</i>
1205)     <p>
1206) Tor is documented to be blocked in <a
1207) href="https://censorshipwiki.torproject.org">several countries</a>. Analyzing
1208) these censorship incidents can be a tedious task; especially without access to
1209) machines inside the censoring networks. To make analysis easier, it would be
1210) great to have a lightweight analysis tool which can be run by censored users.
1211) This tool would conduct a number of networking tests and figure out if and how
1212) Tor could be blocked. The tool's final report should then somehow make it back
1213) to the Tor project.
1214)     </p>
1215) 
1216)     <p>
1217) The theory behind this tool is already <a

1218) href="http://www.cs.kau.se/philwint/pdf/foci2013.pdf">documented

1219) in a research paper</a>. What we now need is code! Implementing it would first
1220) mean getting familiar with <a href="https://ooni.torproject.org">OONI</a> and
1221) <a href="http://twistedmatrix.com/trac/">Twisted</a>. After that, the tool
1222) should be implemented as a number of OONI-specific networking tests.
1223)     </p>
1224)     </li>
1225) 

1226)     <a id="makeTorbirdyBetter"></a>
1227)     <li>
1228)     <b>Make TorBirdy Better</b>
1229)     <br>
1230)     Effort Level: <i>High</i>
1231)     <br>
1232)     Skill Level: <i>Medium</i>
1233)     <br>
1234)     Likely Mentors: <i>Sukhbir Singh (sukhe), Jacob Appelbaum (ioerror)</i>
1235)     <p>
1236) TorBirdy is an extension that configures Thunderbird to make connections over
1237) the Tor anonymity network. TorBirdy has been under development for quite a
1238) while but there are two known leaks that prevent it from being used by a wider
1239) audience. As part of this project, you will be working on plugging the known
1240) leaks and implementing a HTTP proxy.
1241)     </p>
1242) 
1243)     <p>
1244) <b>Part 1:</b> There are two patches pending with Mozilla that will plug the two known
1245) leaks in Thunderbird where the local time is disclosed through the date and the
1246) message-ID header. As part of your project, you will work on getting these
1247) patches finished/reimplemented and getting them merged with Mozilla. Please
1248) look at tickets <a
1249) href="https://trac.torproject.org/projects/tor/ticket/6314">#6314</a> and <a
1250) href="https://trac.torproject.org/projects/tor/ticket/6315">#6315</a> for more
1251) information.
1252)     </p>
1253) 
1254)     <p>
1255) <b>Part 2:</b> TorBirdy needs a HTTP proxy or a HTTP -&gt; SOCKS5 shim. Please look at
1256) ticket <a href="https://trac.torproject.org/projects/tor/ticket/6958">#6958</a>
1257) for more information. Note: this has to be done using JavaScript and not using
1258) an external proxy.
1259)     </p>
1260) 
1261)     <p>
1262) If time permits and you are awesome enough to finish the above two tasks, you
1263) will be working on the remaining TorBirdy tickets.
1264)     </p>
1265) 
1266)     <p>
1267) Applicants should be familiar with C++ and JavaScript. As part of your
1268) application for this project, please submit code samples for previous C++ and
1269) JavaScript projects that you have developed or point us to projects you have
1270) been involved with (links to a public Git/GitHub repository preferred). Prior
1271) extension development is a big plus and will be given preference during
1272) application ranking.
1273)     </p>
1274) 
1275)     <p>

1276) You may contact the mentors on IRC for more information. (sukhe on #tor-dev, #tor on irc.oftc.net)

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

1280)     <a id="ooniprobePcapsSupport"></a>
1281)     <li>
1282)     <b>Add Support for Reporting Pcaps to OoniBackend and OoniProbe</b>
1283)     <br>
1284)     Effort Level: <i>Medium</i>
1285)     <br>
1286)     Skill Level: <i>Medium</i>
1287)     <br>
1288)     Likely Mentors: <i>Arturo (hellais), Aaron (aagbsn)</i>
1289)     <p>
1290) The feature should also add support for including only packet capture data that
1291) is relevant to the test being run. This means that the pcap should not contain
1292) all the data sniffed on the users machine, but only that which was generated
1293) and intended to be received by ooniprobe.
1294)     </p>
1295) 
1296)     <p>
1297) This can probably be implemented by setting up a tun/tap device and routing all
1298) the ooniprobe traffic through it and only capturing data sent and received from
1299) that device. The task for the student will also be that of doing research into
1300) what are possible strategies for doing this. <b><a
1301) href="https://trac.torproject.org/projects/tor/ticket/7416">For more
1302) information see ticket 7416.</a></b>
1303)     </p>
1304)     </li>
1305) 

1306)     <a id="orbotVPN"></a>
1307)     <li>
1308)     <b>Orbot Android VPN</b>
1309)     <br>
1310)     Effort Level: <i>Medium</i>
1311)     <br>
1312)     Skill Level: <i>High</i>
1313)     <br>
1314)     Likely Mentors: <i>Nathan (n8fr8)</i>
1315)     <p>
1316) Android offers the ability for any application to establish a
1317) VPNService through which all traffic on the device is sent. We want to
1318) implement this type of service in order to route all traffic through
1319) the Tor network. This is a feature that will be implemented directly
1320) into Orbot: Tor for Android if successfully implemented.
1321)     </p>
1322) 
1323)     <p>
1324) The deliverables for the project will be a working Android VPN
1325) implementation that routes traffic through Tor, and integration of VPN
1326) code into the Orbot app. There must also be time made for reporting on
1327) the project through blog posts, network auditing of tracking to ensure
1328) leakage is not occurring.
1329)     </p>
1330) 
1331)     <p>
1332) Useful links and documentation to study:
1333)     </p>
1334) 
1335)     <ul>
1336)       <li><a href="https://gitweb.torproject.org/orbot.git">Orbot</a></li>
1337)       <li><a href="http://developer.android.com/reference/android/net/VpnService.html">Android VPNService API</a></li>
1338)       <li><a href="https://github.com/guardianproject/OrbotVPN">Existing work on Orbot VPN</a></li>
1339)     </ul>
1340) 
1341)     <p>
1342) Applicant should have the ability to build Orbot application from
1343) source using Android SDK and NDK tools. A solid understanding of IP
1344) routing, iptables, netfilter and VPN protocols would also be very
1345) helpful. The ability to use Wireshark or other network monitoring
1346) software to test and verify solution is something that can be taught,
1347) but if you already know how, bonus! Finally, understanding how the
1348) exiting Tor software can be used with various transparent proxying
1349) configurations is a good first step to understanding this problem.
1350)     </p>
1351)     </li>
1352) 
1353)     <a id="orfox"></a>
1354)     <li>
1355)     <b>Orfox - Firefox/Gecko-based Android Browser for Tor</b>
1356)     <br>
1357)     Effort Level: <i>High</i>
1358)     <br>
1359)     Skill Level: <i>Medium</i>
1360)     <br>
1361)     Likely Mentors: <i>Nathan (n8fr8)</i>
1362)     <p>
1363) With almost 1 million downloads, our Orweb browser has been a popular
1364) solution for easily accessing the web via Tor or any other HTTP or
1365) SOCKS proxy, while also ensuring local data caches are cleared and
1366) cookies are properly managed. Orweb is based on WebView, which has its
1367) limitations unfortunately. We would like to move to a
1368) Firefox/Fennec/GeckoView based browser, and have created a prototype
1369) for it. Mozilla has begun releasing GeckoView as a standalone
1370) component, as well, but it needs more testing, debugging and work on
1371) integration into our streamlined browser app model. Our end goal is to
1372) have a mobile browser that matches Tor Browser in terms of privacy
1373) enhancing features and security.
1374)     </p>
1375) 
1376)     <p>
1377) The deliverables for the project are expected to be the creation of a
1378) alpha quality release of Orfox, a GeckoView-based browser with feature
1379) parity of Orweb browser. A bonus goal is to implement additional
1380) features and capabilities based on Tor Browser patches for
1381) Fennec/Mozilla core. Finally, as always, a required activity is a
1382) network audit testing of implemented solution with write-ups, reports
1383) posted publicly.
1384)     </p>
1385) 
1386)     <p>
1387) Useful links to review:
1388)     </p>
1389) 
1390)     <ul>
1391)       <li><a href="https://github.com/guardianproject/orfox">Orfox (gecko prototype)</a></li>
1392)       <li><a href="https://github.com/guardianproject/orweb">Orweb (production browser on WebView)</a></li>
1393)       <li><a href="http://starkravingfinkle.org/blog/2013/10/geckoview-embedding-gecko-in-your-android-application/">GeckoView info</a></li>
1394)       <li><a href="https://www.torproject.org/projects/torbrowser.html.en">Tor Browser (desktop)</a></li>
1395)     </ul>
1396) 
1397)     <p>
1398) Applicant should have the ability to build Fennec and GeckoView
1399) libraries from source using Android SDK and NDK. Some experince with
1400) browser security models and threats would be a useful background to
1401) have. Ability to do network audits to ensure browser proxying is not
1402) leaking DNS, media streams or other network traffic, as well as tests
1403) against common browser de-anonymizing attacks are necessary.
1404)     </p>
1405)     </li>
1406) 
1407)     <a id="improveTorTestCoverage"></a>
1408)     <li>
1409)     <b>Improve test coverage in Tor</b>
1410)     <br>
1411)     Effort Level: <i>Medium</i>
1412)     <br>
1413)     Skill Level: <i>Medium</i>
1414)     <br>
1415)     Likely Mentors: <i>Nick (nickm)</i>
1416)     <p>
1417) Right now, our unit test coverage with the tests we ship is around 30%
1418) -- only 30% of the executable lines in our source are reached by the
1419) unit tests.  Improving this test coverage could make Tor development
1420) much more reliable.
1421)     </p>
1422) 
1423)     <p>
1424) So we need better unit tests, and we need better integration tests too.
1425)     </p>
1426) 
1427)     <p>
1428) Improving unit tests would would involve refactoring functions to be more
1429) testable, and writing a bunch of unit tests.
1430)     </p>
1431) 
1432)     <p>
1433) Improving integratino tests would involve refactoring and improving
1434) the "chutney" program that launches a test tor network, and writing a
1435) bunch of tests to see what works and what doesn't work on such a
1436) network.  It could also involve writing tests using the library "<a
1437) href="https://stem.torproject.org/">stem</a>" to script individual clients on a
1438) Chutney network.
1439)     </p>
1440) 
1441)     <p>
1442) To get a feel for how testing works in Tor today, download Tor and
1443) Chutney, and make sure you can build Tor and use Chutney.  See how the
1444) unit tests work by skimming some of the test code in the src/test
1445) subdirectory.  Try computing test coverage (according to the
1446) instructions in the doc/HACKING file.
1447)     </p>
1448) 
1449)     <p>
1450) Also, have a look at the one current integration test that works on
1451) chutney today: it is a shell script distributed with Tor as
1452) src/test/test-tor-network.sh .  We probably don't want to have all of
1453) our integration tests be written as shell scripts, but it's interesting
1454) to see how one works.
1455)     </p>
1456) 
1457)     <p>
1458) If working on designs for an improved or refactored Chutney, watch out for <a
1459) href="http://www.joelonsoftware.com/articles/fog0000000018.html">"archicture
1460) astronautics"</a>: while it's important that we have a well-designed and
1461) maintainable Chutney architecture, it wouldn't be very useful if a good
1462) architecture were the <em>only</em> outcome here: we need tests too.
1463)     </p>
1464) 
1465)     <p>
1466) As part of the application process, please contribute a patch that makes
1467) a non-trivial improvement to chutney, and/or include a new test for some
1468) interesting Tor function. (Please pick a function that isn't completely
1469) easy to test.)
1470)     </p>
1471)     </li>
1472) 
1473)     <a id="useMoreCores"></a>
1474)     <li>
1475)     <b>Have the Tor daemon use more cores</b>
1476)     <br>
1477)     Effort Level: <i>Medium</i>
1478)     <br>
1479)     Skill Level: <i>Medium</i>
1480)     <br>
1481)     Likely Mentors: <i>Nick (nickm)</i>
1482)     <p>
1483) Right now, if you run a busy Tor server on a multicore computer, most of
1484) the cores are mostly unused.  We have a "cpuworker" mechanism to move
1485) expensive computations into worker threads, but that mechanism is
1486) currently only used for a small fraction of our cryptography.  Moving
1487) more work into the worker threads could improve performance immensely.
1488)     </p>
1489) 
1490)     <p>
1491) So it would be great to parallelize our cryptography more in order to
1492) better handle more cores.  See
1493) <a href="https://trac.torproject.org/projects/tor/wiki/org/projects/Tor/MultithreadedCrypto">MultithreadedCrypto</a>
1494) for some background info, and
1495) <a href="https://trac.torproject.org/projects/tor/ticket/7572">ticket 7572</a> for some subtickets
1496) on our tracker.
1497)     </p>
1498) 
1499)     <p>
1500) (If you're reading through the code to see how it works today, you will
1501) also want to have a look at the new implementation for cpuworkers
1502) described in <a href="https://trac.torproject.org/projects/tor/ticket/9682">9682</a>.)
1503)     </p>
1504) 
1505)     <p>
1506) Completing the implementation of ticket #7572 --which would move our
1507) circuit crypto onto separate threads-- could be a good summer project.
1508) Alternatively, moving all of the signature generation and verification
1509) code onto the cpuworkers could be fun.  In either case, you will have
1510) some important architectural decisions to make about how to minimize
1511) shared data between the main thread and the workers, how to avoid
1512) race conditions between them, and how to test it all to make sure it has
1513) no hidden failure cases.
1514)     </p>
1515) 
1516)     <p>
1517) As part of the application process for this project, please contribute a
1518) nontrivial patch to Tor -- ideally, one that will affect some part of
1519) the codebase that you want to work on.
1520)     </p>
1521)     </li>
1522) 
1523)     <a id="improveHiddenServices"></a>
1524)     <li>
1525)     <b>Help improve Tor hidden services</b>
1526)     <br>
1527)     Effort Level: <i>Medium</i>
1528)     <br>
1529)     Skill Level: <i>Medium</i>
1530)     <br>
1531)     Likely Mentors: <i>Nick (nickm)</i>
1532)     <p>
1533) We're working on a revamp of the entire Tor hidden service design to
1534) improve the security and reliability of the hidden service system.
1535)     </p>
1536) 
1537)     <p>
1538) This is a big project: see
1539) <a href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/224-rend-spec-ng.txt">proposal
1540) 224</a> for the latest design.  Are you interested in implementing some
1541) part of that?
1542)     </p>
1543) 
1544)     <p>
1545) This is a very ambitious project, so we're deliberately not suggesting
1546) particular sub-topics.  If you're interested in participating, try to
1547) read and understand the <a
1548) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/rend-spec.txt">existing
1549) design</a> and the design proposal for the new design, and then talk to
1550) us about what part you want to work on.
1551)     </p>
1552) 
1553)     <p>
1554) As part of the application process for this project, please contribute a
1555) nontrivial patch to Tor -- ideally, one that will affect some part of
1556) the codebase that you want to work on.
1557)     </p>
1558)     </li>
1559) 
1560)     <a id="consensusDiffs"></a>
1561)     <li>
1562)     <b>Implement consensus diffs</b>
1563)     <br>
1564)     Effort Level: <i>Medium</i>
1565)     <br>
1566)     Skill Level: <i>Medium</i>
1567)     <br>
1568)     Likely Mentors: <i>Nick (nickm)</i>
1569)     <p>
1570) Right now, every few hours, a Tor client downloads a new signed "consensus
1571) document" that describes the state of the network.  Even though these
1572) documents are compressed, thisstill takes almost half a megabyte.
1573)     </p>
1574) 
1575)     <p>
1576) <a
1577) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/140-consensus-diffs.txt">Proposal
1578) 140</a> describes a design to save a lot of bandwidth by transferring
1579) compressed <a href="http://en.wikipedia.org/wiki/Diff">diff</a>s instead
1580) of transferring the entire consensus document.
1581)     </p>
1582) 
1583)     <p>
1584) That's an attractive idea, but it presents some programming challenges.
1585) We probably don't want to ship a 'diff' and 'patch' along with Tor.  Is
1586) there a free, <strong>safe</strong>, robust implementation of one of the
1587) good diff algorithms that we can use?
1588)     </p>
1589) 
1590)     <p>
1591) Alternatively, can we take advantage of regularities in the descriptor
1592) format in order to generate diffs more simply?
1593)     </p>
1594) 
1595)     <p>
1596) As part of the application process for this project, please contribute a
1597) nontrivial patch to Tor -- ideally, one that will affect some part of
1598) the codebase that you want to work on.  Make sure that your application
1599) describes which implementations of the diff and patch algorithms you
1600) intend to use, and that your coding samples show strong evidence that
1601) you can do secure string manipulation in C.
1602)     </p>
1603)     </li>
1604) 
1605)     <a id="improvedDnsSupport"></a>
1606)     <li>
1607)     <b>Improved DNS support for Tor</b>
1608)     <br>
1609)     Effort Level: <i>Medium</i>
1610)     <br>
1611)     Skill Level: <i>Medium</i>
1612)     <br>
1613)     Likely Mentors: <i>Nick (nickm)</i>
1614)     <p>
1615) Right now, you can only use Tor's DNS support to look up IPv4 and IPv6
1616) addresses, and to fetch PTR records.  But DNS can do so much more!
1617)     </p>
1618) 
1619)     <p>
1620) <a
1621) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/219-expanded-dns.txt">Proposal
1622) 219</a> describes some new cell types that Tor could use to support
1623) more types of DNS over Tor.
1624)     </p>
1625) 
1626)     <p>
1627) To see how Tor implements its existing DNS lookups, start by tracing the
1628) the connection_exit_begin_resolve() function in src/or/connection_edge.c ,
1629) and see how we pass these requests downwards through src/or/dns.c to the
1630) underlying resolver.  It's not too complicated, but there are some
1631) tricky parts to understand.
1632)     </p>
1633) 
1634)     <p>
1635) As part of the application process for this project, please contribute a
1636) nontrivial patch to Tor -- ideally, one that will affect some part of
1637) the codebase that you want to work on.
1638)     </p>
1639)     </li>
1640) 
1641)     <a id="torSandboxing"></a>
1642)     <li>
1643)     <b>Help improve Tor sandboxing</b>
1644)     <br>
1645)     Effort Level: <i>Medium</i>
1646)     <br>
1647)     Skill Level: <i>Medium</i>
1648)     <br>
1649)     Likely Mentors: <i>Nick (nickm)</i>
1650)     <p>
1651) The seccomp2 mechanism on Linux lets programs improve their robustness
1652) against unforseen bugs by running with restrictions on which system
1653) calls they can invoke and how they can call them.  This can help
1654) security a lot.
1655)     </p>
1656) 
1657)     <p>
1658) Thanks to a GSOC student from last year, we now have seccomp2 support on
1659) Linux, which we use to restrict the capabilities of the entire Tor
1660) process.  (For implementation details, see src/commmon/sandbox.c in the
1661) Tor source.)
1662)     </p>
1663) 
1664)     <p>
1665) But since the restrictions are done over the whole process, all pieces
1666) of the Tor code have permission to do things that only small parts of
1667) the Tor program need to do.  Also, since we use seccomp2, these
1668) restrictions only work on Linux.
1669)     </p>
1670) 
1671)     <p>
1672) It would be great to instead divide the main Tor program into multiple
1673) processes with a robust IPC mechanism and assign each process its own
1674) minimal set of privileges; and to have this work (as best we can) on
1675) systems that don't have seccomp2 (eg Windows, Mac).
1676)     </p>
1677) 
1678)     <p>
1679) Either of these could be a whole GSOC project.
1680)     </p>
1681) 
1682)     <p>
1683) To get started, make sure you understand the existing sandboxing code.
1684) If you're interested in splitting Tor into multiple processes, think
1685) about the architecture, and think about how we could reach this
1686) architecture without completely rewriting the codebase.  (Remember that
1687) even if you're focusing on Linux, Tor still needs to work on other
1688) operating systems.)
1689)     </p>
1690) 
1691)     <p>
1692) If you're interested in supporting more platforms, make sure you
1693) understand and can explain what sandboxing mechansisms you want to use,
1694) and what they're capable of.  (You might want to investigate the way
1695) that other open-source programs, like the Chrome web browser, do their
1696) sandboxing on different platforms.)
1697)     </p>
1698) 
1699)     <p>
1700) As part of the application process for this project, please contribute a
1701) nontrivial patch to Tor -- ideally, one that will affect some part of
1702) the codebase that you want to work on.
1703)     </p>
1704)     </li>
1705) 

1706)     <a id="panopticlick"></a>
1707)     <li>
1708)     <b>Panopticlick</b>
1709)     <br>
1710)     Effort Level: <i>Medium</i>
1711)     <br>
1712)     Skill Level: <i>Medium</i>
1713)     <br>
1714)     Likely Mentors: <i>Georg (GeKo)</i>
1715)     <p>
1716) Tor Browser users are often complaining about their browser fingerprint
1717) being not as good as it should according to the <a
1718) href="https://panopticlick.eff.org">Panopticlick of the EFF</a>. To fix
1719) that the student should develop an own <a
1720) href="https://panopticlick.eff.org/browser-uniqueness.pdf">Panopticlick</a>
1721) instance which performs, in a first step, basic tests estimating the

1722) uniformity among Tor Browser Bundle users. The user should get

1723) feedback on how she performed and the test results should be available
1724) in a machine readable format (e.g. JSON). In a second step one could
1725) think about adding more sophisticated tests or <a
1726) href="https://trac.torproject.org/projects/tor/ticket/6119#comment:1">supporting
1727) other browser vendors</a> that might want to test the uniformity amongst

1728) their userbase as well.

1729)     </p>
1730)     </li>
1731) 

1732)     <a id="revamp_gettor"></a>
1733)     <li>
1734)     <b>Revamp GetTor</b>
1735)     <br>
1736)     Effort Level: <i>High</i>
1737)     <br>
1738)     Skill Level: <i>Medium</i>
1739)     <br>
1740)     Likely Mentors: <i>Sukhbir Singh (sukhe), Nima Fatemi (mrphs)</i>
1741)     <p>
1742) GetTor is a program that serves Tor bundles and related components over SMTP.
1743) Users request the Tor Browser Bundle by sending an email to GetTor, which sends

1744) back the bundle as email attachments. In countries where the Tor Project
1745) website is blocked, GetTor is a convenient way for users to get access to the
1746) bundles.

1747)     </p>
1748) 
1749)     <p>
1750) GetTor has been unmaintained for a while and needs a revamp. The main issue is
1751) that because the Tor Browser Bundle size exceeds 25 MB, sending it through
1752) GetTor no longer works as most email providers don't support attachments
1753) exceeding 25 MB. To alleviate this issue, bundles are now uploaded on
1754) cloud-based services such as Google Drive and Dropbox and links are sent
1755) out in the email body instead of attachments. This current setup is far from
1756) complete -- GetTor needs a lot of work to get it to a point where it can do
1757) smart things again and do them in the right way.
1758)     </p>
1759) 
1760)     <p>
1761) As part of this project, you should:
1762)     </p>
1763) 
1764)     <ul>
1765)       <li>Have some understanding of what GetTor does in general and the current state of its operation.</li>
1766)       <li>Come up with ideas on how to make it better.</li>
1767)       <li>Convince us if you would like to fix the existing code or want to rewrite GetTor from scratch.</li>
1768)     </ul>
1769) 
1770)     <p>
1771) In addition to the above points, applications should be familiar with Python.
1772) As part of the application process, study the <a
1773) href="https://gitweb.torproject.org/gettor.git">GetTor code</a> and submit a
1774) patch for returning the SHA1 checksum of the package instead of the text in
1775) sendSorrySize() in response.py. (since you cannot test the patch, as long as it
1776) is clear that you had some idea of what you were doing, it should be fine)
1777)     </p>
1778) 
1779)     <p>

1780) Note: Please do not submit an application without talking to the mentors: #sukhe and #mrphs on IRC. IRC is preferred but if for any reason you don't want/can't use it, please email the mentors.

1781)     </p>
1782)     </li>
1783) 

1784)     <a id="rewriteWeather"></a>
1785)     <li>
1786)     <b>Rewrite Tor Weather</b>
1787)     <br>
1788)     Effort Level: <i>Medium</i>
1789)     <br>
1790)     Skill Level: <i>Medium</i>
1791)     <br>
1792)     Likely Mentors: <i>Karsten (karsten)</i>
1793)     <p>
1794) <a href="https://weather.torproject.org/">Tor Weather</a> provides an
1795) email notification service to any users who want to monitor the status
1796) of a Tor node.  Its favorite feature is to notify relay operators when
1797) their relay has earned them a Tor t-shirt.  Tor Weather is written in
1798) Python/Django.
1799)     </p>
1800) 
1801)     <p>
1802) The Tor Weather codebase is pretty much unmaintained these days.  The
1803) first part of this project would be to simplify the code by fetching Tor
1804) network status data from <a
1805) href="https://onionoo.torproject.org/">Onionoo</a> rather than running a
1806) local tor client and keeping an own relay history database.  See the
1807) related <a
1808) href="https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014">community
1809) effort to rewrite Weather</a> that started in January 2014.  After that,
1810) there's a <a
1811) href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Tor+Weather">long
1812) list of open tickets</a> to be resolved.
1813)     </p>
1814) 
1815)     <p>
1816) Ideally, the student would become the new Weather maintainer after the
1817) summer.  If that doesn't work out, the codebase should have become a lot
1818) smaller by end of summer, so that it becomes easier to find somebody
1819) else as new maintainer.
1820)     </p>
1821)     </li>
1822) 
1823)     <a id="improveStegotorus"></a>
1824)     <li>
1825)     <b>Improve Stegotorus</b>
1826)     <br>
1827)     Effort Level: <i>Medium</i>
1828)     <br>
1829)     Skill Level: <i>Medium</i>
1830)     <br>
1831)     Likely Mentors: <i>vmon</i>
1832)     <p>
1833) Stegotorus is a fork of obfsproxy which helps developers to write more intelligent pluggable transports which can hide easier from deep packet inspector (DPI) system.
1834)     </p>
1835) 
1836)     <p>
1837) For example, Stegotorus is equipped with a "chopper module" which takes care of following aspects:
1838)     </p>
1839) 
1840)     <ol>
1841)       <li>It randomize the packet size so it is harder for the DPI system to detect the traffic base on the distribution of the packet size.</li>
1842)       <li>It makes sure that it only handle as much (or as less) information as the transport module can handle.</li>
1843)       <li>Chopper is equipped with it is own acknowledge/retransmit protocol. If the censor trying to disturb the connection by dropping or disturbing some of packets, it can recover the data by sending them many times.</li>
1844)     </ol>
1845) 
1846)     <p>
1847) More importantly, Stegotorus is coming with its own HTTP transport module which obfuscates Tor or any other encrypted traffic in HTTP content such as Javascript code or images. HTTP transport module is also written in a way which new module developers can easily add new obfuscation modules for new contents or improve current obfuscation algorithms without the need of dealing with networking aspect of the problem.
1848)     </p>
1849) 
1850)     <p>
1851) Stegotorus is written in C++. you can find the latest code <a href="https://github.com/zackw/stegotorus/tree/tor-improve">here</a>.
1852)     </p>
1853) 
1854)     <p>
1855) In this regard, Stegotorus is offering one of the most complete and sophisticated platforms for writing stealthy pluggable transports.
1856)     </p>
1857) 
1858)     <p>
1859) If you know C++ and interested in Stegotorus and excited about battling censorship, there are many ways that you can contribute to Stegotorus. Here are few important tasks. Your proposal might contain a good number of them:
1860)     </p>
1861) 
1862)     <ol>
1863)       <li>Currently Stegotorus handshake is encrypted using the symmetric secret key of the Stegotorus bridge. However, we would like to implement a totally random handshake and considering that some transports suffer badly from "bandwidth shortage", our best choice currently is to implement <a href="http://elligator.cr.yp.to/">this algorithm</a>.</li>
1864)       <li>Stegotorus defense against active probing is to authenticate the header of the received packet. If the authentication fails Stegotorus turns into a transparent proxy. The capability of Stegotorus as a transparent proxy needs improvement and further testing.</li>
1865)       <li>Stegotorus has a new framework for writing Steg module. However some of the Steg modules (PDF, SWF and JS) are written in the old framework, we need to refactor their code in the new framework.</li>
1866)       <li>As writting new Steg modules in python is easier and safer, it is desirable to write an Steg module interface for Stegotorus which can accept and interact with Steg modules written in python/cython.</li>
1867)       <li>To make detection of anomalies in the traffic harder, Stegotorus hands a noise-to-signal ratio to each Steg modules. Steg modules' algorithms need to use more intelligent way of embedding to use this ratio.</li>
1868)       <li>Stegotorus has several parameters to tweak its behavior. Currently all these parameters are given in command line. We would like to have a config file to store these parameters as an alternative method.</li>
1869)       <li>The general security of the code needs to be reviewed and audited for buffer overflow, memory leak etc.</li>
1870)       <li>Steg modules for new file format for the HTTP transport are always welcome to reflect the actual traffic of the Internet.</li>
1871)       <li>Packaging Stegotorus for windows.</li>
1872)       <li>There is a parallel efforts to improve Stegotorus at SRI. We would like to merge the useful feature developed by SRI in our branch of Stegotorus.</li>
1873)       <li>Stegotorus needs to support SOCKS protocol to be able to receive the initial parameters from Tor through SOCKS handshake.</li>
1874)     </ol>
1875) 
1876)     <p>
1877) You can find a list of open issues concerning Stegotorus <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Stegotorus&order=priority">here</a>.
1878)     </p>
1879) 
1880)     <p>
1881) You also can think of lots of other awesome creative ways of improving Stegotorus and include those in your proposal.
1882)     </p>
1883)     </li>
1884) 

1885) <!--
1886)     <a id=""></a>
1887)     <li>
1888)     <b></b>
1889)     <br>
1890)     Effort Level: <i>Medium</i>
1891)     <br>
1892)     Skill Level: <i>Medium</i>
1893)     <br>
1894)     Likely Mentors: <i>Damian (atagar)</i>
1895)     <p>
1896) 
1897)     </p>
1898) 
1899)     <p>
1900) 
1901)     </p>
1902)     </li>
1903) -->
1904) 

1905)     <li>
1906)     <b>Bring up new ideas!</b>

1907)     <br>

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

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

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

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

1913)     might also be short on developers.
1914)     </li>

1915) 

1916)     </ol>

1917) 

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

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

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

1933) 

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

1939) 

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

1949) 

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

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

1954)     Tor if needed.</li>

1955) 

1956)     <li>Write a <a
1957)     href="https://secure.wikimedia.org/wikipedia/en/wiki/Fuzz_testing">fuzzer</a>
1958)     for Tor to discover security vulnerabilities. Determine if there
1959)     are good fuzzing frameworks out there for what we want. Win fame by

1960)     getting credit when we put out a new release because of you!</li>

1961) 

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

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

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

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

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

1972) 

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

1976) 

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

1983) 

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

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

1987)     System</a>.
1988)     </li>

1989) 

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

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

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

2002) 

2003)     </ol>

2004) 

2005)     <a id="Research"></a>
2006)     <h2><a class="anchor" href="#Research">Research</a></h2>
2007)     <ol>
2008)     <li>The "end-to-end traffic confirmation attack":
2009)     by watching traffic at Alice and at Bob, we can <a
2010)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
2011)     traffic signatures and become convinced that we're watching the same
2012)     stream</a>. So far Tor accepts this as a fact of life and assumes this
2013)     attack is trivial in all cases. First of all, is that actually true? How
2014)     much traffic of what sort of distribution is needed before the adversary
2015)     is confident he has won? Are there scenarios (e.g. not transmitting much)
2016)     that slow down the attack? Do some traffic padding or traffic shaping
2017)     schemes work better than others?</li>
2018)     <li>A related question is: Does running a relay/bridge provide additional
2019)     protection against these timing attacks? Can an external adversary that can't
2020)     see inside TLS links still recognize individual streams reliably?
2021)     Does the amount of traffic carried degrade this ability any? What if the
2022)     client-relay deliberately delayed upstream relayed traffic to create a queue
2023)     that could be used to mimic timings of client downstream traffic to make it
2024)     look like it was also relayed? This same queue could also be used for masking
2025)     timings in client upstream traffic with the techniques from <a
2026)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
2027)     but without the need for additional traffic. Would such an interleaving of
2028)     client upstream traffic obscure timings for external adversaries? Would the
2029)     strategies need to be adjusted for asymmetric links? For example, on
2030)     asymmetric links, is it actually possible to differentiate client traffic from
2031)     natural bursts due to their asymmetric capacity? Or is it easier than
2032)     symmetric links for some other reason?</li>
2033)     <li>Repeat Murdoch and Danezis's <a
2034)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
2035)     Oakland 05</a> on the current Tor network. See if you can learn why it
2036)     works well on some nodes and not well on others. (My theory is that the
2037)     fast nodes with spare capacity resist the attack better.) If that's true,
2038)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
2039)     options to run a relay that is used as a client while relaying the
2040)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
2041)     attack get harder? What's the right ratio of RelayBandwidthRate to
2042)     actually capacity? Or is it a ratio at all? While we're at it, does a
2043)     much larger set of candidate relays increase the false positive rate
2044)     or other complexity for the attack? (The Tor network is now almost two
2045)     orders of magnitude larger than it was when they wrote their paper.) Be
2046)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
2047)     Clog the Queue</a> too.</li>
2048)     <li>The "routing zones attack": most of the literature thinks of
2049)     the network path between Alice and her entry node (and between the
2050)     exit node and Bob) as a single link on some graph. In practice,
2051)     though, the path traverses many autonomous systems (ASes), and <a
2052)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
2053)     that the same AS appears on both the entry path and the exit path</a>.
2054)     Unfortunately, to accurately predict whether a given Alice, entry,
2055)     exit, Bob quad will be dangerous, we need to download an entire Internet
2056)     routing zone and perform expensive operations on it. Are there practical
2057)     approximations, such as avoiding IP addresses in the same /8 network?</li>
2058)     <li>Other research questions regarding geographic diversity consider
2059)     the tradeoff between choosing an efficient circuit and choosing a random
2060)     circuit. Look at Stephen Rollyson's <a
2061)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
2062)     paper</a> on how to discard particularly slow choices without hurting
2063)     anonymity "too much". This line of reasoning needs more work and more
2064)     thinking, but it looks very promising.</li>
2065)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
2066)     (e.g. cable or DSL). Because Tor has separate TCP connections between
2067)     each hop, if the incoming bytes are arriving just fine and the outgoing
2068)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
2069)     don't really transmit this information back to the incoming streams.
2070)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
2071)     and rate-limit incoming streams to regulate this itself? I can imagine
2072)     a build-up and drop-off scheme where we pick a conservative rate-limit,
2073)     slowly increase it until we get lost packets, back off, repeat. We
2074)     need somebody who's good with networks to simulate this and help design
2075)     solutions; and/or we need to understand the extent of the performance
2076)     degradation, and use this as motivation to reconsider UDP transport.</li>
2077)     <li>A related topic is congestion control. Is our
2078)     current design sufficient once we have heavy use? Maybe
2079)     we should experiment with variable-sized windows rather
2080)     than fixed-size windows? That seemed to go well in an <a

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

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

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

2107)     your browser's UserAgent string by replacing it with a uniform answer for
2108)     every Tor user. That way the attacker can't splinter Tor's anonymity set
2109)     by looking at that header. It tries to pick a string that is commonly used
2110)     by non-Tor users too, so it doesn't stand out. Question one: how badly
2111)     do we hurt ourselves by periodically updating the version of Firefox
2112)     that Torbutton claims to be? If we update it too often, we splinter the
2113)     anonymity sets ourselves. If we don't update it often enough, then all the
2114)     Tor users stand out because they claim to be running a quite old version
2115)     of Firefox. The answer here probably depends on the Firefox versions seen
2116)     in the wild. Question two: periodically people ask us to cycle through N
2117)     UserAgent strings rather than stick with one. Does this approach help,
2118)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
2119)     by their rotating UserAgents; malicious websites who only attack certain
2120)     browsers; and whether the answers to question one impact this answer.
2121)     </li>
2122)     <li>How many bridge relays do you need to know to maintain
2123)     reachability? We should measure the churn in our bridges. If there is
2124)     lots of churn, are there ways to keep bridge users more likely to stay
2125)     connected?
2126)     </li>
2127)     </ol>

2128) 

2129)     <p>
2130)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
2131)     of these!
2132)     </p>
2133)   </div>
2134)   <!-- END MAINCOL -->
2135)   <div id = "sidecol">
2136) #include "side.wmi"
2137) #include "info.wmi"
2138)   </div>
2139)   <!-- END SIDECOL -->
2140) </div>
2141) <!-- END CONTENT -->