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

29) 

30)     <a id="Documentation"></a>
31)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
32)     <ol>

33)     <li>Help translate the
34) <!-- web page and -->
35)     documentation into other

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

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

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

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

44)     programs that interface with Tor</a>. Which ones are useful in which

45)     situations? Please help us test them out and document your results.</li>
46)     </ol>

47) 

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

51)     <li>Monitor some of our <a
52)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo">public mailing
53)     lists</a>, like <a
54)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">tor-talk</a>, <a
55)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">tor-relays</a>, <a
56)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev">tor-dev</a>, or <a
57)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev">tbb-dev</a>,
58)     and summarize noteworthy exchanges into articles for <a
59)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-news">Tor

60)     Weekly News</a>.</li>

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

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

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

66)     <a

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

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

69)     <li>Create a poster around a theme, such as "Tor for Freedom!"</li>

70)     <li>Create a t-shirt design that incorporates "<a
71)     href="https://check.torproject.org/">Congratulations! You are using
72)     Tor!</a>" in any language.</li>

73)     <li>Spread the word about Tor at a symposium or conference and use these
74)     <a href="https://media.torproject.org/misc/2015-03-tor-brochure/">Tor
75)     brochures</a> in PDF and ODG format and translated to at least ten
76)     different languages as conversation starter.</li>

77)     </ol>

78) 

79)     <a id="gsoc"></a>
80)     <h2><a class="anchor" href="#gsoc">Google Summer of Code</a></h2>
81) 
82)     <p>
83)     Tor is also taking part in this year's <a

84)     href="https://summerofcode.withgoogle.com/">Google
85)     Summer of Code</a>! To apply but you need to be either <a
86)     href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">a
87)     present student or just graduated</a>. <b>See our page for <a href="<page
88)     about/gsoc>">Google Summer of Code</a> for more information.</b>

89)     </p>
90) 

91)     <a id="Projects"></a>
92)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

93) 

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

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

101)     </p>

102) 

103)     <p>
104)     For a presentation summarizing many of these projects see...
105)     </p>
106) 
107)     <div id="ecosystem_presentation">

108)       <a href="https://www.youtube.com/watch?v=fb6iqZcQsSg">Tor Ecosystem</a> (<a href="https://media.torproject.org/video/2013-11-t3am-damian-johnson.mp4">mp4</a>, <a href="https://svn.torproject.org/svn/projects/presentations/2013-11-t3am-tor-ecosystem.pdf">slides</a>)

109)     </div>
110) 
111)     <br /></br />
112) 

113)     <table id="projects">
114)       <tr>
115)         <th>Name</th>
116)         <th>Category</th>
117)         <th>Language</th>
118)         <th>Activity</th>
119)         <th>Contributors</th>
120)       </tr>

121) 

122)       <tr>
123)         <td><a href="#project-tor">Tor</a></td>
124)         <td>Core</td>
125)         <td>C</td>
126)         <td>Heavy</td>

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

128)       </tr>

129) 

130)       <tr>

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

132)         <td>Bundle</td>

133)         <td>Javascript, XUL, Scripting</td>

134)         <td>Heavy</td>

135)         <td>mikeperry, Pearl Crescent</td>

136)       </tr>
137) 

138)       <tr>

139)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
140)         <td>Browser Add-on</td>
141)         <td>Javascript</td>

142)         <td>Heavy</td>

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

144)       </tr>

145) 

146)       <tr>

147)         <td><a href="#project-nyx">Nyx</a></td>

148)         <td>User Interface</td>
149)         <td>Python, Curses</td>

150)         <td>Heavy</td>

151)         <td>atagar</td>
152)       </tr>

153) 

154)       <tr>

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

158)         <td>Moderage</td>

159)         <td>n8fr8</td>

160)       </tr>

161) 

162)       <tr>

163)         <td><a href="#project-tails">Tails</a></td>
164)         <td>OS image</td>
165)         <td>Sys Admin</td>
166)         <td>Heavy</td>
167)         <td><a href="https://tails.boum.org/">#tails</a></td>

168)       </tr>

169) 

170)       <tr>

171)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
172)         <td>OS image</td>
173)         <td>Sys Admin</td>

174)         <td>Light</td>

175)         <td>blueness</td>
176)       </tr>
177) 

178)       <tr>

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

182)         <td>Light</td>

183)         <td>David Goulet</td>

184)       </tr>
185) 

186)       <tr>
187)         <td><a href="#project-tormessenger">Tor Messenger</a></td>
188)         <td>Bundle</td>
189)         <td>JavaScript, XUL, Scripting</td>
190)         <td>Heavy</td>
191)         <td>arlolra, boklm, sukhe</td>
192)       </tr>
193) 

194)       <tr>

195)         <td><a href="#project-torbirdy">TorBirdy</a></td>
196)         <td>Browser Add-on</td>
197)         <td>JavaScript</td>

198)         <td>Light</td>
199)         <td>sukhe</td>

200)       </tr>

201) 

202)       <tr>

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

205)         <td>Python</td>

206)         <td>None</td>

207)         <td>asn</td>

208)       </tr>
209) 

210)       <tr>

211)         <td><a href="#project-flash-proxy">Flash Proxy</a></td>
212)         <td>Client Add-on</td>
213)         <td>Python, JavaScript, Go</td>

214)         <td>Light</td>

215)         <td>dcf, infinity0, Arlo Breault</td>

216)       </tr>

217) 

218)       <tr>

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

220)         <td>Simulator</td>

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

222)         <td>Heavy</td>

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

225) 

226)       <tr>
227)         <td><a href="#project-chutney">Chutney</a></td>
228)         <td>Simulator</td>
229)         <td>Python</td>
230)         <td>Light</td>
231)         <td>nickm</td>
232)       </tr>
233) 

234)       <tr>

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

236)         <td>Library</td>
237)         <td>Python</td>

238)         <td>Heavy</td>

239)         <td>atagar</td>

240)       </tr>

241) 

242)       <tr>

243)         <td><a href="#project-txtorcon">Txtorcon</a></td>
244)         <td>Library</td>
245)         <td>Python, Twisted</td>

246)         <td>Light</td>

247)         <td>meejah</td>
248)       </tr>

249) 

250)       <tr>

251)         <td><a href="#project-tlsdate">Tlsdate</a></td>
252)         <td>Utility</td>
253)         <td>C</td>

254)         <td>None</td>

255)         <td>ioerror</td>
256)       </tr>

257) 

258)       <tr>

259)         <td><a href="#project-metrics">Metrics</a></td>
260)         <td>Client Service</td>
261)         <td>Java</td>

262)         <td>Moderate</td>

263)         <td>karsten</td>
264)       </tr>

265) 

266)       <tr>

267)         <td><a href="#project-atlas">Atlas</a></td>
268)         <td>Client Service</td>
269)         <td>JavaScript</td>

270)         <td>None</td>

271)         <td></td>

272)       </tr>

273) 

