tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

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

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

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

11)   <div id="maincol">

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

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

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

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

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

33) 

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

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

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

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

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

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

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

51) 

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

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

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

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

60)     <a

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

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

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

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

68)     </ol>

69) 

70)     <a id="Projects"></a>
71)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

72) 

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

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

80)     </p>

81) 

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

90) 

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

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

97)       </tr>

98) 

99)       <tr class="alt">

100)         <td>*<a href="#project-jtor">JTor</a></td>
101)         <td>Core</td>
102)         <td>Java</td>
103)         <td>None</td>
104)         <td>bleidl</td>
105)       </tr>
106) 
107)       <tr>

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

109)         <td>Bundle</td>

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

111)         <td>Moderate</td>

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

113)       </tr>

114) 

115)       <tr class="alt">

116)         <td><a href="#project-torbutton">Torbutton</a></td>
117)         <td>Browser Add-on</td>
118)         <td>Javascript</td>
119)         <td>Moderate</td>
120)         <td>mikeperry</td>

121)       </tr>

122) 

123)       <tr>

124)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
125)         <td>Browser Add-on</td>
126)         <td>Javascript</td>
127)         <td>Moderate</td>
128)         <td>pde, mikeperry</td>

129)       </tr>

130) 

131)       <tr class="alt">

132)         <td><a href="#project-vidalia">Vidalia</a></td>
133)         <td>User Interface</td>
134)         <td>C++, Qt</td>

135)         <td>None</td>

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

138) 

139)       <tr>

140)         <td><a href="#project-arm">Arm</a></td>
141)         <td>User Interface</td>
142)         <td>Python, Curses</td>

143)         <td>Light</td>

144)         <td>atagar</td>
145)       </tr>

146) 

147)       <tr class="alt">

148)         <td><a href="#project-orbot">Orbot</a></td>
149)         <td>User Interface</td>
150)         <td>Java</td>

151)         <td>Light</td>

152)         <td>n8fr8</td>

153)       </tr>

154) 

155)       <tr>

156)         <td><a href="#project-tails">Tails</a></td>
157)         <td>OS image</td>
158)         <td>Sys Admin</td>
159)         <td>Heavy</td>
160)         <td><a href="https://tails.boum.org/">#tails</a></td>

161)       </tr>

162) 

163)       <tr class="alt">

164)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
165)         <td>OS image</td>
166)         <td>Sys Admin</td>
167)         <td>Light</td>
168)         <td>blueness</td>
169)       </tr>
170) 

171)       <tr>

172)         <td>*<a href="#project-torouter">Torouter</a></td>
173)         <td>OS image</td>
174)         <td>Sys Admin</td>

175)         <td>None</td>

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

179)       <tr class="alt">

180)         <td><a href="#project-torsocks">Torsocks</a></td>
181)         <td>Usability</td>
182)         <td>C</td>

183)         <td>Light</td>

184)         <td>ioerror, nickm</td>
185)       </tr>
186) 

187)       <tr>

188)         <td><a href="#project-torbirdy">TorBirdy</a></td>
189)         <td>Browser Add-on</td>
190)         <td>JavaScript</td>
191)         <td>Heavy</td>
192)         <td>Sukhbir (sukhe), ioerror</td>
193)       </tr>

194) 

195)       <tr class="alt">

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

198)         <td>C, Python</td>
199)         <td>Moderate</td>
200)         <td>asn, nickm</td>

201)       </tr>
202) 

203)       <tr>

204)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
205)         <td>Client Add-on</td>
206)         <td>Python, JavaScript, Go</td>

207)         <td>Heavy</td>

208)         <td>dcf, aallai, jct</td>
209)       </tr>

210) 

211)       <tr class="alt">

212)         <td>*<a href="#project-thandy">Thandy</a></td>
213)         <td>Updater</td>
214)         <td>Python</td>

215)         <td>None</td>

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

217)       </tr>

218) 

219)       <tr>

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

221)         <td>Simulator</td>

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

223)         <td>Heavy</td>

224)         <td>robgjansen</td>
225)       </tr>

226) 

