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 web page and documentation into other
38)     languages. See the <a href="<page getinvolved/translation>">translation
39)     guidelines</a> if you want to help out. We especially need Arabic or
40)     Farsi translations, for the many Tor users in censored areas.</li>
41)     <li>Evaluate and document

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

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

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

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

49)     

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

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

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

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

58)     <a

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

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

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

62)     such as "Tor for Freedom!".</li>

63)     <li>Create a t-shirt design that incorporates "Congratulations!
64)     You are using Tor!" in any language.</li>

65)     </ol>

66)     

67)     <a id="Projects"></a>
68)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

69)     

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

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

77)     </p>

78)     

79)     <table id="projects">
80)       <tr>
81)         <th>Name</th>
82)         <th>Category</th>
83)         <th>Language</th>
84)         <th>Activity</th>
85)         <th>Contributors</th>
86)       </tr>

87)       

88)       <tr>
89)         <td><a href="#project-tor">Tor</a></td>
90)         <td>Core</td>
91)         <td>C</td>
92)         <td>Heavy</td>

93)         <td>nickm, arma, Sebastian</td>

94)       </tr>

95)       

96)       <tr class="alt">

97)         <td>*<a href="#project-jtor">JTor</a></td>
98)         <td>Core</td>
99)         <td>Java</td>
100)         <td>None</td>
101)         <td></td>
102)       </tr>

103)       

104)       <tr>

105)         <td><a href="#project-tbb">TBB</a></td>
106)         <td>Usability</td>

107)         <td>Sys Admin</td>
108)         <td>Moderate</td>

109)         <td>Erinn</td>

110)       </tr>

111)       

112)       <tr class="alt">

113)         <td><a href="#project-tails">Tails</a></td>

114)         <td>Usability</td>

115)         <td>Sys Admin</td>

116)         <td>Heavy</td>

117)         <td><a href="https://tails.boum.org/">#tails</a></td>

118)       </tr>

119)       

120)       <tr>

121)         <td><a href="#project-torsocks">Torsocks</a></td>
122)         <td>Usability</td>
123)         <td>C</td>

124)         <td>None</td>

125)         <td>mwenge</td>
126)       </tr>

127)       

128)       <tr class="alt">

129)         <td>*<a href="#project-torouter">Torouter</a></td>
130)         <td>Usability</td>

131)         <td>Sys Admin</td>

132)         <td>Light</td>

133)         <td>ioerror</td>

134)       </tr>

135)       

136)       <tr>

137)         <td><a href="#project-vidalia">Vidalia</a></td>
138)         <td>User Interface</td>
139)         <td>C++, Qt</td>
140)         <td>Light</td>
141)         <td>chiiph</td>
142)       </tr>

143)       

144)       <tr class="alt">

145)         <td><a href="#project-arm">Arm</a></td>
146)         <td>User Interface</td>
147)         <td>Python, Curses</td>

148)         <td>Light</td>

149)         <td>atagar</td>
150)       </tr>

151)       

152)       <tr>

153)         <td><a href="#project-orbot">Orbot</a></td>
154)         <td>User Interface</td>
155)         <td>Java</td>

156)         <td>Moderate</td>

157)         <td>n8fr8</td>
158)       </tr>

159)       

160)       <tr class="alt">

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

167)       

168)       <tr>

169)         <td><a href="#project-obfsproxy">Obfsproxy</a></td>
170)         <td>Client Add-on</td>
171)         <td>C</td>
172)         <td>Moderate</td>
173)         <td>nickm, asn</td>
174)       </tr>

175)       

176)       <tr class="alt">

177)         <td>*<a href="#project-thandy">Thandy</a></td>
178)         <td>Updater</td>
179)         <td>Python</td>
180)         <td>Light</td>

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

182)       </tr>

183)       

184)       <tr>

185)         <td>*<a href="#project-ooni-probe">Ooni Probe</a></td>
186)         <td>Scanner</td>
187)         <td>Python</td>
188)         <td>Moderate</td>
189)         <td>hellais, ioerror</td>
190)       </tr>

191)       

192)       <tr class="alt">

193)         <td><a href="#project-shadow">Shadow</a></td>
194)         <td>Experimentation</td>
195)         <td>C, Python</td>
196)         <td>Moderate</td>
197)         <td>robgjansen</td>
198)       </tr>

199)       

200)       <tr>

201)         <td><a href="#project-torctl">TorCtl</a></td>
202)         <td>Library</td>
203)         <td>Python</td>

204)         <td>None</td>
205)         <td>aagbsn</td>

206)       </tr>

207)       

208)       <tr class="alt">

209)         <td>*<a href="#project-stem">Stem</a></td>
210)         <td>Library</td>
211)         <td>Python</td>
212)         <td>Heavy</td>

213)         <td>atagar, neena</td>

214)       </tr>

215)       

216)       <tr>

217)         <td><a href="#project-metrics">Metrics</a></td>
218)         <td>Client Service</td>
219)         <td>Java</td>
220)         <td>Heavy</td>
221)         <td>karsten</td>
222)       </tr>

223)       

224)       <tr class="alt">

225)         <td><a href="#project-atlas">Atlas</a></td>
226)         <td>Client Service</td>
227)         <td>JavaScript</td>
228)         <td>Moderate</td>
229)         <td>hellais</td>
230)       </tr>

231)       

232)       <tr>

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

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

236)         <td>None</td>
237)         <td></td>
238)       </tr>

239)       

240)       <tr class="alt">

241)         <td><a href="#project-compass">Compass</a></td>
242)         <td>Client Service</td>
243)         <td>Python</td>
244)         <td>Heavy</td>
245)         <td>gsathya, karsten</td>
246)       </tr>
247)       
248)       <tr>

249)         <td><a href="#project-weather">Weather</a></td>
250)         <td>Client Service</td>
251)         <td>Python</td>

252)         <td>None</td>

253)         <td>kaner</td>
254)       </tr>

255)       

256)       <tr class="alt">

257)         <td><a href="#project-gettor">GetTor</a></td>
258)         <td>Client Service</td>
259)         <td>Python</td>

260)         <td>None</td>

261)         <td>kaner</td>

262)       </tr>

263)       

264)       <tr>

265)         <td><a href="#project-torcheck">TorCheck</a></td>
266)         <td>Client Service</td>
267)         <td>Python, Perl</td>
268)         <td>None</td>
269)         <td></td>
270)       </tr>

271)       

272)       <tr class="alt">

273)         <td><a href="#project-onionoo">Onionoo</a></td>
274)         <td>Backend Service</td>

275)         <td>Java, Python</td>

276)         <td>Moderate</td>

277)         <td>karsten, gsathya</td>

278)       </tr>

279)       

280)       <tr>

281)         <td><a href="#project-bridgedb">BridgeDB</a></td>
282)         <td>Backend Service</td>
283)         <td>Python</td>

284)         <td>None</td>

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

286)       </tr>

287)       

288)       <tr class="alt">

289)         <td><a href="#project-torflow">TorFlow</a></td>
290)         <td>Backend Service</td>
291)         <td>Python</td>

292)         <td>None</td>
293)         <td>aagbsn</td>

294)       </tr>

295)       

296)       <tr>

297)         <td>*<a href="#project-torbel">TorBEL</a></td>
298)         <td>Backend Service</td>
299)         <td>Python</td>
300)         <td>None</td>
301)         <td>Sebastian</td>
302)       </tr>
303)     </table>

304)     

305)     <sub>
306)     * Project is still in an alpha state.
307)     </sub>

308)     

309)     <br /><br />

310)     

311)     <a id="project-tor"></a>
312)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
313)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Client&component=Tor+Relay&component=vidalia&order=priority">bug
314)     tracker</a>)</h3>