274)       <tr>
275)         <td><a href="#project-globe">Globe</a></td>
276)         <td>Client Service</td>
277)         <td>JavaScript</td>

278)         <td>None</td>
279)         <td></td>

280)       </tr>
281) 

282)       <tr>

283)         <td><a href="#project-compass">Compass</a></td>
284)         <td>Client Service</td>
285)         <td>Python</td>

286)         <td>None</td>
287)         <td></td>

288)       </tr>

289) 

290)       <tr>

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

293)         <td>Java</td>

294)         <td>Light</td>

295)         <td>karsten</td>

296)       </tr>
297) 

298)       <tr>
299)         <td><a href="#project-exitmap">ExitMap</a></td>
300)         <td>Backend Service</td>
301)         <td>Python</td>

302)         <td>Light</td>

303)         <td>phw</td>
304)       </tr>
305) 

306)       <tr>
307)         <td><a href="#project-doctor">DocTor</a></td>
308)         <td>Backend Service</td>
309)         <td>Python</td>

310)         <td>Light</td>

311)         <td>atagar</td>
312)       </tr>
313) 

314)       <tr>

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

318)         <td>None</td>

319)         <td>kaner</td>
320)       </tr>

321) 

322)       <tr>

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

326)         <td>Light</td>
327)         <td>ilv</td>

328)       </tr>

329) 

330)       <tr>

331)         <td><a href="#project-torcheck">TorCheck</a></td>
332)         <td>Client Service</td>

333)         <td>Go</td>

334)         <td>None</td>

335)         <td>Arlo</td>

336)       </tr>

337) 

338)       <tr>

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

342)         <td>Light</td>

343)         <td>isis</td>

344)       </tr>

345) 

346)       <tr>

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

348)         <td>Scanner</td>
349)         <td>Python</td>

350)         <td>Moderate</td>

351)         <td>hellais, aagbsn</td>

352)       </tr>
353) 

354)       <tr>
355)         <td><a href="#project-torps">TorPS</a></td>
356)         <td>Backend Service</td>
357)         <td>Python</td>

358)         <td>None</td>

359)         <td>Aaron Johnson</td>
360)       </tr>
361) 

362)       <tr>

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

366)         <td>None</td>

367)         <td>aagbsn</td>

368)       </tr>

369) 

370)       <tr>

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

373)         <td>Python</td>

374)         <td>Heavy</td>

375)         <td>evilaliv3, hellais</td>

376)       </tr>

377) 

378)       <tr>

379)         <td><a href="#project-anonbib">Anonbib</a></td>
380)         <td>Website</td>

381)         <td>Python</td>

382)         <td>Light</td>

383)         <td>arma, nickm</td>
384)       </tr>

385)     </table>

386) 

387)     <sub>
388)     * Project is still in an alpha state.
389)     </sub>

390) 

391)     <br /><br />

392) 

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

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

396)     tracker</a>)</h3>

397) 

398)     <p>
399)     Central project, providing the core software for using and participating in
400)     the Tor network. Numerous people contribute to the project to varying
401)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
402)     </p>

403) 

404)     <p>
405)     <b>Project Ideas:</b><br />

406)     <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i>

407)     </p>

408) 

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

410)     <h3><a href="<page projects/torbrowser>">Tor Browser</a> (<a

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

412)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&component=Tor+Launcher&component=Tor+Browser&component=Tor+bundles%2Finstallation&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">bug

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

415)     <p>

416)     Tor Browser is an easy-to-use, portable package of Tor, HTTPS-Everywhere,
417)     NoScript, TorLauncher, Torbutton, and a Firefox fork, all  preconfigured

418)     to work together out of
419)     the box. The modified copy of Firefox aims to resolve the

420)     privacy and security issues in mainline version.

421)     </p>

422) 

423)     <p>
424)     <b>Project Ideas:</b><br />
425)     <i><a href="#panopticlick">Panopticlick</a></i><br />

426)     <i><a href="#feedbackExtension">Feedback Extension for Tor Browser</a></i><br />

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-nyx"></a>
442)     <h3><a href="https://www.atagar.com/arm/">Nyx</a> (<a
443)     href="https://gitweb.torproject.org/nyx.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=arm&order=priority">bug
445)     tracker</a>)</h3>

446) 

447)     <p>

448)     Nyx (previously <i>arm</i>) is a terminal status monitor for Tor

449)     intended for command-line aficionados, ssh connections, and anyone with a
450)     tty terminal. This works much like top does for system usage, providing
451)     real time statistics for bandwidth, resource usage, connections, and quite
452)     a bit more.

453)     </p>

454) 

455)     <p>
456)     <b>Project Ideas:</b><br />
457)     <i><a href="#expand_nyx">Expand Nyx</a></i>
458)     </p>
459) 

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

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

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

465) 
466)     <p>

467)     Provides Tor on the Android platform. The project is under active
468)     development, updates to latest Tor releases, and working to stay up to

469)     date with all changes in Android and mobile threats.

470)     </p>
471) 
472)     <a id="project-tails"></a>
473)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

476)     tracker</a>, <a href="https://tails.boum.org/doc">documentation</a>, <a
477)     href="https://tails.boum.org/contribute/design/">design</a>, <a
478)     href="https://tails.boum.org/contribute">contribute</a>)</h3>

479) 
480)     <p>
481)     The Amnesic Incognito Live System is a live CD/USB distribution
482)     preconfigured so that everything is safely routed through Tor and leaves no
483)     trace on the local system. This is a merger of the Amnesia and <a
484)     href="http://www.anonymityanywhere.com/incognito/">Incognito</a> projects,
485)     and still under very active development.
486)     </p>
487) 

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

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

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

492) 
493)     <p>

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

496)     </p>
497) 

498)     <a id="project-torsocks"></a>

499)     <h3>Torsocks (<a

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

504)     <p>

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

508)     </p>

509) 

510)     <a id="project-tormessenger"></a>
511)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger">Tor Messenger</a> (<a
512)     href="https://gitweb.torproject.org/tor-messenger-build.git">code</a>, <a
513)     href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Tor+Messenger">bug tracker</a>)</h3>
514) 
515)     <p>
516)     Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor.
517)     </p>
518) 

519)     <a id="project-torbirdy"></a>
520)     <h3>TorBirdy (<a

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

522)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
523)     tracker</a>)</h3>

524) 

525)     <p>
526)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
527)     </p>

528) 

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

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

531)     href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git">code</a>,
532)     <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Pluggable+transport&order=priority">bug

533)     tracker</a>)</h3>

534) 

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

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

538)     </p>

539) 

540)     <a id="project-flash-proxy"></a>
541)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
542)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a
543)     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
544)     tracker</a>)</h3>

545) 

546)     <p>
547)     Pluggable transport using proxies running in web browsers to defeat
548)     address-based blocking.
549)     </p>

550) 

551)     <a id="project-chutney"></a>
552)     <h3>Chutney (<a href="https://gitweb.torproject.org/chutney.git">code</a>,
553)     <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&component=Chutney">bug
554)     tracker</a>)</h3>
555) 
556)     <p>
557)     Integration test suite that spawns a local tor network, checking the
558)     interactions of its components.
559)     </p>
560) 