227)       <tr class="alt">

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

229)         <td>Library</td>
230)         <td>Python</td>
231)         <td>Heavy</td>

232)         <td>atagar</td>

233)       </tr>

234) 

235)       <tr>

236)         <td><a href="#project-txtorcon">Txtorcon</a></td>
237)         <td>Library</td>
238)         <td>Python, Twisted</td>

239)         <td>Heavy</td>

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

242) 

243)       <tr class="alt">

244)         <td><a href="#project-tlsdate">Tlsdate</a></td>
245)         <td>Utility</td>
246)         <td>C</td>

247)         <td>Moderate</td>

248)         <td>ioerror</td>
249)       </tr>

250) 

251)       <tr>

252)         <td><a href="#project-metrics">Metrics</a></td>
253)         <td>Client Service</td>
254)         <td>Java</td>
255)         <td>Heavy</td>
256)         <td>karsten</td>
257)       </tr>

258) 

259)       <tr class="alt">

260)         <td><a href="#project-atlas">Atlas</a></td>
261)         <td>Client Service</td>
262)         <td>JavaScript</td>

263)         <td>Light</td>

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

265)       </tr>

266) 

267)       <tr>

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

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

271)         <td>None</td>
272)         <td></td>
273)       </tr>

274) 

275)       <tr class="alt">

276)         <td><a href="#project-compass">Compass</a></td>
277)         <td>Client Service</td>
278)         <td>Python</td>

279)         <td>Light</td>

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

281)       </tr>

282) 

283)       <tr>

284)         <td><a href="#project-onionoo">Onionoo</a></td>
285)         <td>Backend Service</td>
286)         <td>Java, Python</td>

287)         <td>Light</td>

288)         <td>karsten, gsathya</td>
289)       </tr>
290) 

291)       <tr class="alt">

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

295)         <td>None</td>

296)         <td>kaner</td>
297)       </tr>

298) 

299)       <tr>

300)         <td><a href="#project-gettor">GetTor</a></td>
301)         <td>Client Service</td>
302)         <td>Python</td>

303)         <td>None</td>

304)         <td>kaner</td>

305)       </tr>

306) 

307)       <tr class="alt">

308)         <td><a href="#project-torcheck">TorCheck</a></td>
309)         <td>Client Service</td>
310)         <td>Python, Perl</td>
311)         <td>None</td>

312)         <td>ioerror</td>

313)       </tr>

314) 

315)       <tr>

316)         <td><a href="#project-bridgedb">BridgeDB</a></td>
317)         <td>Backend Service</td>
318)         <td>Python</td>

319)         <td>None</td>

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

321)       </tr>

322) 

323)       <tr class="alt">

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

325)         <td>Scanner</td>
326)         <td>Python</td>

327)         <td>Heavy</td>

328)         <td>hellais, isis, ioerror</td>
329)       </tr>
330) 

331)       <tr>

332)         <td><a href="#project-torflow">TorFlow</a></td>
333)         <td>Backend Service</td>
334)         <td>Python</td>

335)         <td>None</td>

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

337)       </tr>

338) 

339)       <tr class="alt">

340)         <td>*<a href="#project-torbel">TorBEL</a></td>
341)         <td>Backend Service</td>
342)         <td>Python</td>
343)         <td>None</td>
344)         <td>Sebastian</td>
345)       </tr>

346) 

347)       <tr>

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

350)         <td>Python</td>

351)         <td>Moderate</td>

352)         <td>hellais</td>

353)       </tr>

354) 

355)       <tr class="alt">

356)         <td><a href="#project-anonbib">Anonbib</a></td>
357)         <td>Website</td>

358)         <td>Python</td>

359)         <td>Light</td>
360)         <td>arma, nickm</td>
361)       </tr>
362) 

363)     </table>

364) 

365)     <sub>
366)     * Project is still in an alpha state.
367)     </sub>

368) 

369)     <br /><br />

370) 

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

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

374)     tracker</a>)</h3>

375) 

376)     <p>
377)     Central project, providing the core software for using and participating in
378)     the Tor network. Numerous people contribute to the project to varying
379)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
380)     </p>

