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/c/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, dgoulet, asn, teor</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, GeKo</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>Moderate</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>Moderate</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>Moderate</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-flash-proxy">Flash Proxy</a></td>
204)         <td>Client Add-on</td>
205)         <td>Python, JavaScript, Go</td>

206)         <td>Light</td>

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

208)       </tr>

209) 

210)       <tr>

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

212)         <td>Simulator</td>

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

214)         <td>Moderate</td>

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

217) 

218)       <tr>
219)         <td><a href="#project-chutney">Chutney</a></td>
220)         <td>Simulator</td>
221)         <td>Python</td>
222)         <td>Light</td>

223)         <td>teor</td>

224)       </tr>
225) 

226)       <tr>

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

228)         <td>Library</td>
229)         <td>Python</td>

230)         <td>Heavy</td>

231)         <td>atagar</td>

232)       </tr>

233) 

234)       <tr>

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

238)         <td>Moderate</td>

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

241) 

242)       <tr>
243)         <td><a href="#project-metrics-lib">metrics-lib</a></td>
244)         <td>Library</td>
245)         <td>Java</td>
246)         <td>Moderate</td>
247)         <td>karsten, iwakeh</td>
248)       </tr>
249) 

250)       <tr>

251)         <td><a href="#project-metrics">Metrics</a></td>
252)         <td>Client Service</td>
253)         <td>Java</td>

254)         <td>Heavy</td>

255)         <td>karsten, iwakeh</td>

256)       </tr>

257) 

258)       <tr>

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

262)         <td>Light</td>

263)         <td>irl</td>

264)       </tr>

265) 

266)       <tr>

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

270)         <td>None</td>
271)         <td></td>

272)       </tr>

273) 

274)       <tr>

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

277)         <td>Java</td>

278)         <td>Heavy</td>
279)         <td>karsten, iwakeh</td>

280)       </tr>
281) 

282)       <tr>
283)         <td><a href="#project-exitmap">ExitMap</a></td>
284)         <td>Backend Service</td>
285)         <td>Python</td>

286)         <td>None</td>

287)         <td>phw</td>
288)       </tr>
289) 

290)       <tr>
291)         <td><a href="#project-doctor">DocTor</a></td>
292)         <td>Backend Service</td>
293)         <td>Python</td>

294)         <td>Light</td>

295)         <td>atagar</td>
296)       </tr>
297) 

298)       <tr>

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

302)         <td>None</td>

303)         <td>ilv</td>

304)       </tr>

305) 

306)       <tr>

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

309)         <td>Go</td>

310)         <td>None</td>

311)         <td>Arlo</td>

312)       </tr>

313) 

314)       <tr>

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

318)         <td>Light</td>

319)         <td>isis</td>

320)       </tr>

321) 

322)       <tr>

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

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

326)         <td>Heavy</td>

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

328)       </tr>
329) 

330)       <tr>
331)         <td><a href="#project-torps">TorPS</a></td>
332)         <td>Backend Service</td>
333)         <td>Python</td>

334)         <td>None</td>

335)         <td>Aaron Johnson</td>
336)       </tr>
337) 

338)       <tr>

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

342)         <td>None</td>

343)         <td>aagbsn</td>

344)       </tr>

345) 

346)       <tr>

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

349)         <td>Python</td>

350)         <td>Heavy</td>

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

352)       </tr>

353) 

354)       <tr>
355)         <td><a href="#project-collector">CollecTor</a></td>
356)         <td>Backend Service</td>
357)         <td>Java</td>

358)         <td>Moderate</td>

359)         <td>karsten, iwakeh</td>
360)       </tr>
361) 
362)       <tr>
363)         <td><a href="#project-exonerator">ExoneraTor</a></td>
364)         <td>Client Service</td>
365)         <td>Java</td>
366)         <td>Light</td>
367)         <td>karsten, iwakeh</td>
368)       </tr>

369) 
370)       <tr>
371)         <td><a href="#project-anonbib">Anonbib</a></td>
372)         <td>Website</td>
373)         <td>Python</td>
374)         <td>None</td>
375)         <td>arma, nickm</td>
376)       </tr>
377)     </table

378) 

379)     <sub>
380)     * Project is still in an alpha state.
381)     </sub>

382) 

383)     <br /><br />

384) 

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

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

388)     tracker</a>)</h3>