561)     <a id="project-shadow"></a>
562)     <h3><a href="https://shadow.cs.umn.edu/">Shadow</a> (<a
563)     href="https://github.com/shadow">code</a>, <a
564)     href="https://github.com/shadow/shadow/issues">bug
565)     tracker</a>)</h3>

566) 

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

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

573)     </p>

574) 

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

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

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

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

579)     tracker</a>)</h3>

580) 

581)     <p>

582)     Python controller library for scripts and controller applications using
583)     Tor.

584)     </p>

585) 

586)     <p>
587)     <b>Project Ideas:</b><br />
588)     <i><a href="#descriptor_parsing_in_go">Stem Descriptor Parsing in Go</a></i>
589)     </p>
590) 

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

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

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

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

595) 

596)     <p>
597)     Twisted-based asynchronous Tor control protocol implementation. Includes
598)     unit-tests, examples, state-tracking code and configuration abstraction.
599)     Used by OONI and APAF.
600)     </p>

601) 

602)     <p>
603)     <b>Project Ideas:</b><br />
604)     <i><a href="#txtorcon_use_txaio">Convert txtorcon to use txaio</a></i><br />
605)     <i><a href="#txtorcon_use_pytest">Convert txtorcon to py.test</a></i>
606)     </p>
607) 

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

610) 

611)     <p>
612)     tlsdate: secure parasitic rdate replacement
613)     </p>

614) 

615)     <p>
616)     tlsdate sets the local clock by securely connecting with TLS to remote
617)     servers and extracting the remote time out of the secure handshake. Unlike
618)     ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
619)     enabled service, and provides some protection against adversaries that try
620)     to feed you malicious time information.
621)     </p>

622) 

623)     <a id="project-metrics"></a>
624)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
625)     href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a

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

627) 

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

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

633)     </p>

634) 

635)     <a id="project-atlas"></a>
636)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
637)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

638) 

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

642)     their past usage.

643)     </p>

644) 

645)     <p>

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

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

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

651)     </p>

652) 

653)     <a id="project-globe"></a>
654)     <h3><a href="http://globe.rndm.de/">Globe</a> (<a
655)     href="https://github.com/makepanic/globe">code</a>, <a
656)     href="https://github.com/makepanic/globe/issues">bug tracker</a>)</h3>
657) 
658)     <p>
659)     Globe is a web application that allows you to search for Tor relays and
660)     bridges. It gives you a detailed overview of properties and configurations
661)     of a relay or bridge.
662)     </p>
663) 

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

669) 

670)     <p>
671)     Compass is a web and command line application that filters and
672)     aggregates the Tor relays based on various attributes.
673)     </p>

674) 
675)     <a id="project-onionoo"></a>

676)     <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a
677)     href="https://gitweb.torproject.org/onionoo.git">code</a>,
678)     <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>

679) 
680)     <p>
681)     Onionoo is a JSON based protocol to learn information about currently
682)     running Tor relays and bridges.
683)     </p>
684) 

685)     <a id="project-exitmap"></a>
686)     <h3><a href="http://www.cs.kau.se/philwint/spoiled_onions/">ExitMap</a> (<a
687)     href="https://github.com/NullHypothesis/exitmap">code</a>, <a
688)     href="https://github.com/NullHypothesis/exitmap/issues">bug tracker</a>)</h3>
689) 
690)     <p>

691)     Scanner for the Tor network by Philipp Winter to detect malicious and
692)     misconfigured exits. For more information about how it works see his <a
693)     href="http://www.cs.kau.se/philwint/spoiled_onions/pets2014.pdf">Spoiled

694)     Onions</a> research paper.
695)     </p>
696) 

697)     <p>
698)     <b>Project Ideas:</b><br />
699)     <i><a href="#exitmap_improvements">Exitmap Improvements</a></i>
700)     </p>
701) 

702)     <a id="project-doctor"></a>
703)     <h3>DocTor (<a
704)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a
705)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=DocTor&order=priority">bug
706)     tracker</a>)</h3>
707) 
708)     <p>
709)     DocTor is a notification service that monitors newly published descriptor
710)     information for issues. This is primarily a service to help the tor
711)     directory authority operators, but it also checks for a handful of other
712)     issues like sybil attacks.
713)     </p>
714) 

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

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

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

720) 

721)     <p>
722)     Provides automatic notification to subscribed relay operators when their
723)     relay's unreachable. This underwent a rewrite by the <a
724)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
725)     in early 2011.
726)     </p>

727) 

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

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

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

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

733) 

734)     <p>
735)     E-mail autoresponder providing Tor's packages over SMTP. This has been
736)     relatively unchanged for quite a while.
737)     </p>

738) 

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

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

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

742)     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
743)     tracker</a>)</h3>

744) 

745)     <p>

746)     Site for determining if the visitor is using Tor or not.

747)     </p>

748) 

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

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

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

754) 

755)     <p>
756)     Backend bridge distributor, handling the various pools they're distributed
757)     in. This was actively developed until Fall of 2010.
758)     </p>

759) 
760)     <a id="project-ooni-probe"></a>

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

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

771)     <a id="project-torps"></a>
772)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
773) 
774)     <p>
775)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
776)     path selection in Tor. It chooses circuits and assigns user streams to
777)     those circuits in the same way that Tor does. TorPS is fast enough to
778)     perform thousands of simulations over periods of months.
779)     </p>
780) 

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

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

783)     href="https://gitweb.torproject.org/torflow.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=Torflow&order=priority">bug
785)     tracker</a>)</h3>

786) 

787)     <p>
788)     Library and collection of services for actively monitoring the Tor network.
789)     These include the Bandwidth Scanners (measuring throughput of relays) and
790)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
791)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
792)     months later. Both have been under active use since then, but development
793)     has stopped.
794)     </p>

795) 
796)     <a id="project-tor2web"></a>
797)     <h3><a

798)     href="https://www.tor2web.org">Tor2web</a> (<a

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

808)     <a id="project-anonbib"></a>
809)     <h3><a
810)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
811)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
812) 
813)     <p>

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

817)     </p>
818) 

819)     <a id="Coding"></a>
820)     <a id="Summer"></a>

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

822) 

823)     <p>

824)     You may find some of these projects to be good ideas for <a href="<page

825)     about/gsoc>">Google Summer of Code</a>. We have labelled each idea with
826)     which of our <a href="<page about/corepeople>">core developers</a> would be
827)     good mentors. If one or more of these ideas looks promising to you, please
828)     <a href="<page about/contact>">contact us</a> to discuss your plans rather
829)     than sending blind applications. You may also want to propose your own
830)     project idea &mdash; which often results in the best applications.

831)     </p>

832) 

833)     <ol>

834) 

835)     <a id="improveHiddenServices"></a>
836)     <li>
837)     <b>Help improve Tor hidden services</b>
838)     <br>

