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)     <table id="projects">
108)       <tr>
109)         <th>Name</th>
110)         <th>Category</th>
111)         <th>Language</th>
112)         <th>Activity</th>
113)         <th>Contributors</th>
114)       </tr>

115) 

116)       <tr>
117)         <td><a href="#project-tor">Tor</a></td>
118)         <td>Core</td>
119)         <td>C</td>
120)         <td>Heavy</td>

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

122)       </tr>

123) 

124)       <tr>

125)         <td>*<a href="#project-jtor">JTor</a></td>
126)         <td>Core</td>
127)         <td>Java</td>

128)         <td>Moderate</td>

129)         <td>bleidl</td>
130)       </tr>
131) 
132)       <tr>

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

134)         <td>Bundle</td>

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

136)         <td>Moderate</td>

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

138)       </tr>

139) 

140)       <tr>

141)         <td><a href="#project-torbutton">Torbutton</a></td>
142)         <td>Browser Add-on</td>
143)         <td>Javascript</td>
144)         <td>Moderate</td>
145)         <td>mikeperry</td>

146)       </tr>

147) 

148)       <tr>

149)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
150)         <td>Browser Add-on</td>
151)         <td>Javascript</td>

152)         <td>Heavy</td>

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

154)       </tr>

155) 

156)       <tr>

157)         <td><a href="#project-vidalia">Vidalia</a></td>
158)         <td>User Interface</td>
159)         <td>C++, Qt</td>

160)         <td>None</td>

161)         <td>chiiph</td>
162)       </tr>

163) 

164)       <tr>

165)         <td><a href="#project-arm">Arm</a></td>
166)         <td>User Interface</td>
167)         <td>Python, Curses</td>

168)         <td>Light</td>

169)         <td>atagar</td>
170)       </tr>

171) 

172)       <tr>

173)         <td><a href="#project-orbot">Orbot</a></td>
174)         <td>User Interface</td>
175)         <td>Java</td>

176)         <td>Light</td>

177)         <td>n8fr8</td>

178)       </tr>

179) 

180)       <tr>

181)         <td><a href="#project-tails">Tails</a></td>
182)         <td>OS image</td>
183)         <td>Sys Admin</td>
184)         <td>Heavy</td>
185)         <td><a href="https://tails.boum.org/">#tails</a></td>

186)       </tr>

187) 

188)       <tr>

189)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
190)         <td>OS image</td>
191)         <td>Sys Admin</td>

192)         <td>None</td>

193)         <td>blueness</td>
194)       </tr>
195) 

196)       <tr>

197)         <td>*<a href="#project-torouter">Torouter</a></td>
198)         <td>OS image</td>
199)         <td>Sys Admin</td>

200)         <td>None</td>

201)         <td>ioerror</td>
202)       </tr>
203) 

204)       <tr>

205)         <td><a href="#project-torsocks">Torsocks</a></td>
206)         <td>Usability</td>
207)         <td>C</td>

208)         <td>Light</td>

209)         <td>ioerror, nickm</td>
210)       </tr>
211) 

212)       <tr>

213)         <td><a href="#project-torbirdy">TorBirdy</a></td>
214)         <td>Browser Add-on</td>
215)         <td>JavaScript</td>
216)         <td>Heavy</td>

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

218)       </tr>

219) 

220)       <tr>

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

223)         <td>Python</td>

224)         <td>Moderate</td>

225)         <td>asn</td>

226)       </tr>
227) 

228)       <tr>

229)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
230)         <td>Client Add-on</td>
231)         <td>Python, JavaScript, Go</td>

232)         <td>Heavy</td>

233)         <td>dcf, aallai, jct</td>
234)       </tr>

235) 

236)       <tr>

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

238)         <td>Simulator</td>

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

240)         <td>Heavy</td>

241)         <td>robgjansen</td>
242)       </tr>

243) 

244)       <tr>

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

246)         <td>Library</td>
247)         <td>Python</td>
248)         <td>Heavy</td>

249)         <td>atagar</td>

250)       </tr>

251) 

252)       <tr>

253)         <td><a href="#project-txtorcon">Txtorcon</a></td>
254)         <td>Library</td>
255)         <td>Python, Twisted</td>

256)         <td>Moderate</td>

257)         <td>meejah</td>
258)       </tr>

