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>Monitor some of our <a 
56)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo">public mailing 
57)     lists</a>, like <a 
58)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">tor-talk</a>, <a 
59)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">tor-relays</a>, <a 
60)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev">tor-dev</a>, or <a 
61)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev">tbb-dev</a>, 
62)     and summarize noteworthy exchanges into articles for <a 
63)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo">Tor 
64)     Weekly News</a>.</li>

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

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

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

70)     <a

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

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

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

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

78)     </ol>

79) 

80) <!--

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

103) -->

104) 

105)     <a id="Projects"></a>
106)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

107) 

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

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

115)     </p>

116) 

117)     <p>
118)     For a presentation summarizing many of these projects see...
119)     </p>
120) 
121)     <div id="ecosystem_presentation">
122)       <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>)
123)     </div>
124) 
125)     <br /></br />
126) 

127)     <table id="projects">
128)       <tr>
129)         <th>Name</th>
130)         <th>Category</th>
131)         <th>Language</th>
132)         <th>Activity</th>
133)         <th>Contributors</th>
134)       </tr>

135) 

136)       <tr>
137)         <td><a href="#project-tor">Tor</a></td>
138)         <td>Core</td>
139)         <td>C</td>
140)         <td>Heavy</td>

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

142)       </tr>

143) 

144)       <tr>

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

146)         <td>Core</td>
147)         <td>Java</td>

148)         <td>Moderate</td>

149)         <td>bleidl</td>
150)       </tr>
151) 
152)       <tr>

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

154)         <td>Bundle</td>

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

156)         <td>Moderate</td>

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

158)       </tr>

159) 

160)       <tr>

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

166)       </tr>

167) 

168)       <tr>

169)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
170)         <td>Browser Add-on</td>
171)         <td>Javascript</td>

172)         <td>Heavy</td>

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

174)       </tr>

175) 

176)       <tr>

177)         <td><a href="#project-vidalia">Vidalia</a></td>
178)         <td>User Interface</td>
179)         <td>C++, Qt</td>

180)         <td>None</td>

181)         <td>chiiph</td>
182)       </tr>

183) 

184)       <tr>

185)         <td><a href="#project-arm">Arm</a></td>
186)         <td>User Interface</td>
187)         <td>Python, Curses</td>

188)         <td>Light</td>

189)         <td>atagar</td>
190)       </tr>

191) 

192)       <tr>

193)         <td><a href="#project-orbot">Orbot</a></td>
194)         <td>User Interface</td>
195)         <td>Java</td>

196)         <td>Light</td>

197)         <td>n8fr8</td>

198)       </tr>

199) 

200)       <tr>

201)         <td><a href="#project-tails">Tails</a></td>
202)         <td>OS image</td>
203)         <td>Sys Admin</td>
204)         <td>Heavy</td>
205)         <td><a href="https://tails.boum.org/">#tails</a></td>

206)       </tr>

207) 

208)       <tr>

209)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
210)         <td>OS image</td>
211)         <td>Sys Admin</td>

212)         <td>None</td>

213)         <td>blueness</td>
214)       </tr>
215) 

216)       <tr>

217)         <td>*<a href="#project-torouter">Torouter</a></td>
218)         <td>OS image</td>
219)         <td>Sys Admin</td>

220)         <td>None</td>

221)         <td>ioerror</td>
222)       </tr>
223) 

224)       <tr>

225)         <td><a href="#project-torsocks">Torsocks</a></td>
226)         <td>Usability</td>
227)         <td>C</td>

228)         <td>Light</td>

229)         <td>ioerror, nickm</td>
230)       </tr>
231) 

232)       <tr>

233)         <td><a href="#project-torbirdy">TorBirdy</a></td>
234)         <td>Browser Add-on</td>
235)         <td>JavaScript</td>
236)         <td>Heavy</td>

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

238)       </tr>

239) 

240)       <tr>

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

243)         <td>Python</td>

244)         <td>Moderate</td>

245)         <td>asn</td>

246)       </tr>
247) 

248)       <tr>

249)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
250)         <td>Client Add-on</td>
251)         <td>Python, JavaScript, Go</td>

252)         <td>Heavy</td>

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

254)       </tr>

255) 

256)       <tr>

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

258)         <td>Simulator</td>

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

260)         <td>Heavy</td>

261)         <td>robgjansen</td>
262)       </tr>

263) 

264)       <tr>

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

266)         <td>Library</td>
267)         <td>Python</td>
268)         <td>Heavy</td>

269)         <td>atagar</td>

270)       </tr>

271) 

272)       <tr>

273)         <td><a href="#project-txtorcon">Txtorcon</a></td>
274)         <td>Library</td>
275)         <td>Python, Twisted</td>

276)         <td>Moderate</td>

277)         <td>meejah</td>
278)       </tr>

279) 

280)       <tr>

281)         <td><a href="#project-tlsdate">Tlsdate</a></td>
282)         <td>Utility</td>
283)         <td>C</td>

284)         <td>Moderate</td>

285)         <td>ioerror</td>
286)       </tr>

287) 

288)       <tr>

289)         <td><a href="#project-metrics">Metrics</a></td>
290)         <td>Client Service</td>
291)         <td>Java</td>

292)         <td>Moderate</td>

293)         <td>karsten</td>
294)       </tr>

295) 

296)       <tr>

297)         <td><a href="#project-atlas">Atlas</a></td>
298)         <td>Client Service</td>
299)         <td>JavaScript</td>

300)         <td>Light</td>

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

302)       </tr>

303) 

304)       <tr>
305)         <td><a href="#project-globe">Globe</a></td>
306)         <td>Client Service</td>
307)         <td>JavaScript</td>
308)         <td>Heavy</td>
309)         <td>Christian</td>
310)       </tr>
311) 

312)       <tr>

313)         <td><a href="#project-compass">Compass</a></td>
314)         <td>Client Service</td>
315)         <td>Python</td>

316)         <td>Light</td>

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

318)       </tr>

319) 

320)       <tr>

321)         <td><a href="#project-onionoo">Onionoo</a></td>
322)         <td>Backend Service</td>
323)         <td>Java, Python</td>

324)         <td>Moderate</td>

325)         <td>karsten, gsathya</td>
326)       </tr>
327) 

328)       <tr>
329)         <td><a href="#project-doctor">DocTor</a></td>
330)         <td>Backend Service</td>
331)         <td>Python</td>
332)         <td>Light</td>
333)         <td>atagar</td>
334)       </tr>
335) 

336)       <tr>

337)         <td><a href="#project-weather">Weather</a></td>
338)         <td>Client Service</td>
339)         <td>Python</td>

340)         <td>None</td>

341)         <td>kaner</td>
342)       </tr>

343) 

344)       <tr>

345)         <td><a href="#project-gettor">GetTor</a></td>
346)         <td>Client Service</td>
347)         <td>Python</td>

348)         <td>None</td>

349)         <td>kaner</td>

350)       </tr>

351) 

352)       <tr>

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

355)         <td>Go</td>
356)         <td>Moderate</td>
357)         <td>Arlo</td>

358)       </tr>

359) 

360)       <tr>