315)     

316)     <p>
317)     Central project, providing the core software for using and participating in
318)     the Tor network. Numerous people contribute to the project to varying
319)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
320)     </p>

321)     

322)     <p>
323)     <b>Project Ideas:</b><br />
324)     <i><a href="#resistCensorship">Improving Tor's ability to resist

325)     censorship</a></i><br />
326)     <i><a href="#user-space-transport">Integrating Tor with user-space
327)     transport protocol libraries</a></i>

328)     </p>

329)     

330)     <a id="project-jtor"></a>
331)     <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a
332)     href="https://github.com/brl/JTor">code</a>, <a
333)     href="https://github.com/brl/JTor/issues">bug
334)     tracker</a>)</h3>

335)     

336)     <p>
337)     Java implementation of Tor and successor to <a
338)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
339)     isn't yet complete, and has been inactive since Fall 2010.
340)     </p>

341)     

342)     <a id="project-tbb"></a>
343)     <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
344)     href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
345)     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
346)     tracker</a>)</h3>

347)     

348)     <p>
349)     The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
350)     and Firefox preconfigured to work together out of the box. This is actively
351)     being worked on by Erinn Clark.
352)     </p>

353)     

354)     <p>
355)     <b>Project Ideas:</b><br />
356)     <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
357)     <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
358)     </p>

359)     

360)     <a id="project-tails"></a>

361)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

362)     href="http://git.immerda.ch/?p=amnesia.git;a=summary">code</a>, <a

363)     href="https://tails.boum.org/bugs/">bug

364)     tracker</a>)</h3>

365)     

366)     <p>

367)     The Amnesic Incognito Live System is a live CD/USB distribution

368)     preconfigured so that everything is safely routed through Tor and leaves no
369)     trace on the local system. This is a merger of the Amnesia and <a
370)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
371)     and still under very active development.
372)     </p>

373)     

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

376)     <i><a href="#tailsHiddenServicePetnames">Petname system for Tor hidden
377)     services</a></i><br />
378)     <i><a href="#tailsServer">Tails server: Self-hosted services behind
379)     Tails-powered Tor hidden services</a></i>

380)     </p>

381)     

382)     <a id="project-torsocks"></a>
383)     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
384)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
385)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
386)     tracker</a>)</h3>

387)     

388)     <p>
389)     Utility for adapting other applications to work with Tor. Development has
390)     slowed and compatibility issues remain with some platforms, but it's
391)     otherwise feature complete.
392)     </p>

393)     

394)     <!--

395)     <p>
396)     <b>Project Ideas:</b><br />
397)     <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
398)     </p>

399)     -->

400)     

401)     <a id="project-torouter"></a>
402)     <h3><a

403)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

406)     

407)     <p>
408)     Project to provide an easy-to-use, embedded Tor instance for routers. This

409)     had high activity in late 2010, but has since been rather quiet.

410)     </p>

411)     

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

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

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

417)     

418)     <p>
419)     The most commonly used user interface for Tor. Matt Edman started the
420)     project in 2006 and brought it to its current stable state. Development
421)     slowed for several years, though Tomás Touceda has since taken a lead with
422)     pushing the project forward.
423)     </p>

424)     

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

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

429)     </p>

430)     

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

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

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

436)     

437)     <p>
438)     Command-line monitor for Tor. This has been under very active development
439)     by its author, Damian Johnson, since early 2009 to make it a better
440)     general-purpose controller for *nix environments.
441)     </p>

442)     

443)     <!--

444)     <p>
445)     <b>Project Ideas:</b><br />

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

448)     </p>

449)     -->

450)     

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

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

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

456)     

457)     <p>
458)     Provides Tor on the Android platform. This was under very active
459)     development up through Fall 2010, after which things have been quiet.
460)     </p>

461)     

462)     <!--

463)     <p>
464)     <b>Project Ideas:</b><br />

465)     <i><a href="#orbot-torbutton">TorButton for Mobile Firefox 4 or Custom Browser on Android</a></i><br />
466)     <i><a href="#orbot-userInterface">Build a better user interface for Orbot</a></i><br />

467)     <i><a href="#orbot-optimisation">Core Tor mobile optimisation</a></i>

468)     </p>

469)     -->

470)     

471)     <a id="project-torbutton"></a>
472)     <h3><a href="<page torbutton/index>">Torbutton</a> (<a
473)     href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
474)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug
475)     tracker</a>)</h3>

476)     

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

484)     

485)     <a id="project-obfsproxy"></a>
486)     <h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc">Obfsproxy</a> (<a
487)     href="https://gitweb.torproject.org/obfsproxy.git">code</a>, <a
488)     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
489)     tracker</a>)</h3>

490)     

491)     <p>
492)     A proxy that shapes Tor traffic, making it harder for censors to detect and
493)     block Tor.
494)     </p>

495)     

496)     <p>
497)     <b>Project Ideas:</b><br />
498)     <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
499)     <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
500)     <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
501)     </p>

502)     

503)     <a id="project-thandy"></a>
504)     <h3>Thandy (<a
505)     href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>

506)     

507)     <p>
508)     Updater for Tor. The project began in the Summer of 2008 but wasn't
509)     completed. Recently interest in it has been rekindled and many aspects of
510)     its design (including the language it'll be in) are currently in flux.
511)     </p>

512)     

513)     <a id="project-ooni-probe"></a>
514)     <h3>Ooni Probe (<a
515)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
516)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
517)     tracker</a>)</h3>

518)     

519)     <p>
520)     Censorship scanner, checking your local connection for blocked or modified
521)     content.
522)     </p>

523)     

524)     <a id="project-shadow"></a>
525)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
526)     href="https://github.com/shadow">code</a>, <a
527)     href="https://github.com/shadow/shadow/issues">bug
528)     tracker</a>)</h3>

529)     

530)     <p>
531)     Shadow is a discrete-event network simulator that runs the real
532)     Tor software as a plug-in. Shadow is open-source software that enables
533)     accurate, efficient, controlled, and repeatable Tor experimentation.
534)     </p>

535)     

536)     <a id="project-torctl"></a>
537)     <h3>TorCtl (<a
538)     href="https://gitweb.torproject.org/pytorctl.git">code</a>, <a
539)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority">bug
540)     tracker</a>)</h3>

541)     

542)     <p>
543)     Python bindings and utilities for using the Tor control port. It has been
544)     stable for several years, with only minor revisions.
545)     </p>

546)     

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

548)     <h3><a href="https://stem.readthedocs.org/en/latest/index.html">Stem</a> (<a

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

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

551)     tracker</a>)</h3>

552)     

553)     <p>
554)     Python controller library with a similar scope to TorCtl, but with better
555)     testing, documentation, and API. This project is not yet feature complete.
556)     </p>

557)     

558)     <p>
559)     <b>Project Ideas:</b><br />
560)     <i><a href="#stemPathsupport">Stem PathSupport Capabilities</a></i>
561)     </p>

562)     

563)     <a id="project-metrics"></a>
564)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
565)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
566)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
567)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
568)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
569)     tracker</a>)</h3>

570)     

571)     <p>
572)     Processing and analytics of consensus data, provided to users via the
573)     metrics portal. This has been under active development for several years by
574)     Karsten Loesing.
575)     </p>

576)     

577)     <p>
578)     <b>Project Ideas:</b><br />
579)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
580)     </p>

581)     

582)     <a id="project-atlas"></a>
583)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
584)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

585)     

586)     <p>
587)     Atlas is a web application to discover Tor relays and bridges. It provides
588)     useful information on how relays are configured along with graphics about
589)     their past usage. This is the third evolution of the TorStatus application.
590)     </p>