381) 

382)     <p>
383)     <b>Project Ideas:</b><br />

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

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

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

388)     </p>

389) 

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

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

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

395) 

396)     <p>
397)     Java implementation of Tor and successor to <a
398)     href="http://onioncoffee.sourceforge.net/">OnionCoffee</a>. This project
399)     isn't yet complete, and has been inactive since Fall 2010.
400)     </p>

401) 

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

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

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

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

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

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

413)     </p>

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

419)     tracker</a>)</h3>

420) 

421)     <p>

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

427)     </p>

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

433)     tracker</a>)</h3>

434) 

435)     <p>

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

439)     </p>

440) 

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

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

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

446) 

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

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

452)     </p>

453) 

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

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

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

459) 

460)     <p>

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

466)     </p>

467) 

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

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

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

473) 
474)     <p>
475)     Provides Tor on the Android platform. This was under very active
476)     development up through Fall 2010, after which things have been quiet.
477)     </p>
478) 
479)     <a id="project-tails"></a>
480)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a
481)     href="http://git.immerda.ch/?p=amnesia.git;a=summary">code</a>, <a
482)     href="https://tails.boum.org/bugs/">bug
483)     tracker</a>)</h3>
484) 
485)     <p>
486)     The Amnesic Incognito Live System is a live CD/USB distribution
487)     preconfigured so that everything is safely routed through Tor and leaves no
488)     trace on the local system. This is a merger of the Amnesia and <a
489)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
490)     and still under very active development.
491)     </p>
492) 

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

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

497) 
498)     <p>

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

501)     </p>
502) 

503)     <a id="project-torouter"></a>
504)     <h3><a
505)     href="<wiki>doc/Torouter">Torouter</a> (<a

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

507)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
508)     tracker</a>)</h3>
509) 
510)     <p>
511)     Project to provide an easy-to-use, embedded Tor instance for routers. This
512)     had high activity in late 2010, but has since been rather quiet.
513)     </p>
514) 
515)     <a id="project-torsocks"></a>
516)     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
517)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
518)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
519)     tracker</a>)</h3>
520) 

521)     <p>

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

525)     </p>

526) 

527)     <a id="project-torbirdy"></a>
528)     <h3>TorBirdy (<a
529)     href="https://github.com/ioerror/torbirdy">code</a>, <a
530)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
531)     tracker</a>)</h3>

532) 

533)     <p>
534)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
535)     </p>

536) 

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

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

539)     href="https://gitweb.torproject.org/obfsproxy.git">C codebase</a>, <a
540)     href="https://gitweb.torproject.org/user/asn/pyobfsproxy.git">python
541)     codebase</a>, <a

542)     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
543)     tracker</a>)</h3>

544) 

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

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

548)     </p>

549) 

550)     <a id="project-flash-proxy"></a>
551)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
552)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
553)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Flashproxy">bug
554)     tracker</a>)</h3>

555) 

556)     <p>
557)     Pluggable transport using proxies running in web browsers to defeat
558)     address-based blocking.
559)     </p>

560) 

561)     <a id="project-thandy"></a>
562)     <h3>Thandy (<a

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

564) 

565)     <p>

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

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

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

576)     </p>

577) 

578)     <a id="project-shadow"></a>
579)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
580)     href="https://github.com/shadow">code</a>, <a
581)     href="https://github.com/shadow/shadow/issues">bug
582)     tracker</a>)</h3>

583) 

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

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

590)     </p>

591) 

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

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

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

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

596)     tracker</a>)</h3>

597) 

598)     <p>

599)     Python controller library for scripts and controller applications using
600)     Tor.

601)     </p>

602) 

603)     <p>
604)     <b>Project Ideas:</b><br />

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

606)     <i><a href="#metrics-pyDoctor">PyDoctor</a></i><br />

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

609)     </p>

610) 

611)     <a id="project-txtorcon"></a>
612)     <h3>Txtorcon (<a
613)     href="https://github.com/meejah/txtorcon">code</a>, <a
614)     href="https://txtorcon.readthedocs.org">docs</a>)</h3>