361)         <td><a href="#project-bridgedb">BridgeDB</a></td>
362)         <td>Backend Service</td>
363)         <td>Python</td>

364)         <td>Light</td>

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

366)       </tr>

367) 

368)       <tr>

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

370)         <td>Scanner</td>
371)         <td>Python</td>

372)         <td>Moderate</td>

373)         <td>hellais, isis, ioerror</td>
374)       </tr>
375) 

376)       <tr>
377)         <td><a href="#project-torps">TorPS</a></td>
378)         <td>Backend Service</td>
379)         <td>Python</td>
380)         <td>Light</td>
381)         <td>Aaron Johnson</td>
382)       </tr>
383) 

384)       <tr>

385)         <td><a href="#project-torflow">TorFlow</a></td>
386)         <td>Backend Service</td>
387)         <td>Python</td>

388)         <td>None</td>

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

390)       </tr>

391) 

392)       <tr>

393)         <td>*<a href="#project-torbel">TorBEL</a></td>
394)         <td>Backend Service</td>
395)         <td>Python</td>
396)         <td>None</td>
397)         <td>Sebastian</td>
398)       </tr>

399) 

400)       <tr>

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

403)         <td>Python</td>

404)         <td>Moderate</td>

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

406)       </tr>

407) 

408)       <tr>

409)         <td><a href="#project-anonbib">Anonbib</a></td>
410)         <td>Website</td>

411)         <td>Python</td>

412)         <td>Light</td>
413)         <td>arma, nickm</td>
414)       </tr>
415) 

416)     </table>

417) 

418)     <sub>
419)     * Project is still in an alpha state.
420)     </sub>

421) 

422)     <br /><br />

423) 

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

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

427)     tracker</a>)</h3>

428) 

429)     <p>
430)     Central project, providing the core software for using and participating in
431)     the Tor network. Numerous people contribute to the project to varying
432)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
433)     </p>

434) 

435)     <p>
436)     <b>Project Ideas:</b><br />

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

438)     <i><a href="#improveTorTestCoverage">Improve test coverage in Tor</a></i><br />
439)     <i><a href="#useMoreCores">Have the Tor daemon use more cores</a></i><br />
440)     <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br />
441)     <i><a href="#consensusDiffs">Implement consensus diffs</a></i><br />
442)     <i><a href="#improvedDnsSupport">Improved DNS support for Tor</a></i><br />
443)     <i><a href="#torSandboxing">Help improve Tor sandboxing</a></i>

444)     </p>

445) 

446)     <a id="project-orchid"></a>
447)     <h3><a href="https://github.com/subgraph/Orchid">Orchid</a> (<a
448)     href="https://github.com/subgraph/Orchid">code</a>, <a
449)     href="https://github.com/subgraph/Orchid/issues">bug

450)     tracker</a>)</h3>

451) 

452)     <p>

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

454)     </p>

455) 

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

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

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

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

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

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

467)     </p>

468) 

469)     <p>
470)     <b>Project Ideas:</b><br />
471)     <i><a href="#panopticlick">Panopticlick</a></i><br />
472)     </p>
473) 

474)     <a id="project-torbutton"></a>

475)     <h3><a href="<page docs/torbutton/index>">Torbutton</a> (<a

476)     href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
477)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug

478)     tracker</a>)</h3>

479) 

480)     <p>

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

486)     </p>

487) 
488)     <a id="project-httpseverywhere"></a>
489)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
490)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
491)     href="https://trac.torproject.org/projects/tor/report/19">bug

492)     tracker</a>)</h3>

493) 

494)     <p>

495)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
496)     your communications with many major websites, making your browsing
497)     more secure.

498)     </p>

499) 

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

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

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

505) 

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

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

511)     </p>

512) 

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

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

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

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

518) 

519)     <p>

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

525)     </p>

526) 

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

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

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

532) 
533)     <p>

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

537)     </p>
538) 

539)     <p>
540)     <b>Project Ideas:</b><br />
541)     <i><a href="#orbotVPN">Orbot Android VPN</a></i><br />
542)     <i><a href="#orfox">Orfox - Firefox/Gecko-based Android Browser for Tor</a></i>
543)     </p>
544) 

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

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

549)     tracker</a>)</h3>
550) 
551)     <p>
552)     The Amnesic Incognito Live System is a live CD/USB distribution
553)     preconfigured so that everything is safely routed through Tor and leaves no
554)     trace on the local system. This is a merger of the Amnesia and <a
555)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
556)     and still under very active development.
557)     </p>
558) 

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

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

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

563) 
564)     <p>

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

567)     </p>
568) 

569)     <a id="project-torouter"></a>
570)     <h3><a
571)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

573)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
574)     tracker</a>)</h3>
575) 
576)     <p>
577)     Project to provide an easy-to-use, embedded Tor instance for routers. This
578)     had high activity in late 2010, but has since been rather quiet.
579)     </p>
580) 
581)     <a id="project-torsocks"></a>

582)     <h3>Torsocks (<a

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

587)     <p>

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

591)     </p>

592) 

593)     <a id="project-torbirdy"></a>
594)     <h3>TorBirdy (<a
595)     href="https://github.com/ioerror/torbirdy">code</a>, <a
596)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
597)     tracker</a>)</h3>

598) 

599)     <p>
600)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
601)     </p>

602) 

603)     <p>
604)     <b>Project Ideas:</b><br />
605)     <i><a href="#makeTorbirdyBetter">Make TorBirdy Better</a></i>
606)     </p>
607) 

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

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

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

612)     tracker</a>)</h3>

613) 

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

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

617)     </p>

618) 

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

621)     <i><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Helpneeded">Various coding tasks</a></i> <br/>

622)     <i><a href="#betterPluggableTransports">Build Better Pluggable Transports</a></i>
623)     </p>
624) 

625)     <a id="project-flash-proxy"></a>
626)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
627)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
628)     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
629)     tracker</a>)</h3>

630) 

631)     <p>
632)     Pluggable transport using proxies running in web browsers to defeat
633)     address-based blocking.
634)     </p>

635) 

636)     <a id="project-shadow"></a>
637)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
638)     href="https://github.com/shadow">code</a>, <a
639)     href="https://github.com/shadow/shadow/issues">bug
640)     tracker</a>)</h3>

641) 

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

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

648)     </p>

649) 

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

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

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

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

654)     tracker</a>)</h3>

655) 

656)     <p>

657)     Python controller library for scripts and controller applications using
658)     Tor.

659)     </p>

660) 

661)     <p>
662)     <b>Project Ideas:</b><br />

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

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

665)     </p>

666) 

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

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

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

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

671) 

672)     <p>
673)     Twisted-based asynchronous Tor control protocol implementation. Includes
674)     unit-tests, examples, state-tracking code and configuration abstraction.
675)     Used by OONI and APAF.
676)     </p>

677) 

678)     <p>
679)     <b>Project Ideas:</b><br />
680)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
681)     </p>
682) 

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

685) 

686)     <p>
687)     tlsdate: secure parasitic rdate replacement
688)     </p>

689) 