389) 

390)     <p>
391)     Central project, providing the core software for using and participating in
392)     the Tor network. Numerous people contribute to the project to varying
393)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
394)     </p>

395) 

396)     <p>
397)     <b>Project Ideas:</b><br />

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

399)     </p>

400) 

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

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

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

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

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

407)     <p>

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

410)     to work together out of
411)     the box. The modified copy of Firefox aims to resolve the

412)     privacy and security issues in mainline version.

413)     </p>

414) 

415)     <p>
416)     <b>Project Ideas:</b><br />

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

418)     <i><a href="#torBrowserCrashReport">Crash Reporter for Tor Browser</a></i><br />
419)     <i><a href="#fasterTorBrowser">Make Tor Browser Faster</a></i>

420)     </p>
421) 

422)     <a id="project-httpseverywhere"></a>
423)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
424)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
425)     href="https://trac.torproject.org/projects/tor/report/19">bug

426)     tracker</a>)</h3>

427) 

428)     <p>

429)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
430)     your communications with many major websites, making your browsing
431)     more secure.

432)     </p>

433) 

434)     <a id="project-nyx"></a>
435)     <h3><a href="https://www.atagar.com/arm/">Nyx</a> (<a
436)     href="https://gitweb.torproject.org/nyx.git">code</a>, <a

437)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FNyx&order=priority">bug

438)     tracker</a>)</h3>

439) 

440)     <p>

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

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

446)     </p>

447) 

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

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

451)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FOrbot&order=priority">bug

452)     tracker</a>)</h3>

453) 
454)     <p>

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

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

458)     </p>
459) 
460)     <a id="project-tails"></a>
461)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

464)     tracker</a>, <a href="https://tails.boum.org/doc/">documentation</a>, <a

465)     href="https://tails.boum.org/contribute/design/">design</a>, <a

466)     href="https://tails.boum.org/contribute/">contribute</a>)</h3>

467) 
468)     <p>
469)     The Amnesic Incognito Live System is a live CD/USB distribution
470)     preconfigured so that everything is safely routed through Tor and leaves no
471)     trace on the local system. This is a merger of the Amnesia and <a

472)     href="https://web.archive.org/web/20080512054152/http://anonymityanywhere.com/incognito/">Incognito</a> projects,

473)     and still under very active development.
474)     </p>
475) 

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

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

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

480) 
481)     <p>

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

484)     </p>
485) 

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

487)     <h3>Torsocks (<a

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

489)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FTorsocks&order=priority">bug

490)     tracker</a>)</h3>
491) 

492)     <p>

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

496)     </p>

497) 

498)     <a id="project-tormessenger"></a>
499)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger">Tor Messenger</a> (<a
500)     href="https://gitweb.torproject.org/tor-messenger-build.git">code</a>, <a

501)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Applications%2FTor+Messenger&order=priority">bug tracker</a>)</h3>

502) 
503)     <p>
504)     Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor.
505)     </p>
506) 

507)     <a id="project-torbirdy"></a>
508)     <h3>TorBirdy (<a

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

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

512) 

513)     <p>
514)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
515)     </p>

516) 

517)     <a id="project-flash-proxy"></a>
518)     <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a
519)     href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a

520)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Archived%2FFlashproxy&order=priority">bug

521)     tracker</a>)</h3>

522) 

523)     <p>
524)     Pluggable transport using proxies running in web browsers to defeat
525)     address-based blocking.
526)     </p>

527) 

528)     <a id="project-shadow"></a>

529)     <h3><a href="http://shadow.github.io/">Shadow</a> (<a

530)     href="https://github.com/shadow">code</a>, <a
531)     href="https://github.com/shadow/shadow/issues">bug
532)     tracker</a>)</h3>

533) 

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

538)     For another simulator, see <a

539)     href="https://crysp.uwaterloo.ca/software/exptor/">ExperimenTor</a>.

540)     </p>

541) 

542)     <a id="project-chutney"></a>
543)     <h3>Chutney (<a href="https://gitweb.torproject.org/chutney.git">code</a>,
544)     <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=Core+Tor%2FChutney&order=priority">bug
545)     tracker</a>)</h3>
546) 
547)     <p>
548)     Integration test suite that spawns a local tor network, checking the
549)     interactions of its components.
550)     </p>
551) 

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

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

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

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

