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)     <a id="Projects"></a>
71)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

72) 

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

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

80)     </p>

81) 

82)     <table id="projects">
83)       <tr>
84)         <th>Name</th>
85)         <th>Category</th>
86)         <th>Language</th>
87)         <th>Activity</th>
88)         <th>Contributors</th>
89)       </tr>

90) 

91)       <tr>
92)         <td><a href="#project-tor">Tor</a></td>
93)         <td>Core</td>
94)         <td>C</td>
95)         <td>Heavy</td>

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

97)       </tr>

98) 

99)       <tr class="alt">

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

101)         <td>Bundle</td>

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

103)         <td>Moderate</td>

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

105)       </tr>

106) 

107)       <tr>

108)         <td><a href="#project-torbutton">Torbutton</a></td>
109)         <td>Browser Add-on</td>
110)         <td>Javascript</td>
111)         <td>Moderate</td>
112)         <td>mikeperry</td>

113)       </tr>

114) 

115)       <tr class="alt">

116)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
117)         <td>Browser Add-on</td>
118)         <td>Javascript</td>
119)         <td>Moderate</td>
120)         <td>pde, mikeperry</td>

121)       </tr>

122) 

123)       <tr>

124)         <td><a href="#project-vidalia">Vidalia</a></td>
125)         <td>User Interface</td>
126)         <td>C++, Qt</td>

127)         <td>None</td>

128)         <td>chiiph</td>
129)       </tr>

130) 

131)       <tr class="alt">

132)         <td><a href="#project-arm">Arm</a></td>
133)         <td>User Interface</td>
134)         <td>Python, Curses</td>

135)         <td>Light</td>

136)         <td>atagar</td>
137)       </tr>

138) 

139)       <tr>

140)         <td><a href="#project-orbot">Orbot</a></td>
141)         <td>User Interface</td>
142)         <td>Java</td>

143)         <td>Light</td>

144)         <td>n8fr8</td>

145)       </tr>

146) 

147)       <tr class="alt">

148)         <td><a href="#project-tails">Tails</a></td>
149)         <td>OS image</td>
150)         <td>Sys Admin</td>
151)         <td>Heavy</td>
152)         <td><a href="https://tails.boum.org/">#tails</a></td>

153)       </tr>

154) 

155)       <tr>

156)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
157)         <td>OS image</td>
158)         <td>Sys Admin</td>
159)         <td>Light</td>
160)         <td>blueness</td>
161)       </tr>
162) 

163)       <tr class="alt">

164)         <td>*<a href="#project-torouter">Torouter</a></td>
165)         <td>OS image</td>
166)         <td>Sys Admin</td>

167)         <td>None</td>

168)         <td>ioerror</td>
169)       </tr>
170) 

171)       <tr>

172)         <td><a href="#project-torsocks">Torsocks</a></td>
173)         <td>Usability</td>
174)         <td>C</td>

175)         <td>Light</td>

176)         <td>ioerror, nickm</td>
177)       </tr>
178) 

179)       <tr class="alt">

180)         <td><a href="#project-torbirdy">TorBirdy</a></td>
181)         <td>Browser Add-on</td>
182)         <td>JavaScript</td>
183)         <td>Heavy</td>
184)         <td>Sukhbir (sukhe), ioerror</td>
185)       </tr>

186) 

187)       <tr>

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

190)         <td>C, Python</td>
191)         <td>Moderate</td>
192)         <td>asn, nickm</td>

193)       </tr>
194) 

195)       <tr class="alt">

196)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
197)         <td>Client Add-on</td>
198)         <td>Python, JavaScript, Go</td>

199)         <td>Heavy</td>

200)         <td>dcf, aallai, jct</td>
201)       </tr>

202) 

203)       <tr>

204)         <td>*<a href="#project-thandy">Thandy</a></td>
205)         <td>Updater</td>
206)         <td>Python</td>

207)         <td>None</td>

208)         <td>chiiph, Erinn, nickm</td>

209)       </tr>

210) 

211)       <tr class="alt">

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

213)         <td>Simulator</td>

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

215)         <td>Heavy</td>

216)         <td>robgjansen</td>
217)       </tr>

218) 

219)       <tr>

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

221)         <td>Library</td>
222)         <td>Python</td>
223)         <td>Heavy</td>

224)         <td>atagar</td>

225)       </tr>

226) 

227)       <tr class="alt">

228)         <td><a href="#project-txtorcon">Txtorcon</a></td>
229)         <td>Library</td>
230)         <td>Python, Twisted</td>

231)         <td>Heavy</td>

232)         <td>meejah</td>
233)       </tr>

234) 

235)       <tr>

236)         <td><a href="#project-tlsdate">Tlsdate</a></td>
237)         <td>Utility</td>
238)         <td>C</td>

239)         <td>Moderate</td>

240)         <td>ioerror</td>
241)       </tr>

242) 

243)       <tr class="alt">

244)         <td><a href="#project-metrics">Metrics</a></td>
245)         <td>Client Service</td>
246)         <td>Java</td>
247)         <td>Heavy</td>
248)         <td>karsten</td>
249)       </tr>

250) 

251)       <tr>

252)         <td><a href="#project-atlas">Atlas</a></td>
253)         <td>Client Service</td>
254)         <td>JavaScript</td>

255)         <td>Light</td>

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

257)       </tr>

258) 

259)       <tr class="alt">

260)         <td><a href="#project-torstatus">TorStatus</a></td>
261)         <td>Client Service</td>

262)         <td>Python, Django</td>

263)         <td>None</td>
264)         <td></td>
265)       </tr>

266) 

267)       <tr>

268)         <td><a href="#project-compass">Compass</a></td>
269)         <td>Client Service</td>
270)         <td>Python</td>

271)         <td>Light</td>

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

273)       </tr>

274) 

275)       <tr class="alt">

276)         <td><a href="#project-onionoo">Onionoo</a></td>
277)         <td>Backend Service</td>
278)         <td>Java, Python</td>

279)         <td>Light</td>

280)         <td>karsten, gsathya</td>
281)       </tr>
282) 

283)       <tr>

284)         <td><a href="#project-weather">Weather</a></td>
285)         <td>Client Service</td>
286)         <td>Python</td>

287)         <td>None</td>

288)         <td>kaner</td>
289)       </tr>

290) 

291)       <tr class="alt">

292)         <td><a href="#project-gettor">GetTor</a></td>
293)         <td>Client Service</td>
294)         <td>Python</td>

295)         <td>None</td>

296)         <td>kaner</td>

297)       </tr>

298) 

299)       <tr>

300)         <td><a href="#project-torcheck">TorCheck</a></td>
301)         <td>Client Service</td>
302)         <td>Python, Perl</td>
303)         <td>None</td>

304)         <td>ioerror</td>

305)       </tr>

306) 

307)       <tr class="alt">

308)         <td><a href="#project-bridgedb">BridgeDB</a></td>
309)         <td>Backend Service</td>
310)         <td>Python</td>

311)         <td>None</td>

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

313)       </tr>

314) 

315)       <tr>

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

317)         <td>Scanner</td>
318)         <td>Python</td>

319)         <td>Heavy</td>

320)         <td>hellais, isis, ioerror</td>
321)       </tr>
322) 

323)       <tr class="alt">

324)         <td><a href="#project-torflow">TorFlow</a></td>
325)         <td>Backend Service</td>
326)         <td>Python</td>

327)         <td>None</td>

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

329)       </tr>

330) 

331)       <tr>

332)         <td>*<a href="#project-torbel">TorBEL</a></td>
333)         <td>Backend Service</td>
334)         <td>Python</td>
335)         <td>None</td>
336)         <td>Sebastian</td>
337)       </tr>

338) 

339)       <tr class="alt">

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

342)         <td>Python</td>

343)         <td>Moderate</td>

344)         <td>hellais</td>

345)       </tr>

346) 

347)       <tr>