591)     

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

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

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

595)     

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

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

603)     </p>

604)     

605)     <a id="project-compass"></a>
606)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
607)     href="https://gitweb.torproject.org/compass.git">code</a>, <a
608)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Compass&order=priority">bug
609)     tracker</a>)</h3>
610)     
611)     <p>
612)     Compass is a web and command line application that filters and
613)     aggregates the Tor relays based on various attributes.
614)     </p>
615)     

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

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

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

621)     

622)     <p>
623)     Provides automatic notification to subscribed relay operators when their
624)     relay's unreachable. This underwent a rewrite by the <a
625)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
626)     in early 2011.
627)     </p>

628)     

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

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

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

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

634)     

635)     <p>
636)     E-mail autoresponder providing Tor's packages over SMTP. This has been
637)     relatively unchanged for quite a while.
638)     </p>

639)     

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

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

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

645)     

646)     <p>
647)     Provides a simple site for determining if the visitor is using Tor or not.
648)     This has been relatively unchanged for quite a while.
649)     </p>

650)     

651)     <a id="project-onionoo"></a>
652)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a

653)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
654)     href="https://gitweb.torproject.org/pyonionoo.git">python
655)     codebase</a>)</h3>

656)     

657)     <p>
658)     Onionoo is a JSON based protocol to learn information about currently
659)     running Tor relays and bridges.
660)     </p>

661)     

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

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

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

667)     

668)     <p>
669)     Backend bridge distributor, handling the various pools they're distributed
670)     in. This was actively developed until Fall of 2010.
671)     </p>

672)     

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

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

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

678)     

679)     <p>
680)     Library and collection of services for actively monitoring the Tor network.
681)     These include the Bandwidth Scanners (measuring throughput of relays) and
682)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
683)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
684)     months later. Both have been under active use since then, but development
685)     has stopped.
686)     </p>

687)     

688)     <a id="project-torbel"></a>
689)     <h3><a

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

692)     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
693)     tracker</a>)</h3>

694)     

695)     <p>
696)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
697)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
698)     (though unmaintained) Haskell application for this purpose. The initial
699)     version of TorBEL was started in GSOC 2010 but since then the project has
700)     been inactive.
701)     </p>

702)     

703)     <a id="Coding"></a>
704)     <a id="Summer"></a>

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

706)     

707)     <p>
708)     You may find some of these projects to be good <a href="<page

709)     about/gsoc>">Google Summer of Code</a> ideas. We have labelled each idea

710)     with how useful it would be to the overall Tor project (priority), how
711)     much work we expect it would be (effort level), how much clue you should
712)     start with (skill level), and which of our <a href="<page

713)     about/corepeople>">core developers</a> would be good mentors.

714)     If one or more of these ideas looks promising to you, please <a
715)     href="<page about/contact>">contact us</a> to discuss your plans rather than
716)     sending blind applications. You may also want to propose your own project
717)     idea &mdash; which often results in the best applications.
718)     </p>

719)     

720)     <ol>

721)     

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

723)     <li>

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

725)     <br>

726)     Priority: <i>High</i>

727)     <br>

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

729)     <br>

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

731)     <br>

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

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

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

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

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

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

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

747)     </li>

748)     

749)     <a id="firewallProbeTool"></a>
750)     <li>
751)     <b>Develop a fully automatic firewall-probing system</b>
752)     <br>
753)     Priority: <i>High</i>
754)     <br>
755)     Effort Level: <i>Medium to High</i>
756)     <br>
757)     Skill Level: <i>High</i>
758)     <br>

759)     Likely Mentors: <i>Robert Ransom, Jacob</i>

760)     <p>We would like to have a fully automatic firewall-probing system for
761)     blocking systems with no long-term state (i.e. firewalls that can
762)     examine each connection, but do not change their behaviour for future
763)     connections based on the traffic they have seen).</p>
764)     <p>Ideally, volunteers would only need to set up one or more test servers,
765)     and run the probe client program on a publicly accessible computer
766)     behind the firewall.</p>
767)     <p>The test tool should:</p>
768)     <ul>
769)     <li>generate packet captures on both ends (and send them out to the
770)         extent possible),</li>
771)     <li>cycle through all the SSL configurations we might want to test
772)         through a censorship device, and</li>
773)     <li>also test some other protocols to see whether they are allowed
774)         through the firewall (IMAP and other mail protocols, BitTorrent,
775)         DTLS, etc.).</li>
776)     </ul>
777)     </li>

778)     

779)     <!--

780)     <a id="orbot-torbutton"></a>
781)     <li>
782)     <b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>
783)     <br>
784)     Priority: <i>High</i>
785)     <br>
786)     Effort Level: <i>High</i>
787)     <br>
788)     Skill Level: <i>High</i>
789)     <br>

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

791)     <p>Initial work has been done on implementing a proxy-setting add-on for
792)     Firefox on Android (see <a
793)     href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a
794)     full port of TorButton needs to be done (dependent upon Firefox 4 port of
795)     TorButton). The other approach is to implement a custom &quot;Tor
796)     Browser&quot; based on Firefox or Webkit browser. See <a
797)     href="http://code.google.com/p/torora/wiki/Android">Torora</a> for progress
798)     on this so far.</p>
799)     </li>

800)     -->

801)     

802)     <a id="obfsproxy-new-transports"></a>
803)     <li>
804)     <b>New and innovative pluggable transports</b>
805)     <br>
806)     Priority: <i>High</i>
807)     <br>
808)     Effort Level: <i>High</i>
809)     <br>
810)     Skill Level: <i>High</i>
811)     <br>

812)     Likely Mentors: <i>asn, Steven</i>

813)     <p>Not-very-smart transports like ROT13 and base64 are nice but not super
814)     interesting. Other ideas like bittorrent transports might be relevant,
815)     but you will have to provide security proofs on why they are harder to
816)     detect and block than other less-sophisticated transports.</p>

817)     

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

820)     

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

823)     

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

828)     

829)     <a id="obfsproxy-scanning-measures"></a>
830)     <li>
831)     <b>Defensive bridge active scanning measures</b>
832)     <br>
833)     Priority: <i>High</i>
834)     <br>
835)     Effort Level: <i>High</i>
836)     <br>
837)     Skill Level: <i>High</i>
838)     <br>
839)     Likely Mentors: <i>asn</i>
840)     <p>Involves providing good answers to <a
841)     href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html">this
842)     thread</a> as well as concrete implementation plans for it.</p>

843)     

844)     <p>This also involves implementing proposals <a
845)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a>
846)     and <a
847)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p>
848)     </li>

849)     

850)     <a id="stemPathsupport"></a>
851)     <li>
852)     <b>Stem PathSupport Capabilities</b>
853)     <br>
854)     Priority: <i>High</i>
855)     <br>
856)     Effort Level: <i>High</i>
857)     <br>
858)     Skill Level: <i>Medium</i>
859)     <br>
860)     Likely Mentors: <i>Damian (atagar)</i>
861)     <p><a
862)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a
863)     python controller library for tor. Like it's predecessor, <a
864)     href="#project-torctl">TorCtl</a>, it uses tor's <a
865)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control
866)     protocol</a> to help developers program against the tor process, enabling
867)     them to build things similar to <a href="#project-vidalia">Vidalia</a> and
868)     <a href="#project-arm">arm</a>.</p>

869)     

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

874)     

875)     <p>At the moment stem is still very much incomplete, missing several pieces
876)     of functionality that TorCtl provides. This is a project to fix that by
877)     porting TorCtl's <a
878)     href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport
879)     module</a> to stem, writing tests for it, and migrate a couple clients to
880)     use it.</p>

