tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 4-optional
4) 
5) #include "head.wmi" TITLE="Tor: Volunteer" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page getinvolved/volunteer>">Volunteer</a>
10)   </div>

11)   <div id="maincol">

12)     <!-- PUT CONTENT AFTER THIS TAG -->
13)     <h1>A few things everyone can do now:</h1>
14)     <ol>
15)     <li>Please consider <a href="<page docs/tor-doc-relay>">running
16)     a relay</a> to help the Tor network grow.</li>

17)     <li>Do you have an Amazon account? Are you willing to spend up to $3 a

18)     month? Then spin up your own Tor <a href="<page
19)     docs/bridges>">bridge</a> in less than 10 minutes with <a

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

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

33) 

34)     <a id="Documentation"></a>
35)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
36)     <ol>

37)     <li>Help translate the
38) <!-- web page and -->
39)     documentation into other

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

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

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

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

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

51) 

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

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

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

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

60)     <a

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

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

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

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

68)     </ol>

69) 

70) <!--

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

93) -->

94) 

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

97) 

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

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

105)     </p>

106) 

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

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

125) 

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

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

132)       </tr>

133) 

134)       <tr>

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

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

138)         <td>Moderate</td>

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

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

144)         <td>Bundle</td>

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

146)         <td>Moderate</td>

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

148)       </tr>

149) 

150)       <tr>

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

156)       </tr>

157) 

158)       <tr>

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

162)         <td>Heavy</td>

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

164)       </tr>

165) 

166)       <tr>

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

170)         <td>None</td>

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

173) 

174)       <tr>

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

178)         <td>Light</td>

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

181) 

182)       <tr>

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

186)         <td>Light</td>

187)         <td>n8fr8</td>

188)       </tr>

189) 

190)       <tr>

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

196)       </tr>

197) 

198)       <tr>

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

202)         <td>None</td>

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

206)       <tr>

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

210)         <td>None</td>

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

214)       <tr>

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

218)         <td>Light</td>

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

222)       <tr>

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

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

228)       </tr>

229) 

230)       <tr>

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

233)         <td>Python</td>

234)         <td>Moderate</td>

235)         <td>asn</td>

236)       </tr>
237) 

238)       <tr>

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

242)         <td>Heavy</td>

243)         <td>dcf, aallai, jct</td>
244)       </tr>

245) 

246)       <tr>

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

248)         <td>Simulator</td>

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

250)         <td>Heavy</td>

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

253) 

254)       <tr>

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

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

259)         <td>atagar</td>

260)       </tr>

261) 

262)       <tr>

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

266)         <td>Moderate</td>

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

269) 

270)       <tr>

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

274)         <td>Moderate</td>

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

277) 

278)       <tr>

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

282)         <td>Moderate</td>

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

285) 

286)       <tr>

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

290)         <td>Light</td>

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

292)       </tr>

293) 

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

302)       <tr>

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

306)         <td>Light</td>

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

308)       </tr>

309) 

310)       <tr>

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

314)         <td>Moderate</td>

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

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

326)       <tr>

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

330)         <td>None</td>

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

333) 

334)       <tr>

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

338)         <td>None</td>

339)         <td>kaner</td>

340)       </tr>

341) 

342)       <tr>

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

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

348)       </tr>

349) 

350)       <tr>

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

354)         <td>Light</td>

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

356)       </tr>

357) 

358)       <tr>

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

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

362)         <td>Moderate</td>

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

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

374)       <tr>

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

378)         <td>None</td>

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

380)       </tr>

381) 

382)       <tr>

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

389) 

390)       <tr>

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

393)         <td>Python</td>

394)         <td>Moderate</td>

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

396)       </tr>

397) 

398)       <tr>

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

401)         <td>Python</td>

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

406)     </table>

407) 

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

411) 

412)     <br /><br />

413) 

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

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

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

418) 

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

424) 

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

427)     <i><a href="#limitCapabilities">Run With Limited Capabilities</a></i><br />
428)     <i><a href="#torCleanup">Tor Codebase Cleanup</a></i><br />

429)     <i><a href="#httpsImpersonation">HTTPS Server Impersonation</a></i><br />

430)     <i><a href="#chutneyExpansion">Make Chutney Do More, More Reliably</a></i>

431)     </p>

432) 

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

437)     tracker</a>)</h3>

438) 

439)     <p>

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

441)     </p>

442) 

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

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

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

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

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

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

454)     </p>

455) 
456)     <a id="project-torbutton"></a>
457)     <h3><a href="<page torbutton/index>">Torbutton</a> (<a
458)     href="https://gitweb.torproject.org/torbutton.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=Torbutton&order=priority">bug

460)     tracker</a>)</h3>

461) 

462)     <p>

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