348)         <td><a href="#project-anonbib">Anonbib</a></td>
349)         <td>Website</td>

350)         <td>Python</td>

351)         <td>Light</td>
352)         <td>arma, nickm</td>
353)       </tr>
354) 

355)     </table>

356) 

357)     <sub>
358)     * Project is still in an alpha state.
359)     </sub>

360) 

361)     <br /><br />

362) 

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

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

366)     tracker</a>)</h3>

367) 

368)     <p>
369)     Central project, providing the core software for using and participating in
370)     the Tor network. Numerous people contribute to the project to varying
371)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
372)     </p>

373) 

374)     <p>
375)     <b>Project Ideas:</b><br />

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

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

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

380)     </p>

381) 

382)     <!--

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

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

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

388) 

389)     <p>
390)     Java implementation of Tor and successor to <a
391)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
392)     isn't yet complete, and has been inactive since Fall 2010.
393)     </p>

394)     -->

395) 

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

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

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

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

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

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

407)     </p>

408) 

409)     <!--

410)     <p>
411)     <b>Project Ideas:</b><br />
412)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
413)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
414)     </p>

415)     -->

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

421)     tracker</a>)</h3>

422) 

423)     <p>

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

429)     </p>

430) 
431)     <a id="project-httpseverywhere"></a>
432)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
433)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
434)     href="https://trac.torproject.org/projects/tor/report/19">bug

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

436) 

437)     <p>

438)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
439)     your communications with many major websites, making your browsing
440)     more secure.

441)     </p>

442) 

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

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

448) 

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

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

454)     </p>

455) 

456)     <!--

457)     <p>
458)     <b>Project Ideas:</b><br />

459)     <i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i><br />
460)     <i><a href="#vidalia-hidden-service-panel">Torrc plugin and improved hidden service configuration panel</a></i>

461)     </p>

462)     -->

463) 

464)     <a id="project-arm"></a>
465)     <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a

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

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

469) 

470)     <p>

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

476)     </p>

477) 

478)     <!--

479)     <p>
480)     <b>Project Ideas:</b><br />

481)     <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i><br />
482)     <i><a href="#armGui">GUI for Arm</a></i>

483)     </p>

484)     -->

485) 

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

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

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

491) 
492)     <p>
493)     Provides Tor on the Android platform. This was under very active
494)     development up through Fall 2010, after which things have been quiet.
495)     </p>
496) 
497)     <!--
498)     <p>
499)     <b>Project Ideas:</b><br />
500)     <i><a href="#orbot-torbutton">TorButton for Mobile Firefox 4 or Custom Browser on Android</a></i><br />
501)     <i><a href="#orbot-userInterface">Build a better user interface for Orbot</a></i><br />
502)     <i><a href="#orbot-optimisation">Core Tor mobile optimisation</a></i>
503)     </p>
504)     -->
505) 
506)     <a id="project-tails"></a>
507)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a
508)     href="http://git.immerda.ch/?p=amnesia.git;a=summary">code</a>, <a
509)     href="https://tails.boum.org/bugs/">bug
510)     tracker</a>)</h3>
511) 
512)     <p>
513)     The Amnesic Incognito Live System is a live CD/USB distribution
514)     preconfigured so that everything is safely routed through Tor and leaves no
515)     trace on the local system. This is a merger of the Amnesia and <a
516)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
517)     and still under very active development.
518)     </p>
519) 
520)     <!--
521)     <p>
522)     <b>Project Ideas:</b><br />
523)     <i><a href="#tailsHiddenServicePetnames">Petname system for Tor hidden
524)     services</a></i><br />
525)     <i><a href="#tailsServer">Tails server: Self-hosted services behind
526)     Tails-powered Tor hidden services</a></i>
527)     </p>
528)     -->
529) 

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

532)     href="http://opensource.dyc.edu/gitweb/?p=tor-ramdisk.git;a=summary">code</a>, <a
533)     href="http://opensource.dyc.edu/tor-ramdisk-documentation">documentation</a>)</h3>

534) 
535)     <p>

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

538)     </p>
539) 

540)     <a id="project-torouter"></a>
541)     <h3><a
542)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

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

558)     <p>

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

562)     </p>

563) 

564)     <!--

565)     <p>
566)     <b>Project Ideas:</b><br />

567)     <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>

568)     </p>

569)     -->

570) 

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

576) 

577)     <p>
578)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
579)     </p>

580) 

581)     <p>
582)     <b>Project Ideas:</b><br />
583)     <i><a href="#improveTorbirdy">Improving TorBirdy</a></i><br />
584)     </p>

585) 

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

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

588)     href="https://gitweb.torproject.org/obfsproxy.git">C codebase</a>, <a
589)     href="https://gitweb.torproject.org/user/asn/pyobfsproxy.git">python
590)     codebase</a>, <a

591)     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
592)     tracker</a>)</h3>

593) 

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

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

597)     </p>

598) 

599)     <!--

600)     <p>
601)     <b>Project Ideas:</b><br />
602)     <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
603)     <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
604)     <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
605)     </p>

606)     -->

607) 

608)     <a id="project-flash-proxy"></a>
609)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
610)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
611)     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
612)     tracker</a>)</h3>

613) 

614)     <p>
615)     Pluggable transport using proxies running in web browsers to defeat
616)     address-based blocking.
617)     </p>

618) 

619)     <a id="project-thandy"></a>
620)     <h3>Thandy (<a

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

622) 

623)     <p>

624)     Updater for Tor. The project <a
625)     href="http://google-opensource.blogspot.com/2009/03/thandy-secure-update-for-tor.html">began

626)     in the Summer of 2008</a> and produced a functional secure updater. The
627)     remaining steps are to deploy a Thandy repository, and integrate Thandy
628)     into one of our bundles &mdash; which requires UI changes in the bundles,
629)     Python packaging on various platforms, etc. Later interest in it was

630)     rekindled and many aspects of <a
631)     href="http://freehaven.net/~arma/tuf-ccs2010.pdf">its design</a> (including
632)     the language it'll be in) are currently in flux. This is related to <a
633)     href="https://www.updateframework.com/">TUF</a>.

634)     </p>

635) 

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

641) 

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

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

648)     </p>

649) 

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

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

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

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

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

655) 

656)     <p>

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

659)     </p>

660) 

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

663)     <i><a href="#stemUsability">Stem Usability and Porting</a></i>

664)     </p>

665) 

666)     <a id="project-txtorcon"></a>
667)     <h3>Txtorcon (<a
668)     href="https://github.com/meejah/txtorcon">code</a>, <a
669)     href="https://txtorcon.readthedocs.org">docs</a>)</h3>

670) 

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

676) 

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

679) 

680)     <p>
681)     tlsdate: secure parasitic rdate replacement
682)     </p>

683) 

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

691) 

692)     <a id="project-metrics"></a>
693)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
694)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
695)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
696)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
697)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
698)     tracker</a>)</h3>

699) 

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

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

705)     </p>

706) 

707)     <p>
708)     <b>Project Ideas:</b><br />
709)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
710)     </p>

711) 

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

715) 

716)     <p>
717)     Atlas is a web application to discover Tor relays and bridges. It provides
718)     useful information on how relays are configured along with graphics about
719)     their past usage. This is the third evolution of the TorStatus application.
720)     </p>

721) 

722)     <a id="project-torstatus"></a>

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

724)     href="https://gitweb.torproject.org/torstatus.git">code</a>)</h3>

725) 

726)     <p>
727)     Portal providing an overview of the Tor network, and details on any of its
728)     current relays. Though very actively used, this project has been

729)     unmaintained for a long while. The <a
730)     href="https://svn.torproject.org/svn/torstatus/trunk/">original
731)     codebase</a> was written in PHP, and students from Wesleyan wrote the new
732)     Django counterpart.

733)     </p>

734) 

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

740) 