881)     

882)     <p>PathSupport provides applications with programmatic control over how
883)     tor's circuits are built, for instance letting you exit from particular
884)     relays. This is used by projects like <a href="#project-torbel">TorBEL</a>,
885)     <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>.</p>

886)     

887)     <p>This project can be broken into three parts...</p>

888)     

889)     <ol style="list-style-type: decimal">
890)       <li><p>Look at PathSupport's clients to figure out how it is used and
891)       come up with the API that we will use for stem. Note that the goal if
892)       this project is <b>not</b> to simply copy PathSupport, but to make it
893)       better. This task would ideally be done as part of writing the GSoC
894)       application.</p></li>
895)       <li><p>Implement the PathSupport counterpart for stem. This should be
896)       done in an incremental fashion, writing the feature, tests, and going
897)       through a code review before moving on. I'll be pretty anal about making
898)       it as good as we can during these code reviews so plan for this to take a
899)       while. ;)</p></li>
900)       <li><p>The real test of the API that you've developed will come when we
901)       use it in some real applications. Try to migrate a TorCtl client or two
902)       to stem, filling in functionality that we're missing and improving our
903)       API as we discover issues. A particularly good client to start with would
904)       be TorBEL.</p></li>
905)     </ol>

906)     

907)     <p><b>
908)     Upon reflection this is not an especially good project for this year's GSoC. You are still perfectly wecome to apply for this project, but <a href="https://trac.torproject.org/projects/tor/wiki/doc/stem">other stem related tasks</a> such as implementing a general controller, descriptor fetching, and client migrations would be better. For the discussion that lead to this see <a href="http://archives.seul.org/or/dev/Apr-2012/msg00006.html">this thread</a>.
909)     </b></p>
910)     </li>
911)     

912)     <!--

913)     <a id="orbot-userInterface"></a>
914)     <li>
915)     <b>Build a better user interface for Orbot</b>
916)     <br>
917)     Priority: <i>High</i>
918)     <br>
919)     Effort Level: <i>Medium</i>
920)     <br>
921)     Skill Level: <i>Medium</i>
922)     <br>

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

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

938)     -->

939)     

940)     <a id="user-space-transport"></a>
941)     <li>
942)     <b>Integrating Tor with user-space transport protocol libraries</b>
943)     <br>
944)     Priority: <i>Medium to High</i>
945)     <br>
946)     Effort Level: <i>High</i>
947)     <br>
948)     Skill Level: <i>High</i>
949)     <br>
950)     Likely Mentors: <i>Steven</i>
951)     <p>Tor currently sends data over TCP links between nodes. <a
952)     href="http://static.usenix.org/events/sec09/tech/full_papers/reardon.pdf">Prior
953)     research</a> has indicated that this may not be optimal, and instead the
954)     role that TCP plays (congestion control and reliability) should be moved
955)     into Tor itself. This would allow a number of desirable changes, such as
956)     preventing errors on one circuit delaying another, and giving Tor control
957)     and visibility of congestion control.</p>
958)     <p>There are <a
959)     href="http://www.cl.cam.ac.uk/~sjm217/papers/tor11datagramcomparison.pdf">many
960)     ways to do this</a>, each with their own tradeoffs and difficulty of
961)     implementation. This project will be to select one (or more) option and
962)     implement it in Tor. The primary goal will be to test this modified version
963)     of Tor in simulation, but if it turns out to work well, it could be
964)     deployed in the live Tor network.</p>
965)     <p>Excellent C programming skills are needed, and knowledge of Tor
966)     internals are highly desirable.</p>
967)     </li>

968)     

969)     <a id="resistCensorship"></a>

970)     <li>
971)     <b>Improving Tor's ability to resist censorship</b>

972)     <br>

973)     Priority: <i>Medium to High</i>

974)     <br>

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

976)     <br>

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

978)     <br>

979)     Likely Mentors: <i>Jake, Thomas</i>

980)     <p>The Tor 0.2.1.x series makes <a

981)     href="<svnprojects>design-paper/blocking.html">significant
982)     improvements</a> in resisting national and organizational censorship.
983)     But Tor still needs better mechanisms for some parts of its

984)     anti-censorship design.</p>
985)     <p>One huge category of work is adding features to our <a

986)     href="https://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a>

987)     service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge
988)     relay addresses</a> to users that can't reach the Tor network
989)     directly, but there's an arms race between algorithms for distributing
990)     addresses and algorithms for gathering and blocking them. See <a

991)     href="<blog>bridge-distribution-strategies">our

992)     blog post on the topic</a> as an overview, and then look at <a

993)     href="https://lists.torproject.org/pipermail/tor-dev/2009-December/000666.html">Roger's
994)     or-dev post</a> from December 2009 for more recent thoughts &mdash; lots of

995)     design work remains.</p>
996)     <p>If you want to get more into the guts of Tor itself (C), a more minor problem

997)     we should address is that current Tors can only listen on a single
998)     address/port combination at a time. There's

999)     <a href="<specblob>proposals/118-multiple-orports.txt">a

1000)     proposal to address this limitation</a> and allow clients to connect
1001)     to any given Tor on multiple addresses and ports, but it needs more

1002)     work.</p>
1003)     <p>This project could involve a lot of research and design. One of the big

1004)     challenges will be identifying and crafting approaches that can still
1005)     resist an adversary even after the adversary knows the design, and

1006)     then trading off censorship resistance with usability and
1007)     robustness.</p>

1008)     </li>

1009)     

1010)     <a id="tailsHiddenServicePetnames"></a>
1011)     <li>
1012)     <b>Petname system for Tor hidden services</b>
1013)     <br>
1014)     Priority: <i>Medium</i>
1015)     <br>
1016)     Effort Level: <i>High</i>
1017)     <br>
1018)     Skill Level: <i>High</i>
1019)     <br>
1020)     Likely Mentors: <i>ague</i>
1021)     <p>Tor provides hidden services. These services are only reachable through
1022)     Tor itself, and provide greater anonymity both for the providers of the
1023)     service and for its users.</p>
1024)     <p>One current downside of Tor hidden services is that they are addressed
1025)     using 80-bit base32-encoded addresses such as "v2cbb2l4lsnpio4q.onion".
1026)     These addresses are hard to remember; this makes them hard to use
1027)     within amnesic environment like Tails.</p>
1028)     <p>The project is to implement a petname system for Tor hidden services:
1029)     a way for users or providers of Tor hidden services to add a simple
1030)     'nickname' to a central database. Users could then query this central
1031)     database to retrieve a full hidden service address by giving
1032)     a nickname.</p>
1033)     <p>Adding petnames to the database could be done using a web interface or
1034)     automated fetch like those described in the <a
1035)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/ideas/xxx-onion-nyms.txt">&quot;.onion
1036)     nym system&quot; proposal</a>.</p>
1037)     <p>Querying the database could be done using a web interface, a REST API and
1038)     a DNS interface.</p>
1039)     <p>In order not to grow indefinitely, the software should make regular tests to
1040)     see if hidden services are still reachable and, depending on the last time
1041)     a nickname was accessed, cleanup the database as necessary.</p>
1042)     <p>The software should allow a distributed, fault-tolerant setup.
1043)     All nodes should have a synchronized copy of the database, should be
1044)     ready to answer queries and should coordinate the tests for hidden
1045)     service availability.</p>
1046)     <p>The resulting codebase must be easy to deploy: it should not be hard to
1047)     setup new databases.</p>
1048)     <p>It is expected that the volunteer will be using Behaviour Driven
1049)     Development methods. Either in Ruby using Cucumber and RSpec, or in
1050)     Python using similar tools.</p>
1051)     </li>