468)     </p>

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

474)     tracker</a>)</h3>

475) 

476)     <p>

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

480)     </p>

481) 

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

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

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

487) 

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

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

493)     </p>

494) 

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

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

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

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

500) 

501)     <p>

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

507)     </p>

508) 

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

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

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

514) 
515)     <p>
516)     Provides Tor on the Android platform. This was under very active
517)     development up through Fall 2010, after which things have been quiet.
518)     </p>
519) 
520)     <a id="project-tails"></a>
521)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

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

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

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

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

538) 
539)     <p>

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

542)     </p>
543) 

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

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

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

557)     <h3>Torsocks (<a

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

562)     <p>

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

566)     </p>

567) 

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

573) 

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

577) 

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

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

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

582)     tracker</a>)</h3>

583) 

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

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

587)     </p>

588) 

589)     <p>
590)     <b>Project Ideas:</b><br />
591)     <i><a href="#betterPluggableTransports">Build Better Pluggable Transports</a></i>
592)     </p>
593) 

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

599) 

600)     <p>
601)     Pluggable transport using proxies running in web browsers to defeat
602)     address-based blocking.
603)     </p>

604) 

605)     <a id="project-shadow"></a>
606)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
607)     href="https://github.com/shadow">code</a>, <a
608)     href="https://github.com/shadow/shadow/issues">bug
609)     tracker</a>)</h3>

610) 

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

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

617)     </p>

618) 

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

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

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

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

623)     tracker</a>)</h3>

624) 

625)     <p>

626)     Python controller library for scripts and controller applications using
627)     Tor.

628)     </p>

629) 

630)     <p>
631)     <b>Project Ideas:</b><br />

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

633)     <i><a href="#stemUsability">Stem Usability and Porting</a></i><br />
634)     <i><a href="#stemTestingForTor">Stem Tests for Tor</a></i>

635)     </p>

636) 

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

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

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

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

641) 

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

647) 

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

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

655) 

656)     <p>
657)     tlsdate: secure parasitic rdate replacement
658)     </p>

659) 

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

667) 

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

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

673) 

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

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

679)     </p>

680) 

681)     <p>
682)     <b>Project Ideas:</b><br />
683)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
684)     </p>

685) 

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

689) 

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

693)     their past usage.

694)     </p>

695) 

696)     <p>

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

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

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

702)     </p>

703) 

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

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

720) 

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

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

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

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

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

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

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

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

755) 

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

762) 

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

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

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

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

768) 

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

773) 

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

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

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

777)     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
778)     tracker</a>)</h3>

779) 

780)     <p>

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

782)     </p>

783) 

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

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

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

789) 

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

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

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

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

806)     <p>
807)     <b>Project Ideas:</b><br />

808)     <i><a href="#ooniprobeSimulator">Create an Internet Censorship Virtual Machine Based Simulator</a></i><br />
809)     <i><a href="#censorshipAnalyzer">Develop a Censorship Analyzer</a></i>

810)     </p>
811) 

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

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

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

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

827) 

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

836) 

837)     <a id="project-torbel"></a>
838)     <h3><a

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

841)     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
842)     tracker</a>)</h3>

843) 

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

851) 

852)     <p>
853)     <b>Project Ideas:</b><br />
854)     <i><a href="#stemUsability">Stem Usability and Porting (this includes an idea for finishing off TorBEL)</a></i>
855)     </p>
856) 

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

869)     <a id="project-anonbib"></a>
870)     <h3><a
871)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
872)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
873) 
874)     <p>

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

878)     </p>
879) 

880)     <a id="Coding"></a>
881)     <a id="Summer"></a>

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

883) 

884)     <p>

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

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

895)     </p>

896) 

897)     <ol>

898) 

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

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

927)     <p>This would very likely involve changes to both libraries, although
928)     most would be expected to be in txtorcon. meejah is available to
929)     mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>
930)     <p>It would help if you're already familiar with event-based programming,
931)     bonus points if it's Twisted.</p>
932)     </li>
933) 

934)     <a id="httpsImpersonation"></a>

935)     <li>
936)     <b>HTTPS Server Impersonation</b>
937)     <br>
938)     Effort Level: <i>Medium to High</i>
939)     <br>
940)     Skill Level: <i>Medium to High</i>
941)     <br>
942)     Likely Mentors: <i>Nick (nickm)</i>

943)     <p>

944)     We have an open proposal for a way to make Tor bridges avoid censorship by
945)     impersonating an HTTPS server.  Specifically, we need to hack some popular
946)     SSL "reverse proxy" (your choice) so that it relays regular web connections
947)     to an HTTP server, but certain connections to a local Tor process.  <a
948)     href="https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/203-https-frontend.txt">Proposal
949)     203</a> has a general design sketch.