690)     <p>
691)     tlsdate sets the local clock by securely connecting with TLS to remote
692)     servers and extracting the remote time out of the secure handshake. Unlike
693)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
694)     enabled service, and provides some protection against adversaries that try
695)     to feed you malicious time information.
696)     </p>

697) 

698)     <a id="project-metrics"></a>
699)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
700)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
701)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a

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

703) 

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

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

709)     </p>

710) 

711)     <a id="project-atlas"></a>
712)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
713)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

714) 

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

718)     their past usage.

719)     </p>

720) 

721)     <p>

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

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

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

727)     </p>

728) 

729)     <a id="project-globe"></a>
730)     <h3><a href="http://globe.rndm.de/">Globe</a> (<a
731)     href="https://github.com/makepanic/globe">code</a>, <a
732)     href="https://github.com/makepanic/globe/issues">bug tracker</a>)</h3>
733) 
734)     <p>
735)     Globe is a web application that allows you to search for Tor relays and
736)     bridges. It gives you a detailed overview of properties and configurations
737)     of a relay or bridge.
738)     </p>
739) 

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

745) 

746)     <p>
747)     Compass is a web and command line application that filters and
748)     aggregates the Tor relays based on various attributes.
749)     </p>

750) 
751)     <a id="project-onionoo"></a>
752)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a
753)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
754)     href="https://gitweb.torproject.org/pyonionoo.git">python

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

756) 
757)     <p>
758)     Onionoo is a JSON based protocol to learn information about currently
759)     running Tor relays and bridges.
760)     </p>
761) 

762)     <a id="project-doctor"></a>
763)     <h3>DocTor (<a
764)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a
765)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=DocTor&order=priority">bug
766)     tracker</a>)</h3>
767) 
768)     <p>
769)     DocTor is a notification service that monitors newly published descriptor
770)     information for issues. This is primarily a service to help the tor
771)     directory authority operators, but it also checks for a handful of other
772)     issues like sybil attacks.
773)     </p>
774) 

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

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

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

780) 

781)     <p>
782)     Provides automatic notification to subscribed relay operators when their
783)     relay's unreachable. This underwent a rewrite by the <a
784)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
785)     in early 2011.
786)     </p>

787) 

788)     <p>
789)     <b>Project Ideas:</b><br />
790)     <i><a href="#rewriteWeather">Rewrite Tor Weather</a></i><br />
791)     </p>
792) 

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

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

795)     href="https://gitweb.torproject.org/gettor.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=GetTor&order=priority">bug
797)     tracker</a>)</h3>

798) 

799)     <p>
800)     E-mail autoresponder providing Tor's packages over SMTP. This has been
801)     relatively unchanged for quite a while.
802)     </p>

803) 

804)     <p>
805)     <b>Project Ideas:</b><br />
806)     <i><a href="#revamp_gettor">Revamp GetTor</a></i>
807)     </p>
808) 

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

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

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

812)     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
813)     tracker</a>)</h3>

814) 

815)     <p>

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

817)     </p>

818) 

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

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

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

824) 

825)     <p>
826)     Backend bridge distributor, handling the various pools they're distributed
827)     in. This was actively developed until Fall of 2010.
828)     </p>

829) 

830)     <p>
831)     <b>Project Ideas:</b><br />
832)     <i><a href="#newBridgedbDistributor">New BridgeDB Distributor</a></i>
833)     </p>
834) 

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

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

837)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
838)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
839)     tracker</a>)</h3>
840) 
841)     <p>
842)     Censorship scanner, checking your local connection for blocked or modified
843)     content.
844)     </p>
845) 

846)     <p>
847)     <b>Project Ideas:</b><br />

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

850)     </p>
851) 

852)     <a id="project-torps"></a>
853)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
854) 
855)     <p>
856)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
857)     path selection in Tor. It chooses circuits and assigns user streams to
858)     those circuits in the same way that Tor does. TorPS is fast enough to
859)     perform thousands of simulations over periods of months.
860)     </p>
861) 

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

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

864)     href="https://gitweb.torproject.org/torflow.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=Torflow&order=priority">bug
866)     tracker</a>)</h3>

867) 

868)     <p>
869)     Library and collection of services for actively monitoring the Tor network.
870)     These include the Bandwidth Scanners (measuring throughput of relays) and
871)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
872)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
873)     months later. Both have been under active use since then, but development
874)     has stopped.
875)     </p>

876) 

877)     <a id="project-torbel"></a>
878)     <h3><a

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

881)     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
882)     tracker</a>)</h3>

883) 

884)     <p>
885)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
886)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
887)     (though unmaintained) Haskell application for this purpose. The initial
888)     version of TorBEL was started in GSOC 2010 but since then the project has
889)     been inactive.
890)     </p>

891) 
892)     <a id="project-tor2web"></a>
893)     <h3><a
894)     href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a
895)     href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3>
896) 
897)     <p>
898)     Tor2web allows Internet users to browse websites running in <a
899)     href="<page docs/hidden-services>">Tor hidden services</a>. It trades
900)     user anonymity for usability by allowing anonymous content to be
901)     distributed to non-anonymous users.
902)     </p>
903) 

904)     <a id="project-anonbib"></a>
905)     <h3><a
906)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
907)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
908) 
909)     <p>

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

913)     </p>
914) 

915)     <a id="Coding"></a>
916)     <a id="Summer"></a>

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

918) 

919)     <p>

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

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

930)     </p>

931) 

932)     <ol>

933) 

934)     <a id="txtorcon-stemIntegration"></a>
935)     <li>
936)     <b>Txtorcon/Stem Integration</b>
937)     <br>
938)     Effort Level: <i>Medium</i>
939)     <br>
940)     Skill Level: <i>Medium</i>
941)     <br>
942)     Likely Mentors: <i>meejah, Damian (atagar)</i>
943)     <p>Txtorcon is a Twisted-based Python controller library, and Stem is a
944)     synchronous (threaded) one, also in Python. There is no need to have
945)     two implementations of (at least) the protocol parsing code. This
946)     project would entail eliminating duplication by leveraging Stem's
947)     parsing in txtorcon while keeping txtorcon's API the same (or at least
948)     close).</p>

949)     <p>Besides this you should identify some additional tasks to improve our
950)     controller space across these two libraries. Some ideas are...</p>
951)     <ul>
952)       <li>Write a tutorial for <a
953)       href="https://stem.torproject.org/tutorials.html">stem's tutorial
954)       page</a> demonstrating cross txtorcon/stem usage.</li>
955)       <li>Expand the txtorcon API to include functionality of <a
956)       href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's
957)       controller</a> that would be of interest to twisted users. All additions
958)       should include tests!</li>
959)       <li>Come up with some ideas of your own! We'd love to discuss them with
960)       you.</li>
961)     </ul>

962)     <p>This would very likely involve changes to both libraries, although
963)     most would be expected to be in txtorcon. meejah is available to
964)     mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>
965)     <p>It would help if you're already familiar with event-based programming,
966)     bonus points if it's Twisted.</p>
967)     </li>
968) 

969)     <a id="relayWebPanel"></a>
970)     <li>

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

972)     <br>
973)     Effort Level: <i>Medium</i>
974)     <br>
975)     Skill Level: <i>Medium</i>
976)     <br>
977)     Likely Mentors: <i>Damian (atagar)</i>
978)     <p>
979)     Relay operators presently have a couple options for monitoring the status
980)     of their relay: <a