1052)     

1053)     <a id="tailsServer"></a>
1054)     <li>
1055)     <b>Tails server: Self-hosted services behind Tails-powered Tor hidden services</b>
1056)     <br>
1057)     Priority: <i>Medium</i>
1058)     <br>
1059)     Effort Level: <i>High</i>
1060)     <br>
1061)     Skill Level: <i>Medium, but wide-scoped</i>
1062)     <br>
1063)     Likely Mentors: <i>intrigeri, anonym</i>
1064)     <p>Let's talk about group collaboration, communication and data sharing
1065)     infrastructure, such as chat servers, wikis, or file repositories.</p>
1066)     <p>Hosting such data and infrastructure <b>in the cloud</b> generally
1067)     implies to trust the service providers not to disclose content, usage or
1068)     users location information to third-parties. Hence, there are many threat
1069)     models in which cloud hosting is not suitable.</p>
1070)     <p>Tor partly answers the <b>users location</b> part; this is great, but
1071)     <b>content</b> is left unprotected.</p>
1072)     <p>There are two main ways to protect such content: either to encrypt it
1073)     client-side (<b>security by design</b>), or to avoid putting it into
1074)     untrusted hands in the first place.</p>
1075)     <p>Cloud solutions that offer security by design are rare and generally
1076)     not mature yet. The <b>Tails server</b> project is about exploring the
1077)     other side of the alternative: avoiding to put private data into
1078)     untrusted hands in the first place.</p>
1079)     <p>This is made possible thanks to Tor hidden services, that allow users
1080)     to offer location-hidden services, and make self-hosting possible in
1081)     many threat models. Self-hosting has its own lot of problems, however,
1082)     particularly in contexts where the physical security of the hosting
1083)     place is not assured. Combining Tor hidden services with Tails'
1084)     amnesia property and limited support for persistent encrypted data
1085)     allows to protect content, to a great degree, even in such contexts.</p>
1086)     <p>In short, setting up a new Tails server would be done by:</p>

1087)     

1088)     <ol style="list-style-type: decimal">
1089)       <li>Alice plugs a USB stick into a running desktop Tails system.</li>
1090)       <li>Alice uses a GUI to easily configure the needed services.</li>
1091)       <li>Alice unplugs the USB stick, that now contains encrypted services
1092)       configuration and data storage space.</li>
1093)       <li>Alice plugs that USB stick (and possibly a Tails Live CD) into the
1094)       old laptop that was dedicated to run Tails server.</li>
1095)       <li>Once booted, Alice enters the encryption passphrase either
1096)       directly using the keyboard or through a web interface listening on the
1097)       local network.</li>
1098)       <li>Then, Bob can use the configured services once he gets a hold on
1099)       the hidden service address. (The <b>petname system for Tor hidden
1100)       services</b> project would be very complementary to this one, by the
1101)       way.)</li>
1102)     </ol>

1103)     

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

1108)     

1109)     <ul>
1110)       <li>Design and write the services configuration GUI [keywords: edit
1111)       configuration files, upgrade between major Debian versions,
1112)       debconf].</li>
1113)       <li>How to create the hidden service key? [keywords: Vidalia, control
1114)       protocol].</li>
1115)       <li>Adapt the Tails boot process to allow switching to &quot;server
1116)       mode&quot; when appropriate.</li>
1117)       <li>Add support, to the Tails persistence setup process, for asking an
1118)       encryption passphrase without X, and possibly with a broken keyboard
1119)       and/or screen [keywords: local network, SSL/TLS?, certificate?].</li>
1120)     </ul>

1121)     

1122)     <p>This project can easily grow quite large, so the first task would
1123)     probably be to clarify what it would need to get an initial (minimal
1124)     but working) implementation ready to be shipped to users.</p>
1125)     <p>This project does not require to be an expert in one specific field,
1126)     but it requires to be experienced and at ease with a large scope of
1127)     software development tools, processes, and operating system knowledge.</p>
1128)     <p>Undertaking this project requires in-depth knowledge of Debian-like
1129)     systems (self-test: do the "dpkg conffile" and "debconf preseeding"
1130)     words sound new to your ear?); the Debian Live persistence system
1131)     being written in shell, being at ease with robust shell scripting is
1132)     a must; to end with, at least two pieces of software need to be
1133)     written from scratch (a GUI and a webapp): the preferred languages for
1134)     these tasks would be Python and Perl. Using Behaviour Driven
1135)     Development methods to convey expectations and acceptance criteria
1136)     would be most welcome.</p>
1137)     <p>For more information see https://tails.boum.org/todo/server_edition/</p>
1138)     </li>

1139)     

1140)     <a id="geoIPUpgrade"></a>
1141)     <li>
1142)     <b>Improve our GeoIP file format</b>
1143)     <br>
1144)     Priority: <i>Medium</i>
1145)     <br>
1146)     Effort Level: <i>Medium</i>
1147)     <br>
1148)     Skill Level: <i>Medium to High</i>
1149)     <br>
1150)     Likely Mentors: <i>Robert Ransom</i>

1151)     <p>Currently, Tor bridges and relays read an entire IP-&gt;country database

1152)     into memory from a text file during startup.  We would like to
1153)     distribute this database and store it on disk in a much more compact

1154)     form, and perform IP->country lookups on it in its on-disk format if

1155)     possible.</p>

1156)     <p>We have <a href='https://trac.torproject.org/projects/tor/ticket/2506'>a
1157)     sketch of a design</a> for a moderately optimized format for IPv4 GeoIP
1158)     data; this project will involve both implementing the IPv4 format and
1159)     designing and implementing a format for IPv6 GeoIP data.</p>

1160)     <p>Since the core of this project is researching IPv6 GeoIP data and

1161)     designing the IPv6 format, this is not likely to be a good GSoC

1162)     project.</p>

1163)     </li>

1164)     

1165)     <!--

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

1167)     <li>
1168)     <b>Client Mode Use Cases for Arm</b>
1169)     <br>
1170)     Priority: <i>Medium</i>
1171)     <br>
1172)     Effort Level: <i>High</i>
1173)     <br>
1174)     Skill Level: <i>Medium</i>
1175)     <br>

1176)     Likely Mentors: <i>Damian (atagar)</i>

1177)     <p><a href="<page projects/arm>">Arm</a> is a Tor command line status
1178)     monitor on *nix environments (Linux, Mac, and BSD). It functions much like
1179)     top does, giving a CLI overlay of Tor's bandwidth usage, connections,
1180)     configuration, log, etc. Thus far its design has been geared for Tor relay
1181)     operators. However, this doesn't need to be the case. This project would be
1182)     to expand and simplify arm to make it useful for Tor's client users
1183)     too.</p>

1184)     

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

1187)     

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

1197)       

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

1200)       

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

1203)       

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

1208)       

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

1212)       

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

1216)       

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

1219)     

1220)     <p>

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

1222)     </p>

1223)     </li>

1224)     -->

1225)     

1226)     <a id="vidalia-hidden-service-panel"></a>
1227)     <li>
1228)     <b>Torrc plugin and improved hidden service configuration panel</b>
1229)     <br>
1230)     Priority: <i>Medium</i>
1231)     <br>
1232)     Effort Level: <i>Medium</i>
1233)     <br>
1234)     Skill Level: <i>Medium</i>
1235)     <br>
1236)     Likely Mentors: <i>Tomás</i>
1237)     <p>Vidalia's configuration handling has changed in the alpha branch. Now
1238)     every Tor option is saved in the torrc file. With that change, the
1239)     Hidden Service configuration panel was removed due to its specificity
1240)     and its multiple bugs.</p>

1241)     

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

1245)     

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

1252)     