839)     Language: <i>C</i>

840)     <br>

841)     Likely Mentors: <i>George (asn), David Goulet (dgoulet)</i>

842)     <br><br>

843)     <p>
844) We're working on a revamp of the entire Tor hidden service design to
845) improve the security and reliability of the hidden service system.
846)     </p>
847) 
848)     <p>
849) This is a big project: see

850) <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt">proposal

851) 224</a> for the latest design.  Are you interested in implementing some
852) part of that?
853)     </p>
854) 
855)     <p>
856) This is a very ambitious project, so we're deliberately not suggesting
857) particular sub-topics.  If you're interested in participating, try to
858) read and understand the <a

859) href="https://gitweb.torproject.org/torspec.git/tree/rend-spec.txt">existing

860) design</a> and the design proposal for the new design, and then talk to
861) us about what part you want to work on.
862)     </p>
863) 
864)     <p>
865) As part of the application process for this project, please contribute a
866) nontrivial patch to Tor -- ideally, one that will affect some part of
867) the codebase that you want to work on.
868)     </p>
869)     </li>
870) 

871)     <a id="exitmap_improvements"></a>
872)     <li>
873)     <b>Exitmap Improvements</b>
874)     <br>

875)     Language: <i>Python</i>

876)     <br>
877)     Likely Mentors: <i>Philipp (phw)</i>

878)     <br><br>

879)     <p>
880) The Tor Project makes use of the Python tool <a
881) href="https://gitweb.torproject.org/user/phw/exitmap.git/">Exitmap</a> to
882) systematically scan for malicious and misbehaving exit relays.  Once such a
883) relay is found, it is assigned the BadExit flag which prevents clients from
884) selecting the relay as last hop in their circuit.
885)     </p>
886) 
887)     <p>
888) Exitmap supports scanning modules which implement a specific scan over
889) exit relays.  Examples are the DNS module which checks for DNS poisoning
890) or the patching check module which looks out for tampered file
891) downloads.
892)     </p>
893) 
894)     <p>
895) This project is meant to extend exitmap in several ways.  First, it
896) should be made fully autonomous.  That means that exitmap should be able
897) to run in the background, periodically fetch new relay descriptors, and
898) have a smart algorithm which keeps scanning all exit relays
899) periodically.  Second, exitmap should be able to emulate some user
900) interaction and dynamically "explore" the web in order to detect
901) tampering.  Third, unit tests should be added for existing and new code
902) in order to make the code base more robust.
903)     </p>
904)     </li>

905) 

906)     <a id="expand_nyx"></a>
907)     <li>
908)     <b>Expand Nyx</b>
909)     <br>

910)     Language: <i>Python</i>

911)     <br>
912)     Likely Mentors: <i>Damian (atagar)</i>

913)     <br><br>

914)     <p>
915) Nyx (previously known as <a href="https://www.atagar.com/arm/">arm</a>) is an
916) ncurses monitor that provides Tor relay operators...
917)     </p>
918) 
919)     <ul>
920)       <li><a href="https://www.atagar.com/arm/images/screenshot_page1_full.png">bandwidth graphs and event log</a></li>
921)       <li><a href="https://www.atagar.com/arm/images/screenshot_page2_full.png">connections</a></li>
922)       <li><a href="https://www.atagar.com/arm/images/screenshot_page3_full.png">user's torrc</a></li>
923)       <li><a href="https://www.atagar.com/arm/images/screenshot_configPanel_full.png">config editor</a></li>
924)     </ul>
925) 
926)     <p>
927) Nyx is presently under development in preparation for its next release. If you
928) like python, terminals, and collaborating on an active codebase this just might
929) be the project for you!
930)     </p>
931) 
932)     <p>
933) Proposals should involve a grab-bag of moderately small improvements you'd like
934) to make. You're encouraged to brainstorm ideas of their own but here's a few to
935) get ya started...
936)     </p>
937) 
938)     <ul>
939)       <li>Bring back the <a href="https://www.atagar.com/arm/images/screenshot_interpretor_full.png">interpreter panel</a>. This panel was dropped when refactoring Nyx, but it would be a neat component to bring back. You can <a href="https://gitweb.torproject.org/nyx.git/tree/src/cli/interpretorPanel.py?h=release">find old code for it in the history</a> and Stem (the library backing Nyx) has a much improved <a href="https://stem.torproject.org/tutorials/down_the_rabbit_hole.html">variant of this we can leverage</a>. This task would involve writing the curses code around Stem's interpreter functions.</li>
940)       <li>Windows support. Like most curses applications Nyx doesn't run natively on Windows. We've had dozens of users request this and <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#Windows">it should be possible</a>. This would involve supporting PDCurses and expanding Stem to be able to query the cpu/memory usage of the tor process.</li>
941)       <li>Unit testing! Nyx has <a href="https://gitweb.torproject.org/nyx.git/tree/test">started adding tests</a> but it's still very minimal. Achieving any substantial code coverage will require us to figure out how to unit test curses components.</li>
942)       <li>Onionoo provides additional relay information that could enrich our connection panel such as geoip and rdns. Trick is that at present we can only query it on a per-relay basis which would leak our connections (no-go for security). However, if we could get information about all relays in bulk it would sidestep this. For some old thoughts on this see <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#CircuitDetails">here</a>.</li>

943)       <li>Relay setup wizard. Our last release had this (screenshots: <a href="https://www.atagar.com/transfer/tmp/arm_wizard1.png">1</a>, <a href="https://www.atagar.com/transfer/tmp/arm_wizard2.png">2</a>, <a href="https://www.atagar.com/transfer/tmp/arm_wizard3.png">3</a>). This has been removed because including it directly in Nyx confused users, but we might want to resurrect it as a separate <i>setup-tor-relay</i> command.</li>

944)       <li><a href="https://trac.torproject.org/projects/tor/ticket/18499">Improved dialog</a> for selecting events to log.</li>

945)       <li>... and more! Again, don't hesitate to propose ideas of your own.</li>
946)     </ul>
947) 
948)     <p>
949)     <b>As part of your application for this project please get your hands wet with the codebase by contributing patches for <a href="https://gitweb.torproject.org/nyx.git">Nyx</a> and <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b>
950)     </p>
951)     </li>
952) 