556)     tracker</a>)</h3>

557) 

558)     <p>

559)     Python controller library for scripts and controller applications using
560)     Tor.

561)     </p>

562) 

563)     <p>
564)     <b>Project Ideas:</b><br />
565)     <i><a href="#stemDescriptors">Stem Descriptors</a></i>
566)     </p>
567) 

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

569)     <h3><a href="https://txtorcon.readthedocs.io/en/latest/">Txtorcon</a> (<a

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

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

572) 

573)     <p>
574)     Twisted-based asynchronous Tor control protocol implementation. Includes
575)     unit-tests, examples, state-tracking code and configuration abstraction.
576)     Used by OONI and APAF.
577)     </p>

578) 

579)     <a id="project-metrics-lib"></a>
580)     <h3>metrics-lib
581)     (<a href="https://gitweb.torproject.org/metrics-lib.git">code</a>,
582)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2Fmetrics-lib&order=priority">bug tracker</a>)</h3>
583) 
584)     <p>metrics-lib is a Java library that processes Tor network data
585)     provided by <a href="#project-collector">CollecTor</a> or from other
586)     sources.</p>
587) 

588)     <a id="project-metrics"></a>

589)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (<a

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

591) 

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

595)     Karsten Loesing.

596)     </p>

597) 

598)     <a id="project-atlas"></a>
599)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
600)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

601) 

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

605)     their past usage.

606)     </p>

607) 

608)     <p>

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

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

612)     codebase</a> for which was written in PHP, and rewritten by students from

613)     Wesleyan as Django. If you dig into this space then also check out <a
614)     href="http://globe.rndm.de/">Globe</a>, another similar site that's since
615)     been discontinued.

616)     </p>
617) 

618)     <a id="project-compass"></a>
619)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
620)     href="https://gitweb.torproject.org/compass.git">code</a>, <a

621)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FCompass&order=priority">bug

622)     tracker</a>)</h3>

623) 

624)     <p>
625)     Compass is a web and command line application that filters and
626)     aggregates the Tor relays based on various attributes.
627)     </p>

628) 
629)     <a id="project-onionoo"></a>

630)     <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a
631)     href="https://gitweb.torproject.org/onionoo.git">code</a>,

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

633) 
634)     <p>
635)     Onionoo is a JSON based protocol to learn information about currently
636)     running Tor relays and bridges.
637)     </p>
638) 

639)     <a id="project-exitmap"></a>
640)     <h3><a href="http://www.cs.kau.se/philwint/spoiled_onions/">ExitMap</a> (<a
641)     href="https://github.com/NullHypothesis/exitmap">code</a>, <a
642)     href="https://github.com/NullHypothesis/exitmap/issues">bug tracker</a>)</h3>
643) 
644)     <p>

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

648)     Onions</a> research paper.
649)     </p>
650) 

651)     <a id="project-doctor"></a>
652)     <h3>DocTor (<a
653)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a

654)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FDocTor&order=priority">bug

655)     tracker</a>)</h3>
656) 
657)     <p>
658)     DocTor is a notification service that monitors newly published descriptor
659)     information for issues. This is primarily a service to help the tor
660)     directory authority operators, but it also checks for a handful of other
661)     issues like sybil attacks.
662)     </p>
663) 

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

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

666)     href="https://gitweb.torproject.org/weather.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=Metrics%2FTor+Weather&order=priority">bug

668)     tracker</a>)</h3>

669) 

670)     <p>
671)     Provides automatic notification to subscribed relay operators when their
672)     relay's unreachable. This underwent a rewrite by the <a
673)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
674)     in early 2011.
675)     </p>

676) 

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

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

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

680)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FGetTor&order=priority">bug

681)     tracker</a>)</h3>

682) 

683)     <p>
684)     E-mail autoresponder providing Tor's packages over SMTP. This has been
685)     relatively unchanged for quite a while.
686)     </p>

687) 

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

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

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

691)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FTor+Check&order=priority">bug

692)     tracker</a>)</h3>

693) 

694)     <p>

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

696)     </p>

697) 

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

699)     <h3><a href="https://pythonhosted.org/bridgedb/">BridgeDB</a> (<a

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

701)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Obfuscation%2FBridgeDB&order=priority">bug

702)     tracker</a>)</h3>

703) 

