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)     <p>
486)     <b>Project Ideas:</b><br />
487)     <i><a href="#torbuttonForThunderbird">Torbutton equivalent for Thunderbird</a></i>
488)     </p>

489)     

490)     <a id="project-obfsproxy"></a>
491)     <h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc">Obfsproxy</a> (<a
492)     href="https://gitweb.torproject.org/obfsproxy.git">code</a>, <a
493)     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
494)     tracker</a>)</h3>

495)     

496)     <p>
497)     A proxy that shapes Tor traffic, making it harder for censors to detect and
498)     block Tor.
499)     </p>

500)     

501)     <p>
502)     <b>Project Ideas:</b><br />
503)     <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
504)     <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
505)     <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
506)     </p>

507)     

508)     <a id="project-thandy"></a>
509)     <h3>Thandy (<a
510)     href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>

511)     

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

517)     

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

523)     

524)     <p>
525)     Censorship scanner, checking your local connection for blocked or modified
526)     content.
527)     </p>

528)     

529)     <a id="project-shadow"></a>
530)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
531)     href="https://github.com/shadow">code</a>, <a
532)     href="https://github.com/shadow/shadow/issues">bug
533)     tracker</a>)</h3>

534)     

535)     <p>
536)     Shadow is a discrete-event network simulator that runs the real
537)     Tor software as a plug-in. Shadow is open-source software that enables
538)     accurate, efficient, controlled, and repeatable Tor experimentation.
539)     </p>

540)     

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

546)     

547)     <p>
548)     Python bindings and utilities for using the Tor control port. It has been
549)     stable for several years, with only minor revisions.
550)     </p>

551)     

552)     <a id="project-stem"></a>
553)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> (<a
554)     href="https://gitweb.torproject.org/stem.git">code</a>, <a
555)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Stem&order=priority">bug
556)     tracker</a>)</h3>

557)     

558)     <p>
559)     Python controller library with a similar scope to TorCtl, but with better
560)     testing, documentation, and API. This project is not yet feature complete.
561)     </p>

562)     

563)     <p>
564)     <b>Project Ideas:</b><br />
565)     <i><a href="#stemPathsupport">Stem PathSupport Capabilities</a></i>
566)     </p>

567)     

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

575)     

576)     <p>
577)     Processing and analytics of consensus data, provided to users via the
578)     metrics portal. This has been under active development for several years by
579)     Karsten Loesing.
580)     </p>

581)     

582)     <p>
583)     <b>Project Ideas:</b><br />
584)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
585)     </p>

586)     

587)     <a id="project-atlas"></a>
588)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
589)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

590)     

591)     <p>
592)     Atlas is a web application to discover Tor relays and bridges. It provides
593)     useful information on how relays are configured along with graphics about
594)     their past usage. This is the third evolution of the TorStatus application.
595)     </p>

596)     

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

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

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

600)     

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

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

608)     </p>

609)     

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

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

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

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

626)     

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

633)     

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

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

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

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

639)     

640)     <p>
641)     E-mail autoresponder providing Tor's packages over SMTP. This has been
642)     relatively unchanged for quite a while.
643)     </p>

644)     

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

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

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

650)     

651)     <p>
652)     Provides a simple site for determining if the visitor is using Tor or not.
653)     This has been relatively unchanged for quite a while.
654)     </p>

655)     

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

658)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
659)     href="https://gitweb.torproject.org/pyonionoo.git">python
660)     codebase</a>)</h3>

661)     

662)     <p>
663)     Onionoo is a JSON based protocol to learn information about currently
664)     running Tor relays and bridges.
665)     </p>

666)     

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

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

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

672)     

673)     <p>
674)     Backend bridge distributor, handling the various pools they're distributed
675)     in. This was actively developed until Fall of 2010.
676)     </p>

677)     

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

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

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

683)     

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

692)     

693)     <a id="project-torbel"></a>
694)     <h3><a

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

697)     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
698)     tracker</a>)</h3>

699)     

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

707)     

708)     <a id="Coding"></a>
709)     <a id="Summer"></a>

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

711)     

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

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

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

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

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

724)     

725)     <ol>

726)     

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