953)     <a id="descriptor_parsing_in_go"></a>
954)     <li>
955)     <b>Stem Descriptor Parsing in Go</b>
956)     <br>
957)     Language: <i>Go, Python</i>
958)     <br>
959)     Likely Mentors: <i>Damian (atagar), Philipp (phw)</i>
960)     <br><br>
961)     <p>
962)     Tor consists of two parts: the application and a distributed network of a
963)     few thousand volunteer relays. Information about these relays is public,
964)     and made up of documents called <b><a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#what-is-a-descriptor">descriptors</a></b>. We have
965)     <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#are-there-any-other-parsing-libraries">three libraries capable of reading these documents</a>...
966)     </p>
967) 
968)     <ul>
969)       <li><b><a href="https://stem.torproject.org/">Stem</a></b> (Python)</li>
970)       <li><b><a href="https://gitweb.torproject.org/metrics-lib.git/">Metrics-lib</a></b> (Java)</li>
971)       <li><b><a href="https://gitweb.torproject.org/user/phw/zoossh.git/">Zoossh</a></b> (Go)</li>
972)     </ul>
973) 
974)     <p>
975)     Stem is the most feature rich but slowest, and conversely Zoossh is fastest
976)     but limited. But what if Stem used CFFI bindings to do the heavy lifting in
977)     Go? Could we unify these libraries, getting the feature set of Stem with
978)     the performance of Zoossh?
979)     </p>
980) 
981)     <p>
982)     <b>Applicants should be familiar with both Python and Go. As part of your
983)     application for this project please write a demo CFFI binding for Stem as a
984)     proof of concept.</b> Bonus points if you <a
985)     href="https://stem.torproject.org/faq.html#how-do-i-get-started">get your
986)     hands wet by contributing patches</a>!
987)     </p>
988)     </li>
989) 

990)     <a id="txtorcon_use_txaio"></a>
991)     <li>
992)     <b>Convert txtorcon to use txaio</b>
993)     <br>
994)     Language: <i>Python, asyncio, Twisted</i>
995)     <br>
996)     Likely Mentors: <i>meejah</i>
997)     <br><br>
998)     <p>
999)     txtorcon is currently supports only Twisted users. Re-working txtorcon
1000)     to use the txaio library would allow users to choose between Twisted and
1001)     asyncio for the client code.
1002)     </p>
1003) 
1004)     <p>
1005)     This would involve fairly extensive refactoring to txtorcon, as it
1006)     currently makes heavy use of @inlineCallbacks which doesn't work with
1007)     txaio. A prospective student should be very familiar with event-based
1008)     programming in general, and be familiar with one of Twisted or asyncio.
1009)     See also: https://github.com/meejah/txtorcon/issues/135
1010)     </p>
1011)     </li>
1012) 
1013)     <a id="txtorcon_use_pytest"></a>
1014)     <li>
1015)     <b>Convert txtorcon to py.test</b>
1016)     <br>
1017)     Language: <i>Python, Twisted</i>
1018)     <br>
1019)     Likely Mentors: <i>meejah</i>
1020)     <br><br>
1021)     <p>
1022)     Currently txtorcon uses the built-in "unittest" module, as well as
1023)     Twisted's Deferred-respecting extensions on top. However, meejah has
1024)     found py.test's "fixture" approach to be much more powerful in other
1025)     situations.
1026)     </p>
1027) 
1028)     <p>
1029)     This project would be to port at least part of txtorcon's test-suite to
1030)     use py.test style tests and fixtures and evaluate: are the tests easier
1031)     to read? are there fewer lines of code? If so, the rest of the suite
1032)     should be ported and txtorcon switched over to use py.test exclusively.
1033)     </p>
1034) 
1035)     <p>
1036)     As some of txtorcon's tests aren't very well-written, this would take a
1037)     prospective student who is very strong in unit-testing knowledge. As
1038)     txtorcon is event-based, familiarity with that style of programming
1039)     (preferrably with Twisted) is ideal.
1040)     See also: https://github.com/meejah/txtorcon/issues/136
1041)     </p>
1042)     </li>
1043) 

1044)     <a id="coniks_in_messenger"></a>
1045)     <li>
1046)     <b>Implement and Integrate CONIKS for Tor Messenger</b>
1047)     <br>

1048)     Language: <i>C, JavaScript</i>

1049)     <br>

1050)     Likely Mentors: <i>Marcela (masomel), Arlo (arlolra)</i>

1051)     <br><br>

1052)     <p>
1053) CONIKS is an end-user key management and verification system for end-to-end
1054) secure communication services, which improves upon existing key management
1055) systems by providing both strong security and better usability using a model
1056) called key transparency. CONIKS does this by requiring providers to manage
1057) tamper-evident, publicly-auditable key directories, which contain mappings from
1058) usernames to public keys, on behalf of their users. This design makes it easier
1059) for users (both "default" users and power users) to establish trust since they
1060) don't have to worry about or even see keys, but users also don't have to
1061) trust the provider to be well-behaved because the CONIKS client can run as
1062) part of the secure messaging app and automatically check that the service
1063) provider doesn’t map spurious keys to their users' usernames, and it can
1064) verify that observed name-to-key mappings are consistent with what other
1065) clients in the system are seeing. Unlike existing key transparency solutions,
1066) CONIKS also provides strong privacy guarantees by employing cryptographic
1067) primitives for robust data obfuscation.
1068)     </p>
1069) 
1070)     <p>
1071) The CONIKS system design, protocols, and proof-of-concept are described in
1072) great detail in the <a
1073) href="https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper-melara.pdf">CONIKS
1074) research paper</a>, and basic reference implementations of a CONIKS key server
1075) and a CONIKS client are avialable on <a
1076) href="https://github.com/coniks-sys/coniks-ref-implementation">Github</a>.
1077)     </p>
1078) 
1079)     <p>
1080) This project has two main components: (1) designing and implementing a CONIKS
1081) key server tailored to Tor Messenger users, and (2) building a CONIKS client
1082) which integrates with the Tor Messenger client. One challenge the applicant
1083) will face is ensuring that the key server design is efficient and scalable for
1084) large volumes of users, concurrent traffic and guarantees this scalability even
1085) as Tor Messenger's user base grows. On the client side, the main challenges
1086) will be to focus on space efficiency as well as minimizing computational
1087) overhead when implementing the CONIKS consistency checks, and determining how
1088) to best communicate CONIKS consistency check results to users in the UI. Since
1089) Tor Messenger does not hand out online identities per se, as most online
1090) communication services do (like, say, Twitter, in which each user has a unique
1091) handle), the CONIKS key server for Tor Messenger will have to map usernames
1092) from third-party communication services to the encryption keys used in Tor
1093) Messenger. One additional important challenge that the applicant will have to
1094) help address is ensuring that each such third-party username remains unique in
1095) the Tor Messenger space and that such external, third-party identities are
1096) indeed controlled by the expected user of that third-party communication
1097) service.
1098)     </p>
1099) 
1100)     <p>
1101) Some design and implementation questions have been discussed in <a
1102) href="https://trac.torproject.org/projects/tor/ticket/17961">Ticket #17961</a>.
1103)     </p>
1104) 
1105)     <p>
1106) The applicant should have some familiarity with well-known crypto primitives
1107) and algorithms, as well as have a basic understanding of the key transparency
1108) model. Client side integration will require some basic use of JavaScript.
1109) Consider submitting a patch for <a
1110) href="https://github.com/arlolra/ctypes-otr/issues">one of the open key
1111) verification issues</a> as part of the application process.
1112)     </p>
1113)     </li>

1114) 
1115)     <a id="panopticlick"></a>
1116)     <li>
1117)     <b>Panopticlick</b>
1118)     <br>