615) 

616)     <p>
617)     Twisted-based asynchronous Tor control protocol implementation. Includes
618)     unit-tests, examples, state-tracking code and configuration abstraction.
619)     Used by OONI and APAF.
620)     </p>

621) 

622)     <p>
623)     <b>Project Ideas:</b><br />
624)     <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
625)     </p>
626) 

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

629) 

630)     <p>
631)     tlsdate: secure parasitic rdate replacement
632)     </p>

633) 

634)     <p>
635)     tlsdate sets the local clock by securely connecting with TLS to remote
636)     servers and extracting the remote time out of the secure handshake. Unlike
637)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
638)     enabled service, and provides some protection against adversaries that try
639)     to feed you malicious time information.
640)     </p>

641) 

642)     <a id="project-metrics"></a>
643)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
644)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
645)     href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
646)     href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
647)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
648)     tracker</a>)</h3>

649) 

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

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

655)     </p>

656) 

657)     <p>
658)     <b>Project Ideas:</b><br />

659)     <i><a href="#metrics-pyDoctor">PyDoctor</a></i><br />

660)     <i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
661)     </p>

662) 

663)     <a id="project-atlas"></a>
664)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
665)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

666) 

667)     <p>
668)     Atlas is a web application to discover Tor relays and bridges. It provides
669)     useful information on how relays are configured along with graphics about
670)     their past usage. This is the third evolution of the TorStatus application.
671)     </p>

672) 

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

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

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

676) 

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

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

684)     </p>

685) 

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

691) 

692)     <p>
693)     Compass is a web and command line application that filters and
694)     aggregates the Tor relays based on various attributes.
695)     </p>

696) 
697)     <a id="project-onionoo"></a>
698)     <h3><a href="<page projects/onionoo>">Onionoo</a> (<a
699)     href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a
700)     href="https://gitweb.torproject.org/pyonionoo.git">python

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

702) 
703)     <p>
704)     Onionoo is a JSON based protocol to learn information about currently
705)     running Tor relays and bridges.
706)     </p>
707) 

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

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

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

713) 

714)     <p>
715)     Provides automatic notification to subscribed relay operators when their
716)     relay's unreachable. This underwent a rewrite by the <a
717)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
718)     in early 2011.
719)     </p>

720) 

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

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

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

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

726) 

727)     <p>
728)     E-mail autoresponder providing Tor's packages over SMTP. This has been
729)     relatively unchanged for quite a while.
730)     </p>

731) 

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

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

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

737) 

738)     <p>
739)     Provides a simple site for determining if the visitor is using Tor or not.
740)     This has been relatively unchanged for quite a while.
741)     </p>

742) 

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

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

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

748) 

749)     <p>
750)     Backend bridge distributor, handling the various pools they're distributed
751)     in. This was actively developed until Fall of 2010.
752)     </p>

753) 
754)     <a id="project-ooni-probe"></a>

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

756)     href="https://gitweb.torproject.org/ooni-probe.git">code</a>, <a
757)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority">bug
758)     tracker</a>)</h3>
759) 
760)     <p>
761)     Censorship scanner, checking your local connection for blocked or modified
762)     content.
763)     </p>
764) 

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

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

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

770) 

771)     <p>
772)     Library and collection of services for actively monitoring the Tor network.
773)     These include the Bandwidth Scanners (measuring throughput of relays) and
774)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
775)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
776)     months later. Both have been under active use since then, but development
777)     has stopped.
778)     </p>

779) 

780)     <a id="project-torbel"></a>
781)     <h3><a

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

784)     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
785)     tracker</a>)</h3>

786) 

787)     <p>
788)     The Tor Bulk Exitlist provides a method of identifying if IPs belong to
789)     exit nodes or not. This is a replacement for TorDNSEL which is a stable
790)     (though unmaintained) Haskell application for this purpose. The initial
791)     version of TorBEL was started in GSOC 2010 but since then the project has
792)     been inactive.
793)     </p>

794) 

795)     <p>
796)     <b>Project Ideas:</b><br />
797)     <i><a href="#stemUsability">Stem Usability and Porting (this includes an idea for finishing off TorBEL)</a></i>
798)     </p>
799) 