981)     href="#project-vidalia">Vidalia</a>

982)     which is a gui and <a href="https://www.atagar.com/arm/">arm</a> which uses
983)     curses. This project would be to make a new kind of monitor specifically
984)     for relay operators that provides a status dashboard site on localhost.
985)     </p>
986)     <p>
987)     The interface will likely <a
988)     href="https://www.atagar.com/arm/screenshots.php">borrow heavily from
989)     arm</a>, except of course in areas where we can improve upon it. Two
990)     important design constraints is that a localhost controller provides a
991)     bigger attack surface than guis or curses, so we should be a little more
992)     wary of what it does. This should be a read-only controller (ie, you can't
993)     *do* anything to the relay) and by default not surface any sensitive

994)     information (such as arm's connection panel). Also take a peek at <a
995)     href="http://www.ntop.org/products/ntop/">ntop</a> for ideas on what we can
996)     do with a web interface.

997)     </p>
998)     <p>
999)     This project will likely include two parts: an AJAX site and a localhost
1000)     daemon to fulfill those requests. <a
1001)     href="https://stem.torproject.org/">Stem</a> is the backend of arm, and can
1002)     be used to get everything you see in arm's interface (making it a natural
1003)     choice for the daemon). That said, this project might entail some Stem
1004)     improvements if we run across any gaps.
1005)     </p>
1006)     <p>

1007)     This project has the potential for numerous users, one of which is an
1008)     interface for <a

1009)     href="#project-torouter">Torouter</a>.

1010)     We should check if Torouter has any special use cases or constraints we
1011)     should take into consideration.
1012)     </p>
1013)     <p>

1014)     Applicants should be familiar with Python, JavaScript, and learn about
1015)     <a href="https://stem.torproject.org/">Stem</a>. <b>As part of your
1016)     application for this project please make both mockups of the interface and
1017)     a proof of concept demo application using JS to surface something with
1018)     Stem. <a
1019)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">Involvement
1020)     with Stem development</a> during the application process is also a big
1021)     plus.</b>
1022)     </p>
1023)     </li>
1024) 

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

1026)     <li>

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

1028)     <br>

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

1030)     <br>

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

1032)     <br>

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

1034)     <p>

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

1043)     </p>

1044) 

1045)     <p>

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

1051)     </p>

1052) 

1053)     <p>

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

1058)     </p>

1059) 
1060)     <p>
1061)     <b>As part of your application for this project please identify one of the
1062)     thorniest Tor functions and submit a patch refactoring it to be better. If
1063)     you find this to be difficult then this likely isn't the project for
1064)     you.</b>
1065)     </p>

1066)     </li>

1067) 

1068)     <a id="betterPluggableTransports"></a>
1069)     <li>
1070)     <b>Build Better Pluggable Transports</b>
1071)     <br>
1072)     Effort Level: <i>Medium to High</i>
1073)     <br>
1074)     Skill Level: <i>Medium</i>
1075)     <br>

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

1077)     <p>

1078)     For Tor users in censored countries, we have a <a

1079)     href="<page docs/pluggable-transports>">

1080)     pluggable transports</a> framework that uses external programs to bypass
1081)     censorship in different ways. Each of these have their own strengths and
1082)     weaknesses.

1083)     </p>
1084) 
1085)     <p>

1086)     We have deployed <a

1087)     href="<page projects/obfsproxy>">obfsproxy</a>

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

1136)     </p>
1137) 

1138)     <a id="hsSearchEngine"></a>
1139)     <li>
1140)     <b>Search Engine for Hidden Services</b>
1141)     <br>
1142)     Effort Level: <i>Medium</i>
1143)     <br>
1144)     Skill Level: <i>Medium</i>
1145)     <br>
1146)     Likely Mentors: <i>George (asn)</i>
1147)     <p>
1148)     This project involves researching and developing a search engine for
1149)     Hidden Services.
1150)     </p>
1151) 
1152)     <p>
1153)     The student is expected to develop a search engine that can index
1154)     hidden services and reply to search queries. The student should also
1155)     develop a crawler that can search both "clear web" and hidden service
1156)     websites to find more addresses. The student is expected to use and
1157)     improve already existing search engine frameworks (e.g. YaCy), and not
1158)     reinvent the wheel when it's possible.
1159)     </p>
1160) 
1161)     <p>
1162)     The student should have a decent understanding of how search engines
1163)     work, what algorithms they use, and of any related open source tools
1164)     that are currently available.
1165)     </p>
1166) 

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

1193)     <a id="httpsEverywhereRulesetTesting"></a>
1194)     <li>
1195)     <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>
1196)     <br>
1197)     Effort Level: <i>Medium</i>
1198)     <br>
1199)     Skill Level: <i>Medium</i>
1200)     <br>

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

1202)     <p>
1203) Ondrej Mikle has implemented a codebase for testing HTTPS Everywhere rulesets
1204) by crawling pages that are affected by the ruleset (<a href="https://github.com/hiviah/https-everywhere-checker">repository</a>).
1205)     </p>
1206) 
1207)     <p>
1208) This codebase still has some rough edges that need to be smoothed over, but
1209) once those are done it should be incorporated into the HTTPS Everywhere build
1210) process, in order to improve the quality of our releases.
1211)     </p>
1212)     </li>
1213) 

1214)     <a id="censorshipAnalyzer"></a>
1215)     <li>
1216)     <b>Develop a Censorship Analyzer</b>
1217)     <br>
1218)     Effort Level: <i>Medium</i>
1219)     <br>
1220)     Skill Level: <i>Medium to High (depends on the implemented tests)</i>
1221)     <br>
1222)     Likely Mentors: <i>Philipp (phw)</i>
1223)     <p>
1224) Tor is documented to be blocked in <a
1225) href="https://censorshipwiki.torproject.org">several countries</a>. Analyzing
1226) these censorship incidents can be a tedious task; especially without access to
1227) machines inside the censoring networks. To make analysis easier, it would be
1228) great to have a lightweight analysis tool which can be run by censored users.
1229) This tool would conduct a number of networking tests and figure out if and how
1230) Tor could be blocked. The tool's final report should then somehow make it back
1231) to the Tor project.
1232)     </p>
1233) 
1234)     <p>
1235) The theory behind this tool is already <a

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

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

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

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

1295)     </p>
1296)     </li>
1297) 

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