1119)     Likely Mentors: <i>Georg (GeKo)</i>, <i>G&uuml;nes Acar</i>, <i>Nicolas (boklm)</i>

1120)     <p>
1121) 
1122) The <a href="https://panopticlick.eff.org">Panopticlick project by the EFF</a>
1123) revolutionized how people think about <a
1124) href="https://panopticlick.eff.org/browser-uniqueness.pdf">browser
1125) fingerprinting</a>, both by developing tests and metrics to measure browser
1126) fingerprintability, and by crowdsourcing the evaluation and contribution of
1127) individual browser features to overall fingerprintability.
1128) 
1129)     </p>
1130)     <p>
1131) 
1132) Unfortunately, the way Panopticlick is designed <a
1133) href="https://blog.torproject.org/blog/effs-panopticlick-and-torbutton">makes
1134) it difficult</a> to evaluate defenses to browser fingerprinting, especially
1135) for browsers with a relatively small userbase such as Tor Browser. This is
1136) because any approach we take to reduce fingerprinting automatically makes our
1137) users more distinct from the previous users who submitted their fingerprint
1138) data to the EFF. Indeed, it is also impossible to ever expect that users of
1139) one browser will ever be able to blend in with users of another browser
1140) (Chrome users will always be distinguishable from Firefox users for example,
1141) based on feature set alone).
1142) 
1143)    </p>
1144)    <p>
1145) 
1146) To address this, we would like to have <a
1147) href="https://trac.torproject.org/projects/tor/ticket/6119">our own
1148) fingerprint test suite</a> to evaluate the fingerprintability of each browser
1149) feature for users running a specific Tor Browser version. There are also <a
1150) href="https://trac.torproject.org/projects/tor/query?keywords=~tbb-fingerprinting">additional
1151) fingerprinting tests</a> we can add beyond those deployed by Panopticlick.
1152)    </p>
1153)    <p>
1154) 
1155) For this project, the student would develop a website that users can
1156) voluntarily visit to test and record their Tor Browser fingerprint.  The user
1157) should get feedback on how she performed and the test results should be
1158) available in a machine readable format (e.g. JSON), broken down by Tor Browser
1159) version.  In a second step one could think about adding more sophisticated
1160) tests or supporting other browser vendors that might want to test the
1161) uniformity amongst their userbase as well. Of course, results from each
1162) browser would also need to be broken down by both browser implementation and
1163) version, so that results would only reflect the population of that specific
1164) implementation.
1165) 
1166)     </p>
1167)     </li>
1168) 

1169)     <a id="stegotorus"></a>
1170)     <li>
1171)     <b>Make Stegotorus deployment ready</b>
1172)     <br>
1173)     Language: <i>C++</i>
1174)     <br>
1175)     Likely Mentors: <i>vmon</i>
1176)     <br><br>
1177)     <p>
1178)     <a
1179)     href="https://github.com/TheTorProject/stegotorus/tree/master/src">Stegotorus</a>
1180)     is a PT framework which streamline the development stealthier pluggable
1181)     transport. An HTTP pluggable transport is already implemented in Stegotorus
1182)     framework and can be used when encrypted payloads are throttled and only
1183)     ephemeral connections are tolerated.
1184)     </p>
1185) 
1186)     <p>
1187)     The majority of work on Stegotorus is done and it can be deployed with a relatively minor improvements including:
1188)     </p>
1189) 
1190)     <ul>
1191)       <li><b>#8098 A config file file for Stegotorus</b>
1192)         <p>
1193)         Stegotorus needs many configuration settings specially on the bridge
1194)         side. This include also the configuration required by each steg module.
1195)         Currently the configuration is fed to Stegotorus as command line
1196)         arguments but a file like torrc is needed so all tweaking can be read
1197)         from there.
1198)         </p>
1199) 
1200)         <p><i>
1201)         Current Status and work needed to be done: The code for reading the
1202)         config file is written by SRI but it is not yet used in the Stegotorus
1203)         to read the config.
1204)         </i></p>
1205)       </li>
1206) 
1207)       <li><b>#8101 Debugging the transparent proxy</b>
1208)         <p>
1209)         Stegotorus http module uses other websites payload to hide and serve
1210)         censored traffic. As such it needs to decide if the request is
1211)         genuinely to the auxiliary website, in that case becomes a transparent
1212)         proxy and serves the website content as requested, or if the request is
1213)         actually a request to serve censored material which should be delivered
1214)         to steg modules.
1215)         </p>
1216) 
1217)         <p><i>
1218)         Current Status: This is completely implemented. However, the transparent proxy sometimes crashes and need to be triaged, debugged and fixed.
1219)         </i></p>
1220)       </li>
1221) 
1222)       <li><b>#11337 refactoring the steg module code</b>
1223)         <p>
1224)         The http steg module code, although not essentials to the core of the
1225)         Stegotorus. needs some improvement and clean up. The solution is to
1226)         refactor the steg modules as children of FileStegMod.
1227)         </p>
1228) 
1229)         <p><i>
1230)         Current status and work needed to be done: This has already been done
1231)         but still needs testing and refactoring before it can be reliably merge
1232)         to the master branch.
1233)         </i></p>
1234)       </li>
1235) 
1236)       <li><b>#8089 Adding Elligator to Stegotorus handshake and test</b>
1237)         <p>
1238)         The current Stegotorus handshake is distinguishable from random byte
1239)         string, which can be used to flag and detect Stegotorus traffic
1240)         deterministically and need to be implemented similar to
1241)         ScrambleSuite. Also because the capacity of client to server channel
1242)         might be slim depending on the choice of steg module it is desirable
1243)         to be implemented using Elliptic curve crypto. Hence, Elligator
1244)         protocol is ideal solution for this situation. All we need is to replace Stegotorus handshake by Elligator.
1245)         </p>
1246) 
1247)         <p><i>
1248)         Current Status and work needed to be done: Elligator handshake code is
1249)         included in stegotorus code base, it is only needed to be called by
1250)         instead of the current handshake and be tested.
1251)         </i></p>
1252)       </li>
1253) 
1254)       <li><b>Make Stegotorus memory safe by using shared pointers</b>
1255)         <p>
1256)         Stegotorus has large code base and it is not written in a memory safe
1257)         languages. To facilitate its audit, we need to replace (almost all) use
1258)         of pointers to shared pointers.
1259)         </p>
1260) 
1261)         <p><i>
1262)         Current Status: No progress has not been done.
1263)         </i></p>
1264)       </li>
1265) 
1266)       <li><b>Security Audit and writing more unit test</b>
1267)         <p>
1268)         To be able to deploy Stegotorus for real world use we need to audit the
1269)         code and write more unit test covering new aspects of the Stegotorus
1270)         (new http transport, proxy server, Elligator handshake)
1271)         </p>
1272) 
1273)         <p><i>
1274)         Current Status: No progress has been done.
1275)         </i></p>
1276)       </li>
1277) 
1278)       <li><b>SRI branch merging</b>
1279)         <p>
1280)         Stegotorus has been forked from the initial development from SRI. Now
1281)         that SRI is hosting Stegotorus publicly it is desirable to merge the
1282)         two branches so we can benefit from both developments.
1283)         </p>
1284) 
1285)         <p><i>
1286)         Current Status: No progress has been done.
1287)         </i></p>
1288)       </li>
1289) 
1290)       <li><b>#8099 deterministic build</b>
1291)         <p>
1292)         To make deterministic build possible we need to build many of
1293)         Stegotorus dependency from scratch. Boost library is a a huge
1294)         dependency for Stegotorus to access the file system. As we are only
1295)         planning to deploy Stegotorus bridges on Linux machines we can simplify
1296)         such access without that dependency. By dropping such dependency, it
1297)         should be straight forward to have deterministic build for Stegotorus.
1298)         </p>
1299) 
1300)         <p><i>
1301)         Current Status: No progress has been done.
1302)         </i></p>
1303)       </li>
1304)     </ul>
1305)     </li>
1306) 