800)     <a id="project-tor2web"></a>
801)     <h3><a
802)     href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a
803)     href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3>
804) 
805)     <p>
806)     Tor2web allows Internet users to browse websites running in <a
807)     href="<page docs/hidden-services>">Tor hidden services</a>. It trades
808)     user anonymity for usability by allowing anonymous content to be
809)     distributed to non-anonymous users.
810)     </p>
811) 

812)     <a id="project-anonbib"></a>
813)     <h3><a
814)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
815)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
816) 
817)     <p>

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

821)     </p>
822) 

823)     <a id="Coding"></a>
824)     <a id="Summer"></a>

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

826) 

827)     <p>

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

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

840) 

841)     <p>
842)     <b>If you came to this site for Google Summer of Code then please keep in
843)     mind that Google has not yet announced the participating organisations, and
844)     Tor might not be selected. See the <a
845)     href="https://www.google-melange.com/document/show/gsoc_program/google/gsoc2013/help_page#2._What_is_the_program_timeline">timeline</a>
846)     for more information.</b>
847)     </p>
848) 

849)     <ol>

850) 

851)     <a id="metrics-pyDoctor"></a>
852)     <li>
853)     <b>PyDoctor</b>
854)     <br>
855)     Effort Level: <i>Medium</i>
856)     <br>
857)     Skill Level: <i>Medium</i>
858)     <br>
859)     Likely Mentors: <i>karsten, Damian (atagar)</i>
860)     <p><a href="https://gitweb.torproject.org/doctor.git">DocTor</a>, also
861)     known as the consensus-health checker, is a service that periodically
862)     checks the Tor network for consensus conflicts and other hiccups.  In order
863)     to do so it downloads the Tor consensus and votes from the Tor directory
864)     authorities and checks them for consensus problems.  DocTor writes its
865)     findings to local files which can then be sent to a <a
866)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-consensus-health">mailing
867)     list</a> or IRC bot (nsa in #tor-bots on OFTC), or which can be served by
868)     an <a href="https://metrics.torproject.org/consensus-health.html">HTTP
869)     server</a>.</p>
870) 
871)     <p>This project would be about rewriting DocTor in Python and using Stem
872)     for the descriptor parsing.  This would require extending Stem to download
873)     consensuses and votes (and later server descriptors for Damian's
874)     consensus checker), and it would require rewriting the DocTor code in
875)     Python.</p>
876)     </li>
877) 

878)     <a id="txtorcon-stemIntegration"></a>
879)     <li>
880)     <b>Txtorcon/Stem Integration</b>
881)     <br>
882)     Effort Level: <i>Medium</i>
883)     <br>
884)     Skill Level: <i>Medium</i>
885)     <br>
886)     Likely Mentors: <i>meejah, Damian (atagar)</i>
887)     <p>Txtorcon is a Twisted-based Python controller library, and Stem is a
888)     synchronous (threaded) one, also in Python. There is no need to have
889)     two implementations of (at least) the protocol parsing code. This
890)     project would entail eliminating duplication by leveraging Stem's
891)     parsing in txtorcon while keeping txtorcon's API the same (or at least
892)     close).</p>
893)     <p>This would very likely involve changes to both libraries, although
894)     most would be expected to be in txtorcon. meejah is available to
895)     mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>
896)     <p>It would help if you're already familiar with event-based programming,
897)     bonus points if it's Twisted.</p>
898)     </li>
899) 

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

901)     <li>
902)     <b>HTTPS Server Impersonation</b>
903)     <br>
904)     Effort Level: <i>Medium to High</i>
905)     <br>
906)     Skill Level: <i>Medium to High</i>
907)     <br>
908)     Likely Mentors: <i>Nick (nickm)</i>

909)     <p>

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

916)     </p>

917) 
918)     <p>
919)     <b>This project is likely trickier than it looks. You should avoid applying
920)     for this if you're uncertain about being able to complete it.</b>
921)     </p>
922)     </li>

923)     </li>

924) 

