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="#chutneyExpansion">Make Chutney Do More, More Reliably</a></i>

429)     </p>

430) 

431)     <a id="project-orchid"></a>
432)     <h3><a href="https://github.com/subgraph/Orchid">Orchid</a> (<a
433)     href="https://github.com/subgraph/Orchid">code</a>, <a
434)     href="https://github.com/subgraph/Orchid/issues">bug

435)     tracker</a>)</h3>

436) 

437)     <p>

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

439)     </p>

440) 

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

442)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
443)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
444)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+bundles/installation&order=priority">bug

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

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

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

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

452)     </p>

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

458)     tracker</a>)</h3>

459) 

460)     <p>

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

466)     </p>

467) 
468)     <a id="project-httpseverywhere"></a>
469)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
470)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
471)     href="https://trac.torproject.org/projects/tor/report/19">bug

472)     tracker</a>)</h3>

473) 

474)     <p>

475)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
476)     your communications with many major websites, making your browsing
477)     more secure.

478)     </p>

479) 

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

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

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

485) 

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

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

491)     </p>

492) 

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

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

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

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

498) 

499)     <p>

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

505)     </p>

506) 

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

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

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

512) 
513)     <p>

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

517)     </p>
518) 
519)     <a id="project-tails"></a>
520)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

523)     tracker</a>)</h3>
524) 
525)     <p>
526)     The Amnesic Incognito Live System is a live CD/USB distribution
527)     preconfigured so that everything is safely routed through Tor and leaves no
528)     trace on the local system. This is a merger of the Amnesia and <a
529)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
530)     and still under very active development.
531)     </p>
532) 

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

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

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

537) 
538)     <p>

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

541)     </p>
542) 

543)     <a id="project-torouter"></a>
544)     <h3><a
545)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

547)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
548)     tracker</a>)</h3>
549) 
550)     <p>
551)     Project to provide an easy-to-use, embedded Tor instance for routers. This
552)     had high activity in late 2010, but has since been rather quiet.
553)     </p>
554) 
555)     <a id="project-torsocks"></a>

556)     <h3>Torsocks (<a

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

561)     <p>

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

565)     </p>

566) 

567)     <a id="project-torbirdy"></a>
568)     <h3>TorBirdy (<a
569)     href="https://github.com/ioerror/torbirdy">code</a>, <a
570)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
571)     tracker</a>)</h3>

572) 

573)     <p>
574)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
575)     </p>

576) 

577)     <p>
578)     <b>Project Ideas:</b><br />
579)     <i><a href="#makeTorbirdyBetter">Make TorBirdy Better</a></i>
580)     </p>
581) 

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

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

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

586)     tracker</a>)</h3>

587) 

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

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

591)     </p>

592) 

593)     <p>
594)     <b>Project Ideas:</b><br />
595)     <i><a href="#betterPluggableTransports">Build Better Pluggable Transports</a></i>
596)     </p>
597) 

598)     <a id="project-flash-proxy"></a>
599)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
600)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
601)     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
602)     tracker</a>)</h3>

603) 

604)     <p>
605)     Pluggable transport using proxies running in web browsers to defeat
606)     address-based blocking.
607)     </p>

608) 

609)     <a id="project-shadow"></a>
610)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
611)     href="https://github.com/shadow">code</a>, <a
612)     href="https://github.com/shadow/shadow/issues">bug
613)     tracker</a>)</h3>

614) 

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

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

621)     </p>

622) 

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

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

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

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

627)     tracker</a>)</h3>

628) 

629)     <p>

630)     Python controller library for scripts and controller applications using
631)     Tor.

632)     </p>

633) 

634)     <p>
635)     <b>Project Ideas:</b><br />

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

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

638)     </p>

639) 

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

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

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

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

644) 

645)     <p>
646)     Twisted-based asynchronous Tor control protocol implementation. Includes
647)     unit-tests, examples, state-tracking code and configuration abstraction.
648)     Used by OONI and APAF.
649)     </p>

650) 

651)     <p>
652)     <b>Project Ideas:</b><br />
653)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
654)     </p>
655) 

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

658) 

659)     <p>
660)     tlsdate: secure parasitic rdate replacement
661)     </p>