1253)     <a id="metricsSearch"></a>
1254)     <li>
1255)     <b>Searchable Tor descriptor and Metrics data archive</b>
1256)     <br>
1257)     Priority: <i>Medium</i>
1258)     <br>
1259)     Effort Level: <i>Medium</i>
1260)     <br>
1261)     Skill Level: <i>Medium</i>
1262)     <br>
1263)     Likely Mentors: <i>Karsten</i>

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

1265)     

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

1267)     

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

1269)     

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

1271)     

1272)     <!--

1273)     <a id="unitTesting"></a>

1274)     <li>
1275)     <b>Improve our unit testing process</b>

1276)     <br>

1277)     Priority: <i>Medium</i>

1278)     <br>

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

1280)     <br>

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

1282)     <br>

1283)     Likely Mentors: <i>Nick, Erinn</i>

1284)     <p>Tor needs to be tested far more thoroughly. This is a
1285)     multi-part effort. To start with, our unit test coverage should
1286)     rise substantially, especially in the areas outside the utility
1287)     functions. This will require significant refactoring of some parts
1288)     of Tor, in order to dissociate as much logic as possible from
1289)     globals.</p>

1290)     <p>Additionally, we need to automate our performance testing. We've got

1291)     buildbot to automate our regular integration and compile testing already
1292)     (though we need somebody to set it up on Windows),
1293)     but we need to get our network simulation tests (as built in <a
1294)     href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
1295)     updated for more recent versions of Tor, and designed to launch a test
1296)     network either on a single machine, or across several, so we can test

1297)     changes in performance on machines in different roles automatically.</p>

1298)     </li>

1299)     -->

1300)     

1301)     <!--

1302)     <a id="simulateSlowConnections"></a>

1303)     <li>
1304)     <b>Simulator for slow Internet connections</b>

1305)     <br>

1306)     Priority: <i>Medium</i>

1307)     <br>

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

1309)     <br>

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

1311)     <br>

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

1313)     <p>

1314)     Many users of Tor have poor-quality Internet connections, giving low
1315)     bandwidth, high latency, and high packet loss/re-ordering. User
1316)     experience is that Tor reacts badly to these conditions, but it is
1317)     difficult to improve the situation without being able to repeat the
1318)     problems in the lab.

1319)     </p>

1320)     

1321)     <p>

1322)     This project would be to build a simulation environment which
1323)     replicates the poor connectivity so that the effect on Tor performance
1324)     can be measured. Other components would be a testing utility to
1325)     establish what are the properties of connections available, and to
1326)     measure the effect of performance-improving modifications to Tor.

1327)     </p>

1328)     

1329)     <p>

1330)     The tools used would be up to the student, but dummynet (for FreeBSD)
1331)     and nistnet (for Linux) are two potential components on which this
1332)     project could be built. Students should be experienced with network
1333)     programming/debugging and TCP/IP, and preferably familiar with C and a
1334)     scripting language.

1335)     </p>

1336)     </li>

1337)     -->

1338)     

1339)     <a id="improveTorbirdy"></a>

1340)     <li>

1341)     <b>Improving TorBirdy</b>

1342)     <br>

1343)     Priority: <i>High</i>

1344)     <br>

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

1346)     <br>

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

1348)     <br>

1349)     Likely Mentors: <i>Sukhbir, Jacob</i>
1350)     <p>
1351)     TorBirdy is Torbutton for Thunderbird, Icedove and related Mozilla mail
1352)     clients.
1353)     </p>
1354)     <p>
1355)     TorBirdy is under active development and is available from <a
1356)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy">our wiki</a>
1357)     and <a
1358)     href="https://addons.mozilla.org/en-US/thunderbird/addon/torbirdy/">mozilla's
1359)     addons site</a>.
1360)     </p>
1361)     
1362)     <p>
1363)     The goal of this project is to improve TorBirdy by:
1364)     </p>
1365)     
1366)     <ul>
1367)       <li>
1368)         Writing a Thunderbird patch to plug known leaks. We have already <a
1369)         href="https://bugzilla.mozilla.org/show_bug.cgi?id=776397">submitted a
1370)         patch to Thunderbird</a> but we anticipate there will be much more work
1371)         required before it is accepted, possibly involving rewriting the entire
1372)         patch; this appears trivial, but it is not, as we are proposing a
1373)         completely new privacy-safe message-ID header generation algorithm for
1374)         Thunderbird.
1375)       </li>
1376)       <li>
1377)         Implementing a JavaScript HTTP proxy (see the <a
1378)         href="https://trac.torproject.org/projects/tor/ticket/6958">ticket</a>)
1379)       </li>
1380)       <li>
1381)         Auditing TorBirdy for leaks and for use with other add-ons (as an
1382)         example see its <a
1383)         href="https://trac.torproject.org/projects/tor/ticket/6319">ticket</a>)
1384)       </li>
1385)     </ul>
1386)     

1387)     <p>

1388)     A student undertaking this project should have some C++ and JavaScript
1389)     development experience. Previous experience with Firefox/Thunderbird
1390)     extension development is a plus, but not required.

1391)     </p>

1392)     </li>

1393)     

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

1395)     <li>
1396)     <b>Usability testing of Tor</b>

1397)     <br>

1398)     Priority: <i>Medium</i>

1399)     <br>

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

1401)     <br>

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

1403)     <br>

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

1405)     <p>

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

1410)     </p>

1411)     

1412)     <p>
1413)     Please note that since this isn't a coding project, it isn't suitable for
1414)     Google Summer of Code.
1415)     </p>

1416)     </li>

1417)     

1418)     <!--

1419)     <a id="torsocksForOSX"></a>

1420)     <li>
1421)     <b>Make torsocks/dsocks work on OS X</b>

1422)     <br>

1423)     Priority: <i>Medium</i>

1424)     <br>

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

1426)     <br>

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

1428)     <br>

1429)     Likely Mentors: <i>Robert Hogan</i>

1430)     <p>

1431)     <a href="https://code.google.com/p/torsocks/">Torsocks</a> and <a
1432)     href="https://code.google.com/p/dsocks/">dsocks</a> are wrappers that will

1433)     run applications, intercept their outgoing network connections, and push
1434)     those connections through Tor. The goal is to handle applications that
1435)     don't support proxies (or don't supporting them well). To get it right,
1436)     they need to intercept many system calls. The syscalls you need to
1437)     intercept on Linux differ dramatically from those on BSD. So Torsocks
1438)     works fine on Linux, dsocks works ok on BSD (though it may be less
1439)     maintained and thus might miss more syscalls), and nothing works well
1440)     on both. First, we should patch dsocks to use Tor's <i>mapaddress</i>
1441)     commands from the controller interface, so we don't waste a whole
1442)     round-trip inside Tor doing the resolve before connecting. Second,
1443)     we should make our <i>torify</i> script detect which of torsocks or
1444)     dsocks is installed, and call them appropriately. This probably means
1445)     unifying their interfaces, and might involve sharing code between them
1446)     or discarding one entirely.

1447)     </p>
1448)     </li>

1449)     -->

1450)     

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

1452)     <li>
1453)     <b>Tor Controller Status Event Interface for Vidalia</b>
1454)     <br>
1455)     Priority: <i>Medium</i>
1456)     <br>
1457)     Effort Level: <i>Medium</i>
1458)     <br>
1459)     Skill Level: <i>Low to Medium</i>
1460)     <br>

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