741)     <p>
742)     Compass is a web and command line application that filters and
743)     aggregates the Tor relays based on various attributes.
744)     </p>

745) 

746)     <p>
747)     <b>Project Ideas:</b><br />
748)     <i><a href="#compassRefactoring">Compass Refactoring</a></i>
749)     </p>

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

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

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

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

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

764)     href="https://gitweb.torproject.org/weather.git">code</a>, <a
765)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Weather&order=priority">bug
766)     tracker</a>)</h3>

767) 

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

774) 

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

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

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

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

780) 

781)     <p>
782)     E-mail autoresponder providing Tor's packages over SMTP. This has been
783)     relatively unchanged for quite a while.
784)     </p>

785) 

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

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

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

791) 

792)     <p>
793)     Provides a simple site for determining if the visitor is using Tor or not.
794)     This has been relatively unchanged for quite a while.
795)     </p>

796) 

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

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

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

802) 

803)     <p>
804)     Backend bridge distributor, handling the various pools they're distributed
805)     in. This was actively developed until Fall of 2010.
806)     </p>

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

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

810)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
811)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
812)     tracker</a>)</h3>
813) 
814)     <p>
815)     Censorship scanner, checking your local connection for blocked or modified
816)     content.
817)     </p>
818) 

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

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

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

824) 

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

833) 

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

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

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

840) 

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

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

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

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

870)     </p>
871) 

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

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

875) 

876)     <p>

877)     You may find some of these projects to be good ideas for <a href="<page
878)     about/gsoc>">Google Summer of Code</a> and the <a
879)     href="https://live.gnome.org/OutreachProgramForWomen">Outreach Program for
880)     Women</a>. We have labelled each idea with how useful it would be to the
881)     overall Tor project (priority), how much work we expect it would be (effort
882)     level), how much clue you should start with (skill level), and which of our
883)     <a href="<page about/corepeople>">core developers</a> would be good
884)     mentors. If one or more of these ideas looks promising to you, please <a

885)     href="<page about/contact>">contact us</a> to discuss your plans rather than
886)     sending blind applications. You may also want to propose your own project
887)     idea &mdash; which often results in the best applications.
888)     </p>

889) 

890)     <ol>

891) 

892)     <!--

893)     <a id="auditTBB"></a>

894)     <li>

895)     <b>Audit Tor Browser Bundles for data leaks</b>

896)     <br>

897)     Effort Level: <i>High</i>

898)     <br>

899)     Skill Level: <i>Medium</i>

900)     <br>

901)     Likely Mentors: <i>Jacob</i>

902)     <p>The Tor Browser Bundle incorporates Tor, Firefox, Polipo, and the Vidalia

903)     user interface (and optionally the <a href="http://pidgin.im/">Pidgin</a>
904)     Instant Messaging client). Components are pre-configured to operate in a
905)     secure way, and it has very few dependencies on the installed operating
906)     system. It has therefore become one of the most easy to use, and popular,

907)     ways to use Tor on Windows.</p>
908)     <p>This project is to identify all of the traces left behind by
909)     using a Tor Browser Bundle on Windows, Mac OS X, or Linux.  Developing
910)     ways to stop, counter, or remove these traces is a final step.</p>
911)     <p>Students should be familiar with operating system analysis,

912)     application development on one or preferably all of Windows, Linux,

913)     and Mac OS X, and be comfortable with C/C++ and shell scripting.</p>

914)     <p>Since the core of this project is researching and auditing TBB this is
915)     not likely to be a good GSoC project.</p>

916)     </li>

917)     -->

918) 

919)     <!--

920)     <a id="orbot-userInterface"></a>

921)     <li>

922)     <b>Build a better user interface for Orbot</b>

923)     <br>

924)     Effort Level: <i>Medium</i>

925)     <br>

926)     Skill Level: <i>Medium</i>

927)     <br>

928)     Likely Mentors: <i>Jake</i>
929)     <p>Improved home screen to show confirmation of connection (via a TorCheck
930)     API call), better statistics about data transferred (up/down), number of
931)     circuits connected, quality of connection and so on. The &quot;Tether
932)     Wifi&quot; Android application is a good model to follow in how it shows a
933)     realtime count of bytes transferred as well as notifications when wifi
934)     clients connect. In addition, better handling of Tor system and error
935)     messages would also be very helpful, include use of standard Android
936)     operating systems notifications. The addition of a wizard or tutorial
937)     walkthrough for novice users to explain to them exactly what is and what is
938)     not anonymized or protected would greatly improve the likelihood they will
939)     use Orbot correctly. All of this should work on the range of screens and
940)     device types now offered for Android, from 2&quot; phone to 10&quot;
941)     Tablet.</p>

942)     </li>

943)     -->

944) 

945)     <!--

946)     <a id="armClientMode"></a>

947)     <li>

948)     <b>Client Mode Use Cases for Arm</b>

949)     <br>
950)     Effort Level: <i>High</i>
951)     <br>

952)     Skill Level: <i>Medium</i>

953)     <br>

954)     Likely Mentors: <i>Damian (atagar)</i>
955)     <p><a href="<page projects/arm>">Arm</a> is a Tor command line status
956)     monitor on *nix environments (Linux, Mac, and BSD). It functions much like
957)     top does, giving a CLI overlay of Tor's bandwidth usage, connections,
958)     configuration, log, etc. Thus far its design has been geared for Tor relay
959)     operators. However, this doesn't need to be the case. This project would be
960)     to expand and simplify arm to make it useful for Tor's client users
961)     too.</p>

962) 

963)     <p>This would include UI design, experimenting, and a lot of python
964)     hacking. Here's some ideas for client functionality arm could provide:</p>

965) 

966)     <ul>
967)       <li>A panel for client connections, showing each hop of the user's
968)       circuits with the ISP, country, and jurisdiction where those relays
969)       reside. Other interesting information would be the circuit's latency, how
970)       long its been around, and its possible exit ports. Some of this will be
971)       pretty tricky and require some experimentation to figure out what
972)       information can be fetched safely (for instance, scraping rdns and whois
973)       lookups could give hints about a relay's ISP, but we'd need to do it on
974)       all Tor relays to avoid leaking our connections to the resolver).</li>

975) 

976)       <li>Options to let the user request new circuits (the &quot;New
977)       Identity&quot; feature in Vidalia), select the exit country, etc.</li>

978) 

979)       <li>A panel showing Internet application and if their connections are
980)       being routed through Tor or not (giving a warning if there's leaks).</li>

981) 

982)       <li>The status of the bridges we're configured to use (ie, are they up?).
983)       This would include adding control port functionality to Tor for <a
984)       href="https://trac.torproject.org/projects/tor/ticket/2068">ticket
985)       2068</a>.</li>

986) 

987)       <li>A one click option to set Tor to be a client, relay, or bridge. The
988)       goal would be to make it trivial for users to voluntarily contribute to
989)       the Tor network.</li>

990) 

991)       <li>Menus as an alternative to hotkeys to make the interface more
992)       intuitive and usable for beginners (<a
993)       href="http://gnosis.cx/publish/programming/charming_python_6.html">example</a>).</li>

994) 

995)       <li>Look at Vidalia and TorK for ideas and solicit input from the Tor community.</li>
996)     </ul>

997) 

998)     <p>
999)     More information is available in the following sections of arm's dev notes: <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#ConnectionListingExpansion">Connection Listing Expansion</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#CircuitDetails">Circuit Details</a>, and <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#ClientModeUseCases">Client Mode Use Cases</a>
1000)     </p>

1001)     </li>

1002)     -->

1003) 

1004)     <a id="compassRefactoring"></a>

1005)     <li>

1006)     <b>Compass Refactoring</b>

1007)     <br>

1008)     Effort Level: <i>Medium</i>

1009)     <br>