662) 

663)     <p>
664)     tlsdate sets the local clock by securely connecting with TLS to remote
665)     servers and extracting the remote time out of the secure handshake. Unlike
666)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
667)     enabled service, and provides some protection against adversaries that try
668)     to feed you malicious time information.
669)     </p>

670) 

671)     <a id="project-metrics"></a>
672)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
673)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
674)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a

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

676) 

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

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

682)     </p>

683) 

684)     <a id="project-atlas"></a>
685)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
686)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

687) 

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

691)     their past usage.

692)     </p>

693) 

694)     <p>

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

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

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

700)     </p>

701) 

702)     <a id="project-globe"></a>
703)     <h3><a href="http://globe.rndm.de/">Globe</a> (<a
704)     href="https://github.com/makepanic/globe">code</a>, <a
705)     href="https://github.com/makepanic/globe/issues">bug tracker</a>)</h3>
706) 
707)     <p>
708)     Globe is a web application that allows you to search for Tor relays and
709)     bridges. It gives you a detailed overview of properties and configurations
710)     of a relay or bridge.
711)     </p>
712) 

713)     <a id="project-compass"></a>
714)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
715)     href="https://gitweb.torproject.org/compass.git">code</a>, <a
716)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Compass&order=priority">bug
717)     tracker</a>)</h3>

718) 

719)     <p>
720)     Compass is a web and command line application that filters and
721)     aggregates the Tor relays based on various attributes.
722)     </p>

723) 
724)     <a id="project-onionoo"></a>
725)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a
726)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
727)     href="https://gitweb.torproject.org/pyonionoo.git">python

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

729) 
730)     <p>
731)     Onionoo is a JSON based protocol to learn information about currently
732)     running Tor relays and bridges.
733)     </p>
734) 

735)     <a id="project-doctor"></a>
736)     <h3>DocTor (<a
737)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a
738)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=DocTor&order=priority">bug
739)     tracker</a>)</h3>
740) 
741)     <p>
742)     DocTor is a notification service that monitors newly published descriptor
743)     information for issues. This is primarily a service to help the tor
744)     directory authority operators, but it also checks for a handful of other
745)     issues like sybil attacks.
746)     </p>
747) 

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

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

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

753) 

754)     <p>
755)     Provides automatic notification to subscribed relay operators when their
756)     relay's unreachable. This underwent a rewrite by the <a
757)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
758)     in early 2011.
759)     </p>

760) 

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

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

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

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

766) 

767)     <p>
768)     E-mail autoresponder providing Tor's packages over SMTP. This has been
769)     relatively unchanged for quite a while.
770)     </p>

771) 

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

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

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

775)     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
776)     tracker</a>)</h3>

777) 

778)     <p>

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

780)     </p>

781) 

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

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

784)     href="https://gitweb.torproject.org/bridgedb.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=BridgeDB&order=priority">bug
786)     tracker</a>)</h3>

787) 

788)     <p>
789)     Backend bridge distributor, handling the various pools they're distributed
790)     in. This was actively developed until Fall of 2010.
791)     </p>

792) 
793)     <a id="project-ooni-probe"></a>

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

795)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
796)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
797)     tracker</a>)</h3>
798) 
799)     <p>
800)     Censorship scanner, checking your local connection for blocked or modified
801)     content.
802)     </p>
803) 

804)     <p>
805)     <b>Project Ideas:</b><br />

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

808)     </p>
809) 

810)     <a id="project-torps"></a>
811)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
812) 
813)     <p>
814)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
815)     path selection in Tor. It chooses circuits and assigns user streams to
816)     those circuits in the same way that Tor does. TorPS is fast enough to
817)     perform thousands of simulations over periods of months.
818)     </p>
819) 

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

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

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

825) 

826)     <p>
827)     Library and collection of services for actively monitoring the Tor network.
828)     These include the Bandwidth Scanners (measuring throughput of relays) and
829)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
830)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
831)     months later. Both have been under active use since then, but development
832)     has stopped.
833)     </p>

834) 

835)     <a id="project-torbel"></a>
836)     <h3><a

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

839)     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
840)     tracker</a>)</h3>

841) 