950)     </p>

951) 
952)     <p>
953)     <b>This project is likely trickier than it looks. You should avoid applying
954)     for this if you're uncertain about being able to complete it.</b>
955)     </p>
956)     </li>

957)     </li>

958) 

959)     <a id="chutneyExpansion"></a>
960)     <li>
961)     <b>Make Chutney Do More, More Reliably</b>
962)     <br>
963)     Effort Level: <i>Medium to High, depending on scope of project</i>
964)     <br>
965)     Skill Level: <i>Medium</i>
966)     <br>

967)     Likely Mentors: <i>Nick (nickm)</i>
968)     <p>

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

973)     </p>

974) 

975)     <p>

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

979)     </p>

980) 
981)     <p>
982)     <b>As part of your application for this project please submit a patch that
983)     expands Chutney.</b>
984)     </p>
985) 

986)     </li>

987) 

988)     <a id="limitCapabilities"></a>

989)     <li>

990)     <b>Run With Limited Capabilities</b>

991)     <br>
992)     Effort Level: <i>Medium to High</i>
993)     <br>

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

995)     <br>
996)     Likely Mentors: <i>Nick (nickm)</i>
997)     <p>

998)     Many modern operating systems give a running program the ability to drop
999)     capabilities that it no longer needs, and other ways for a program to run
1000)     pieces of itself in a sandbox with diminished privileges.

1001)     </p>

1002) 

1003)     <p>

1004)     We'd like to do this with Tor, to improve its resistance to attacks.  The
1005)     easiest areas to address would be on systems like <a
1006)     href="https://lwn.net/Articles/475361/">recent Linux kernels</a> that make
1007)     it easy to drop or restrict the set of syscalls that a program can invoke.
1008)     That's a great project, but probably not big enough for an internship just
1009)     on its own.  For that, we'd want to make progress on at least multiple
1010)     platforms, or look into refactoring Tor into pieces that need more
1011)     privileges and pieces that don't with an eye towards sandboxing them
1012)     differently.

1013)     </p>

1014) 

1015)     <p>

1016)     See tickets <a href="https://trac.torproject.org/7005">#7005</a> and <a
1017)     href="https://trac.torproject.org/5219">#5219</a>, and their descendants,
1018)     for more information.

1019)     </p>
1020)     </li>

1021) 

1022)     <a id="metricsSearch"></a>

1023)     <li>

1024)     <b>Searchable Tor descriptor and Metrics data archive</b>

1025)     <br>
1026)     Effort Level: <i>Medium</i>
1027)     <br>
1028)     Skill Level: <i>Medium</i>
1029)     <br>

1030)     Likely Mentors: <i>Karsten</i>
1031)     <p>The <a href="https://metrics.torproject.org/data.html">Metrics data
1032)     archive</a> of Tor relay descriptors and other Tor-related network data has
1033)     grown to over 100G in size, bz2-compressed.  We have developed two search
1034)     interfaces: the <a
1035)     href="https://metrics.torproject.org/relay-search.html">relay search</a>
1036)     finds relays by nickname, fingerprint, or IP address in a given month; <a
1037)     href="https://metrics.torproject.org/exonerator.html">ExoneraTor</a> finds
1038)     whether a given IP address was a relay on a given day.</p>

1039) 

1040)     <p>We'd like to have a more general search application for Tor descriptors
1041)     and metrics data.  There are more <a
1042)     href="https://metrics.torproject.org/formats.html">descriptor types</a>
1043)     that we'd like to include in the search.  The search application should
1044)     handle most of them and understand some semantics like what's a timestamp,
1045)     what's an IP address, and what's a link to another descriptor.  Users
1046)     should then be able to search for arbitrary strings or limit their search
1047)     to given time periods or IP address ranges.  Descriptors that reference
1048)     other descriptors should contain links, and descriptors should be able to
1049)     say from where they are linked.  The goal is to make the archive easily
1050)     browsable.</p>

1051) 

1052)     <p>The search application shall be separate from the metrics website and
1053)     shouldn't rely on the metrics website codebase.  The search application
1054)     will contain hourly updated descriptor data from the metrics website via
1055)     rsync.  Programming language and database system are not specified yet,
1056)     though there's a slight preference for Python/Django and Postgres for
1057)     maintenance reasons.  If there are good reasons to pick something else,
1058)     e.g, some NoSQL variant or some search application framework, that's fine,
1059)     too.  Further requirements are that lookups should be really fast and that
1060)     changes to the search application can be implemented in reasonable
1061)     time.</p>

1062) 

1063)     <p>Applications for this project should come with a design of the proposed
1064)     search application, ideally with a proof-of-concept based on a subset of
1065)     the available data to show that it will be able to handle the 100G+ of
1066)     data.</p>