1010)     Skill Level: <i>Medium</i>
1011)     <br>
1012)     Likely Mentors: <i>gsathya, karsten</i>
1013)     <p>
1014)     Compass was first designed to be a cli app and then hacked into a web app.
1015)     The codebase needs to be refactored such that the main processing code is
1016)     separated from the display functions(probably into separate files) and made
1017)     modular so that adding more features (<a
1018)     href="https://trac.torproject.org/6612">#6612</a>) is easy. For example, the
1019)     main processing logic could be in compass.py, whereas print_groups() and other
1020)     display related functions could be part of a separate cli.py; web.py would also
1021)     have to modified to make use of this new modular code. Bonus points for adding
1022)     features to compass(<a href="https://trac.torproject.org/6619">#6619</a>, <a
1023)     href="https://trac.torproject.org/6612">#6612</a>, <a
1024)     href="https://trac.torproject.org/6728">#6728</a>).
1025)     </p>
1026)     </li>

1027) 

1028)     <!--
1029)     <a id="orbot-optimisation"></a>
1030)     <li>
1031)     <b>Core Tor mobile optimisation</b>
1032)     <br>
1033)     Effort Level: <i>Medium</i>

1034)     <br>
1035)     Skill Level: <i>High</i>
1036)     <br>

1037)     Likely Mentors: <i>Jake</i>
1038)     <p>
1039)     The existing port of Tor to Android is basically a straight
1040)     cross-compile to Linux ARM. There has been no work done in looking at
1041)     possible optimizations of Tor within a mobile hardware environment or on
1042)     mobile networks. In addition, a number of additional Android OS APIs are
1043)     available (such as wireless network status) that could be taken
1044)     advantage of.
1045)     </p>

1046) 

1047)     <p>
1048)     It should be noted, that even without optimisation, Tor is handling the
1049)     mobile network environment very well, automatically detecting change in
1050)     IP addresses, opening circuits, etc, as the device switches from no
1051)     coverage to 2G, 3G or Wifi constantly as it changes position. However,
1052)     this observation of &quot;very well&quot;, is just based on user
1053)     experience, and not any detailed study of what exactly is happening, and
1054)     what threats might exist because of this constantly changing network state.
1055)     </p>

1056) 

1057)     <p>
1058)     Finally, the build process needs to be moved to the Android NDK from the
1059)     custom GCC toolchain we are now using, and compatibility with Android
1060)     2.3 and 3.x Honeycomb OS need to be verified.
1061)     </p>

1062) 

1063)     <p>
1064)     For more information see the <a
1065)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD">Orbot
1066)     build documentation</a>.
1067)     </p>

1068)     </li>

1069)     -->

1070) 

1071)     <!--

1072)     <a id="obfsproxy-scanning-measures"></a>
1073)     <li>
1074)     <b>Defensive bridge active scanning measures</b>
1075)     <br>
1076)     Effort Level: <i>High</i>
1077)     <br>
1078)     Skill Level: <i>High</i>
1079)     <br>
1080)     Likely Mentors: <i>asn</i>
1081)     <p>Involves providing good answers to <a
1082)     href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html">this
1083)     thread</a> as well as concrete implementation plans for it.</p>

1084) 

1085)     <p>This also involves implementing proposals <a
1086)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a>
1087)     and <a
1088)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p>
1089)     </li>

1090)     -->

1091) 

1092)     <!--
1093)     <a id="firewallProbeTool"></a>

1094)     <li>

1095)     <b>Develop a fully automatic firewall-probing system</b>

1096)     <br>
1097)     Effort Level: <i>Medium to High</i>
1098)     <br>
1099)     Skill Level: <i>High</i>
1100)     <br>

1101)     Likely Mentors: <i>Robert Ransom, Jacob</i>
1102)     <p>We would like to have a fully automatic firewall-probing system for
1103)     blocking systems with no long-term state (i.e. firewalls that can
1104)     examine each connection, but do not change their behaviour for future
1105)     connections based on the traffic they have seen).</p>
1106)     <p>Ideally, volunteers would only need to set up one or more test servers,
1107)     and run the probe client program on a publicly accessible computer
1108)     behind the firewall.</p>
1109)     <p>The test tool should:</p>
1110)     <ul>
1111)     <li>generate packet captures on both ends (and send them out to the
1112)         extent possible),</li>
1113)     <li>cycle through all the SSL configurations we might want to test
1114)         through a censorship device, and</li>
1115)     <li>also test some other protocols to see whether they are allowed
1116)         through the firewall (IMAP and other mail protocols, BitTorrent,
1117)         DTLS, etc.).</li>
1118)     </ul>
1119)     </li>
1120)     -->

1121) 

1122)     <!--
1123)     <a id="obfsproxy-fuzzer"></a>
1124)     <li>
1125)     <b>Fuzzer for the Tor protocol</b>
1126)     <br>
1127)     Effort Level: <i>Medium to High</i>
1128)     <br>
1129)     Skill Level: <i>High</i>
1130)     <br>
1131)     Likely Mentors: <i>asn</i>
1132)     <p>Involves researching good and smart ways to fuzz stateful network
1133)     protocols, and also implementing the fuzzer.</p>

1134) 

1135)     <p>We are mostly looking for a fuzzer that fuzzes the Tor protocol
1136)     itself, and not the Tor directory protocol.</p>

1137) 

1138)     <p>Bonus points if it's extremely modular. Relevant research:</p>

1139) 

1140)     <ul>
1141)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1142)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1143)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1144)       Testing and Machine Learning</li>
1145)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1146)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1147)       <li>Also look at the concepts of &quot;model checking&quot; and
1148)       &quot;symbolic execution&quot; to get inspired.</li>
1149)     </ul>
1150)     </li>
1151)     -->

1152) 
1153)     <a id="httpsImpersonation"></a>

1154)     <li>
1155)     <b>HTTPS Server Impersonation</b>
1156)     <br>
1157)     Effort Level: <i>Medium to High</i>
1158)     <br>
1159)     Skill Level: <i>Medium to High</i>
1160)     <br>
1161)     Likely Mentors: <i>Nick (nickm)</i>

1162)     <p>

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

1169)     </p>
1170)     </li>

1171) 

1172)     <!--
1173)     <a id="geoIPUpgrade"></a>

1174)     <li>

1175)     <b>Improve our GeoIP file format</b>

1176)     <br>

1177)     Effort Level: <i>Medium</i>
1178)     <br>
1179)     Skill Level: <i>Medium to High</i>
1180)     <br>
1181)     Likely Mentors: <i>Robert Ransom</i>
1182)     <p>Currently, Tor bridges and relays read an entire IP-&gt;country database
1183)     into memory from a text file during startup.  We would like to
1184)     distribute this database and store it on disk in a much more compact
1185)     form, and perform IP-&gt;country lookups on it in its on-disk format if
1186)     possible.</p>
1187)     <p>We have <a href='https://trac.torproject.org/projects/tor/ticket/2506'>a
1188)     sketch of a design</a> for a moderately optimized format for IPv4 GeoIP
1189)     data; this project will involve both implementing the IPv4 format and
1190)     designing and implementing a format for IPv6 GeoIP data.</p>
1191)     <p>Since the core of this project is researching IPv6 GeoIP data and
1192)     designing the IPv6 format, this is not likely to be a good GSoC
1193)     project.</p>
1194)     </li>
1195)     -->

1196) 

1197)     <!--
1198)     <a id="unitTesting"></a>
1199)     <li>
1200)     <b>Improve our unit testing process</b>

1201)     <br>
1202)     Effort Level: <i>Medium</i>
1203)     <br>
1204)     Skill Level: <i>Medium</i>
1205)     <br>