1324)     <a id="orbotVPN"></a>
1325)     <li>
1326)     <b>Orbot Android VPN</b>
1327)     <br>
1328)     Effort Level: <i>Medium</i>
1329)     <br>
1330)     Skill Level: <i>High</i>
1331)     <br>
1332)     Likely Mentors: <i>Nathan (n8fr8)</i>
1333)     <p>
1334) Android offers the ability for any application to establish a
1335) VPNService through which all traffic on the device is sent. We want to
1336) implement this type of service in order to route all traffic through
1337) the Tor network. This is a feature that will be implemented directly
1338) into Orbot: Tor for Android if successfully implemented.
1339)     </p>
1340) 
1341)     <p>
1342) The deliverables for the project will be a working Android VPN
1343) implementation that routes traffic through Tor, and integration of VPN
1344) code into the Orbot app. There must also be time made for reporting on
1345) the project through blog posts, network auditing of tracking to ensure
1346) leakage is not occurring.
1347)     </p>
1348) 
1349)     <p>
1350) Useful links and documentation to study:
1351)     </p>
1352) 
1353)     <ul>
1354)       <li><a href="https://gitweb.torproject.org/orbot.git">Orbot</a></li>
1355)       <li><a href="http://developer.android.com/reference/android/net/VpnService.html">Android VPNService API</a></li>
1356)       <li><a href="https://github.com/guardianproject/OrbotVPN">Existing work on Orbot VPN</a></li>
1357)     </ul>
1358) 
1359)     <p>
1360) Applicant should have the ability to build Orbot application from
1361) source using Android SDK and NDK tools. A solid understanding of IP
1362) routing, iptables, netfilter and VPN protocols would also be very
1363) helpful. The ability to use Wireshark or other network monitoring
1364) software to test and verify solution is something that can be taught,
1365) but if you already know how, bonus! Finally, understanding how the
1366) exiting Tor software can be used with various transparent proxying
1367) configurations is a good first step to understanding this problem.
1368)     </p>
1369)     </li>
1370) 
1371)     <a id="orfox"></a>
1372)     <li>
1373)     <b>Orfox - Firefox/Gecko-based Android Browser for Tor</b>
1374)     <br>
1375)     Effort Level: <i>High</i>
1376)     <br>
1377)     Skill Level: <i>Medium</i>
1378)     <br>
1379)     Likely Mentors: <i>Nathan (n8fr8)</i>
1380)     <p>
1381) With almost 1 million downloads, our Orweb browser has been a popular
1382) solution for easily accessing the web via Tor or any other HTTP or
1383) SOCKS proxy, while also ensuring local data caches are cleared and
1384) cookies are properly managed. Orweb is based on WebView, which has its
1385) limitations unfortunately. We would like to move to a
1386) Firefox/Fennec/GeckoView based browser, and have created a prototype
1387) for it. Mozilla has begun releasing GeckoView as a standalone
1388) component, as well, but it needs more testing, debugging and work on
1389) integration into our streamlined browser app model. Our end goal is to
1390) have a mobile browser that matches Tor Browser in terms of privacy
1391) enhancing features and security.
1392)     </p>
1393) 
1394)     <p>
1395) The deliverables for the project are expected to be the creation of a
1396) alpha quality release of Orfox, a GeckoView-based browser with feature
1397) parity of Orweb browser. A bonus goal is to implement additional
1398) features and capabilities based on Tor Browser patches for
1399) Fennec/Mozilla core. Finally, as always, a required activity is a
1400) network audit testing of implemented solution with write-ups, reports
1401) posted publicly.
1402)     </p>
1403) 
1404)     <p>
1405) Useful links to review:
1406)     </p>
1407) 
1408)     <ul>
1409)       <li><a href="https://github.com/guardianproject/orfox">Orfox (gecko prototype)</a></li>
1410)       <li><a href="https://github.com/guardianproject/orweb">Orweb (production browser on WebView)</a></li>
1411)       <li><a href="http://starkravingfinkle.org/blog/2013/10/geckoview-embedding-gecko-in-your-android-application/">GeckoView info</a></li>

1412)       <li><a href="<page projects/torbrowser>">Tor Browser (desktop)</a></li>