728)     <li>

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

730)     <br>

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

732)     <br>

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

734)     <br>

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

736)     <br>

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

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

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

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

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

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

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

752)     </li>

753)     

754)     <a id="firewallProbeTool"></a>
755)     <li>
756)     <b>Develop a fully automatic firewall-probing system</b>
757)     <br>
758)     Priority: <i>High</i>
759)     <br>
760)     Effort Level: <i>Medium to High</i>
761)     <br>
762)     Skill Level: <i>High</i>
763)     <br>

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

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

783)     

784)     <!--

785)     <a id="orbot-torbutton"></a>
786)     <li>
787)     <b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>
788)     <br>
789)     Priority: <i>High</i>
790)     <br>
791)     Effort Level: <i>High</i>
792)     <br>
793)     Skill Level: <i>High</i>
794)     <br>

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

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

805)     -->

806)     

807)     <a id="obfsproxy-new-transports"></a>
808)     <li>
809)     <b>New and innovative pluggable transports</b>
810)     <br>
811)     Priority: <i>High</i>
812)     <br>
813)     Effort Level: <i>High</i>
814)     <br>
815)     Skill Level: <i>High</i>
816)     <br>

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

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

822)     

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

825)     

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

828)     

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

833)     

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

848)     

849)     <p>This also involves implementing proposals <a
850)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a>
851)     and <a
852)     href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p>
853)     </li>

854)     

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

874)     

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

879)     

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

886)     

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

891)     

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

893)     

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

911)     

912)     <p><b>
913)     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>.
914)     </b></p>
915)     </li>
916)     

917)     <!--

918)     <a id="orbot-userInterface"></a>
919)     <li>
920)     <b>Build a better user interface for Orbot</b>
921)     <br>
922)     Priority: <i>High</i>
923)     <br>
924)     Effort Level: <i>Medium</i>
925)     <br>
926)     Skill Level: <i>Medium</i>
927)     <br>

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

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

943)     -->

944)     

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

973)     

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

975)     <li>
976)     <b>Improving Tor's ability to resist censorship</b>

977)     <br>

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

979)     <br>

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

981)     <br>

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

983)     <br>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1011)     then trading off censorship resistance with usability and
1012)     robustness.</p>

1013)     </li>

1014)     

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

1057)     

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

1092)     

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

1108)     

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

1113)     

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

1126)     

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

1144)     

1145)     <a id="geoIPUpgrade"></a>
1146)     <li>
1147)     <b>Improve our GeoIP file format</b>
1148)     <br>
1149)     Priority: <i>Medium</i>
1150)     <br>
1151)     Effort Level: <i>Medium</i>
1152)     <br>
1153)     Skill Level: <i>Medium to High</i>
1154)     <br>
1155)     Likely Mentors: <i>Robert Ransom</i>

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

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

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

1160)     possible.</p>

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

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

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

1167)     project.</p>

1168)     </li>

1169)     

1170)     <!--

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

1172)     <li>
1173)     <b>Client Mode Use Cases for Arm</b>
1174)     <br>
1175)     Priority: <i>Medium</i>
1176)     <br>
1177)     Effort Level: <i>High</i>
1178)     <br>
1179)     Skill Level: <i>Medium</i>
1180)     <br>

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

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

1189)     

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

1192)     

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

1202)       

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

1205)       

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

1208)       

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

1213)       

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

1217)       

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

1221)       

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

1224)     

1225)     <p>

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

1227)     </p>

1228)     </li>

1229)     -->

1230)     

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

1246)     

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

1250)     

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

1257)     

1258)     <a id="metricsSearch"></a>
1259)     <li>
1260)     <b>Searchable Tor descriptor and Metrics data archive</b>
1261)     <br>
1262)     Priority: <i>Medium</i>
1263)     <br>
1264)     Effort Level: <i>Medium</i>
1265)     <br>
1266)     Skill Level: <i>Medium</i>
1267)     <br>
1268)     Likely Mentors: <i>Karsten</i>

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

1270)     

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

1272)     

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

1274)     

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

1276)     

1277)     <!--

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

1279)     <li>
1280)     <b>Improve our unit testing process</b>