1206)     Likely Mentors: <i>Nick, Erinn</i>
1207)     <p>Tor needs to be tested far more thoroughly. This is a
1208)     multi-part effort. To start with, our unit test coverage should
1209)     rise substantially, especially in the areas outside the utility
1210)     functions. This will require significant refactoring of some parts
1211)     of Tor, in order to dissociate as much logic as possible from
1212)     globals.</p>
1213)     <p>Additionally, we need to automate our performance testing. We've got
1214)     buildbot to automate our regular integration and compile testing already
1215)     (though we need somebody to set it up on Windows),
1216)     but we need to get our network simulation tests (as built in <a
1217)     href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
1218)     updated for more recent versions of Tor, and designed to launch a test
1219)     network either on a single machine, or across several, so we can test
1220)     changes in performance on machines in different roles automatically.</p>
1221)     </li>
1222)     -->

1223) 

1224)     <!--
1225)     <a id="vidaliaNetworkMap"></a>
1226)     <li>
1227)     <b>Improved and More Usable Network Map in Vidalia</b>
1228)     <br>
1229)     Effort Level: <i>Medium</i>
1230)     <br>
1231)     Skill Level: <i>Medium</i>
1232)     <br>
1233)     Likely Mentors: <i>Tomás</i>

1234)     <p>

1235)     One of Vidalia's existing features is a network map that shows the user
1236)     the approximate geographic location of relays in the Tor network and
1237)     plots the paths the user's traffic takes as it is tunneled through the
1238)     Tor network. The map is currently not very interactive and has rather
1239)     poor graphics. Instead, we implemented KDE's Marble widget such
1240)     that it gives us a better quality map and enables improved interactivity,
1241)     such as allowing the user to click on individual relays or circuits to
1242)     display additional information. We want to add the ability
1243)     for users to click on a particular relay or a country containing one or
1244)     more Tor exit relays and say, "I want my connections to exit
1245)     from here."
1246)     </p>

1247) 

1248)     <p>
1249)     This project will first involve getting familiar with Vidalia
1250)     and the Marble widget's API. One will then integrate the widget
1251)     into Vidalia and customize Marble to be better suited for our application,
1252)     such as making circuits clickable, storing cached map data in Vidalia's
1253)     own data directory, and customizing some of the widget's dialogs.
1254)     </p>

1255) 

1256)     <p>
1257)     A person undertaking this project should have good C++ development
1258)     experience. Previous experience with Qt and CMake is helpful, but not
1259)     required.

1260)     </p>
1261)     </li>

1262)     -->

1263) 

1264)     <!--
1265)     <a id="resistCensorship"></a>

1266)     <li>

1267)     <b>Improving Tor's ability to resist censorship</b>

1268)     <br>

1269)     Effort Level: <i>Medium to High</i>

1270)     <br>

1271)     Skill Level: <i>High</i>
1272)     <br>
1273)     Likely Mentors: <i>Jake, Thomas</i>
1274)     <p>The Tor 0.2.1.x series makes <a
1275)     href="<svnprojects>design-paper/blocking.html">significant
1276)     improvements</a> in resisting national and organizational censorship.
1277)     But Tor still needs better mechanisms for some parts of its
1278)     anti-censorship design.</p>
1279)     <p>One huge category of work is adding features to our <a
1280)     href="https://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a>
1281)     service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge
1282)     relay addresses</a> to users that can't reach the Tor network
1283)     directly, but there's an arms race between algorithms for distributing
1284)     addresses and algorithms for gathering and blocking them. See <a
1285)     href="<blog>bridge-distribution-strategies">our
1286)     blog post on the topic</a> as an overview, and then look at <a
1287)     href="https://lists.torproject.org/pipermail/tor-dev/2009-December/000666.html">Roger's
1288)     or-dev post</a> from December 2009 for more recent thoughts &mdash; lots of
1289)     design work remains.</p>
1290)     <p>If you want to get more into the guts of Tor itself (C), a more minor problem
1291)     we should address is that current Tors can only listen on a single
1292)     address/port combination at a time. There's
1293)     <a href="<specblob>proposals/118-multiple-orports.txt">a
1294)     proposal to address this limitation</a> and allow clients to connect
1295)     to any given Tor on multiple addresses and ports, but it needs more
1296)     work.</p>
1297)     <p>This project could involve a lot of research and design. One of the big
1298)     challenges will be identifying and crafting approaches that can still
1299)     resist an adversary even after the adversary knows the design, and
1300)     then trading off censorship resistance with usability and
1301)     robustness.</p>
1302)     </li>
1303)     -->

1304) 

1305)     <a id="improveTorbirdy"></a>
1306)     <li>
1307)     <b>Improving TorBirdy</b>
1308)     <br>
1309)     Effort Level: <i>High</i>

1310)     <br>
1311)     Skill Level: <i>Medium to High</i>
1312)     <br>

1313)     Likely Mentors: <i>Sukhbir, Jacob</i>
1314)     <p>
1315)     TorBirdy is Torbutton for Thunderbird, Icedove and related Mozilla mail
1316)     clients.
1317)     </p>
1318)     <p>
1319)     TorBirdy is under active development and is available from <a
1320)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy">our wiki</a>
1321)     and <a
1322)     href="https://addons.mozilla.org/en-US/thunderbird/addon/torbirdy/">mozilla's
1323)     addons site</a>.
1324)     </p>

1325) 

1326)     <p>
1327)     The goal of this project is to improve TorBirdy by:
1328)     </p>

1329) 

1330)     <ul>
1331)       <li>
1332)         Writing a Thunderbird patch to plug known leaks. We have already <a
1333)         href="https://bugzilla.mozilla.org/show_bug.cgi?id=776397">submitted a
1334)         patch to Thunderbird</a> but we anticipate there will be much more work
1335)         required before it is accepted, possibly involving rewriting the entire
1336)         patch; this appears trivial, but it is not, as we are proposing a
1337)         completely new privacy-safe message-ID header generation algorithm for
1338)         Thunderbird.
1339)       </li>
1340)       <li>
1341)         Implementing a JavaScript HTTP proxy (see the <a
1342)         href="https://trac.torproject.org/projects/tor/ticket/6958">ticket</a>)
1343)       </li>
1344)       <li>
1345)         Auditing TorBirdy for leaks and for use with other add-ons (as an
1346)         example see its <a
1347)         href="https://trac.torproject.org/projects/tor/ticket/6319">ticket</a>)
1348)       </li>
1349)     </ul>

1350) 

1351)     <p>
1352)     A student undertaking this project should have some C++ and JavaScript
1353)     development experience. Previous experience with Firefox/Thunderbird
1354)     extension development is a plus, but not required.
1355)     </p>
1356)     </li>

1357) 

1358)     <!--
1359)     <a id="user-space-transport"></a>
1360)     <li>
1361)     <b>Integrating Tor with user-space transport protocol libraries</b>
1362)     <br>
1363)     Effort Level: <i>High</i>
1364)     <br>
1365)     Skill Level: <i>High</i>
1366)     <br>
1367)     Likely Mentors: <i>Steven</i>
1368)     <p>Tor currently sends data over TCP links between nodes. <a
1369)     href="http://static.usenix.org/events/sec09/tech/full_papers/reardon.pdf">Prior
1370)     research</a> has indicated that this may not be optimal, and instead the
1371)     role that TCP plays (congestion control and reliability) should be moved
1372)     into Tor itself. This would allow a number of desirable changes, such as
1373)     preventing errors on one circuit delaying another, and giving Tor control
1374)     and visibility of congestion control.</p>
1375)     <p>There are <a
1376)     href="http://www.cl.cam.ac.uk/~sjm217/papers/tor11datagramcomparison.pdf">many
1377)     ways to do this</a>, each with their own tradeoffs and difficulty of
1378)     implementation. This project will be to select one (or more) option and
1379)     implement it in Tor. The primary goal will be to test this modified version
1380)     of Tor in simulation, but if it turns out to work well, it could be
1381)     deployed in the live Tor network.</p>
1382)     <p>Excellent C programming skills are needed, and knowledge of Tor
1383)     internals are highly desirable.</p>
1384)     </li>
1385)     -->

1386) 