1067)     </li>

1068) 

1069)     <a id="stemUsability"></a>

1070)     <li>

1071)     <b>Stem Usability and Porting</b>

1072)     <br>
1073)     Effort Level: <i>Medium</i>
1074)     <br>
1075)     Skill Level: <i>Medium</i>
1076)     <br>

1077)     Likely Mentors: <i>Damian (atagar), Sebastian</i>

1078)     <p>

1079)     <a href="https://stem.torproject.org/">Stem</a> is a

1080)     python controller library for tor. Like it's predecessor, <a

1081)     href="https://gitweb.torproject.org/pytorctl.git">TorCtl</a>, it uses tor's <a

1082)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control
1083)     protocol</a> to help developers program against the tor process, enabling
1084)     them to build things similar to <a href="#project-vidalia">Vidalia</a> and

1085)     <a href="https://www.atagar.com/arm/">arm</a>.

1086)     </p>

1087) 

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

1094) 

1095)     <p>

1096)     Stem has largely met these goals but there's still plenty of low hanging
1097)     fruit in terms of usability improvements. Also, we have clients still using

1098)     TorCtl that need to be ported over. This project would include several
1099)     subtasks. Some ideas for instance are...

1100)     </p>

1101) 

1102)     <ol>
1103)       <li>Come up with a better, more developer friendly "Module Overview" for our documentation (<a href="https://stem.torproject.org/api/control.html">example page</a>). For instance, it would be nice to provide interlinking between the overview and the classes/methods that it lists. This will probably involve asking for help from the <a href="http://sphinx-doc.org/">Sphinx user list</a>. (<a href="https://trac.torproject.org/7632">ticket</a>)</li>

1104)       <li>After getting some exposure to stem it would be time to give using it a try. Tor has a couple clients (<a href="https://trac.torproject.org/8263">TorBEL</a> and <a href="https://trac.torproject.org/8264">Tor Weather</a>) that are ready to be moved to stem. Hopefully porting these will also provide us with some lessons on how we can further improve stem's API. <b>Note that this would also involve polishing off <a href="#project-torbel">TorBEL</a>, including the <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&group=component&component=TorDNSEL%2FTorBEL&order=priority">issues that prevent us from deploying it</a></b>. This later portion would be primarily mentored by Sebastian.</li>

1105)       <li><b>... other ideas?</b> The above are just some ideas I've come up with to improve usability and likely not enough to fill the summer. Feel free to suggest some of your own! For instance, one option would be to expand <a href="https://stem.torproject.org/tutorials.html">stem's tutorials</a> with more examples, maybe <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">contacting tor-dev@</a> to brainstorm ideas. This last bit is pretty open so I look forward to seeing what you come up with!</li>

1106)     </ol>

1107) 

1108)     <p>

1109)     <b>As part of your application for this project please write a script that does something interesting with stem.</b> Bonus points if this is something that we can <a href="https://stem.torproject.org/tutorials.html">make a tutorial</a> around!

1110)     </p>

1111) 

1112)     <a id="stemTestingForTor"></a>
1113)     <li>
1114)     <b>Stem Tests for Tor</b>
1115)     <br>
1116)     Effort Level: <i>Medium</i>
1117)     <br>
1118)     Skill Level: <i>Medium</i>
1119)     <br>
1120)     Likely Mentors: <i>Damian (atagar)</i>
1121)     <p>
1122)     Stem is a library for interacting with Tor (see '<a href="#stemUsability">Stem Usability and Porting</a>' above for a summary). The library has both <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/unit">unit</a> and <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/integ">integration</a> tests. The unit tests provide a quick, direct test of stem's codebase while the integration test exercises its functionality against a live instance of Tor.
1123)     </p>
1124) 
1125)     <p>
1126)     Stem's integration tests have thus far been (unsurprisingly) designed to test stem but there's no need for them to be limited to that. Stem is a complete implementation of Tor's <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control-spec</a> and <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt">dir-spec</a>. As such, stem's tests could be easily expanded to more dedicatedly test behavior involved in those portions of Tor's codebase, as well as provide a smoke test for its general functionality.
1127)     </p>
1128) 
1129)     <p>
1130)     This project would involve several components:
1131)     </p>
1132) 
1133)     <ol>
1134)       <li>Determine what kind of tests we need. <b>This should be done during the application phase</b> by <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">contacting tor-dev@</a>. Hopefully this will give us an idea of what would be the most useful kind of tests of this nature for Tor development.</li>

1135)       <li>Our <a href="https://jenkins.torproject.org/job/stem-tor-ci/">automated testing environment</a> presently sends the test output when they fail. We should think about having our tests optionally provide html formatted results (maybe this is something a testing framework can already provide?).</li>