1281)     <br>

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

1283)     <br>

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

1285)     <br>

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

1287)     <br>

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

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

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

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

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

1303)     </li>

1304)     -->

1305)     

1306)     <!--

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

1308)     <li>
1309)     <b>Simulator for slow Internet connections</b>

1310)     <br>

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

1312)     <br>

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

1314)     <br>

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

1316)     <br>

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

1318)     <p>

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

1324)     </p>

1325)     

1326)     <p>

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

1332)     </p>

1333)     

1334)     <p>

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

1340)     </p>

1341)     </li>

1342)     -->

1343)     

1344)     <a id="torbuttonForThunderbird"></a>

1345)     <li>
1346)     <b>Torbutton equivalent for Thunderbird</b>

1347)     <br>

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

1349)     <br>

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

1351)     <br>

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

1353)     <br>

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

1355)     <p>

1356)     We're hearing from an increasing number of users that they want to use
1357)     Thunderbird with Tor. However, there are plenty of application-level
1358)     concerns, for example, by default Thunderbird will put your hostname in
1359)     the outgoing mail that it sends. At some point we should start a new
1360)     push to build a Thunderbird extension similar to Torbutton.

1361)     </p>

1362)     </li>

1363)     

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

1365)     <li>
1366)     <b>Usability testing of Tor</b>

1367)     <br>

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

1369)     <br>

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

1371)     <br>

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

1373)     <br>

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

1375)     <p>

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

1380)     </p>

1381)     

1382)     <p>
1383)     Please note that since this isn't a coding project, it isn't suitable for
1384)     Google Summer of Code.
1385)     </p>

1386)     </li>

1387)     

1388)     <!--

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

1390)     <li>
1391)     <b>Make torsocks/dsocks work on OS X</b>

1392)     <br>

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

1394)     <br>

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

1396)     <br>

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

1398)     <br>

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

1400)     <p>

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

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

1417)     </p>
1418)     </li>

1419)     -->

1420)     

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

1422)     <li>
1423)     <b>Tor Controller Status Event Interface for Vidalia</b>
1424)     <br>
1425)     Priority: <i>Medium</i>
1426)     <br>
1427)     Effort Level: <i>Medium</i>
1428)     <br>
1429)     Skill Level: <i>Low to Medium</i>
1430)     <br>

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

1432)     <p>There are a number of status changes inside Tor of which the user may need
1433)     to be informed. For example, if the user is trying to set up his Tor as a
1434)     relay and Tor decides that its ports are not reachable from outside
1435)     the user's network, we should alert the user. Currently, all the user
1436)     gets is a couple of log messages in Vidalia's 'message log' window, which they
1437)     likely never see since they don't receive a notification that something
1438)     has gone wrong. Even if the user does actually look at the message log,
1439)     most of the messages make little sense to the novice user.</p>
1440)     <p>Tor has the ability to inform Vidalia of many such status
1441)     changes, and we recently implemented support for a couple of these
1442)     events. Still, there are many more status events which the user should
1443)     be informed of, and we need a better UI for actually displaying them
1444)     to the user.</p>
1445)     <p>The goal of this project then is to design and implement a UI for
1446)     displaying Tor status events to the user. For example, we might put a
1447)     little badge on Vidalia's tray icon that alerts the user to new status
1448)     events they should look at. Double-clicking the icon could bring up a
1449)     dialog that summarizes recent status events in simple terms and maybe
1450)     suggests a remedy for any negative events if they can be corrected by
1451)     the user. Of course, this is just an example and one is free to
1452)     suggest another approach.</p>
1453)     <p>A person undertaking this project should have good UI design and layout
1454)     skills and some C++ development experience. Previous experience with Qt and
1455)     Qt's Designer will be very helpful, but are not required. Some
1456)     English writing ability will also be useful, since this project will
1457)     likely involve writing small amounts of help documentation that should
1458)     be understandable by non-technical users. Bonus points for some graphic
1459)     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
1460)     </li>

1461)     

1462)     <!--