704)     <p>
705)     Backend bridge distributor, handling the various pools they're distributed
706)     in. This was actively developed until Fall of 2010.
707)     </p>

708) 
709)     <a id="project-ooni-probe"></a>

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

711)     href="https://github.com/TheTorProject/ooni-probe/">code</a>, <a
712)     href="https://github.com/TheTorProject/ooni-probe/issues">bug

713)     tracker</a>)</h3>
714) 
715)     <p>
716)     Censorship scanner, checking your local connection for blocked or modified
717)     content.
718)     </p>
719) 

720)     <a id="project-torps"></a>
721)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
722) 
723)     <p>
724)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
725)     path selection in Tor. It chooses circuits and assigns user streams to
726)     those circuits in the same way that Tor does. TorPS is fast enough to
727)     perform thousands of simulations over periods of months.
728)     </p>
729) 

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

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

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

733)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FTorflow&order=priority">bug

734)     tracker</a>)</h3>

735) 

736)     <p>
737)     Library and collection of services for actively monitoring the Tor network.
738)     These include the Bandwidth Scanners (measuring throughput of relays) and
739)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
740)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
741)     months later. Both have been under active use since then, but development
742)     has stopped.
743)     </p>

744) 
745)     <a id="project-tor2web"></a>
746)     <h3><a

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

748)     href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3>
749) 
750)     <p>
751)     Tor2web allows Internet users to browse websites running in <a
752)     href="<page docs/hidden-services>">Tor hidden services</a>. It trades
753)     user anonymity for usability by allowing anonymous content to be
754)     distributed to non-anonymous users.
755)     </p>
756) 

757)     <a id="project-collector"></a>
758)     <h3><a href="https://collector.torproject.org/">CollecTor</a>
759)     (<a href="https://gitweb.torproject.org/collector.git">code</a>,
760)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FCollecTor&order=priority">bug tracker</a>)</h3>
761) 
762)     <p>CollecTor is the Tor network data archive that powers other
763)     services like <a href="#project-metrics">Metrics</a> and
764)     <a href="#project-onionoo">Onionoo</a>.</p>
765) 
766)     <a id="project-exonerator"></a>
767)     <h3><a href="https://exonerator.torproject.org/">ExoneraTor</a>
768)     (<a href="https://gitweb.torproject.org/exonerator.git">code</a>,
769)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FExoneraTor&order=priority">bug tracker</a>)</h3>
770) 
771)     <p>ExoneraTor is a service that answers the question whether there was
772)     a Tor relay running on a given IP address on a given date.</p>
773) 

774)     <a id="project-anonbib"></a>
775)     <h3><a
776)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
777)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
778) 
779)     <p>
780)     Anonbib is a list of important papers in the field of anonymity. It's
781)     also a set of scripts to generate the website from Latex (bibtex). If
782)     we're missing any important papers, please let us know!
783)     </p>
784) 

785)     <a id="Coding"></a>
786)     <a id="Summer"></a>

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

788) 

789)     <p>

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

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

797)     </p>

798) 

799)     <ol>

800) 

801)     <a id="improveHiddenServices"></a>
802)     <li>
803)     <b>Help improve Tor hidden services</b>
804)     <br>

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

806)     <br>

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

808)     <br><br>

809)     <p>

810) The hidden services team is busy implementing <a
811) href="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt">proposal
812) 224</a> but we are always open to mentoring fun and exciting hidden
813) service projects.

814)     </p>
815) 
816)     <p>

817) In the past, we've mentored a wide variety of projects related to hidden
818) services, ranging from <a
819) href="https://lists.torproject.org/pipermail/tor-dev/2016-April/010832.html">onion
820) search engines</a>, <a
821) href="https://lists.torproject.org/pipermail/tor-talk/2015-May/037966.html">to
822) scaling techniques for hidden services</a>,
823) and also various approaches
824) of making onion services more <a
825) href="https://lists.torproject.org/pipermail/tor-dev/2012-June/003588.html">usable</a>
826) <a href="https://lists.torproject.org/pipermail/tor-dev/2015-May/008826.html">by
827) common people</a>.

828)     </p>
829) 
830)     <p>

831) Let us know if you have a project you would like to work on, or check
832) our proposals and technical documents for <a
833) href="https://lists.torproject.org/pipermail/tor-dev/2016-October/011514.html">various</a>
834) ideas.