1136)       <li>Implement the new suite of integration tests for Tor. This will likely include expanding Tor to support better testability. One useful candidate, for instance, would be a controller method to fetch our own descriptor. This would let us easily test various configurations to see if they provide valid descriptor content.</li>
1137)     </ol>
1138) 
1139)     <p>

1140)     <b>As part of your application for this project please write some code to expand stem's tests.</b> Bonus points if it implements one of your suggestions for better testing Tor!

1141)     </p>
1142) 

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

1144)     <li>

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

1146)     <br>

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

1148)     <br>

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

1150)     <br>

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

1152)     <p>

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

1161)     </p>

1162) 

1163)     <p>

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

1169)     </p>

1170) 

1171)     <p>

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

1176)     </p>

1177) 
1178)     <p>
1179)     <b>As part of your application for this project please identify one of the
1180)     thorniest Tor functions and submit a patch refactoring it to be better. If
1181)     you find this to be difficult then this likely isn't the project for
1182)     you.</b>
1183)     </p>

1184)     </li>

1185) 

1186)     <a id="ooniprobeSimulator"></a>
1187)     <li>
1188)     <b>Create an Internet Censorship Virtual Machine Based Simulator</b>
1189)     <br>
1190)     Effort Level: <i>Medium</i>
1191)     <br>
1192)     Skill Level: <i>Medium</i>
1193)     <br>
1194)     Likely Mentors: <i>hellais</i>
1195)     <p>
1196)     The purpose of this is to create a virtual machine based environment for
1197)     recreating censorship. The task of the student will be to document and
1198)     implement a system that allows you to recreated a censored network with the
1199)     purpose of testing the proper functioning of ooniprobe tests.
1200)     </p>
1201) 
1202)     <p>
1203)     Some ideas of things that would be useful to have be emulated by the test
1204)     lab:
1205)     </p>
1206) 
1207)     <ul>
1208)       <li>A transparent HTTP proxy (based on squid)</li>
1209)       <li>NAT traversal</li>
1210)       <li>HTTP proxy blocking certain sites</li>
1211)       <li>DNS based censorship</li>
1212)     </ul>
1213) 
1214)     <p>
1215)     The process of setting up the virtual machines and simulating censorship
1216)     should be fully automated (<a
1217)     href="https://trac.torproject.org/projects/tor/ticket/7233">related
1218)     ticket</a>).
1219)     </p>
1220)     </li>
1221) 

1222)     <a id="steganographyBrowserAddon"></a>
1223)     <li>
1224)     <b>Steganography Browser Addon</b>
1225)     <br>
1226)     Effort Level: <i>Medium</i>
1227)     <br>
1228)     Skill Level: <i>Medium</i>
1229)     <br>
1230)     Likely Mentors: <i>sukhbir, Moritz (gamambel)</i>
1231)     <p>
1232)     To facilitate the sharing of bridge addresses and other secrets, we want
1233)     a browser addon that detects steganographically and  asymmetrically
1234)     encrypted content embedded in website content. It would ship with a set
1235)     of preconfigured keys, as well as allow users to modify that set.
1236)     Additionally, it should be able to embed secrets. It must be written in
1237)     an extensible way, so that other steganography libraries and supported
1238)     media types can be added to the code easily.
1239)     </p>
1240) 
1241)     <p>
1242)     As part of your application for this project assess the current state of
1243)     Javascript steganography libraries, tell us which one you would pick
1244)     primarily, and why. Ideally, your application comes with some mockups of
1245)     how parts of the user interface of your addon would look like.
1246)     </p>

1247) 
1248)     <p>
1249)     For more information see the <a
1250)     href="http://www.cs.kau.se/philwint/censorbib/#Invernizzi2012">Message In A
1251)     Bottle: Sailing Past Censorship</a> research paper.
1252)     </p>

1253)     </li>
1254) 