259) 

260)       <tr>

261)         <td><a href="#project-tlsdate">Tlsdate</a></td>
262)         <td>Utility</td>
263)         <td>C</td>

264)         <td>Moderate</td>

265)         <td>ioerror</td>
266)       </tr>

267) 

268)       <tr>

269)         <td><a href="#project-metrics">Metrics</a></td>
270)         <td>Client Service</td>
271)         <td>Java</td>

272)         <td>Moderate</td>

273)         <td>karsten</td>
274)       </tr>

275) 

276)       <tr>

277)         <td><a href="#project-atlas">Atlas</a></td>
278)         <td>Client Service</td>
279)         <td>JavaScript</td>

280)         <td>Light</td>

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

282)       </tr>

283) 

284)       <tr>
285)         <td><a href="#project-globe">Globe</a></td>
286)         <td>Client Service</td>
287)         <td>JavaScript</td>
288)         <td>Heavy</td>
289)         <td>Christian</td>
290)       </tr>
291) 

292)       <tr>

293)         <td><a href="#project-compass">Compass</a></td>
294)         <td>Client Service</td>
295)         <td>Python</td>

296)         <td>Light</td>

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

298)       </tr>

299) 

300)       <tr>

301)         <td><a href="#project-onionoo">Onionoo</a></td>
302)         <td>Backend Service</td>
303)         <td>Java, Python</td>

304)         <td>Moderate</td>

305)         <td>karsten, gsathya</td>
306)       </tr>
307) 

308)       <tr>
309)         <td><a href="#project-doctor">DocTor</a></td>
310)         <td>Backend Service</td>
311)         <td>Python</td>
312)         <td>Light</td>
313)         <td>atagar</td>
314)       </tr>
315) 

316)       <tr>

317)         <td><a href="#project-weather">Weather</a></td>
318)         <td>Client Service</td>
319)         <td>Python</td>

320)         <td>None</td>

321)         <td>kaner</td>
322)       </tr>

323) 

324)       <tr>

325)         <td><a href="#project-gettor">GetTor</a></td>
326)         <td>Client Service</td>
327)         <td>Python</td>

328)         <td>None</td>

329)         <td>kaner</td>

330)       </tr>

331) 

332)       <tr>

333)         <td><a href="#project-torcheck">TorCheck</a></td>
334)         <td>Client Service</td>
335)         <td>Python, Perl</td>
336)         <td>None</td>

337)         <td>ioerror</td>

338)       </tr>

339) 

340)       <tr>

341)         <td><a href="#project-bridgedb">BridgeDB</a></td>
342)         <td>Backend Service</td>
343)         <td>Python</td>

344)         <td>Light</td>

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

346)       </tr>

347) 

348)       <tr>

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

350)         <td>Scanner</td>
351)         <td>Python</td>

352)         <td>Moderate</td>

353)         <td>hellais, isis, ioerror</td>
354)       </tr>
355) 

356)       <tr>
357)         <td><a href="#project-torps">TorPS</a></td>
358)         <td>Backend Service</td>
359)         <td>Python</td>
360)         <td>Light</td>
361)         <td>Aaron Johnson</td>
362)       </tr>
363) 

364)       <tr>

365)         <td><a href="#project-torflow">TorFlow</a></td>
366)         <td>Backend Service</td>
367)         <td>Python</td>

368)         <td>None</td>

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

370)       </tr>

371) 

372)       <tr>

373)         <td>*<a href="#project-torbel">TorBEL</a></td>
374)         <td>Backend Service</td>
375)         <td>Python</td>
376)         <td>None</td>
377)         <td>Sebastian</td>
378)       </tr>

379) 

380)       <tr>

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

383)         <td>Python</td>

384)         <td>Moderate</td>

385)         <td>hellais</td>

386)       </tr>

387) 

388)       <tr>

389)         <td><a href="#project-anonbib">Anonbib</a></td>
390)         <td>Website</td>

391)         <td>Python</td>

392)         <td>Light</td>
393)         <td>arma, nickm</td>
394)       </tr>
395) 

396)     </table>

397) 

398)     <sub>
399)     * Project is still in an alpha state.
400)     </sub>

401) 

402)     <br /><br />

403) 

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

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

407)     tracker</a>)</h3>

408) 