925)     <a id="chutneyExpansion"></a>
926)     <li>
927)     <b>Make Chutney Do More, More Reliably</b>
928)     <br>
929)     Effort Level: <i>Medium to High, depending on scope of project</i>
930)     <br>
931)     Skill Level: <i>Medium</i>
932)     <br>

933)     Likely Mentors: <i>Nick (nickm)</i>
934)     <p>

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

939)     </p>

940) 

941)     <p>

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

945)     </p>

946) 
947)     <p>
948)     <b>As part of your application for this project please submit a patch that
949)     expands Chutney.</b>
950)     </p>
951) 

952)     </li>

953) 

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

955)     <li>

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

957)     <br>
958)     Effort Level: <i>Medium to High</i>
959)     <br>

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

961)     <br>
962)     Likely Mentors: <i>Nick (nickm)</i>
963)     <p>

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

967)     </p>

968) 

969)     <p>

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

979)     </p>

980) 

981)     <p>

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

985)     </p>
986)     </li>

987) 

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

989)     <li>

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

991)     <br>
992)     Effort Level: <i>Medium</i>
993)     <br>
994)     Skill Level: <i>Medium</i>
995)     <br>

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

1005) 

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

1017) 

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

1028) 

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

1033)     </li>

1034) 

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

1036)     <li>

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

1038)     <br>
1039)     Effort Level: <i>Medium</i>
1040)     <br>
1041)     Skill Level: <i>Medium</i>
1042)     <br>

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

1044)     <p>

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

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

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

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

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

1052)     </p>

1053) 

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

1060) 

1061)     <p>

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

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

1066)     </p>

1067) 

1068)     <ol>
1069)       <li>Come up with a better, more developer friendly "Module Overview" for our documentation (<a href="https://stem.torproject.org/api/control.html">example page</a>). For instance, it would be nice to provide interlinking between the overview and the classes/methods that it lists. This will probably involve asking for help from the <a href="http://sphinx-doc.org/">Sphinx user list</a>. (<a href="https://trac.torproject.org/7632">ticket</a>)</li>
1070)       <li>Navigation of <a href="https://stem.torproject.org">stem's site</a> is clunky, in large part due to the linear page flow supported by sphinx. One possible fix for this would be css-only menus, ideally as a sphinx plugin so we could contribute it back upstream.(<a href="https://trac.torproject.org/8431">ticket</a>)</li>

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

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

1074) 

1075)     <p>

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

1077)     </p>

1078) 

1079)     <a id="stemTestingForTor"></a>
1080)     <li>
1081)     <b>Stem Tests for Tor</b>
1082)     <br>
1083)     Effort Level: <i>Medium</i>
1084)     <br>
1085)     Skill Level: <i>Medium</i>
1086)     <br>
1087)     Likely Mentors: <i>Damian (atagar)</i>
1088)     <p>
1089)     Stem is a library for interacting with Tor (see '<a href="#stemUsability">Stem Usability and Porting</a>' above for a summary). The library has both <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/unit">unit</a> and <a href="https://gitweb.torproject.org/stem.git/tree/HEAD:/test/integ">integration</a> tests. The unit tests provide a quick, direct test of stem's codebase while the integration test exercises its functionality against a live instance of Tor.
1090)     </p>
1091) 
1092)     <p>
1093)     Stem's integration tests have thus far been (unsurprisingly) designed to test stem but there's no need for them to be limited to that. Stem is a complete implementation of Tor's <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control-spec</a> and <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt">dir-spec</a>. As such, stem's tests could be easily expanded to more dedicatedly test behavior involved in those portions of Tor's codebase, as well as provide a smoke test for its general functionality.
1094)     </p>
1095) 
1096)     <p>
1097)     This project would involve several components:
1098)     </p>
1099) 
1100)     <ol>
1101)       <li>Determine what kind of tests we need. <b>This should be done during the application phase</b> by <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">contacting tor-dev@</a>. Hopefully this will give us an idea of what would be the most useful kind of tests of this nature for Tor development.</li>
1102)       <li>To be useful our integration tests need to continually run against the present tip of Tor's codebase. To do this we'll want to (1) fetch and compile the latest version of Tor, (2) run our integration tests against it, (3) compose the results as an html formatted email, and send it to a list. (<a href="https://trac.torproject.org/8261">ticket</a>)</li>
1103)       <li>Implement the new suite of integration tests for Tor. This will likely include expanding Tor to support better testability. One useful candidate, for instance, would be a controller method to fetch our own descriptor. This would let us easily test various configurations to see if they provide valid descriptor content.</li>
1104)     </ol>
1105) 
1106)     <p>

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