835)     </p>
836)     </li>
837) 

838)     <a id="feedbackExtension"></a>
839)     <li>
840)     <b>Feedback Extension for Tor Browser</b>
841)     <br>
842)     Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
843)     <p>
844)     Design and implement an extension for Tor Browser that can be used to gather
845)     end-user UI/UX feedback on an opt-in basis. While the design and
846)     implementation is left as an exercise for the applicant (and also serves as
847)     the qualification task), examples of the information we are looking to gather
848)     can include troubleshooting network connectivity issues, testing the various
849)     pluggable transports, or gathering information about the network of the users.
850)     </p>
851) 
852)     <p>
853)     Please propose the extension design in a way that the information is strictly
854)     on an opt-in basis and scrubs any information that can be used to identify a
855)     user, and also come up with a way to send the gathered information to a
856)     central server, whether to an onion address (if the user has Tor running), or
857)     otherwise. To start with, we are looking to gather only text as part of the
858)     feedback process.
859)     </p>
860)     </li>
861) 
862)     <a id="torBrowserCrashReport"></a>
863)     <li>
864)     <b>Crash Reporter for Tor Browser</b>
865)     <br>
866)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
867)     <p>
868)     Currently Tor Browser disables the Crash Reporter. We would like to
869)     build it reproducible, enable it, and configure it to report crashes
870)     containing non-detailed and impersonal information to Tor, on a .onion
871)     submission platform that would allow us to view and explore the
872)     crashes.
873)     </p>
874) 
875)     <p>
876)     The project will entail enabling the Crash Report on Tor Browser and
877)     creating a backend to receive reports from it. Once created, the crash
878)     reporter data will be analyzed and modified to fit Tor's requirements
879)     for personal data collection. As time permits, we will update the
880)     build system to ensure the crash reporter is built reproducibly and
881)     add data analysis tools for the crash report database to visualize top
882)     crashers and similar statistics.
883)     </p>
884)     </li>
885) 
886)     <a id="fasterTorBrowser"></a>
887)     <li>
888)     <b>Make Tor Browser Faster</b>
889)     <br>
890)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
891)     <p>
892)     This project will enable and take advantage of HTTP/2, the Alt-Srv
893)     header, and tor's new single hop .onion mode to enable websites to
894)     transparently move their traffic to a .onion address. In addition to
895)     improvements in security, we will benchmark page load and paint times
896)     under normal HTTP/1.1, HTTP/2, and when taking advantage of features
897)     such as Server Push.
898)     </p>
899)     </li>
900) 

901)     <a id="stemDescriptors"></a>
902)     <li>
903)     <b>Stem Descriptors</b>
904)     <br>
905)     Language: <i>Python</i>
906)     <br>
907)     Likely Mentors: <i>Damian Johnson (atagar)</i>
908)     <p>
909)     <a href="https://stem.torproject.org/">Stem</a> is a Python library for working with tor. With it you can build applications on tor as well as learn information about the relay network. This project concerns this second capability.
910)     </p>
911) 
912)     <p>
913)     Information about relays are published hourly in documents called <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">descriptors</a>. With Stem you can download, parse, and validate all kinds of descriptor documents.
914)     </p>
915) 
916)     <p>
917)     Ideas welcome! You're encouraged to brainstorm improvements we can make to this space but here's a few to get you started...
918)     </p>
919) 
920)   <ul>
921)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/11045">Validate signatures in the consensus</a></b>. Stem has the ability to validate cryptographic signatures in several descriptor types but not the consensus.</p></li>
922)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/21086">Migrate from pycrypto to a supported library</a></b>. Stem presently uses pycrypto for signature validation but it's no longer maintained. We should evaluate options and move to whatever whavever the cool kids are using nowadays.</p></li>
923)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/18856">Retrieve descriptors over tor's ORPort</a></b>. Tor relays commonly provide two ports, an <b>ORPort</b> which is used by clients and a <b>DirPort</b> which is obsolete nowadays but in the past was used by tor to download descriptors. Stem still uses tor's DirPort to retrieve descriptors, but it would be neat if we could download from the ORPort instead.</p>
924)       <p>This requires implementing part of tor's communication protocol. Depending how complicated this is it might be neat to expand this task to allow the full construction of circuits, allowing client usage of tor without the C executable. Keep in mind though that this later bit hasn't been investigated and might be a pipe dream. ;P</p></li>
925)     <li><p><b>Improve performance of reading descriptors</b>. Stem <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#are-there-any-other-parsing-libraries">isn't the only descriptor parsing library</a> and sadly is the slowest. Tricks like lazy loading have substantially improved our performance but no doubt a dedicated effort to profile Stem would find more low hanging fruit.</p></li>
926)   </ul>
927) 
928) 
929)     <p>
930)     <b>As part of applying for this project please get your hands wet with the codebase by contributing some patches for <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b>
931)     </p>
932)     </li>
933) 