842)     <p>
843)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
844)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
845)     (though unmaintained) Haskell application for this purpose. The initial
846)     version of TorBEL was started in GSOC 2010 but since then the project has
847)     been inactive.
848)     </p>

849) 
850)     <a id="project-tor2web"></a>
851)     <h3><a
852)     href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a
853)     href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3>
854) 
855)     <p>
856)     Tor2web allows Internet users to browse websites running in <a
857)     href="<page docs/hidden-services>">Tor hidden services</a>. It trades
858)     user anonymity for usability by allowing anonymous content to be
859)     distributed to non-anonymous users.
860)     </p>
861) 

862)     <a id="project-anonbib"></a>
863)     <h3><a
864)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
865)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
866) 
867)     <p>

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

871)     </p>
872) 

873)     <a id="Coding"></a>
874)     <a id="Summer"></a>

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

876) 

877)     <p>

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

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

888)     </p>

889) 

890)     <ol>

891) 

892)     <a id="txtorcon-stemIntegration"></a>
893)     <li>
894)     <b>Txtorcon/Stem Integration</b>
895)     <br>
896)     Effort Level: <i>Medium</i>
897)     <br>
898)     Skill Level: <i>Medium</i>
899)     <br>
900)     Likely Mentors: <i>meejah, Damian (atagar)</i>
901)     <p>Txtorcon is a Twisted-based Python controller library, and Stem is a
902)     synchronous (threaded) one, also in Python. There is no need to have
903)     two implementations of (at least) the protocol parsing code. This
904)     project would entail eliminating duplication by leveraging Stem's
905)     parsing in txtorcon while keeping txtorcon's API the same (or at least
906)     close).</p>

907)     <p>Besides this you should identify some additional tasks to improve our
908)     controller space across these two libraries. Some ideas are...</p>
909)     <ul>
910)       <li>Write a tutorial for <a
911)       href="https://stem.torproject.org/tutorials.html">stem's tutorial
912)       page</a> demonstrating cross txtorcon/stem usage.</li>
913)       <li>Expand the txtorcon API to include functionality of <a
914)       href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's
915)       controller</a> that would be of interest to twisted users. All additions
916)       should include tests!</li>
917)       <li>Come up with some ideas of your own! We'd love to discuss them with
918)       you.</li>
919)     </ul>

920)     <p>This would very likely involve changes to both libraries, although
921)     most would be expected to be in txtorcon. meejah is available to
922)     mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>
923)     <p>It would help if you're already familiar with event-based programming,
924)     bonus points if it's Twisted.</p>
925)     </li>
926) 

927)     <a id="relayWebPanel"></a>
928)     <li>

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

930)     <br>
931)     Effort Level: <i>Medium</i>
932)     <br>
933)     Skill Level: <i>Medium</i>
934)     <br>
935)     Likely Mentors: <i>Damian (atagar)</i>
936)     <p>
937)     Relay operators presently have a couple options for monitoring the status
938)     of their relay: <a
939)     href="https://www.torproject.org/getinvolved/volunteer.html.en#project-vidalia">Vidalia</a>
940)     which is a gui and <a href="https://www.atagar.com/arm/">arm</a> which uses
941)     curses. This project would be to make a new kind of monitor specifically
942)     for relay operators that provides a status dashboard site on localhost.
943)     </p>
944)     <p>
945)     The interface will likely <a
946)     href="https://www.atagar.com/arm/screenshots.php">borrow heavily from
947)     arm</a>, except of course in areas where we can improve upon it. Two
948)     important design constraints is that a localhost controller provides a
949)     bigger attack surface than guis or curses, so we should be a little more
950)     wary of what it does. This should be a read-only controller (ie, you can't
951)     *do* anything to the relay) and by default not surface any sensitive
952)     information (such as arm's connection panel).
953)     </p>
954)     <p>
955)     This project will likely include two parts: an AJAX site and a localhost
956)     daemon to fulfill those requests. <a
957)     href="https://stem.torproject.org/">Stem</a> is the backend of arm, and can
958)     be used to get everything you see in arm's interface (making it a natural
959)     choice for the daemon). That said, this project might entail some Stem
960)     improvements if we run across any gaps.
961)     </p>
962)     <p>