1255)     <a id="betterPluggableTransports"></a>
1256)     <li>
1257)     <b>Build Better Pluggable Transports</b>
1258)     <br>
1259)     Effort Level: <i>Medium to High</i>
1260)     <br>
1261)     Skill Level: <i>Medium</i>
1262)     <br>
1263)     Likely Mentors: <i>Steven (sjmurdoch)</i>
1264)     <p>
1265)     For Tor users in censored countries, we currently offer <a
1266)     href="https://www.torproject.org/projects/obfsproxy.html.en">obfsproxy</a>
1267)     bridges, which disguise Tor traffic by making it look random. This works
1268)     for many users, but it has disadvantages: firstly it does not disguise
1269)     packet size and secondly it looks like no real protocol. These weaknesses
1270)     may result in obfsproxy being blocked.
1271)     </p>
1272) 
1273)     <p>
1274)     The goal for this project will be to implement new pluggable transports,
1275)     which resolve these weaknesses and so can be deployed if/when obfsproxy is
1276)     blocked. Ideas for doing so include:
1277)       <ul>
1278)         <li>Impersonate a voice-over-IP protocol</li>
1279)         <li>Impersonate HTTP sufficiently well that traffic will go through a HTTP-only proxy</li>
1280)         <li>Implement <a href="http://cacr.uwaterloo.ca/techreports/2011/cacr2011-21.pdf">scanning resistance</a></a>
1281)       </ul>
1282)     </p>
1283) 
1284)     <a id="profileUDPTransport"></a>
1285)     <li>
1286)     <b>Profile UDP transport protocols</b>
1287)     <br>
1288)     Effort Level: <i>Medium to High</i>
1289)     <br>
1290)     Skill Level: <i>High</i>
1291)     <br>
1292)     Likely Mentors: <i>Steven (sjmurdoch)</i>
1293)     <p>
1294)     There are <a
1295)     href="https://research.torproject.org/techreports/datagram-comparison-2011-11-07.pdf">lots
1296)     of options</a> as to how Tor could send its data over UDP rather than TCP,
1297)     and some will likely perform significantly better than others. This project
1298)     will evaluate these options, so as to decide which should be used in future
1299)     versions of Tor. A first step will be to benchmark the various transport
1300)     protocols being considered, in terms of performance and also code quality,
1301)     including userspace TCP, <a
1302)     href="https://github.com/bittorrent/libutp">&mu;TP</a>, <a
1303)     href="http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol">SCTP</a>
1304)     and <a href="http://curvecp.org/">CurveCP</a>. Initially these transport
1305)     protocols will be examined in isolation, but if the project progresses well
1306)     one or more could be integrated in Tor.
1307)     </p>
1308)     </li>
1309) 

1310)     <a id="reportingBuggyRulesets"></a>
1311)     <li>
1312)     <b>Automated Reporting of Buggy Rulesets</b>
1313)     <br>
1314)     Effort Level: <i>Medium</i>
1315)     <br>
1316)     Skill Level: <i>Medium</i>
1317)     <br>

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

1319)     <p>
1320) When users manually disable an HTTPS Everywhere ruleset via the toolbar menu,
1321) that's a strong hint that that ruleset might be buggy.  If we could obtain
1322) statistics about which rulesets are manually disabled by the users of which
1323) HTTPS E versions, we could get a statistical picture of which rulesets need
1324) the most urgent debugging and/or disablement.  This would enormously improve
1325) the quality of the HTTPS Everywhere user experience.
1326)     </p>
1327) 
1328)     <p>
1329) HTTPS Everywhere already includes a pipeline for anonymised user submissions
1330) (via Tor where available) that is used for the Decentralized SSL Observatory.
1331) We should do a popup that asks the users to submit anonymous reports of
1332) disabled rules, when they manually disable one for the first time.
1333)     </p>
1334) 
1335)     <p>
1336) Perhaps this feature could optionally let users submit the URL of the page
1337) they were looking at when the bug occurred, although we would need to take
1338) care in handling those, and perhaps implement some countermeasures against
1339) sending passwords or auth tokens when URLs contain those.
1340)     </p>
1341)     </li>
1342) 
1343)     <a id="httpsEverywhereForFirefoxModile"></a>
1344)     <li>
1345)     <b>Port HTTPS Everywhere to Firefox Mobile</b>
1346)     <br>
1347)     Effort Level: <i>Medium</i>
1348)     <br>
1349)     Skill Level: <i>Medium</i>
1350)     <br>

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

1352)     <p>
1353) In the past a Firefox Mobile port of HTTPS Everywhere was made impractically
1354) complicated by the Electrolysis threading architecture used in that variant of
1355) Firefox (<a href="https://trac.torproject.org/projects/tor/ticket/2471">ticket</a>).  However with
1356) the implementation of the simple NSIHTTPChannel.redirectTo() API in Firefox
1357) 20+ (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=765934">ticket</a>) we are probably very
1358) close to having a trivial port of HTTPS Everywhere to Firefox on Android.
1359)     </p>
1360) 
1361)     <p>
1362) This would make a great GSOC project for someone who'd like to learn some
1363) introductory skills with hacking on the internals of real web browsers!
1364)     </p>
1365)     </li>
1366) 
1367)     <a id="httpsEverywhereMixedContentHandling"></a>
1368)     <li>
1369)     <b>HTTPS Everywhere mixed content detection and handling</b>
1370)     <br>
1371)     Effort Level: <i>Medium</i>
1372)     <br>
1373)     Skill Level: <i>Medium</i>
1374)     <br>

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