409)     <p>
410)     Central project, providing the core software for using and participating in
411)     the Tor network. Numerous people contribute to the project to varying
412)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
413)     </p>

414) 

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

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

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

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

421)     </p>

422) 

423)     <a id="project-jtor"></a>
424)     <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a

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

426)     href="https://github.com/brl/JTor/issues">bug
427)     tracker</a>)</h3>

428) 

429)     <p>
430)     Java implementation of Tor and successor to <a
431)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
432)     isn't yet complete, and has been inactive since Fall 2010.
433)     </p>

434) 

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

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

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

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

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

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

446)     </p>

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

452)     tracker</a>)</h3>

453) 

454)     <p>

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

460)     </p>

461) 
462)     <a id="project-httpseverywhere"></a>
463)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
464)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
465)     href="https://trac.torproject.org/projects/tor/report/19">bug

466)     tracker</a>)</h3>

467) 

468)     <p>

469)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
470)     your communications with many major websites, making your browsing
471)     more secure.

472)     </p>

473) 

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

476)     href="https://gitweb.torproject.org/vidalia.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=Vidalia&order=priority">bug
478)     tracker</a>)</h3>

479) 

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

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

485)     </p>

486) 

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

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

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

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

492) 

493)     <p>

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

499)     </p>

500) 

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

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

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

506) 
507)     <p>
508)     Provides Tor on the Android platform. This was under very active
509)     development up through Fall 2010, after which things have been quiet.
510)     </p>
511) 
512)     <a id="project-tails"></a>
513)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

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

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

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

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

530) 
531)     <p>

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

534)     </p>
535) 

536)     <a id="project-torouter"></a>
537)     <h3><a
538)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

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

549)     <h3>Torsocks (<a

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

554)     <p>

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

558)     </p>

559) 

560)     <a id="project-torbirdy"></a>
561)     <h3>TorBirdy (<a
562)     href="https://github.com/ioerror/torbirdy">code</a>, <a
563)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
564)     tracker</a>)</h3>

565) 

566)     <p>
567)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
568)     </p>

569) 

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

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

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

574)     tracker</a>)</h3>

575) 

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

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

579)     </p>

580) 

581)     <p>
582)     <b>Project Ideas:</b><br />
583)     <i><a href="#betterPluggableTransports">Build Better Pluggable Transports</a></i>
584)     </p>
585) 

586)     <a id="project-flash-proxy"></a>
587)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
588)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
589)     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
590)     tracker</a>)</h3>

591) 

592)     <p>
593)     Pluggable transport using proxies running in web browsers to defeat
594)     address-based blocking.
595)     </p>

596) 

597)     <a id="project-shadow"></a>
598)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
599)     href="https://github.com/shadow">code</a>, <a
600)     href="https://github.com/shadow/shadow/issues">bug
601)     tracker</a>)</h3>

602) 

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

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

609)     </p>

610) 

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

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

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

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

615)     tracker</a>)</h3>

616) 

617)     <p>

618)     Python controller library for scripts and controller applications using
619)     Tor.

620)     </p>

621) 

622)     <p>
623)     <b>Project Ideas:</b><br />

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

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

627)     </p>

628) 

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

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

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

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

633) 

634)     <p>
635)     Twisted-based asynchronous Tor control protocol implementation. Includes
636)     unit-tests, examples, state-tracking code and configuration abstraction.
637)     Used by OONI and APAF.
638)     </p>

639) 

640)     <p>
641)     <b>Project Ideas:</b><br />
642)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
643)     </p>
644) 

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

647) 

648)     <p>
649)     tlsdate: secure parasitic rdate replacement
650)     </p>

651) 

652)     <p>
653)     tlsdate sets the local clock by securely connecting with TLS to remote
654)     servers and extracting the remote time out of the secure handshake. Unlike
655)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
656)     enabled service, and provides some protection against adversaries that try
657)     to feed you malicious time information.
658)     </p>

659) 

660)     <a id="project-metrics"></a>
661)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
662)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
663)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a

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

665) 

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

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

671)     </p>

672) 

673)     <p>
674)     <b>Project Ideas:</b><br />
675)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
676)     </p>

677) 

678)     <a id="project-atlas"></a>
679)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
680)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

681) 

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

685)     their past usage.

686)     </p>

687) 