1413)     </ul>
1414) 
1415)     <p>
1416) Applicant should have the ability to build Fennec and GeckoView
1417) libraries from source using Android SDK and NDK. Some experince with
1418) browser security models and threats would be a useful background to
1419) have. Ability to do network audits to ensure browser proxying is not
1420) leaking DNS, media streams or other network traffic, as well as tests
1421) against common browser de-anonymizing attacks are necessary.
1422)     </p>
1423)     </li>
1424) 
1425)     <a id="improveTorTestCoverage"></a>
1426)     <li>
1427)     <b>Improve test coverage in Tor</b>
1428)     <br>
1429)     Effort Level: <i>Medium</i>
1430)     <br>
1431)     Skill Level: <i>Medium</i>
1432)     <br>
1433)     Likely Mentors: <i>Nick (nickm)</i>
1434)     <p>
1435) Right now, our unit test coverage with the tests we ship is around 30%
1436) -- only 30% of the executable lines in our source are reached by the
1437) unit tests.  Improving this test coverage could make Tor development
1438) much more reliable.
1439)     </p>
1440) 
1441)     <p>
1442) So we need better unit tests, and we need better integration tests too.
1443)     </p>
1444) 
1445)     <p>
1446) Improving unit tests would would involve refactoring functions to be more
1447) testable, and writing a bunch of unit tests.
1448)     </p>
1449) 
1450)     <p>
1451) Improving integratino tests would involve refactoring and improving
1452) the "chutney" program that launches a test tor network, and writing a
1453) bunch of tests to see what works and what doesn't work on such a
1454) network.  It could also involve writing tests using the library "<a
1455) href="https://stem.torproject.org/">stem</a>" to script individual clients on a
1456) Chutney network.
1457)     </p>
1458) 
1459)     <p>
1460) To get a feel for how testing works in Tor today, download Tor and
1461) Chutney, and make sure you can build Tor and use Chutney.  See how the
1462) unit tests work by skimming some of the test code in the src/test
1463) subdirectory.  Try computing test coverage (according to the
1464) instructions in the doc/HACKING file.
1465)     </p>
1466) 
1467)     <p>
1468) Also, have a look at the one current integration test that works on
1469) chutney today: it is a shell script distributed with Tor as
1470) src/test/test-tor-network.sh .  We probably don't want to have all of
1471) our integration tests be written as shell scripts, but it's interesting
1472) to see how one works.
1473)     </p>
1474) 
1475)     <p>
1476) If working on designs for an improved or refactored Chutney, watch out for <a
1477) href="http://www.joelonsoftware.com/articles/fog0000000018.html">"archicture
1478) astronautics"</a>: while it's important that we have a well-designed and
1479) maintainable Chutney architecture, it wouldn't be very useful if a good
1480) architecture were the <em>only</em> outcome here: we need tests too.
1481)     </p>
1482) 
1483)     <p>
1484) As part of the application process, please contribute a patch that makes
1485) a non-trivial improvement to chutney, and/or include a new test for some
1486) interesting Tor function. (Please pick a function that isn't completely
1487) easy to test.)
1488)     </p>
1489)     </li>
1490) 
1491)     <a id="useMoreCores"></a>
1492)     <li>
1493)     <b>Have the Tor daemon use more cores</b>
1494)     <br>
1495)     Effort Level: <i>Medium</i>
1496)     <br>
1497)     Skill Level: <i>Medium</i>
1498)     <br>
1499)     Likely Mentors: <i>Nick (nickm)</i>
1500)     <p>
1501) Right now, if you run a busy Tor server on a multicore computer, most of
1502) the cores are mostly unused.  We have a "cpuworker" mechanism to move
1503) expensive computations into worker threads, but that mechanism is
1504) currently only used for a small fraction of our cryptography.  Moving
1505) more work into the worker threads could improve performance immensely.
1506)     </p>
1507) 
1508)     <p>
1509) So it would be great to parallelize our cryptography more in order to
1510) better handle more cores.  See
1511) <a href="https://trac.torproject.org/projects/tor/wiki/org/projects/Tor/MultithreadedCrypto">MultithreadedCrypto</a>
1512) for some background info, and
1513) <a href="https://trac.torproject.org/projects/tor/ticket/7572">ticket 7572</a> for some subtickets
1514) on our tracker.
1515)     </p>
1516) 
1517)     <p>
1518) (If you're reading through the code to see how it works today, you will
1519) also want to have a look at the new implementation for cpuworkers
1520) described in <a href="https://trac.torproject.org/projects/tor/ticket/9682">9682</a>.)
1521)     </p>
1522) 
1523)     <p>
1524) Completing the implementation of ticket #7572 --which would move our
1525) circuit crypto onto separate threads-- could be a good summer project.
1526) Alternatively, moving all of the signature generation and verification
1527) code onto the cpuworkers could be fun.  In either case, you will have
1528) some important architectural decisions to make about how to minimize
1529) shared data between the main thread and the workers, how to avoid
1530) race conditions between them, and how to test it all to make sure it has
1531) no hidden failure cases.
1532)     </p>
1533) 
1534)     <p>
1535) As part of the application process for this project, please contribute a
1536) nontrivial patch to Tor -- ideally, one that will affect some part of
1537) the codebase that you want to work on.
1538)     </p>
1539)     </li>
1540) 
1541)     <a id="improveHiddenServices"></a>
1542)     <li>
1543)     <b>Help improve Tor hidden services</b>
1544)     <br>
1545)     Effort Level: <i>Medium</i>
1546)     <br>
1547)     Skill Level: <i>Medium</i>
1548)     <br>
1549)     Likely Mentors: <i>Nick (nickm)</i>
1550)     <p>
1551) We're working on a revamp of the entire Tor hidden service design to
1552) improve the security and reliability of the hidden service system.
1553)     </p>
1554) 
1555)     <p>
1556) This is a big project: see
1557) <a href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/224-rend-spec-ng.txt">proposal
1558) 224</a> for the latest design.  Are you interested in implementing some
1559) part of that?
1560)     </p>
1561) 
1562)     <p>
1563) This is a very ambitious project, so we're deliberately not suggesting
1564) particular sub-topics.  If you're interested in participating, try to
1565) read and understand the <a
1566) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/rend-spec.txt">existing
1567) design</a> and the design proposal for the new design, and then talk to
1568) us about what part you want to work on.
1569)     </p>
1570) 
1571)     <p>
1572) As part of the application process for this project, please contribute a
1573) nontrivial patch to Tor -- ideally, one that will affect some part of
1574) the codebase that you want to work on.
1575)     </p>
1576)     </li>
1577) 
1578)     <a id="consensusDiffs"></a>
1579)     <li>
1580)     <b>Implement consensus diffs</b>
1581)     <br>
1582)     Effort Level: <i>Medium</i>
1583)     <br>
1584)     Skill Level: <i>Medium</i>
1585)     <br>
1586)     Likely Mentors: <i>Nick (nickm)</i>
1587)     <p>
1588) Right now, every few hours, a Tor client downloads a new signed "consensus
1589) document" that describes the state of the network.  Even though these
1590) documents are compressed, thisstill takes almost half a megabyte.
1591)     </p>
1592) 
1593)     <p>
1594) <a
1595) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/140-consensus-diffs.txt">Proposal
1596) 140</a> describes a design to save a lot of bandwidth by transferring
1597) compressed <a href="http://en.wikipedia.org/wiki/Diff">diff</a>s instead
1598) of transferring the entire consensus document.
1599)     </p>
1600) 
1601)     <p>
1602) That's an attractive idea, but it presents some programming challenges.
1603) We probably don't want to ship a 'diff' and 'patch' along with Tor.  Is
1604) there a free, <strong>safe</strong>, robust implementation of one of the
1605) good diff algorithms that we can use?
1606)     </p>
1607) 
1608)     <p>
1609) Alternatively, can we take advantage of regularities in the descriptor
1610) format in order to generate diffs more simply?
1611)     </p>
1612) 
1613)     <p>
1614) As part of the application process for this project, please contribute a
1615) nontrivial patch to Tor -- ideally, one that will affect some part of
1616) the codebase that you want to work on.  Make sure that your application
1617) describes which implementations of the diff and patch algorithms you
1618) intend to use, and that your coding samples show strong evidence that
1619) you can do secure string manipulation in C.
1620)     </p>
1621)     </li>
1622) 
1623)     <a id="improvedDnsSupport"></a>
1624)     <li>
1625)     <b>Improved DNS support for Tor</b>
1626)     <br>
1627)     Effort Level: <i>Medium</i>
1628)     <br>
1629)     Skill Level: <i>Medium</i>
1630)     <br>
1631)     Likely Mentors: <i>Nick (nickm)</i>
1632)     <p>
1633) Right now, you can only use Tor's DNS support to look up IPv4 and IPv6
1634) addresses, and to fetch PTR records.  But DNS can do so much more!
1635)     </p>
1636) 
1637)     <p>
1638) <a
1639) href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/219-expanded-dns.txt">Proposal
1640) 219</a> describes some new cell types that Tor could use to support
1641) more types of DNS over Tor.
1642)     </p>
1643) 
1644)     <p>
1645) To see how Tor implements its existing DNS lookups, start by tracing the
1646) the connection_exit_begin_resolve() function in src/or/connection_edge.c ,
1647) and see how we pass these requests downwards through src/or/dns.c to the
1648) underlying resolver.  It's not too complicated, but there are some
1649) tricky parts to understand.
1650)     </p>
1651) 
1652)     <p>
1653) As part of the application process for this project, please contribute a
1654) nontrivial patch to Tor -- ideally, one that will affect some part of
1655) the codebase that you want to work on.
1656)     </p>
1657)     </li>
1658) 
1659)     <a id="torSandboxing"></a>
1660)     <li>
1661)     <b>Help improve Tor sandboxing</b>
1662)     <br>
1663)     Effort Level: <i>Medium</i>
1664)     <br>
1665)     Skill Level: <i>Medium</i>
1666)     <br>
1667)     Likely Mentors: <i>Nick (nickm)</i>
1668)     <p>
1669) The seccomp2 mechanism on Linux lets programs improve their robustness
1670) against unforseen bugs by running with restrictions on which system
1671) calls they can invoke and how they can call them.  This can help
1672) security a lot.
1673)     </p>
1674) 
1675)     <p>
1676) Thanks to a GSOC student from last year, we now have seccomp2 support on
1677) Linux, which we use to restrict the capabilities of the entire Tor
1678) process.  (For implementation details, see src/commmon/sandbox.c in the
1679) Tor source.)
1680)     </p>
1681) 
1682)     <p>
1683) But since the restrictions are done over the whole process, all pieces
1684) of the Tor code have permission to do things that only small parts of
1685) the Tor program need to do.  Also, since we use seccomp2, these
1686) restrictions only work on Linux.
1687)     </p>
1688) 
1689)     <p>
1690) It would be great to instead divide the main Tor program into multiple
1691) processes with a robust IPC mechanism and assign each process its own
1692) minimal set of privileges; and to have this work (as best we can) on
1693) systems that don't have seccomp2 (eg Windows, Mac).
1694)     </p>
1695) 
1696)     <p>
1697) Either of these could be a whole GSOC project.
1698)     </p>
1699) 
1700)     <p>
1701) To get started, make sure you understand the existing sandboxing code.
1702) If you're interested in splitting Tor into multiple processes, think
1703) about the architecture, and think about how we could reach this
1704) architecture without completely rewriting the codebase.  (Remember that
1705) even if you're focusing on Linux, Tor still needs to work on other
1706) operating systems.)
1707)     </p>
1708) 
1709)     <p>
1710) If you're interested in supporting more platforms, make sure you
1711) understand and can explain what sandboxing mechansisms you want to use,
1712) and what they're capable of.  (You might want to investigate the way
1713) that other open-source programs, like the Chrome web browser, do their
1714) sandboxing on different platforms.)
1715)     </p>
1716) 
1717)     <p>
1718) As part of the application process for this project, please contribute a
1719) nontrivial patch to Tor -- ideally, one that will affect some part of
1720) the codebase that you want to work on.
1721)     </p>
1722)     </li>
1723) 