934)     <a id="stegotorus"></a>
935)     <li>
936)     <b>Make Stegotorus deployment ready</b>
937)     <br>
938)     Language: <i>C++</i>
939)     <br>
940)     Likely Mentors: <i>vmon</i>
941)     <br><br>
942)     <p>
943)     <a
944)     href="https://github.com/TheTorProject/stegotorus/tree/master/src">Stegotorus</a>
945)     is a PT framework which streamline the development stealthier pluggable
946)     transport. An HTTP pluggable transport is already implemented in Stegotorus
947)     framework and can be used when encrypted payloads are throttled and only
948)     ephemeral connections are tolerated.
949)     </p>
950) 
951)     <p>
952)     The majority of work on Stegotorus is done and it can be deployed with a relatively minor improvements including:
953)     </p>
954) 
955)     <ul>
956)       <li><b>#8098 A config file file for Stegotorus</b>
957)         <p>
958)         Stegotorus needs many configuration settings specially on the bridge
959)         side. This include also the configuration required by each steg module.
960)         Currently the configuration is fed to Stegotorus as command line
961)         arguments but a file like torrc is needed so all tweaking can be read
962)         from there.
963)         </p>
964) 
965)         <p><i>
966)         Current Status and work needed to be done: The code for reading the
967)         config file is written by SRI but it is not yet used in the Stegotorus
968)         to read the config.
969)         </i></p>
970)       </li>
971) 
972)       <li><b>#8101 Debugging the transparent proxy</b>
973)         <p>
974)         Stegotorus http module uses other websites payload to hide and serve
975)         censored traffic. As such it needs to decide if the request is
976)         genuinely to the auxiliary website, in that case becomes a transparent
977)         proxy and serves the website content as requested, or if the request is
978)         actually a request to serve censored material which should be delivered
979)         to steg modules.
980)         </p>
981) 
982)         <p><i>
983)         Current Status: This is completely implemented. However, the transparent proxy sometimes crashes and need to be triaged, debugged and fixed.
984)         </i></p>
985)       </li>
986) 
987)       <li><b>#11337 refactoring the steg module code</b>
988)         <p>
989)         The http steg module code, although not essentials to the core of the
990)         Stegotorus. needs some improvement and clean up. The solution is to
991)         refactor the steg modules as children of FileStegMod.
992)         </p>
993) 
994)         <p><i>
995)         Current status and work needed to be done: This has already been done
996)         but still needs testing and refactoring before it can be reliably merge
997)         to the master branch.
998)         </i></p>
999)       </li>
1000) 
1001)       <li><b>#8089 Adding Elligator to Stegotorus handshake and test</b>
1002)         <p>
1003)         The current Stegotorus handshake is distinguishable from random byte
1004)         string, which can be used to flag and detect Stegotorus traffic
1005)         deterministically and need to be implemented similar to
1006)         ScrambleSuite. Also because the capacity of client to server channel
1007)         might be slim depending on the choice of steg module it is desirable
1008)         to be implemented using Elliptic curve crypto. Hence, Elligator
1009)         protocol is ideal solution for this situation. All we need is to replace Stegotorus handshake by Elligator.
1010)         </p>
1011) 
1012)         <p><i>
1013)         Current Status and work needed to be done: Elligator handshake code is
1014)         included in stegotorus code base, it is only needed to be called by
1015)         instead of the current handshake and be tested.
1016)         </i></p>
1017)       </li>
1018) 
1019)       <li><b>Make Stegotorus memory safe by using shared pointers</b>
1020)         <p>
1021)         Stegotorus has large code base and it is not written in a memory safe
1022)         languages. To facilitate its audit, we need to replace (almost all) use
1023)         of pointers to shared pointers.
1024)         </p>
1025) 
1026)         <p><i>
1027)         Current Status: No progress has not been done.
1028)         </i></p>
1029)       </li>
1030) 
1031)       <li><b>Security Audit and writing more unit test</b>
1032)         <p>
1033)         To be able to deploy Stegotorus for real world use we need to audit the
1034)         code and write more unit test covering new aspects of the Stegotorus
1035)         (new http transport, proxy server, Elligator handshake)
1036)         </p>
1037) 
1038)         <p><i>
1039)         Current Status: No progress has been done.
1040)         </i></p>
1041)       </li>
1042) 
1043)       <li><b>SRI branch merging</b>
1044)         <p>
1045)         Stegotorus has been forked from the initial development from SRI. Now
1046)         that SRI is hosting Stegotorus publicly it is desirable to merge the
1047)         two branches so we can benefit from both developments.
1048)         </p>
1049) 
1050)         <p><i>
1051)         Current Status: No progress has been done.
1052)         </i></p>
1053)       </li>
1054) 
1055)       <li><b>#8099 deterministic build</b>
1056)         <p>
1057)         To make deterministic build possible we need to build many of
1058)         Stegotorus dependency from scratch. Boost library is a a huge
1059)         dependency for Stegotorus to access the file system. As we are only
1060)         planning to deploy Stegotorus bridges on Linux machines we can simplify
1061)         such access without that dependency. By dropping such dependency, it
1062)         should be straight forward to have deterministic build for Stegotorus.
1063)         </p>
1064) 
1065)         <p><i>
1066)         Current Status: No progress has been done.
1067)         </i></p>
1068)       </li>
1069)     </ul>
1070)     </li>
1071) 