1108)     </p>
1109) 

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

1111)     <li>

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

1113)     <br>

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

1115)     <br>

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

1117)     <br>

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

1119)     <p>

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

1128)     </p>

1129) 

1130)     <p>

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

1136)     </p>

1137) 

1138)     <p>

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

1143)     </p>

1144) 
1145)     <p>
1146)     <b>As part of your application for this project please identify one of the
1147)     thorniest Tor functions and submit a patch refactoring it to be better. If
1148)     you find this to be difficult then this likely isn't the project for
1149)     you.</b>
1150)     </p>

1151)     </li>

1152) 

1153)     <li>
1154)     <b>Bring up new ideas!</b>

1155)     <br>

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

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

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

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

1161)     might also be short on developers.
1162)     </li>

1163) 

1164)     </ol>

1165) 

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

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

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

1181) 

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

1187) 

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

1197) 

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

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

1202)     Tor if needed.</li>

1203) 

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

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

1209) 

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

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

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

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

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

1220) 

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

1224) 

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

1231) 

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

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

1235)     System</a>.
1236)     </li>

1237) 

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

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

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

1250) 

1251)     </ol>

1252) 

1253)     <a id="Research"></a>
1254)     <h2><a class="anchor" href="#Research">Research</a></h2>
1255)     <ol>
1256)     <li>The "end-to-end traffic confirmation attack":
1257)     by watching traffic at Alice and at Bob, we can <a
1258)     href="http://freehaven.net/anonbib/#danezis:pet2004">compare
1259)     traffic signatures and become convinced that we're watching the same
1260)     stream</a>. So far Tor accepts this as a fact of life and assumes this
1261)     attack is trivial in all cases. First of all, is that actually true? How
1262)     much traffic of what sort of distribution is needed before the adversary
1263)     is confident he has won? Are there scenarios (e.g. not transmitting much)
1264)     that slow down the attack? Do some traffic padding or traffic shaping
1265)     schemes work better than others?</li>
1266)     <li>A related question is: Does running a relay/bridge provide additional
1267)     protection against these timing attacks? Can an external adversary that can't
1268)     see inside TLS links still recognize individual streams reliably?
1269)     Does the amount of traffic carried degrade this ability any? What if the
1270)     client-relay deliberately delayed upstream relayed traffic to create a queue
1271)     that could be used to mimic timings of client downstream traffic to make it
1272)     look like it was also relayed? This same queue could also be used for masking
1273)     timings in client upstream traffic with the techniques from <a
1274)     href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
1275)     but without the need for additional traffic. Would such an interleaving of
1276)     client upstream traffic obscure timings for external adversaries? Would the
1277)     strategies need to be adjusted for asymmetric links? For example, on
1278)     asymmetric links, is it actually possible to differentiate client traffic from
1279)     natural bursts due to their asymmetric capacity? Or is it easier than
1280)     symmetric links for some other reason?</li>
1281)     <li>Repeat Murdoch and Danezis's <a
1282)     href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
1283)     Oakland 05</a> on the current Tor network. See if you can learn why it
1284)     works well on some nodes and not well on others. (My theory is that the
1285)     fast nodes with spare capacity resist the attack better.) If that's true,
1286)     then experiment with the RelayBandwidthRate and RelayBandwidthBurst
1287)     options to run a relay that is used as a client while relaying the
1288)     attacker's traffic: as we crank down the RelayBandwidthRate, does the
1289)     attack get harder? What's the right ratio of RelayBandwidthRate to
1290)     actually capacity? Or is it a ratio at all? While we're at it, does a
1291)     much larger set of candidate relays increase the false positive rate
1292)     or other complexity for the attack? (The Tor network is now almost two
1293)     orders of magnitude larger than it was when they wrote their paper.) Be
1294)     sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
1295)     Clog the Queue</a> too.</li>
1296)     <li>The "routing zones attack": most of the literature thinks of
1297)     the network path between Alice and her entry node (and between the
1298)     exit node and Bob) as a single link on some graph. In practice,
1299)     though, the path traverses many autonomous systems (ASes), and <a
1300)     href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
1301)     that the same AS appears on both the entry path and the exit path</a>.
1302)     Unfortunately, to accurately predict whether a given Alice, entry,
1303)     exit, Bob quad will be dangerous, we need to download an entire Internet
1304)     routing zone and perform expensive operations on it. Are there practical
1305)     approximations, such as avoiding IP addresses in the same /8 network?</li>
1306)     <li>Other research questions regarding geographic diversity consider
1307)     the tradeoff between choosing an efficient circuit and choosing a random
1308)     circuit. Look at Stephen Rollyson's <a
1309)     href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
1310)     paper</a> on how to discard particularly slow choices without hurting
1311)     anonymity "too much". This line of reasoning needs more work and more
1312)     thinking, but it looks very promising.</li>
1313)     <li>Tor doesn't work very well when relays have asymmetric bandwidth
1314)     (e.g. cable or DSL). Because Tor has separate TCP connections between
1315)     each hop, if the incoming bytes are arriving just fine and the outgoing
1316)     bytes are all getting dropped on the floor, the TCP push-back mechanisms
1317)     don't really transmit this information back to the incoming streams.
1318)     Perhaps Tor should detect when it's dropping a lot of outgoing packets,
1319)     and rate-limit incoming streams to regulate this itself? I can imagine
1320)     a build-up and drop-off scheme where we pick a conservative rate-limit,
1321)     slowly increase it until we get lost packets, back off, repeat. We
1322)     need somebody who's good with networks to simulate this and help design
1323)     solutions; and/or we need to understand the extent of the performance
1324)     degradation, and use this as motivation to reconsider UDP transport.</li>
1325)     <li>A related topic is congestion control. Is our
1326)     current design sufficient once we have heavy use? Maybe
1327)     we should experiment with variable-sized windows rather
1328)     than fixed-size windows? That seemed to go well in an <a

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

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

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