1387)     <a id="chutneyExpansion"></a>
1388)     <li>
1389)     <b>Make Chutney Do More, More Reliably</b>
1390)     <br>
1391)     Effort Level: <i>Medium to High, depending on scope of project</i>
1392)     <br>
1393)     Skill Level: <i>Medium</i>
1394)     <br>

1395)     Likely Mentors: <i>Nick (nickm)</i>
1396)     <p>

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

1401)     </p>

1402) 

1403)     <p>

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

1407)     </p>

1408)     </li>

1409) 

1410)     <!--
1411)     <a id="torsocksForOSX"></a>
1412)     <li>
1413)     <b>Make torsocks/dsocks work on OS X</b>
1414)     <br>
1415)     Effort Level: <i>Medium</i>
1416)     <br>
1417)     Skill Level: <i>Medium</i>
1418)     <br>
1419)     Likely Mentors: <i>Robert Hogan</i>

1420)     <p>

1421)     <a href="https://code.google.com/p/torsocks/">Torsocks</a> and <a
1422)     href="https://code.google.com/p/dsocks/">dsocks</a> are wrappers that will
1423)     run applications, intercept their outgoing network connections, and push
1424)     those connections through Tor. The goal is to handle applications that
1425)     don't support proxies (or don't supporting them well). To get it right,
1426)     they need to intercept many system calls. The syscalls you need to
1427)     intercept on Linux differ dramatically from those on BSD. So Torsocks
1428)     works fine on Linux, dsocks works ok on BSD (though it may be less
1429)     maintained and thus might miss more syscalls), and nothing works well
1430)     on both. First, we should patch dsocks to use Tor's <i>mapaddress</i>
1431)     commands from the controller interface, so we don't waste a whole
1432)     round-trip inside Tor doing the resolve before connecting. Second,
1433)     we should make our <i>torify</i> script detect which of torsocks or
1434)     dsocks is installed, and call them appropriately. This probably means
1435)     unifying their interfaces, and might involve sharing code between them
1436)     or discarding one entirely.
1437)     </p>
1438)     </li>
1439)     -->

1440) 

1441)     <!--
1442)     <a id="obfsproxy-new-transports"></a>
1443)     <li>
1444)     <b>New and innovative pluggable transports</b>
1445)     <br>
1446)     Effort Level: <i>High</i>
1447)     <br>
1448)     Skill Level: <i>High</i>
1449)     <br>
1450)     Likely Mentors: <i>asn, Steven</i>
1451)     <p>Not-very-smart transports like ROT13 and base64 are nice but not super
1452)     interesting. Other ideas like bittorrent transports might be relevant,
1453)     but you will have to provide security proofs on why they are harder to
1454)     detect and block than other less-sophisticated transports.</p>

1455) 

1456)     <p>The whole point of this project, though, is to come up with new
1457)     transports that we haven't already thought of. Be creative.</p>

1458) 

1459)     <p>Bonus points if your idea is interesting and still implementable
1460)     through the summer period.</p>

1461) 

1462)     <p>More bonus points if it's implemented on top of obfsproxy, or if your
1463)     implementation has a pluggable transport interface on top of it (as
1464)     specified <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt">here</a>).</p>
1465)     </li>
1466)     -->

1467) 

1468)     <!--
1469)     <a id="orbot-orlibAndOutreach"></a>
1470)     <li>
1471)     <b>Orbot integration library and community outreach</b>
1472)     <br>
1473)     Effort Level: <i>Low</i>
1474)     <br>
1475)     Skill Level: <i>Medium</i>
1476)     <br>
1477)     Likely Mentors: <i>Nathan (n8fr8)</i>
1478)     <p>
1479)     We need additional work on <a
1480)     href="https://github.com/guardianproject/orlib">ORLib</a>, our library for
1481)     use with third-party application to easily enable them to support
1482)     &quot;Torification&quot; on non-rooted devices (i.e. w/o transparent
1483)     proxying). This library includes a SOCKS client, a wrapper for the Apache
1484)     HTTPClient library, a utility class for detecting the state of Orbot
1485)     connectivity, and other relevant/useful things an Android app might need to
1486)     anonymize itself. This work would includes direct development of the
1487)     library, documentation, and sample code. Outreach or effort to implement
1488)     the library within other open-source apps is also needed.

1489)     </p>
1490)     </li>

1491)     -->

1492) 

1493)     <!--
1494)     <a id="tailsHiddenServicePetnames"></a>
1495)     <li>
1496)     <b>Petname system for Tor hidden services</b>
1497)     <br>
1498)     Effort Level: <i>High</i>
1499)     <br>
1500)     Skill Level: <i>High</i>
1501)     <br>
1502)     Likely Mentors: <i>ague</i>
1503)     <p>Tor provides hidden services. These services are only reachable through
1504)     Tor itself, and provide greater anonymity both for the providers of the
1505)     service and for its users.</p>
1506)     <p>One current downside of Tor hidden services is that they are addressed
1507)     using 80-bit base32-encoded addresses such as "v2cbb2l4lsnpio4q.onion".
1508)     These addresses are hard to remember; this makes them hard to use
1509)     within amnesic environment like Tails.</p>
1510)     <p>The project is to implement a petname system for Tor hidden services:
1511)     a way for users or providers of Tor hidden services to add a simple
1512)     'nickname' to a central database. Users could then query this central
1513)     database to retrieve a full hidden service address by giving
1514)     a nickname.</p>
1515)     <p>Adding petnames to the database could be done using a web interface or
1516)     automated fetch like those described in the <a
1517)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/ideas/xxx-onion-nyms.txt">&quot;.onion
1518)     nym system&quot; proposal</a>.</p>
1519)     <p>Querying the database could be done using a web interface, a REST API and
1520)     a DNS interface.</p>
1521)     <p>In order not to grow indefinitely, the software should make regular tests to
1522)     see if hidden services are still reachable and, depending on the last time
1523)     a nickname was accessed, cleanup the database as necessary.</p>
1524)     <p>The software should allow a distributed, fault-tolerant setup.
1525)     All nodes should have a synchronized copy of the database, should be
1526)     ready to answer queries and should coordinate the tests for hidden
1527)     service availability.</p>
1528)     <p>The resulting codebase must be easy to deploy: it should not be hard to
1529)     setup new databases.</p>
1530)     <p>It is expected that the volunteer will be using Behaviour Driven
1531)     Development methods. Either in Ruby using Cucumber and RSpec, or in
1532)     Python using similar tools.</p>
1533)     </li>
1534)     -->

1535) 

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

1537)     <li>

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

1539)     <br>
1540)     Effort Level: <i>Medium to High</i>
1541)     <br>

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

1543)     <br>
1544)     Likely Mentors: <i>Nick (nickm)</i>
1545)     <p>

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

1549)     </p>

1550) 

1551)     <p>

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

1561)     </p>

1562) 

1563)     <p>

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

1567)     </p>
1568)     </li>

1569) 

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

1571)     <li>

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

1573)     <br>
1574)     Effort Level: <i>Medium</i>
1575)     <br>
1576)     Skill Level: <i>Medium</i>
1577)     <br>

1578)     Likely Mentors: <i>Karsten</i>
1579)     <p>The <a href="https://metrics.torproject.org/data.html">Metrics data
1580)     archive</a> of Tor relay descriptors and other Tor-related network data has
1581)     grown to over 100G in size, bz2-compressed.  We have developed two search
1582)     interfaces: the <a
1583)     href="https://metrics.torproject.org/relay-search.html">relay search</a>
1584)     finds relays by nickname, fingerprint, or IP address in a given month; <a
1585)     href="https://metrics.torproject.org/exonerator.html">ExoneraTor</a> finds
1586)     whether a given IP address was a relay on a given day.</p>

1587) 

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

1599) 

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

1610) 

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

1615)     </li>

1616) 

1617)     <!--
1618)     <a id="simulateSlowConnections"></a>

1619)     <li>

1620)     <b>Simulator for slow Internet connections</b>