688)     <p>

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

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

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

694)     </p>

695) 

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

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

712) 

713)     <p>
714)     Compass is a web and command line application that filters and
715)     aggregates the Tor relays based on various attributes.
716)     </p>

717) 
718)     <a id="project-onionoo"></a>
719)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a
720)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
721)     href="https://gitweb.torproject.org/pyonionoo.git">python

722)     codebase</a>, <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>

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

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

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

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

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

747) 

748)     <p>
749)     Provides automatic notification to subscribed relay operators when their
750)     relay's unreachable. This underwent a rewrite by the <a
751)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
752)     in early 2011.
753)     </p>

754) 

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

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

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

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

760) 

761)     <p>
762)     E-mail autoresponder providing Tor's packages over SMTP. This has been
763)     relatively unchanged for quite a while.
764)     </p>

765) 

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

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

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

771) 

772)     <p>
773)     Provides a simple site for determining if the visitor is using Tor or not.
774)     This has been relatively unchanged for quite a while.
775)     </p>

776) 

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

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

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

782) 

783)     <p>
784)     Backend bridge distributor, handling the various pools they're distributed
785)     in. This was actively developed until Fall of 2010.
786)     </p>

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

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

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

799)     <p>
800)     <b>Project Ideas:</b><br />

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

803)     </p>
804) 

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

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

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

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

820) 

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

829) 

830)     <a id="project-torbel"></a>
831)     <h3><a

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

834)     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
835)     tracker</a>)</h3>

836) 

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

844) 

845)     <p>
846)     <b>Project Ideas:</b><br />
847)     <i><a href="#stemUsability">Stem Usability and Porting (this includes an idea for finishing off TorBEL)</a></i>
848)     </p>
849) 

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

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

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

871)     </p>
872) 

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

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

876) 

877)     <p>

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

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

888)     </p>

889) 

890)     <ol>

891) 

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

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

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

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

928)     <li>
929)     <b>HTTPS Server Impersonation</b>
930)     <br>
931)     Effort Level: <i>Medium to High</i>
932)     <br>
933)     Skill Level: <i>Medium to High</i>
934)     <br>
935)     Likely Mentors: <i>Nick (nickm)</i>

936)     <p>

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

943)     </p>

944) 
945)     <p>
946)     <b>This project is likely trickier than it looks. You should avoid applying
947)     for this if you're uncertain about being able to complete it.</b>
948)     </p>
949)     </li>

950)     </li>

951) 

952)     <a id="chutneyExpansion"></a>
953)     <li>
954)     <b>Make Chutney Do More, More Reliably</b>
955)     <br>
956)     Effort Level: <i>Medium to High, depending on scope of project</i>
957)     <br>
958)     Skill Level: <i>Medium</i>
959)     <br>

960)     Likely Mentors: <i>Nick (nickm)</i>
961)     <p>

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

966)     </p>

967) 

968)     <p>

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

972)     </p>

973) 
974)     <p>
975)     <b>As part of your application for this project please submit a patch that
976)     expands Chutney.</b>
977)     </p>
978) 

979)     </li>

980) 

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

982)     <li>

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

984)     <br>
985)     Effort Level: <i>Medium to High</i>
986)     <br>

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

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

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

994)     </p>

995) 

996)     <p>

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

1006)     </p>

1007) 

1008)     <p>

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

1012)     </p>
1013)     </li>

1014) 

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

1016)     <li>

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

1018)     <br>
1019)     Effort Level: <i>Medium</i>
1020)     <br>
1021)     Skill Level: <i>Medium</i>
1022)     <br>

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

1032) 

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

1044) 

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

1055) 

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

1060)     </li>

1061) 

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

1063)     <li>

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

1065)     <br>
1066)     Effort Level: <i>Medium</i>
1067)     <br>
1068)     Skill Level: <i>Medium</i>
1069)     <br>

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

1071)     <p>

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

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

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

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

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

1079)     </p>

1080) 

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

1087) 

1088)     <p>

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

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

1093)     </p>

1094) 

1095)     <ol>
1096)       <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>

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

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

1099)     </ol>

1100) 

1101)     <p>

1102)     <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!

1103)     </p>

1104) 