1355)     your browser's UserAgent string by replacing it with a uniform answer for
1356)     every Tor user. That way the attacker can't splinter Tor's anonymity set
1357)     by looking at that header. It tries to pick a string that is commonly used
1358)     by non-Tor users too, so it doesn't stand out. Question one: how badly
1359)     do we hurt ourselves by periodically updating the version of Firefox
1360)     that Torbutton claims to be? If we update it too often, we splinter the
1361)     anonymity sets ourselves. If we don't update it often enough, then all the
1362)     Tor users stand out because they claim to be running a quite old version
1363)     of Firefox. The answer here probably depends on the Firefox versions seen
1364)     in the wild. Question two: periodically people ask us to cycle through N
1365)     UserAgent strings rather than stick with one. Does this approach help,
1366)     hurt, or not matter? Consider: cookies and recognizing Torbutton users
1367)     by their rotating UserAgents; malicious websites who only attack certain
1368)     browsers; and whether the answers to question one impact this answer.
1369)     </li>
1370)     <li>How many bridge relays do you need to know to maintain
1371)     reachability? We should measure the churn in our bridges. If there is
1372)     lots of churn, are there ways to keep bridge users more likely to stay
1373)     connected?
1374)     </li>
1375)     </ol>

1376) 

1377)     <p>
1378)     <a href="<page about/contact>">Let us know</a> if you've made progress on any
1379)     of these!
1380)     </p>
1381)   </div>
1382)   <!-- END MAINCOL -->
1383)   <div id = "sidecol">
1384) #include "side.wmi"
1385) #include "info.wmi"
1386)   </div>
1387)   <!-- END SIDECOL -->
1388) </div>
1389) <!-- END CONTENT -->