1462)     <p>There are a number of status changes inside Tor of which the user may need
1463)     to be informed. For example, if the user is trying to set up his Tor as a
1464)     relay and Tor decides that its ports are not reachable from outside
1465)     the user's network, we should alert the user. Currently, all the user
1466)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1467)     likely never see since they don't receive a notification that something
1468)     has gone wrong. Even if the user does actually look at the message log,
1469)     most of the messages make little sense to the novice user.</p>
1470)     <p>Tor has the ability to inform Vidalia of many such status
1471)     changes, and we recently implemented support for a couple of these
1472)     events. Still, there are many more status events which the user should
1473)     be informed of, and we need a better UI for actually displaying them
1474)     to the user.</p>
1475)     <p>The goal of this project then is to design and implement a UI for
1476)     displaying Tor status events to the user. For example, we might put a
1477)     little badge on Vidalia's tray icon that alerts the user to new status
1478)     events they should look at. Double-clicking the icon could bring up a
1479)     dialog that summarizes recent status events in simple terms and maybe
1480)     suggests a remedy for any negative events if they can be corrected by
1481)     the user. Of course, this is just an example and one is free to
1482)     suggest another approach.</p>
1483)     <p>A person undertaking this project should have good UI design and layout
1484)     skills and some C++ development experience. Previous experience with Qt and
1485)     Qt's Designer will be very helpful, but are not required. Some
1486)     English writing ability will also be useful, since this project will
1487)     likely involve writing small amounts of help documentation that should
1488)     be understandable by non-technical users. Bonus points for some graphic
1489)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1490)     </li>

1491)     

1492)     <!--

1493)     <a id="orbot-optimisation"></a>
1494)     <li>
1495)     <b>Core Tor mobile optimisation</b>
1496)     <br>
1497)     Priority: <i>Medium</i>
1498)     <br>
1499)     Effort Level: <i>Medium</i>
1500)     <br>
1501)     Skill Level: <i>High</i>
1502)     <br>

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

1504)     <p>
1505)     The existing port of Tor to Android is basically a straight
1506)     cross-compile to Linux ARM. There has been no work done in looking at
1507)     possible optimizations of Tor within a mobile hardware environment or on
1508)     mobile networks. In addition, a number of additional Android OS APIs are
1509)     available (such as wireless network status) that could be taken
1510)     advantage of.
1511)     </p>

1512)     

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

1522)     

1523)     <p>
1524)     Finally, the build process needs to be moved to the Android NDK from the
1525)     custom GCC toolchain we are now using, and compatibility with Android
1526)     2.3 and 3.x Honeycomb OS need to be verified.
1527)     </p>

1528)     

1529)     <p>
1530)     For more information see the <a
1531)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD">Orbot
1532)     build documentation</a>.
1533)     </p>
1534)     </li>

1535)     -->

1536)     

1537)     <!--

1538)     <a id="orbot-orlibAndOutreach"></a>
1539)     <li>
1540)     <b>Orbot integration library and community outreach</b>
1541)     <br>
1542)     Priority: <i>Medium</i>
1543)     <br>
1544)     Effort Level: <i>Low</i>
1545)     <br>
1546)     Skill Level: <i>Medium</i>
1547)     <br>
1548)     Likely Mentors: <i>Nathan (n8fr8)</i>
1549)     <p>
1550)     We need additional work on <a
1551)     href="https://github.com/guardianproject/orlib">ORLib</a>, our library for
1552)     use with third-party application to easily enable them to support
1553)     &quot;Torification&quot; on non-rooted devices (i.e. w/o transparent
1554)     proxying). This library includes a SOCKS client, a wrapper for the Apache
1555)     HTTPClient library, a utility class for detecting the state of Orbot
1556)     connectivity, and other relevant/useful things an Android app might need to
1557)     anonymize itself. This work would includes direct development of the
1558)     library, documentation, and sample code. Outreach or effort to implement
1559)     the library within other open-source apps is also needed.
1560)     </p>
1561)     </li>

1562)     -->

1563)     

1564)     <!--

1565)     <a id="vidaliaNetworkMap"></a>

1566)     <li>
1567)     <b>An Improved and More Usable Network Map in Vidalia</b>
1568)     <br>
1569)     Priority: <i>Low to Medium</i>
1570)     <br>
1571)     Effort Level: <i>Medium</i>
1572)     <br>
1573)     Skill Level: <i>Medium</i>
1574)     <br>

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

1576)     <p>
1577)     One of Vidalia's existing features is a network map that shows the user
1578)     the approximate geographic location of relays in the Tor network and
1579)     plots the paths the user's traffic takes as it is tunneled through the
1580)     Tor network. The map is currently not very interactive and has rather
1581)     poor graphics. Instead, we implemented KDE's Marble widget such
1582)     that it gives us a better quality map and enables improved interactivity,
1583)     such as allowing the user to click on individual relays or circuits to
1584)     display additional information. We want to add the ability
1585)     for users to click on a particular relay or a country containing one or
1586)     more Tor exit relays and say, "I want my connections to exit
1587)     from here."
1588)     </p>

1589)     

1590)     <p>
1591)     This project will first involve getting familiar with Vidalia
1592)     and the Marble widget's API. One will then integrate the widget
1593)     into Vidalia and customize Marble to be better suited for our application,
1594)     such as making circuits clickable, storing cached map data in Vidalia's
1595)     own data directory, and customizing some of the widget's dialogs.
1596)     </p>

1597)     

1598)     <p>
1599)     A person undertaking this project should have good C++ development
1600)     experience. Previous experience with Qt and CMake is helpful, but not
1601)     required.
1602)     </p>

1603)     </li>

1604)     -->

1605)     

1606)     <a id="obfsproxy-fuzzer"></a>
1607)     <li>
1608)     <b>Fuzzer for the Tor protocol</b>
1609)     <br>
1610)     Priority: <i>Low to Medium</i>
1611)     <br>
1612)     Effort Level: <i>Medium to High</i>
1613)     <br>
1614)     Skill Level: <i>High</i>
1615)     <br>
1616)     Likely Mentors: <i>asn</i>
1617)     <p>Involves researching good and smart ways to fuzz stateful network
1618)     protocols, and also implementing the fuzzer.</p>

1619)     

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

1622)     

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

1624)     

1625)     <ul>
1626)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1627)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1628)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1629)       Testing and Machine Learning</li>
1630)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1631)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1632)       <li>Also look at the concepts of &quot;model checking&quot; and
1633)       &quot;symbolic execution&quot; to get inspired.</li>
1634)     </ul>
1635)     </li>

1636)     

1637)     <!--

1638)     <a id="armGui"></a>
1639)     <li>
1640)     <b>GUI for Arm</b>
1641)     <br>
1642)     Priority: <i>Low</i>
1643)     <br>
1644)     Effort Level: <i>High</i>
1645)     <br>
1646)     Skill Level: <i>Medium</i>
1647)     <br>

1648)     Likely Mentors: <i>Damian (atagar)</i>

1649)     <p>
1650)     Arm has several unique features, some of the most interesting being its
1651)     connection listing (correlating netstat results against the Tor consensus)
1652)     and configuration editor (a quick method for editing Tor's config, with
1653)     information pulled from the control port and man page). However, since arm
1654)     is a command line controller it's of limited appeal to certain sets of
1655)     users. This project would be to build a GTK or Qt frontend for the
1656)     controller, providing similar features set but with a windowed interface.
1657)     </p>

1658)     

1659)     <p>
1660)     The vast majority of arm's more interesting functionality lies in its

1661)     backend <a href="https://gitweb.torproject.org/arm.git/tree/HEAD:/src/util">utilities</a>, so

1662)     there should be little to no work decoupling the CLI from its backend.
1663)     Instead, this project would mostly be UI hacking and experimentation,
1664)     trying different interfaces to find something that's elegant and simple,
1665)     but matches the information found in the current terminal application.
1666)     </p>
1667)     </li>