1307)     <a id="letsEncryptClient"></a>
1308)     <li>
1309)     <b>Expand the OS and Server Support of the Let's Encrypt Client</b>
1310)     <br>
1311)     Language: <i>Python, Bash</i>
1312)     <br>
1313)     Likely Mentors: <i>Brad Warren (bmw)</i>
1314)     <br><br>
1315)     <p>
1316)     <a href="https://letsencrypt.org/">Let's Encrypt</a> is a free and open
1317)     certificate authority that allows its users to setup HTTPS on their web
1318)     server in a matter of seconds. The project uses a new protocol called ACME
1319)     to automatically perform domain validation and certificate issuance.
1320)     </p>
1321) 
1322)     <p>
1323)     The Let's Encrypt client currently works on most Unix-like OSes and is
1324)     able to automatically set up HTTPS on many Apache configurations. The
1325)     purpose of this project is to expand Let's Encrypt support to new
1326)     systems.
1327)     </p>
1328) 
1329)     <p>
1330)     Potential targets include:
1331)     </p>
1332) 
1333)     <ul>
1334)       <li>Better OS X support including a port or Homebrew package</li>
1335)       <li>A Let's Encrypt client for Windows / IIS</li>
1336)       <li>Handling of more obscure Apache configurations</li>
1337)       <li>Automated HTTPS configuration for other web servers such as Nginx or lighttpd</li>
1338)       <li>Improved support people using shared hosting who are unable to use the full Let's Encrypt client on their server</li>
1339)     </ul>
1340)     </li>
1341) 

1342)     <a id="ahmiaSearch"></a>
1343)     <li>
1344)     <b>Ahmia - Hidden Service Search</b>
1345)     <br>
1346)     Language: <i>Python, Django</i>
1347)     <br>
1348)     Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i>
1349)     <br><br>
1350)     <p>
1351)     Ahmia is open-source search engine software for Tor hidden service deep
1352)     dark web sites. You can test the running search engine at ahmia.fi. For
1353)     more information see our <a
1354)     href="https://blog.torproject.org/category/tags/ahmiafi">blog post about
1355)     Ahmia's GSoC2014 development</a>.
1356)     </p>
1357) 
1358)     <p>
1359)     Ahmia is a working search engine that indexes, searches, and catalogs
1360)     content published on Tor Hidden Services. Furthermore, it is an environment
1361)     to share meaningful insights, statistics, insights, and news about the Tor
1362)     network itself. In this context, there is a lot of work to do.
1363)     </p>
1364) 
1365)     <p>
1366)     The Ahmia web service is written using the Django web framework. As a
1367)     result, the server-side language is Python. On the client-side, most of the
1368)     pages are plain HTML. There are some pages that require JavaScript, but the
1369)     search itself works without client-side JavaScript.
1370)     </p>
1371) 
1372)     <p>
1373)     There are several possible directions for this project, including...
1374)     </p>
1375) 
1376)     <ol>
1377)       <li>Improving the search results (very important)<br />
1378)         <ul>
1379)           <li>Tweaking search algorithms</li>

1380)           <li>Adjust Elasticsearch</li>

1381)           <li>Enrich the data that is used to rank the search results</li>
1382)         </ul>
1383)       </li>
1384)       <li>Improving UX and UI (very important)<br />
1385)         <ul>
1386)           <li>Showing relevant knowledge</li>
1387)           <li>Design the navigation and information architecture</li>
1388)           <li>HTML5, CSS and Django development</li>
1389)         </ul>
1390)       </li>
1391)       <li>Review code and infrastructure<br />
1392)         <ul>
1393)           <li>Review code and fix bugs</li>
1394)           <li>Writing Django test cases</li>
1395)           <li>Linux configurations, automatizations</li>
1396)         </ul>
1397)       </li>
1398)       <li>Gather statistics over time and publish them<br />
1399)         <ul>
1400)           <li>Gather different kind of stats about Hidden Services</li>
1401)           <li>Publish these stats using HTTP REST API</li>
1402)           <li>Using this API show meaningful tables, charts and visualizations</li>
1403)         </ul>
1404)       </li>
1405)     </ol>
1406)     </li>

1407) 
1408)     <a id="ipHijacking"></a>
1409)     <li>
1410)     <b>IP hijacking detection for the Tor Network</b>
1411)     <br>
1412)     Likely Mentors: <i>Aaron Gibson (aagbsn)</i>
1413)     <br><br>
1414)     <p>
1415)     <a href="https://en.wikipedia.org/wiki/IP_hijacking">IP hijacking</a>
1416)     occurs when a bad actor creates false routing information to redirect
1417)     Internet traffic to or through themselves. This activity is straightforward
1418)     to detect, because the Internet routing tables are public information, but
1419)     currently there are no public services that monitor the Tor network. The
1420)     Tor Network is a dynamic set of relays, so monitoring must be Tor-aware in
1421)     order to keep the set of monitored relays accurate. Additionally, consensus
1422)     archives and historical Internet routing table snapshots are publicly
1423)     available, and this analysis can be performed retroactively.
1424)     </p>
1425) 
1426)     <p>
1427)     The implications of IP hijacking are that Tor traffic can be redirected
1428)     through a network that an attacker controls, even if the attacker does not
1429)     normally have this capability - i.e. they are not in the network path. For
1430)     example, an adversary could hijack the prefix of a Tor Guard relay, in
1431)     order to learn who its clients are, or hijack a Tor Exit relay to tamper
1432)     with requests or name resolution.
1433)     </p>
1434) 
1435)     <p>
1436)     This project comprises building a service that compares network prefixes of
1437)     relays in the consensus with present and historic routing table snapshots
1438)     from looking glass services such as <a
1439)     href="http://routeviews.org">Routeviews</a>, or aggregators such as <a
1440)     href="https://bgpstream.caida.org">Caida BGPStream</a> and then issues
1441)     email alerts to the contact-info in the relay descriptor and a mailing
1442)     list. Network operators are responsive to route injections, and these
1443)     alerts can be used to notify network operators to take immediate action, as
1444)     well as collect information about the occurrence of these type of attacks.
1445)     </p>
1446)     </li>