963)     This project has the potential for numerous users, one of which is an
964)     interface for <a
965)     href="https://www.torproject.org/getinvolved/volunteer.html.en#project-torouter">Torouter</a>.
966)     We should check if Torouter has any special use cases or constraints we
967)     should take into consideration.
968)     </p>
969)     <p>

970)     Applicants should be familiar with Python, JavaScript, and learn about
971)     <a href="https://stem.torproject.org/">Stem</a>. <b>As part of your
972)     application for this project please make both mockups of the interface and
973)     a proof of concept demo application using JS to surface something with
974)     Stem. <a
975)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">Involvement
976)     with Stem development</a> during the application process is also a big
977)     plus.</b>
978)     </p>
979)     </li>
980) 

981)     <a id="chutneyExpansion"></a>
982)     <li>
983)     <b>Make Chutney Do More, More Reliably</b>
984)     <br>
985)     Effort Level: <i>Medium to High, depending on scope of project</i>
986)     <br>
987)     Skill Level: <i>Medium</i>
988)     <br>

989)     Likely Mentors: <i>Nick (nickm)</i>
990)     <p>

991)     We have a little Python tool called <a
992)     href="https://gitweb.torproject.org/nickm/chutney.git">Chutney</a> for
993)     making small local test networks.  It's small, not widely used, and not as
994)     automated as it could be.

995)     </p>

996) 

997)     <p>

998)     It would be great to see chutney extended and a set of supporting tests
999)     built to the point where we could use Chutney to exercise various Tor
1000)     features as an automated integration test.

1001)     </p>

1002) 
1003)     <p>
1004)     <b>As part of your application for this project please submit a patch that
1005)     expands Chutney.</b>
1006)     </p>
1007) 

1008)     </li>

1009) 

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

1011)     <li>

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

1013)     <br>

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

1015)     <br>

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

1017)     <br>

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

1019)     <p>

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

1028)     </p>

1029) 

1030)     <p>

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

1036)     </p>

1037) 

1038)     <p>

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

1043)     </p>

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

1051)     </li>

1052) 

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

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

1062)     <p>

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

1068)     </p>
1069) 
1070)     <p>

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

1121)     </p>
1122) 

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

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

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

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

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

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

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

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

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

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

1280)     </p>
1281)     </li>
1282) 

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

1309)     <li>
1310)     <b>Bring up new ideas!</b>

1311)     <br>

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

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

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

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

1317)     might also be short on developers.
1318)     </li>

1319) 

1320)     </ol>

1321) 

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

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

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

1337) 

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

1343) 

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

1353) 

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

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

1358)     Tor if needed.</li>

1359) 

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

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

1365) 

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

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

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

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

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

1376) 

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

1380) 

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

1387) 

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

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

1391)     System</a>.
1392)     </li>

1393) 

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

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

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

1406) 

1407)     </ol>

1408) 