1105)     <a id="stemTestingForTor"></a>
1106)     <li>
1107)     <b>Stem Tests for Tor</b>
1108)     <br>
1109)     Effort Level: <i>Medium</i>
1110)     <br>
1111)     Skill Level: <i>Medium</i>
1112)     <br>
1113)     Likely Mentors: <i>Damian (atagar)</i>
1114)     <p>
1115)     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.
1116)     </p>
1117) 
1118)     <p>
1119)     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.
1120)     </p>
1121) 
1122)     <p>
1123)     This project would involve several components:
1124)     </p>
1125) 
1126)     <ol>
1127)       <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>

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

1129)       <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>
1130)     </ol>
1131) 
1132)     <p>

1133)     <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!

1134)     </p>
1135) 

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

1137)     <li>

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

1139)     <br>

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

1141)     <br>

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

1143)     <br>

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

1145)     <p>

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

1154)     </p>

1155) 

1156)     <p>

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

1162)     </p>

1163) 

1164)     <p>

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

1169)     </p>

1170) 
1171)     <p>
1172)     <b>As part of your application for this project please identify one of the
1173)     thorniest Tor functions and submit a patch refactoring it to be better. If
1174)     you find this to be difficult then this likely isn't the project for
1175)     you.</b>
1176)     </p>

1177)     </li>

1178) 

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

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

1240) 
1241)     <p>
1242)     For more information see the <a
1243)     href="http://www.cs.kau.se/philwint/censorbib/#Invernizzi2012">Message In A
1244)     Bottle: Sailing Past Censorship</a> research paper.
1245)     </p>

1246)     </li>
1247) 

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

1303)     <a id="reportingBuggyRulesets"></a>
1304)     <li>
1305)     <b>Automated Reporting of Buggy Rulesets</b>
1306)     <br>
1307)     Effort Level: <i>Medium</i>
1308)     <br>
1309)     Skill Level: <i>Medium</i>
1310)     <br>

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

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

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

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

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

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

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

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

1422)     <a id="censorshipAnalyzer"></a>
1423)     <li>
1424)     <b>Develop a Censorship Analyzer</b>
1425)     <br>
1426)     Effort Level: <i>Medium</i>
1427)     <br>
1428)     Skill Level: <i>Medium to High (depends on the implemented tests)</i>
1429)     <br>
1430)     Likely Mentors: <i>Philipp (phw)</i>
1431)     <p>
1432) Tor is documented to be blocked in <a
1433) href="https://censorshipwiki.torproject.org">several countries</a>. Analyzing
1434) these censorship incidents can be a tedious task; especially without access to
1435) machines inside the censoring networks. To make analysis easier, it would be
1436) great to have a lightweight analysis tool which can be run by censored users.
1437) This tool would conduct a number of networking tests and figure out if and how
1438) Tor could be blocked. The tool's final report should then somehow make it back
1439) to the Tor project.
1440)     </p>
1441) 
1442)     <p>
1443) The theory behind this tool is already <a
1444) href="https://www.usenix.org/system/files/conference/foci13/foci13-winter.pdf">documented
1445) in a research paper</a>. What we now need is code! Implementing it would first
1446) mean getting familiar with <a href="https://ooni.torproject.org">OONI</a> and
1447) <a href="http://twistedmatrix.com/trac/">Twisted</a>. After that, the tool
1448) should be implemented as a number of OONI-specific networking tests.
1449)     </p>
1450)     </li>
1451) 

1452)     <li>
1453)     <b>Bring up new ideas!</b>

1454)     <br>

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

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

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

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

1460)     might also be short on developers.
1461)     </li>

1462) 

1463)     </ol>

1464) 

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

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

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

1480) 

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

1486) 

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

1496) 

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

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

1501)     Tor if needed.</li>

1502) 

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

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

1508) 

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

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

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

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

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

1519) 

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

1523) 

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

1530) 

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

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

1534)     System</a>.
1535)     </li>

1536) 

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

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

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

1549) 

1550)     </ol>

1551) 

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

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

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

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

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

1675) 

1676)     <p>
1677)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1678)     of these!
1679)     </p>
1680)   </div>
1681)   <!-- END MAINCOL -->
1682)   <div id = "sidecol">
1683) #include "side.wmi"
1684) #include "info.wmi"
1685)   </div>
1686)   <!-- END SIDECOL -->
1687) </div>
1688) <!-- END CONTENT -->