1463)     <a id="orbot-optimisation"></a>
1464)     <li>
1465)     <b>Core Tor mobile optimisation</b>
1466)     <br>
1467)     Priority: <i>Medium</i>
1468)     <br>
1469)     Effort Level: <i>Medium</i>
1470)     <br>
1471)     Skill Level: <i>High</i>
1472)     <br>

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

1474)     <p>
1475)     The existing port of Tor to Android is basically a straight
1476)     cross-compile to Linux ARM. There has been no work done in looking at
1477)     possible optimizations of Tor within a mobile hardware environment or on
1478)     mobile networks. In addition, a number of additional Android OS APIs are
1479)     available (such as wireless network status) that could be taken
1480)     advantage of.
1481)     </p>

1482)     

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

1492)     

1493)     <p>
1494)     Finally, the build process needs to be moved to the Android NDK from the
1495)     custom GCC toolchain we are now using, and compatibility with Android
1496)     2.3 and 3.x Honeycomb OS need to be verified.
1497)     </p>

1498)     

1499)     <p>
1500)     For more information see the <a
1501)     href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD">Orbot
1502)     build documentation</a>.
1503)     </p>
1504)     </li>

1505)     -->

1506)     

1507)     <!--

1508)     <a id="orbot-orlibAndOutreach"></a>
1509)     <li>
1510)     <b>Orbot integration library and community outreach</b>
1511)     <br>
1512)     Priority: <i>Medium</i>
1513)     <br>
1514)     Effort Level: <i>Low</i>
1515)     <br>
1516)     Skill Level: <i>Medium</i>
1517)     <br>
1518)     Likely Mentors: <i>Nathan (n8fr8)</i>
1519)     <p>
1520)     We need additional work on <a
1521)     href="https://github.com/guardianproject/orlib">ORLib</a>, our library for
1522)     use with third-party application to easily enable them to support
1523)     &quot;Torification&quot; on non-rooted devices (i.e. w/o transparent
1524)     proxying). This library includes a SOCKS client, a wrapper for the Apache
1525)     HTTPClient library, a utility class for detecting the state of Orbot
1526)     connectivity, and other relevant/useful things an Android app might need to
1527)     anonymize itself. This work would includes direct development of the
1528)     library, documentation, and sample code. Outreach or effort to implement
1529)     the library within other open-source apps is also needed.
1530)     </p>
1531)     </li>

1532)     -->

1533)     

1534)     <!--

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

1536)     <li>
1537)     <b>An Improved and More Usable Network Map in Vidalia</b>
1538)     <br>
1539)     Priority: <i>Low to Medium</i>
1540)     <br>
1541)     Effort Level: <i>Medium</i>
1542)     <br>
1543)     Skill Level: <i>Medium</i>
1544)     <br>

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

1546)     <p>
1547)     One of Vidalia's existing features is a network map that shows the user
1548)     the approximate geographic location of relays in the Tor network and
1549)     plots the paths the user's traffic takes as it is tunneled through the
1550)     Tor network. The map is currently not very interactive and has rather
1551)     poor graphics. Instead, we implemented KDE's Marble widget such
1552)     that it gives us a better quality map and enables improved interactivity,
1553)     such as allowing the user to click on individual relays or circuits to
1554)     display additional information. We want to add the ability
1555)     for users to click on a particular relay or a country containing one or
1556)     more Tor exit relays and say, "I want my connections to exit
1557)     from here."
1558)     </p>

1559)     

1560)     <p>
1561)     This project will first involve getting familiar with Vidalia
1562)     and the Marble widget's API. One will then integrate the widget
1563)     into Vidalia and customize Marble to be better suited for our application,
1564)     such as making circuits clickable, storing cached map data in Vidalia's
1565)     own data directory, and customizing some of the widget's dialogs.
1566)     </p>

1567)     

1568)     <p>
1569)     A person undertaking this project should have good C++ development
1570)     experience. Previous experience with Qt and CMake is helpful, but not
1571)     required.
1572)     </p>

1573)     </li>

1574)     -->

1575)     