1376)     <p>
1377) Since version 20, Chrome has automatically blocked the loading of insecure
1378) HTTP scripts and CSS in HTTPS pages.  Firefox version 23 will do the same.
1379) This is good security practice, but it causes havoc with many sites where
1380) HTTPS Everywhere can secure some, but not all, of the site's content.
1381)     </p>
1382) 
1383)     <p>
1384) Before Firefox 23 launches, we will need a more coherent plan for detecting
1385) sites where we are causing these mixed content situations, and either
1386) disabling or working around the limitation.  Failure to do so will mean that
1387) HTTPS Everywhere user experience worsens dramatically when Firefox 23 is
1388) released.  Success will mean a dramatic improvement in user experience with
1389) HTTPS Everywhere for Chrome.
1390)     </p>
1391) 
1392)     <b>Critical-path tickets:</b>
1393) 
1394)     <ul>
1395)       <li><a href="https://trac.torproject.org/projects/tor/ticket/6975">6975</a></li>
1396)       <li><a href="https://trac.torproject.org/projects/tor/ticket/8664">8664</a></li>
1397)       <li><a href="https://trac.torproject.org/projects/tor/ticket/8776">8776</a></li>
1398)     </ul>
1399) 
1400)     <b>Related tickets:</b>
1401) 
1402)     <ul>
1403)       <li><a href="https://trac.torproject.org/projects/tor/ticket/3777">3777</a></li>
1404)       <li><a href="https://trac.torproject.org/projects/tor/ticket/6977">6977</a></li>
1405)     </ul>
1406)     </li>
1407) 
1408)     <a id="httpsEverywhereRulesetTesting"></a>
1409)     <li>
1410)     <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>
1411)     <br>
1412)     Effort Level: <i>Medium</i>
1413)     <br>
1414)     Skill Level: <i>Medium</i>
1415)     <br>

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

1417)     <p>
1418) Ondrej Mikle has implemented a codebase for testing HTTPS Everywhere rulesets
1419) by crawling pages that are affected by the ruleset (<a href="https://github.com/hiviah/https-everywhere-checker">repository</a>).
1420)     </p>
1421) 
1422)     <p>
1423) This codebase still has some rough edges that need to be smoothed over, but
1424) once those are done it should be incorporated into the HTTPS Everywhere build
1425) process, in order to improve the quality of our releases.
1426)     </p>
1427)     </li>
1428) 

1429)     <a id="censorshipAnalyzer"></a>
1430)     <li>
1431)     <b>Develop a Censorship Analyzer</b>
1432)     <br>
1433)     Effort Level: <i>Medium</i>
1434)     <br>
1435)     Skill Level: <i>Medium to High (depends on the implemented tests)</i>
1436)     <br>
1437)     Likely Mentors: <i>Philipp (phw)</i>
1438)     <p>
1439) Tor is documented to be blocked in <a
1440) href="https://censorshipwiki.torproject.org">several countries</a>. Analyzing
1441) these censorship incidents can be a tedious task; especially without access to
1442) machines inside the censoring networks. To make analysis easier, it would be
1443) great to have a lightweight analysis tool which can be run by censored users.
1444) This tool would conduct a number of networking tests and figure out if and how
1445) Tor could be blocked. The tool's final report should then somehow make it back
1446) to the Tor project.
1447)     </p>
1448) 
1449)     <p>
1450) The theory behind this tool is already <a

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

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

1459)     <li>
1460)     <b>Bring up new ideas!</b>

1461)     <br>

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

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

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

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

1467)     might also be short on developers.
1468)     </li>

1469) 

1470)     </ol>

1471) 

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

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

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

1487) 

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

1493) 

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

1503) 

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

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

1508)     Tor if needed.</li>

1509) 

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

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

1515) 

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

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

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

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

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

1526) 

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

1530) 

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

1537) 

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

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

1541)     System</a>.
1542)     </li>

1543) 

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

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

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

1556) 

1557)     </ol>

1558) 