1668)     -->

1669)     

1670)     <a id="APAF"></a>
1671)     <li>
1672)     <b>APAF: Anonymous Python Application Framework</b>
1673)     <br>
1674)     Priority: <i>Medium</i>
1675)     <br>
1676)     Effort Level: <i>Medium</i>
1677)     <br>
1678)     Skill Level: <i>Medium</i>
1679)     <br>
1680)     Likely Mentors: <i>Arturo (hellais)</i>
1681)     <p>

1682)     The goal of APAF is to create a build framework for creating a binary
1683)     package for multiple platforms (.app/dmg, .exe, .deb, etc.) that includes
1684)     the python interpreter (cpython), the Tor binary and all the UI necessary
1685)     to make users be able to easily run the bundled Tor Hidden Service.

1686)     </p>

1687)     

1688)     <p>

1689)     For GSoC the student is expected to create the build system capable of
1690)     building a simple web application that serves static files. It should also
1691)     include a web UI for a wizard setup, checking the status of the HS and
1692)     configuring it.

1693)     </p>

1694)     

1695)     <p>

1696)     For more details on this: check out <a
1697)     href="https://pad.riseup.net/p/1zA8FI4nrYlq">https://pad.riseup.net/p/1zA8FI4nrYlq</a>

1698)     </p>
1699)     </li>

1700)     

1701)     <li>
1702)     <b>Bring up new ideas!</b>

1703)     <br>

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

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

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

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

1709)     might also be short on developers.
1710)     </li>

1711)     

1712)     </ol>

1713)     

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

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

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

1729)     

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

1735)     

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

1745)     

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

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

1750)     Tor if needed.</li>

1751)     

1752)     <li>Perform a security analysis of Tor with <a

1753)     href="https://secure.wikimedia.org/wikipedia/en/wiki/Fuzz_testing">"fuzz"</a>. Determine

1754)     if there are good fuzzing libraries out there for what we want. Win fame by
1755)     getting credit when we put out a new release because of you!</li>

1756)     

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

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

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

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

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

1767)     

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

1771)     

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

1778)     

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

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

1782)     System</a>.
1783)     </li>

1784)     

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

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

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

1797)     

1798)     </ol>

1799)     

1800)     <a id="Research"></a>
1801)     <h2><a class="anchor" href="#Research">Research</a></h2>
1802)     <ol>
1803)     <li>The "end-to-end traffic confirmation attack":
1804)     by watching traffic at Alice and at Bob, we can <a
1805)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1806)     traffic signatures and become convinced that we're watching the same
1807)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1808)     attack is trivial in all cases. First of all, is that actually true? How
1809)     much traffic of what sort of distribution is needed before the adversary
1810)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1811)     that slow down the attack? Do some traffic padding or traffic shaping
1812)     schemes work better than others?</li>
1813)     <li>A related question is: Does running a relay/bridge provide additional
1814)     protection against these timing attacks? Can an external adversary that can't
1815)     see inside TLS links still recognize individual streams reliably?
1816)     Does the amount of traffic carried degrade this ability any? What if the
1817)     client-relay deliberately delayed upstream relayed traffic to create a queue
1818)     that could be used to mimic timings of client downstream traffic to make it
1819)     look like it was also relayed? This same queue could also be used for masking
1820)     timings in client upstream traffic with the techniques from <a
1821)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1822)     but without the need for additional traffic. Would such an interleaving of
1823)     client upstream traffic obscure timings for external adversaries? Would the
1824)     strategies need to be adjusted for asymmetric links? For example, on
1825)     asymmetric links, is it actually possible to differentiate client traffic from
1826)     natural bursts due to their asymmetric capacity? Or is it easier than
1827)     symmetric links for some other reason?</li>
1828)     <li>Repeat Murdoch and Danezis's <a
1829)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1830)     Oakland 05</a> on the current Tor network. See if you can learn why it
1831)     works well on some nodes and not well on others. (My theory is that the
1832)     fast nodes with spare capacity resist the attack better.) If that's true,
1833)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1834)     options to run a relay that is used as a client while relaying the
1835)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1836)     attack get harder? What's the right ratio of RelayBandwidthRate to
1837)     actually capacity? Or is it a ratio at all? While we're at it, does a
1838)     much larger set of candidate relays increase the false positive rate
1839)     or other complexity for the attack? (The Tor network is now almost two
1840)     orders of magnitude larger than it was when they wrote their paper.) Be
1841)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1842)     Clog the Queue</a> too.</li>
1843)     <li>The "routing zones attack": most of the literature thinks of
1844)     the network path between Alice and her entry node (and between the
1845)     exit node and Bob) as a single link on some graph. In practice,
1846)     though, the path traverses many autonomous systems (ASes), and <a
1847)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1848)     that the same AS appears on both the entry path and the exit path</a>.
1849)     Unfortunately, to accurately predict whether a given Alice, entry,
1850)     exit, Bob quad will be dangerous, we need to download an entire Internet
1851)     routing zone and perform expensive operations on it. Are there practical
1852)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1853)     <li>Other research questions regarding geographic diversity consider
1854)     the tradeoff between choosing an efficient circuit and choosing a random
1855)     circuit. Look at Stephen Rollyson's <a
1856)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1857)     paper</a> on how to discard particularly slow choices without hurting
1858)     anonymity "too much". This line of reasoning needs more work and more
1859)     thinking, but it looks very promising.</li>
1860)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1861)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1862)     each hop, if the incoming bytes are arriving just fine and the outgoing
1863)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1864)     don't really transmit this information back to the incoming streams.
1865)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1866)     and rate-limit incoming streams to regulate this itself? I can imagine
1867)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1868)     slowly increase it until we get lost packets, back off, repeat. We
1869)     need somebody who's good with networks to simulate this and help design
1870)     solutions; and/or we need to understand the extent of the performance
1871)     degradation, and use this as motivation to reconsider UDP transport.</li>
1872)     <li>A related topic is congestion control. Is our
1873)     current design sufficient once we have heavy use? Maybe
1874)     we should experiment with variable-sized windows rather
1875)     than fixed-size windows? That seemed to go well in an <a

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

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

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

1902)     your browser's UserAgent string by replacing it with a uniform answer for
1903)     every Tor user. That way the attacker can't splinter Tor's anonymity set
1904)     by looking at that header. It tries to pick a string that is commonly used
1905)     by non-Tor users too, so it doesn't stand out. Question one: how badly
1906)     do we hurt ourselves by periodically updating the version of Firefox
1907)     that Torbutton claims to be? If we update it too often, we splinter the
1908)     anonymity sets ourselves. If we don't update it often enough, then all the
1909)     Tor users stand out because they claim to be running a quite old version
1910)     of Firefox. The answer here probably depends on the Firefox versions seen
1911)     in the wild. Question two: periodically people ask us to cycle through N
1912)     UserAgent strings rather than stick with one. Does this approach help,
1913)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
1914)     by their rotating UserAgents; malicious websites who only attack certain
1915)     browsers; and whether the answers to question one impact this answer.
1916)     </li>
1917)     <li>How many bridge relays do you need to know to maintain
1918)     reachability? We should measure the churn in our bridges. If there is
1919)     lots of churn, are there ways to keep bridge users more likely to stay
1920)     connected?
1921)     </li>
1922)     </ol>

1923)     

1924)     <p>
1925)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1926)     of these!
1927)     </p>
1928)   </div>
1929)   <!-- END MAINCOL -->
1930)   <div id = "sidecol">
1931) #include "side.wmi"
1932) #include "info.wmi"
1933)   </div>
1934)   <!-- END SIDECOL -->
1935) </div>
1936) <!-- END CONTENT -->