1072)     <a id="letsEncryptClient"></a>
1073)     <li>
1074)     <b>Expand the OS and Server Support of the Let's Encrypt Client</b>
1075)     <br>
1076)     Language: <i>Python, Bash</i>
1077)     <br>
1078)     Likely Mentors: <i>Brad Warren (bmw)</i>
1079)     <br><br>
1080)     <p>
1081)     <a href="https://letsencrypt.org/">Let's Encrypt</a> is a free and open
1082)     certificate authority that allows its users to setup HTTPS on their web
1083)     server in a matter of seconds. The project uses a new protocol called ACME
1084)     to automatically perform domain validation and certificate issuance.
1085)     </p>
1086) 
1087)     <p>
1088)     The Let's Encrypt client currently works on most Unix-like OSes and is
1089)     able to automatically set up HTTPS on many Apache configurations. The
1090)     purpose of this project is to expand Let's Encrypt support to new
1091)     systems.
1092)     </p>
1093) 
1094)     <p>
1095)     Potential targets include:
1096)     </p>
1097) 
1098)     <ul>
1099)       <li>Better OS X support including a port or Homebrew package</li>
1100)       <li>A Let's Encrypt client for Windows / IIS</li>
1101)       <li>Handling of more obscure Apache configurations</li>
1102)       <li>Automated HTTPS configuration for other web servers such as Nginx or lighttpd</li>
1103)       <li>Improved support people using shared hosting who are unable to use the full Let's Encrypt client on their server</li>
1104)     </ul>
1105)     </li>
1106) 

1107)     <a id="ipHijacking"></a>
1108)     <li>
1109)     <b>IP hijacking detection for the Tor Network</b>
1110)     <br>
1111)     Likely Mentors: <i>Aaron Gibson (aagbsn)</i>
1112)     <br><br>
1113)     <p>
1114)     <a href="https://en.wikipedia.org/wiki/IP_hijacking">IP hijacking</a>
1115)     occurs when a bad actor creates false routing information to redirect
1116)     Internet traffic to or through themselves. This activity is straightforward
1117)     to detect, because the Internet routing tables are public information, but
1118)     currently there are no public services that monitor the Tor network. The
1119)     Tor Network is a dynamic set of relays, so monitoring must be Tor-aware in
1120)     order to keep the set of monitored relays accurate. Additionally, consensus
1121)     archives and historical Internet routing table snapshots are publicly
1122)     available, and this analysis can be performed retroactively.
1123)     </p>
1124) 
1125)     <p>
1126)     The implications of IP hijacking are that Tor traffic can be redirected
1127)     through a network that an attacker controls, even if the attacker does not
1128)     normally have this capability - i.e. they are not in the network path. For
1129)     example, an adversary could hijack the prefix of a Tor Guard relay, in
1130)     order to learn who its clients are, or hijack a Tor Exit relay to tamper
1131)     with requests or name resolution.
1132)     </p>
1133) 
1134)     <p>
1135)     This project comprises building a service that compares network prefixes of
1136)     relays in the consensus with present and historic routing table snapshots
1137)     from looking glass services such as <a
1138)     href="http://routeviews.org">Routeviews</a>, or aggregators such as <a
1139)     href="https://bgpstream.caida.org">Caida BGPStream</a> and then issues
1140)     email alerts to the contact-info in the relay descriptor and a mailing
1141)     list. Network operators are responsive to route injections, and these
1142)     alerts can be used to notify network operators to take immediate action, as
1143)     well as collect information about the occurrence of these type of attacks.
1144)     </p>
1145)     </li>