1559)     <a id="Research"></a>
1560)     <h2><a class="anchor" href="#Research">Research</a></h2>
1561)     <ol>
1562)     <li>The "end-to-end traffic confirmation attack":
1563)     by watching traffic at Alice and at Bob, we can <a
1564)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1565)     traffic signatures and become convinced that we're watching the same
1566)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1567)     attack is trivial in all cases. First of all, is that actually true? How
1568)     much traffic of what sort of distribution is needed before the adversary
1569)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1570)     that slow down the attack? Do some traffic padding or traffic shaping
1571)     schemes work better than others?</li>
1572)     <li>A related question is: Does running a relay/bridge provide additional
1573)     protection against these timing attacks? Can an external adversary that can't
1574)     see inside TLS links still recognize individual streams reliably?
1575)     Does the amount of traffic carried degrade this ability any? What if the
1576)     client-relay deliberately delayed upstream relayed traffic to create a queue
1577)     that could be used to mimic timings of client downstream traffic to make it
1578)     look like it was also relayed? This same queue could also be used for masking
1579)     timings in client upstream traffic with the techniques from <a
1580)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1581)     but without the need for additional traffic. Would such an interleaving of
1582)     client upstream traffic obscure timings for external adversaries? Would the
1583)     strategies need to be adjusted for asymmetric links? For example, on
1584)     asymmetric links, is it actually possible to differentiate client traffic from
1585)     natural bursts due to their asymmetric capacity? Or is it easier than
1586)     symmetric links for some other reason?</li>
1587)     <li>Repeat Murdoch and Danezis's <a
1588)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1589)     Oakland 05</a> on the current Tor network. See if you can learn why it
1590)     works well on some nodes and not well on others. (My theory is that the
1591)     fast nodes with spare capacity resist the attack better.) If that's true,
1592)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1593)     options to run a relay that is used as a client while relaying the
1594)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1595)     attack get harder? What's the right ratio of RelayBandwidthRate to
1596)     actually capacity? Or is it a ratio at all? While we're at it, does a
1597)     much larger set of candidate relays increase the false positive rate
1598)     or other complexity for the attack? (The Tor network is now almost two
1599)     orders of magnitude larger than it was when they wrote their paper.) Be
1600)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1601)     Clog the Queue</a> too.</li>
1602)     <li>The "routing zones attack": most of the literature thinks of
1603)     the network path between Alice and her entry node (and between the
1604)     exit node and Bob) as a single link on some graph. In practice,
1605)     though, the path traverses many autonomous systems (ASes), and <a
1606)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1607)     that the same AS appears on both the entry path and the exit path</a>.
1608)     Unfortunately, to accurately predict whether a given Alice, entry,
1609)     exit, Bob quad will be dangerous, we need to download an entire Internet
1610)     routing zone and perform expensive operations on it. Are there practical
1611)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1612)     <li>Other research questions regarding geographic diversity consider
1613)     the tradeoff between choosing an efficient circuit and choosing a random
1614)     circuit. Look at Stephen Rollyson's <a
1615)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1616)     paper</a> on how to discard particularly slow choices without hurting
1617)     anonymity "too much". This line of reasoning needs more work and more
1618)     thinking, but it looks very promising.</li>
1619)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1620)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1621)     each hop, if the incoming bytes are arriving just fine and the outgoing
1622)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1623)     don't really transmit this information back to the incoming streams.
1624)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1625)     and rate-limit incoming streams to regulate this itself? I can imagine
1626)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1627)     slowly increase it until we get lost packets, back off, repeat. We
1628)     need somebody who's good with networks to simulate this and help design
1629)     solutions; and/or we need to understand the extent of the performance
1630)     degradation, and use this as motivation to reconsider UDP transport.</li>
1631)     <li>A related topic is congestion control. Is our
1632)     current design sufficient once we have heavy use? Maybe
1633)     we should experiment with variable-sized windows rather
1634)     than fixed-size windows? That seemed to go well in an <a

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

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

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

1661)     your browser's UserAgent string by replacing it with a uniform answer for
1662)     every Tor user. That way the attacker can't splinter Tor's anonymity set
1663)     by looking at that header. It tries to pick a string that is commonly used
1664)     by non-Tor users too, so it doesn't stand out. Question one: how badly
1665)     do we hurt ourselves by periodically updating the version of Firefox
1666)     that Torbutton claims to be? If we update it too often, we splinter the
1667)     anonymity sets ourselves. If we don't update it often enough, then all the
1668)     Tor users stand out because they claim to be running a quite old version
1669)     of Firefox. The answer here probably depends on the Firefox versions seen
1670)     in the wild. Question two: periodically people ask us to cycle through N
1671)     UserAgent strings rather than stick with one. Does this approach help,
1672)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
1673)     by their rotating UserAgents; malicious websites who only attack certain
1674)     browsers; and whether the answers to question one impact this answer.
1675)     </li>
1676)     <li>How many bridge relays do you need to know to maintain
1677)     reachability? We should measure the churn in our bridges. If there is
1678)     lots of churn, are there ways to keep bridge users more likely to stay
1679)     connected?
1680)     </li>
1681)     </ol>

1682) 

1683)     <p>
1684)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1685)     of these!
1686)     </p>
1687)   </div>
1688)   <!-- END MAINCOL -->
1689)   <div id = "sidecol">
1690) #include "side.wmi"
1691) #include "info.wmi"
1692)   </div>
1693)   <!-- END SIDECOL -->
1694) </div>
1695) <!-- END CONTENT -->