1621)     <br>
1622)     Effort Level: <i>Medium</i>
1623)     <br>
1624)     Skill Level: <i>Medium</i>
1625)     <br>

1626)     Likely Mentors: <i>Nick</i>

1627)     <p>

1628)     Many users of Tor have poor-quality Internet connections, giving low
1629)     bandwidth, high latency, and high packet loss/re-ordering. User
1630)     experience is that Tor reacts badly to these conditions, but it is
1631)     difficult to improve the situation without being able to repeat the
1632)     problems in the lab.
1633)     </p>

1634) 

1635)     <p>
1636)     This project would be to build a simulation environment which
1637)     replicates the poor connectivity so that the effect on Tor performance
1638)     can be measured. Other components would be a testing utility to
1639)     establish what are the properties of connections available, and to
1640)     measure the effect of performance-improving modifications to Tor.
1641)     </p>

1642) 

1643)     <p>
1644)     The tools used would be up to the student, but dummynet (for FreeBSD)
1645)     and nistnet (for Linux) are two potential components on which this
1646)     project could be built. Students should be experienced with network
1647)     programming/debugging and TCP/IP, and preferably familiar with C and a
1648)     scripting language.

1649)     </p>
1650)     </li>

1651)     -->

1652) 

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

1654)     <li>

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

1656)     <br>
1657)     Effort Level: <i>Medium</i>
1658)     <br>
1659)     Skill Level: <i>Medium</i>
1660)     <br>

1661)     Likely Mentors: <i>Damian (atagar)</i>
1662)     <p>

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

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

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

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

1669)     <a href="http://www.atagar.com/arm/">arm</a>.

1670)     </p>

1671) 

1672)     <p>
1673)     While TorCtl provided a fine first draft for this sort of functionality,
1674)     it has not proved to be extensible nor maintainable. Stem is a rewrite of
1675)     TorCtl with a heavy focus on testing, documentation, and providing a
1676)     developer friendly API.
1677)     </p>

1678) 

1679)     <p>

1680)     Stem has largely met these goals but there's still plenty of low hanging
1681)     fruit in terms of usability improvements. Also, we have clients still using
1682)     TorCtl that need to be ported over. This project includes several subtasks,
1683)     see the tickets for additional context...

1684)     </p>

1685) 

1686)     <ol>
1687)       <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>
1688)       <li>Navigation of <a href="https://stem.torproject.org">stem's site</a> is clunky, in large part due to the linear page flow supported by sphinx. One possible fix for this would be css-only menus, ideally as a sphinx plugin so we could contribute it back upstream.(<a href="https://trac.torproject.org/8431">ticket</a>)</li>
1689)       <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.</li>
1690)       <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/tutorial.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>
1691)     </ol>

1692) 

1693)     <p>

1694)     <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/tutorial.html">make a tutorial</a> around!

1695)     </p>

1696) 

1697)     <!--

1698)     <a id="tailsServer"></a>
1699)     <li>
1700)     <b>Tails server: Self-hosted services behind Tails-powered Tor hidden services</b>
1701)     <br>
1702)     Effort Level: <i>High</i>
1703)     <br>
1704)     Skill Level: <i>Medium, but wide-scoped</i>
1705)     <br>
1706)     Likely Mentors: <i>intrigeri, anonym</i>
1707)     <p>Let's talk about group collaboration, communication and data sharing
1708)     infrastructure, such as chat servers, wikis, or file repositories.</p>
1709)     <p>Hosting such data and infrastructure <b>in the cloud</b> generally
1710)     implies to trust the service providers not to disclose content, usage or
1711)     users location information to third-parties. Hence, there are many threat
1712)     models in which cloud hosting is not suitable.</p>
1713)     <p>Tor partly answers the <b>users location</b> part; this is great, but
1714)     <b>content</b> is left unprotected.</p>
1715)     <p>There are two main ways to protect such content: either to encrypt it
1716)     client-side (<b>security by design</b>), or to avoid putting it into
1717)     untrusted hands in the first place.</p>
1718)     <p>Cloud solutions that offer security by design are rare and generally
1719)     not mature yet. The <b>Tails server</b> project is about exploring the
1720)     other side of the alternative: avoiding to put private data into
1721)     untrusted hands in the first place.</p>
1722)     <p>This is made possible thanks to Tor hidden services, that allow users
1723)     to offer location-hidden services, and make self-hosting possible in
1724)     many threat models. Self-hosting has its own lot of problems, however,
1725)     particularly in contexts where the physical security of the hosting
1726)     place is not assured. Combining Tor hidden services with Tails'
1727)     amnesia property and limited support for persistent encrypted data
1728)     allows to protect content, to a great degree, even in such contexts.</p>
1729)     <p>In short, setting up a new Tails server would be done by:</p>

1730) 

1731)     <ol style="list-style-type: decimal">
1732)       <li>Alice plugs a USB stick into a running desktop Tails system.</li>
1733)       <li>Alice uses a GUI to easily configure the needed services.</li>
1734)       <li>Alice unplugs the USB stick, that now contains encrypted services
1735)       configuration and data storage space.</li>
1736)       <li>Alice plugs that USB stick (and possibly a Tails Live CD) into the
1737)       old laptop that was dedicated to run Tails server.</li>
1738)       <li>Once booted, Alice enters the encryption passphrase either
1739)       directly using the keyboard or through a web interface listening on the
1740)       local network.</li>
1741)       <li>Then, Bob can use the configured services once he gets a hold on
1742)       the hidden service address. (The <b>petname system for Tor hidden
1743)       services</b> project would be very complementary to this one, by the
1744)       way.)</li>
1745)     </ol>

1746) 

1747)     <p>Tails server should content itself with hardware that is a bit old
1748)     (such as a PIII-450 laptop with 256MB of RAM) and/or half broken (e.g.
1749)     non-functional hard-disk, screen or keyboard).</p>
1750)     <p>The challenges behind this project are:</p>

1751) 

1752)     <ul>
1753)       <li>Design and write the services configuration GUI [keywords: edit
1754)       configuration files, upgrade between major Debian versions,
1755)       debconf].</li>
1756)       <li>How to create the hidden service key? [keywords: Vidalia, control
1757)       protocol].</li>
1758)       <li>Adapt the Tails boot process to allow switching to &quot;server
1759)       mode&quot; when appropriate.</li>
1760)       <li>Add support, to the Tails persistence setup process, for asking an
1761)       encryption passphrase without X, and possibly with a broken keyboard
1762)       and/or screen [keywords: local network, SSL/TLS?, certificate?].</li>
1763)     </ul>

1764) 

1765)     <p>This project can easily grow quite large, so the first task would
1766)     probably be to clarify what it would need to get an initial (minimal
1767)     but working) implementation ready to be shipped to users.</p>

1768)     <p>This project does not require to be an expert in one specific field,
1769)     but it requires to be experienced and at ease with a large scope of
1770)     software development tools, processes, and operating system knowledge.</p>
1771)     <p>Undertaking this project requires in-depth knowledge of Debian-like
1772)     systems (self-test: do the "dpkg conffile" and "debconf preseeding"
1773)     words sound new to your ear?); the Debian Live persistence system
1774)     being written in shell, being at ease with robust shell scripting is
1775)     a must; to end with, at least two pieces of software need to be
1776)     written from scratch (a GUI and a webapp): the preferred languages for
1777)     these tasks would be Python and Perl. Using Behaviour Driven
1778)     Development methods to convey expectations and acceptance criteria
1779)     would be most welcome.</p>
1780)     <p>For more information see https://tails.boum.org/todo/server_edition/</p>

1781)     </li>

1782)     -->

1783) 

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

1785)     <li>

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

1787)     <br>

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

1789)     <br>

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

1791)     <br>

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

1793)     <p>

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

1802)     </p>

1803) 

1804)     <p>

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

1810)     </p>

1811) 

1812)     <p>

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