1724)     <a id="panopticlick"></a>
1725)     <li>
1726)     <b>Panopticlick</b>
1727)     <br>
1728)     Effort Level: <i>Medium</i>
1729)     <br>
1730)     Skill Level: <i>Medium</i>
1731)     <br>

1732)     Likely Mentors: <i>Georg (GeKo)</i>, <i>Mike Perry</i>, <i>Nicolas Vigier</i>
1733)     <p>
1734) 
1735) The <a href="https://panopticlick.eff.org">Panopticlick project by the EFF</a>
1736) revolutionized how people think about <a
1737) href="https://panopticlick.eff.org/browser-uniqueness.pdf">browser
1738) fingerprinting</a>, both by developing tests and metrics to measure browser
1739) fingerprintability, and by crowdsourcing the evaluation and contribution of
1740) individual browser features to overall fingerprintability.
1741) 
1742)     </p>
1743)     <p>
1744) 
1745) Unfortunately, the way Panopticlick is designed <a
1746) href="https://blog.torproject.org/blog/effs-panopticlick-and-torbutton">makes
1747) it difficult</a> to evaluate defenses to browser fingerprinting, especially
1748) for browsers with a relatively small userbase such as Tor Browser. This is
1749) because any approach we take to reduce fingerprinting automatically makes our
1750) users more distinct from the previous users who submitted their fingerprint
1751) data to the EFF. Indeed, it is also impossible to ever expect that users of
1752) one browser will ever be able to blend in with users of another browser
1753) (Chrome users will always be distinguishable from Firefox users for example,
1754) based on feature set alone).
1755) 
1756)    </p>
1757)    <p>
1758) 
1759) To address this, we would like to have <a

1760) href="https://trac.torproject.org/projects/tor/ticket/6119">our own

1761) fingerprint test suite</a> to evaluate the fingerprintability of each browser
1762) feature for users running a specific Tor Browser version. There are also <a
1763) href="https://trac.torproject.org/projects/tor/query?keywords=~tbb-fingerprinting">additional
1764) fingerprinting tests</a> we can add beyond those deployed by Panopticlick.
1765)    </p>
1766)    <p>
1767) 
1768) For this project, the student would develop a website that users can
1769) voluntarily visit to test and record their Tor Browser fingerprint.  The user
1770) should get feedback on how she performed and the test results should be
1771) available in a machine readable format (e.g. JSON), broken down by Tor Browser
1772) version.  In a second step one could think about adding more sophisticated
1773) tests or supporting other browser vendors that might want to test the
1774) uniformity amongst their userbase as well. Of course, results from each
1775) browser would also need to be broken down by both browser implementation and
1776) version, so that results would only reflect the population of that specific
1777) implementation.
1778) 

1779)     </p>
1780)     </li>
1781) 

1782)     <a id="revamp_gettor"></a>
1783)     <li>
1784)     <b>Revamp GetTor</b>
1785)     <br>
1786)     Effort Level: <i>High</i>
1787)     <br>
1788)     Skill Level: <i>Medium</i>
1789)     <br>
1790)     Likely Mentors: <i>Sukhbir Singh (sukhe), Nima Fatemi (mrphs)</i>
1791)     <p>
1792) GetTor is a program that serves Tor bundles and related components over SMTP.
1793) Users request the Tor Browser Bundle by sending an email to GetTor, which sends

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

1797)     </p>
1798) 
1799)     <p>
1800) GetTor has been unmaintained for a while and needs a revamp. The main issue is
1801) that because the Tor Browser Bundle size exceeds 25 MB, sending it through
1802) GetTor no longer works as most email providers don't support attachments
1803) exceeding 25 MB. To alleviate this issue, bundles are now uploaded on
1804) cloud-based services such as Google Drive and Dropbox and links are sent
1805) out in the email body instead of attachments. This current setup is far from
1806) complete -- GetTor needs a lot of work to get it to a point where it can do
1807) smart things again and do them in the right way.
1808)     </p>
1809) 
1810)     <p>
1811) As part of this project, you should:
1812)     </p>
1813) 
1814)     <ul>
1815)       <li>Have some understanding of what GetTor does in general and the current state of its operation.</li>
1816)       <li>Come up with ideas on how to make it better.</li>
1817)       <li>Convince us if you would like to fix the existing code or want to rewrite GetTor from scratch.</li>
1818)     </ul>
1819) 
1820)     <p>
1821) In addition to the above points, applications should be familiar with Python.
1822) As part of the application process, study the <a
1823) href="https://gitweb.torproject.org/gettor.git">GetTor code</a> and submit a
1824) patch for returning the SHA1 checksum of the package instead of the text in
1825) sendSorrySize() in response.py. (since you cannot test the patch, as long as it
1826) is clear that you had some idea of what you were doing, it should be fine)
1827)     </p>
1828) 
1829)     <p>

1830) 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.

1831)     </p>
1832)     </li>
1833) 