1576)     <a id="obfsproxy-fuzzer"></a>
1577)     <li>
1578)     <b>Fuzzer for the Tor protocol</b>
1579)     <br>
1580)     Priority: <i>Low to Medium</i>
1581)     <br>
1582)     Effort Level: <i>Medium to High</i>
1583)     <br>
1584)     Skill Level: <i>High</i>
1585)     <br>
1586)     Likely Mentors: <i>asn</i>
1587)     <p>Involves researching good and smart ways to fuzz stateful network
1588)     protocols, and also implementing the fuzzer.</p>

1589)     

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

1592)     

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

1594)     

1595)     <ul>
1596)       <li>PROTOS - Security Testing of Protocol Implementations</li>
1597)       <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
1598)       <li>Detecting Communication Protocol Security Flaws by Formal Fuzz
1599)       Testing and Machine Learning</li>
1600)       <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li>
1601)       <li>Michal Zalewski's &quot;bugger&quot;</li>
1602)       <li>Also look at the concepts of &quot;model checking&quot; and
1603)       &quot;symbolic execution&quot; to get inspired.</li>
1604)     </ul>
1605)     </li>

1606)     

1607)     <!--

1608)     <a id="armGui"></a>
1609)     <li>
1610)     <b>GUI for Arm</b>
1611)     <br>
1612)     Priority: <i>Low</i>
1613)     <br>
1614)     Effort Level: <i>High</i>
1615)     <br>
1616)     Skill Level: <i>Medium</i>
1617)     <br>

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

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

1628)     

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

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

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

1638)     -->

1639)     

1640)     <a id="APAF"></a>
1641)     <li>
1642)     <b>APAF: Anonymous Python Application Framework</b>
1643)     <br>
1644)     Priority: <i>Medium</i>
1645)     <br>
1646)     Effort Level: <i>Medium</i>
1647)     <br>
1648)     Skill Level: <i>Medium</i>
1649)     <br>
1650)     Likely Mentors: <i>Arturo (hellais)</i>
1651)     <p>

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

1656)     </p>

1657)     

1658)     <p>

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

1663)     </p>

1664)     

1665)     <p>

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

1668)     </p>
1669)     </li>

1670)     

1671)     <li>
1672)     <b>Bring up new ideas!</b>

1673)     <br>

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

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

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

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

1679)     might also be short on developers.
1680)     </li>

1681)     

1682)     </ol>

1683)     

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

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

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

1699)     

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

1705)     

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

1715)     

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

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

1720)     Tor if needed.</li>

1721)     

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

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

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

1726)     

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

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

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

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

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

1737)     

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

1741)     

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

1748)     

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

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

1752)     System</a>.
1753)     </li>

1754)     

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

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

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

1767)     

1768)     </ol>

1769)     

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

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

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

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

1872)     your browser's UserAgent string by replacing it with a uniform answer for
1873)     every Tor user. That way the attacker can't splinter Tor's anonymity set
1874)     by looking at that header. It tries to pick a string that is commonly used
1875)     by non-Tor users too, so it doesn't stand out. Question one: how badly
1876)     do we hurt ourselves by periodically updating the version of Firefox
1877)     that Torbutton claims to be? If we update it too often, we splinter the
1878)     anonymity sets ourselves. If we don't update it often enough, then all the
1879)     Tor users stand out because they claim to be running a quite old version
1880)     of Firefox. The answer here probably depends on the Firefox versions seen
1881)     in the wild. Question two: periodically people ask us to cycle through N
1882)     UserAgent strings rather than stick with one. Does this approach help,
1883)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
1884)     by their rotating UserAgents; malicious websites who only attack certain
1885)     browsers; and whether the answers to question one impact this answer.
1886)     </li>
1887)     <li>How many bridge relays do you need to know to maintain
1888)     reachability? We should measure the churn in our bridges. If there is
1889)     lots of churn, are there ways to keep bridge users more likely to stay
1890)     connected?
1891)     </li>
1892)     </ol>

1893)     

1894)     <p>
1895)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1896)     of these!
1897)     </p>
1898)   </div>
1899)   <!-- END MAINCOL -->
1900)   <div id = "sidecol">
1901) #include "side.wmi"
1902) #include "info.wmi"
1903)   </div>
1904)   <!-- END SIDECOL -->
1905) </div>
1906) <!-- END CONTENT -->