1146) 

1147)     <a id="ahmiaSearch"></a>
1148)     <li>
1149)     <b>Ahmia - Hidden Service Search</b>
1150)     <br>
1151)     Language: <i>Python, Django</i>
1152)     <br>
1153)     Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i>
1154)     <p>
1155)     Ahmia is open-source search engine software for Tor hidden service deep
1156)     dark web sites. You can test the running search engine at ahmia.fi. For
1157)     more information see our <a
1158)     href="https://blog.torproject.org/category/tags/ahmiafi">blog post about
1159)     Ahmia's GSoC2014 development</a>.
1160)     </p>
1161) 
1162)     <p>
1163)     Ahmia is a working search engine that indexes, searches, and catalogs
1164)     content published on Tor Hidden Services. Furthermore, it is an environment
1165)     to share meaningful insights, statistics, insights, and news about the Tor
1166)     network itself. In this context, there is a lot of work to do.
1167)     </p>
1168) 
1169)     <p>
1170)     The Ahmia web service is written using the Django web framework. As a
1171)     result, the server-side language is Python. On the client-side, most of the
1172)     pages are plain HTML. There are some pages that require JavaScript, but the
1173)     search itself works without client-side JavaScript.
1174)     </p>
1175) 
1176)     <p>
1177)     There are several possible directions for this project, including...
1178)     </p>
1179) 
1180)     <ol>
1181)       <li>Automate blacklisting (very important)<br />
1182)         <ul>
1183)           <li>Fetch a list of child abuse media sites</li>
1184)           <li>Remove these sites from the search results</li>
1185)         </ul>
1186)       </li>
1187)       <li>Add hidden services funtion (very important)<br />
1188)         <ul>
1189)           <li>You can add onions using HTML form</li>
1190)           <li>Call the crawler immidiately when a new site is added</li>
1191)         </ul>
1192)       </li>
1193)       <li>Elasticsearch<br />
1194)         <ul>
1195)           <li>Must be updated to 5.X.X sooner or later</li>
1196)           <li>Adjust the settings</li>
1197)           <li>Automatically remove data older than, for instance, 90 days</li>
1198)         </ul>
1199)       </li>
1200)       <li>Maintainance<br />
1201)         <ul>
1202)           <li>Update all software dependencies</li>
1203)           <li>Automate crash recovery for Tor, Elasticsearch and crawler</li>
1204)         </ul>
1205)       </li>
1206)     </ol>
1207)     </li>
1208) 

1209) <!--
1210)     <a id=""></a>
1211)     <li>
1212)     <b></b>
1213)     <br>

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

1215)     <br>
1216)     Likely Mentors: <i>Damian (atagar)</i>

1217)     <br><br>

1218)     <p>
1219) 
1220)     </p>
1221) 
1222)     <p>
1223) 
1224)     </p>
1225)     </li>
1226) -->
1227) 

1228)     <li>
1229)     <b>Bring up new ideas!</b>

1230)     <br>

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

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

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

1234)     and find out what you think needs fixing.

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

1236)     might also be short on developers.
1237)     </li>

1238) 

1239)     </ol>
1240)   </div>
1241)   <!-- END MAINCOL -->
1242)   <div id = "sidecol">
1243) #include "side.wmi"
1244) #include "info.wmi"
1245)   </div>
1246)   <!-- END SIDECOL -->
1247) </div>
1248) <!-- END CONTENT -->