1409)     <a id="Research"></a>
1410)     <h2><a class="anchor" href="#Research">Research</a></h2>
1411)     <ol>
1412)     <li>The "end-to-end traffic confirmation attack":
1413)     by watching traffic at Alice and at Bob, we can <a
1414)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1415)     traffic signatures and become convinced that we're watching the same
1416)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1417)     attack is trivial in all cases. First of all, is that actually true? How
1418)     much traffic of what sort of distribution is needed before the adversary
1419)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1420)     that slow down the attack? Do some traffic padding or traffic shaping
1421)     schemes work better than others?</li>
1422)     <li>A related question is: Does running a relay/bridge provide additional
1423)     protection against these timing attacks? Can an external adversary that can't
1424)     see inside TLS links still recognize individual streams reliably?
1425)     Does the amount of traffic carried degrade this ability any? What if the
1426)     client-relay deliberately delayed upstream relayed traffic to create a queue
1427)     that could be used to mimic timings of client downstream traffic to make it
1428)     look like it was also relayed? This same queue could also be used for masking
1429)     timings in client upstream traffic with the techniques from <a
1430)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1431)     but without the need for additional traffic. Would such an interleaving of
1432)     client upstream traffic obscure timings for external adversaries? Would the
1433)     strategies need to be adjusted for asymmetric links? For example, on
1434)     asymmetric links, is it actually possible to differentiate client traffic from
1435)     natural bursts due to their asymmetric capacity? Or is it easier than
1436)     symmetric links for some other reason?</li>
1437)     <li>Repeat Murdoch and Danezis's <a
1438)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1439)     Oakland 05</a> on the current Tor network. See if you can learn why it
1440)     works well on some nodes and not well on others. (My theory is that the
1441)     fast nodes with spare capacity resist the attack better.) If that's true,
1442)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1443)     options to run a relay that is used as a client while relaying the
1444)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1445)     attack get harder? What's the right ratio of RelayBandwidthRate to
1446)     actually capacity? Or is it a ratio at all? While we're at it, does a
1447)     much larger set of candidate relays increase the false positive rate
1448)     or other complexity for the attack? (The Tor network is now almost two
1449)     orders of magnitude larger than it was when they wrote their paper.) Be
1450)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1451)     Clog the Queue</a> too.</li>
1452)     <li>The "routing zones attack": most of the literature thinks of
1453)     the network path between Alice and her entry node (and between the
1454)     exit node and Bob) as a single link on some graph. In practice,
1455)     though, the path traverses many autonomous systems (ASes), and <a
1456)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1457)     that the same AS appears on both the entry path and the exit path</a>.
1458)     Unfortunately, to accurately predict whether a given Alice, entry,
1459)     exit, Bob quad will be dangerous, we need to download an entire Internet
1460)     routing zone and perform expensive operations on it. Are there practical
1461)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1462)     <li>Other research questions regarding geographic diversity consider
1463)     the tradeoff between choosing an efficient circuit and choosing a random
1464)     circuit. Look at Stephen Rollyson's <a
1465)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1466)     paper</a> on how to discard particularly slow choices without hurting
1467)     anonymity "too much". This line of reasoning needs more work and more
1468)     thinking, but it looks very promising.</li>
1469)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1470)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1471)     each hop, if the incoming bytes are arriving just fine and the outgoing
1472)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1473)     don't really transmit this information back to the incoming streams.
1474)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1475)     and rate-limit incoming streams to regulate this itself? I can imagine
1476)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1477)     slowly increase it until we get lost packets, back off, repeat. We
1478)     need somebody who's good with networks to simulate this and help design
1479)     solutions; and/or we need to understand the extent of the performance
1480)     degradation, and use this as motivation to reconsider UDP transport.</li>
1481)     <li>A related topic is congestion control. Is our
1482)     current design sufficient once we have heavy use? Maybe
1483)     we should experiment with variable-sized windows rather
1484)     than fixed-size windows? That seemed to go well in an <a

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

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

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

1511)     your browser's UserAgent string by replacing it with a uniform answer for
1512)     every Tor user. That way the attacker can't splinter Tor's anonymity set
1513)     by looking at that header. It tries to pick a string that is commonly used
1514)     by non-Tor users too, so it doesn't stand out. Question one: how badly
1515)     do we hurt ourselves by periodically updating the version of Firefox
1516)     that Torbutton claims to be? If we update it too often, we splinter the
1517)     anonymity sets ourselves. If we don't update it often enough, then all the
1518)     Tor users stand out because they claim to be running a quite old version
1519)     of Firefox. The answer here probably depends on the Firefox versions seen
1520)     in the wild. Question two: periodically people ask us to cycle through N
1521)     UserAgent strings rather than stick with one. Does this approach help,
1522)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
1523)     by their rotating UserAgents; malicious websites who only attack certain
1524)     browsers; and whether the answers to question one impact this answer.
1525)     </li>
1526)     <li>How many bridge relays do you need to know to maintain
1527)     reachability? We should measure the churn in our bridges. If there is
1528)     lots of churn, are there ways to keep bridge users more likely to stay
1529)     connected?
1530)     </li>
1531)     </ol>

1532) 

1533)     <p>
1534)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1535)     of these!
1536)     </p>
1537)   </div>
1538)   <!-- END MAINCOL -->
1539)   <div id = "sidecol">
1540) #include "side.wmi"
1541) #include "info.wmi"
1542)   </div>
1543)   <!-- END SIDECOL -->
1544) </div>
1545) <!-- END CONTENT -->