1817)     </p>
1818)     </li>

1819) 

1820)     <!--

1821)     <a id="vidaliaStatusEventInterface"></a>

1822)     <li>
1823)     <b>Tor Controller Status Event Interface for Vidalia</b>
1824)     <br>
1825)     Effort Level: <i>Medium</i>
1826)     <br>
1827)     Skill Level: <i>Low to Medium</i>
1828)     <br>

1829)     Likely Mentors: <i>Tomás</i>

1830)     <p>There are a number of status changes inside Tor of which the user may need
1831)     to be informed. For example, if the user is trying to set up his Tor as a
1832)     relay and Tor decides that its ports are not reachable from outside
1833)     the user's network, we should alert the user. Currently, all the user
1834)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1835)     likely never see since they don't receive a notification that something
1836)     has gone wrong. Even if the user does actually look at the message log,
1837)     most of the messages make little sense to the novice user.</p>
1838)     <p>Tor has the ability to inform Vidalia of many such status
1839)     changes, and we recently implemented support for a couple of these
1840)     events. Still, there are many more status events which the user should
1841)     be informed of, and we need a better UI for actually displaying them
1842)     to the user.</p>
1843)     <p>The goal of this project then is to design and implement a UI for
1844)     displaying Tor status events to the user. For example, we might put a
1845)     little badge on Vidalia's tray icon that alerts the user to new status
1846)     events they should look at. Double-clicking the icon could bring up a
1847)     dialog that summarizes recent status events in simple terms and maybe
1848)     suggests a remedy for any negative events if they can be corrected by
1849)     the user. Of course, this is just an example and one is free to
1850)     suggest another approach.</p>
1851)     <p>A person undertaking this project should have good UI design and layout
1852)     skills and some C++ development experience. Previous experience with Qt and
1853)     Qt's Designer will be very helpful, but are not required. Some
1854)     English writing ability will also be useful, since this project will
1855)     likely involve writing small amounts of help documentation that should
1856)     be understandable by non-technical users. Bonus points for some graphic
1857)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1858)     </li>

1859)     -->

1860) 

1861)     <!--

1862)     <a id="orbot-torbutton"></a>

1863)     <li>

1864)     <b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>

1865)     <br>

1866)     Effort Level: <i>High</i>

1867)     <br>
1868)     Skill Level: <i>High</i>
1869)     <br>

1870)     Likely Mentors: <i>Jake</i>

1871)     <p>Initial work has been done on implementing a proxy-setting add-on for
1872)     Firefox on Android (see <a
1873)     href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a
1874)     full port of TorButton needs to be done (dependent upon Firefox 4 port of
1875)     TorButton). The other approach is to implement a custom &quot;Tor
1876)     Browser&quot; based on Firefox or Webkit browser. See <a
1877)     href="http://code.google.com/p/torora/wiki/Android">Torora</a> for progress
1878)     on this so far.</p>

1879)     </li>

1880)     -->

1881) 

1882)     <!--

1883)     <a id="vidalia-hidden-service-panel"></a>

1884)     <li>

1885)     <b>Torrc plugin and improved hidden service configuration panel</b>

1886)     <br>
1887)     Effort Level: <i>Medium</i>
1888)     <br>
1889)     Skill Level: <i>Medium</i>
1890)     <br>

1891)     Likely Mentors: <i>Tomás</i>

1892)     <p>Vidalia's configuration handling has changed in the alpha branch. Now
1893)     every Tor option is saved in the torrc file. With that change, the
1894)     Hidden Service configuration panel was removed due to its specificity
1895)     and its multiple bugs.</p>

1896) 

1897)     <p>The idea would be to provide the new Torrc class' functionality to the
1898)     Plugin Engine and with that, create a better Hidden Service
1899)     configuration panel as a plugin.</p>

1900) 

1901)     <p>A person undertaking this project should have good UI design, layout
1902)     skills and some C++ development experience. Previous experience with Qt
1903)     and Qt's Designer will be very helpful, but are not required. Javascript
1904)     knowledge is a plus, but it shouldn't be a problem if the person
1905)     complies with the previous requirements.</p>

1906)     </li>

1907)     -->

1908) 

1909)     <!--

1910)     <a id="usabilityTesting"></a>

1911)     <li>

1912)     <b>Usability testing of Tor</b>

1913)     <br>

1914)     Effort Level: <i>Medium</i>

1915)     <br>

1916)     Skill Level: <i>Low to Medium</i>

1917)     <br>

1918)     Likely Mentors: <i>Andrew</i>

1919)     <p>

1920)     Especially the browser bundle, ideally amongst our target demographic.
1921)     That would help a lot in knowing what needs to be done in terms of bug
1922)     fixes or new features. We get this informally at the moment, but a more
1923)     structured process would be better.

1924)     </p>

1925) 

1926)     <p>

1927)     Please note that since this isn't a coding project, it isn't suitable for
1928)     Google Summer of Code.

1929)     </p>
1930)     </li>

1931)     -->

1932) 

1933)     <!--

1934)     <a id="docUpdate"></a>

1935)     <li>

1936)     <b>Website and video documentation update</b>

1937)     <br>
1938)     Effort Level: <i>Medium</i>
1939)     <br>
1940)     Skill Level: <i>Medium</i>
1941)     <br>

1942)     Likely Mentors: <i>Runa, Karen</i>

1943)     <p>

1944)     Identify outdated and/or weak pages on torproject.org and re-write the
1945)     documentation to appeal to a less technical, more goal-oriented
1946)     audience. Create a number of 3-5 minute videos with graphically
1947)     portray the written documentation. See
1948)     <a href="https://trac.torproject.org/projects/tor/query?component=Website&status=new">the
1949)     website tickets</a> for more information and a starting point.

1950)     </p>
1951)     </li>

1952)     -->

1953) 

1954)     <li>
1955)     <b>Bring up new ideas!</b>

1956)     <br>

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

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

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

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

1962)     might also be short on developers.
1963)     </li>

1964) 

1965)     </ol>

1966) 

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

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

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

1982) 

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

1988) 

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

1998) 

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

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

2003)     Tor if needed.</li>

2004) 

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

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

2010) 

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

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

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

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

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

2021) 

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

2025) 

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

2032) 

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

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

2036)     System</a>.
2037)     </li>

2038) 

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

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

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

2051) 

2052)     </ol>

2053) 

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

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

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

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

2156)     your browser's UserAgent string by replacing it with a uniform answer for
2157)     every Tor user. That way the attacker can't splinter Tor's anonymity set
2158)     by looking at that header. It tries to pick a string that is commonly used
2159)     by non-Tor users too, so it doesn't stand out. Question one: how badly
2160)     do we hurt ourselves by periodically updating the version of Firefox
2161)     that Torbutton claims to be? If we update it too often, we splinter the
2162)     anonymity sets ourselves. If we don't update it often enough, then all the
2163)     Tor users stand out because they claim to be running a quite old version
2164)     of Firefox. The answer here probably depends on the Firefox versions seen
2165)     in the wild. Question two: periodically people ask us to cycle through N
2166)     UserAgent strings rather than stick with one. Does this approach help,
2167)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
2168)     by their rotating UserAgents; malicious websites who only attack certain
2169)     browsers; and whether the answers to question one impact this answer.
2170)     </li>
2171)     <li>How many bridge relays do you need to know to maintain
2172)     reachability? We should measure the churn in our bridges. If there is
2173)     lots of churn, are there ways to keep bridge users more likely to stay
2174)     connected?
2175)     </li>
2176)     </ol>

2177) 

2178)     <p>
2179)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
2180)     of these!
2181)     </p>
2182)   </div>
2183)   <!-- END MAINCOL -->
2184)   <div id = "sidecol">
2185) #include "side.wmi"
2186) #include "info.wmi"
2187)   </div>
2188)   <!-- END SIDECOL -->
2189) </div>
2190) <!-- END CONTENT -->