1447) 
1448)     <a id="tailsServer"></a>
1449)     <li>
1450)     <b>Tails server: Self-hosted services behind Tails-powered Tor hidden services</b>
1451)     <br>
1452)     Likely Mentors: <i>anonym, George (asn)</i>
1453)     <p>Let's talk about group collaboration, communication and data sharing
1454)     infrastructure, such as chat servers, wikis, or file repositories.</p>
1455)     <p>Hosting such data and infrastructure <b>in the cloud</b> generally
1456)     implies to trust the service providers not to disclose content, usage or
1457)     users location information to third-parties. Hence, there are many threat
1458)     models in which cloud hosting is not suitable.</p>
1459)     <p>Tor partly answers the <b>users location</b> part; this is great, but
1460)     <b>content</b> is left unprotected.</p>
1461)     <p>There are two main ways to protect such content: either to encrypt it
1462)     client-side (<b>security by design</b>), or to avoid putting it into
1463)     untrusted hands in the first place.</p>
1464)     <p>Cloud solutions that offer security by design are rare and generally
1465)     not mature yet. The <b>Tails server</b> project is about exploring the
1466)     other side of the alternative: avoiding to put private data into
1467)     untrusted hands in the first place.</p>
1468)     <p>This is made possible thanks to Tor hidden services, that allow users
1469)     to offer location-hidden services, and make self-hosting possible in
1470)     many threat models. Self-hosting has its own lot of problems, however,
1471)     particularly in contexts where the physical security of the hosting
1472)     place is not assured. Combining Tor hidden services with Tails'
1473)     amnesia property and limited support for persistent encrypted data
1474)     allows to protect content, to a great degree, even in such contexts.</p>
1475)     <p>In short, setting up a new Tails server would be done by:</p>
1476) 
1477)     <ol style="list-style-type: decimal">
1478)       <li>Alice plugs a USB stick into a running desktop Tails system.</li>
1479)       <li>Alice uses a GUI to easily configure the needed services.</li>
1480)       <li>Alice unplugs the USB stick, that now contains encrypted services
1481)       configuration and data storage space.</li>
1482)       <li>Alice plugs that USB stick (and possibly a Tails Live CD) into the
1483)       old laptop that was dedicated to run Tails server.</li>
1484)       <li>Once booted, Alice enters the encryption passphrase either
1485)       directly using the keyboard or through a web interface listening on the
1486)       local network.</li>
1487)       <li>Then, Bob can use the configured services once he gets a hold on
1488)       the hidden service address. (The <b>petname system for Tor hidden
1489)       services</b> project would be very complementary to this one, by the
1490)       way.)</li>
1491)     </ol>
1492) 
1493)     <p>Tails server should content itself with hardware that is a bit old
1494)     (such as a PIII-450 laptop with 256MB of RAM) and/or half broken (e.g.
1495)     non-functional hard-disk, screen or keyboard).</p>
1496)     <p>The challenges behind this project are:</p>
1497) 
1498)     <ul>
1499)       <li>Design and write the services configuration GUI [keywords: edit
1500)       configuration files, upgrade between major Debian versions,
1501)       debconf].</li>
1502)       <li>How to create the hidden service key? [keywords: Vidalia, control
1503)       protocol].</li>
1504)       <li>Adapt the Tails boot process to allow switching to &quot;server
1505)       mode&quot; when appropriate.</li>
1506)       <li>Add support, to the Tails persistence setup process, for asking an
1507)       encryption passphrase without X, and possibly with a broken keyboard
1508)       and/or screen [keywords: local network, SSL/TLS?, certificate?].</li>
1509)     </ul>
1510) 
1511)     <p>This project can easily grow quite large, so the first task would
1512)     probably be to clarify what it would need to get an initial (minimal
1513)     but working) implementation ready to be shipped to users.</p>
1514)     <p>This project does not require to be an expert in one specific field,
1515)     but it requires to be experienced and at ease with a large scope of
1516)     software development tools, processes, and operating system knowledge.</p>
1517)     <p>Undertaking this project requires in-depth knowledge of Debian-like
1518)     systems (self-test: do the "dpkg conffile" and "debconf preseeding"
1519)     words sound new to your ear?); the Debian Live persistence system
1520)     being written in shell, being at ease with robust shell scripting is
1521)     a must; to end with, at least two pieces of software need to be
1522)     written from scratch (a GUI and a webapp): the preferred languages for
1523)     these tasks would be Python and Perl. Using Behaviour Driven
1524)     Development methods to convey expectations and acceptance criteria
1525)     would be most welcome.</p>
1526)     <p>For more information see https://tails.boum.org/todo/server_edition/</p>
1527)     </li>
1528) 

1529)     <a id="feedbackExtension"></a>
1530)     <li>
1531)     <b>Feedback Extension for Tor Browser</b>
1532)     <br>
1533)     Likely Mentors: <i>Nima (mrphs)</i>, <i>Will (willscott)</i>, <i>Sukhbir (sukhe)</i>
1534)     <p>
1535) 
1536)     Design and implement an extension for Tor Browser that can be used to gather
1537)     end-user UI/UX feedback on an opt-in basis. While the design and
1538)     implementation is left as an exercise for the applicant (and also serves as
1539)     the qualification task), examples of the information we are looking to gather
1540)     can include troubleshooting network connectivity issues, testing the various
1541)     pluggable transports, or gathering information about the network of the users.
1542)     </p>
1543) 
1544)     <p>
1545) 
1546)     Please propose the extension design in a way that the information is strictly
1547)     on an opt-in basis and scrubs any information that can be used to identify a
1548)     user, and also come up with a way to send the gathered information to a
1549)     central server, whether to an onion address (if the user has Tor running), or
1550)     otherwise. To start with, we are looking to gather only text as part of the
1551)     feedback process.
1552) 
1553)     </p>
1554)     </li>

1555) <!--
1556)     <a id=""></a>
1557)     <li>
1558)     <b></b>
1559)     <br>

1560)     Language: <i>Python</i>

1561)     <br>
1562)     Likely Mentors: <i>Damian (atagar)</i>

1563)     <br><br>

1564)     <p>
1565) 
1566)     </p>
1567) 
1568)     <p>
1569) 
1570)     </p>
1571)     </li>
1572) -->
1573) 

1574)     <li>
1575)     <b>Bring up new ideas!</b>

1576)     <br>

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

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

1579)     roadmap</a> for more ideas, or just try out Tor and Tor Browser,

1580)     and find out what you think needs fixing.

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

1582)     might also be short on developers.
1583)     </li>

1584) 

1585)     </ol>
1586)   </div>
1587)   <!-- END MAINCOL -->
1588)   <div id = "sidecol">
1589) #include "side.wmi"
1590) #include "info.wmi"
1591)   </div>
1592)   <!-- END SIDECOL -->
1593) </div>
1594) <!-- END CONTENT -->