1834)     <a id="rewriteWeather"></a>
1835)     <li>
1836)     <b>Rewrite Tor Weather</b>
1837)     <br>
1838)     Effort Level: <i>Medium</i>
1839)     <br>
1840)     Skill Level: <i>Medium</i>
1841)     <br>
1842)     Likely Mentors: <i>Karsten (karsten)</i>
1843)     <p>
1844) <a href="https://weather.torproject.org/">Tor Weather</a> provides an
1845) email notification service to any users who want to monitor the status
1846) of a Tor node.  Its favorite feature is to notify relay operators when
1847) their relay has earned them a Tor t-shirt.  Tor Weather is written in
1848) Python/Django.
1849)     </p>
1850) 
1851)     <p>
1852) The Tor Weather codebase is pretty much unmaintained these days.  The
1853) first part of this project would be to simplify the code by fetching Tor
1854) network status data from <a
1855) href="https://onionoo.torproject.org/">Onionoo</a> rather than running a
1856) local tor client and keeping an own relay history database.  See the
1857) related <a
1858) href="https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014">community
1859) effort to rewrite Weather</a> that started in January 2014.  After that,
1860) there's a <a
1861) href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Tor+Weather">long
1862) list of open tickets</a> to be resolved.
1863)     </p>
1864) 
1865)     <p>
1866) Ideally, the student would become the new Weather maintainer after the
1867) summer.  If that doesn't work out, the codebase should have become a lot
1868) smaller by end of summer, so that it becomes easier to find somebody
1869) else as new maintainer.
1870)     </p>
1871)     </li>
1872) 
1873)     <a id="improveStegotorus"></a>
1874)     <li>
1875)     <b>Improve Stegotorus</b>
1876)     <br>
1877)     Effort Level: <i>Medium</i>
1878)     <br>
1879)     Skill Level: <i>Medium</i>
1880)     <br>
1881)     Likely Mentors: <i>vmon</i>
1882)     <p>
1883) 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.
1884)     </p>
1885) 
1886)     <p>
1887) For example, Stegotorus is equipped with a "chopper module" which takes care of following aspects:
1888)     </p>
1889) 
1890)     <ol>
1891)       <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>
1892)       <li>It makes sure that it only handle as much (or as less) information as the transport module can handle.</li>
1893)       <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>
1894)     </ol>
1895) 
1896)     <p>
1897) 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.
1898)     </p>
1899) 
1900)     <p>
1901) Stegotorus is written in C++. you can find the latest code <a href="https://github.com/zackw/stegotorus/tree/tor-improve">here</a>.
1902)     </p>
1903) 
1904)     <p>
1905) In this regard, Stegotorus is offering one of the most complete and sophisticated platforms for writing stealthy pluggable transports.
1906)     </p>
1907) 
1908)     <p>
1909) 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:
1910)     </p>
1911) 
1912)     <ol>
1913)       <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>
1914)       <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>
1915)       <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>
1916)       <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>
1917)       <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>
1918)       <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>
1919)       <li>The general security of the code needs to be reviewed and audited for buffer overflow, memory leak etc.</li>
1920)       <li>Steg modules for new file format for the HTTP transport are always welcome to reflect the actual traffic of the Internet.</li>
1921)       <li>Packaging Stegotorus for windows.</li>
1922)       <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>
1923)       <li>Stegotorus needs to support SOCKS protocol to be able to receive the initial parameters from Tor through SOCKS handshake.</li>
1924)     </ol>
1925) 
1926)     <p>
1927) 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>.
1928)     </p>
1929) 
1930)     <p>
1931) You also can think of lots of other awesome creative ways of improving Stegotorus and include those in your proposal.
1932)     </p>
1933)     </li>
1934) 

1935)     <a id="newBridgedbDistributor"></a>
1936)     <li>
1937)     <b>New BridgeDB Distributor</b>
1938)     <br>
1939)     Effort Level: <i>Medium</i>
1940)     <br>
1941)     Skill Level: <i>Medium to High</i>
1942)     <br>
1943)     Likely Mentors: <i>isis, sysrqb</i>
1944)     <p>
1945) BridgeDB is a Twisted Python system which runs a number of servers, in order
1946) to distribute Tor bridge relays to users in potentially censored regions. Each
1947) of BridgeDB's Distributors uses some unique channel to communicate bridge
1948) addresses to users, currently there is an <a href="https://bridges.torproject.org">
1949) HTTPS Distributor</a>, and an Email Distributor. This project would involve
1950) designing and creating a new Distributor for BridgeDB. Some ideas for new
1951) Distributors:
1952)     </p>
1953) 
1954)     <ul>
1955)       <li>A Twitter bot which interacts with Chinese and Farsi speaking Twitter users through PMs.</li>
1956)       <li>A distributor which uses XMPP+OTR to give bridges to users.</li>
1957)     </ul>
1958) 
1959)     <p>
1960) It's helpful if you already have some knowledge of Twisted. As part of your
1961) application, please submit a design for a Distributor, as well as supply a
1962) patch for a ticket which demonstrates knowledge of Twisted and Python ―
1963) preferably for BridgeDB, see the
1964) <a href="https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~bridgedb-gsoc-application">
1965) 'bridgedb-gsoc-application' Trac tag</a> for some examples of good tickets to
1966) try, or contact isis or sysrqb on IRC to ask for ticket suggestions or advice.
1967)     </p>
1968)     </li>
1969) 

1970) <!--
1971)     <a id=""></a>
1972)     <li>
1973)     <b></b>
1974)     <br>
1975)     Effort Level: <i>Medium</i>
1976)     <br>
1977)     Skill Level: <i>Medium</i>
1978)     <br>
1979)     Likely Mentors: <i>Damian (atagar)</i>
1980)     <p>
1981) 
1982)     </p>
1983) 
1984)     <p>
1985) 
1986)     </p>
1987)     </li>
1988) -->
1989) 

1990)     <li>
1991)     <b>Bring up new ideas!</b>

1992)     <br>

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

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

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

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

1998)     might also be short on developers.
1999)     </li>

2000) 

2001)     </ol>

2002) 

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

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

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

2018) 

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

2024) 

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

2034) 

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

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

2039)     Tor if needed.</li>

2040) 

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

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

2046) 

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

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

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

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

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

2057) 

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

2061) 

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

2068) 

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

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

2072)     System</a>.
2073)     </li>

2074) 

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

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

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

2087) 

2088)     </ol>

2089) 

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

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

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

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

2192)     your browser's UserAgent string by replacing it with a uniform answer for
2193)     every Tor user. That way the attacker can't splinter Tor's anonymity set
2194)     by looking at that header. It tries to pick a string that is commonly used
2195)     by non-Tor users too, so it doesn't stand out. Question one: how badly
2196)     do we hurt ourselves by periodically updating the version of Firefox
2197)     that Torbutton claims to be? If we update it too often, we splinter the
2198)     anonymity sets ourselves. If we don't update it often enough, then all the
2199)     Tor users stand out because they claim to be running a quite old version
2200)     of Firefox. The answer here probably depends on the Firefox versions seen
2201)     in the wild. Question two: periodically people ask us to cycle through N
2202)     UserAgent strings rather than stick with one. Does this approach help,
2203)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
2204)     by their rotating UserAgents; malicious websites who only attack certain
2205)     browsers; and whether the answers to question one impact this answer.
2206)     </li>
2207)     <li>How many bridge relays do you need to know to maintain
2208)     reachability? We should measure the churn in our bridges. If there is
2209)     lots of churn, are there ways to keep bridge users more likely to stay
2210)     connected?
2211)     </li>
2212)     </ol>

2213) 

2214)     <p>
2215)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
2216)     of these!
2217)     </p>
2218)   </div>
2219)   <!-- END MAINCOL -->
2220)   <div id = "sidecol">
2221) #include "side.wmi"
2222) #include "info.wmi"
2223)   </div>
2224)   <!-- END SIDECOL -->
2225) </div>
2226) <!-- END CONTENT -->