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 onion

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 changes into articles for our blog and <a
59)     href="https://newsletter.torproject.org/">newsletter</a>.</li>

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

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

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

65)     <a

66)     href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy/">Howcast</a>,
67)     and <a href="http://www.youtube.com/c/thetorproject">YouTube</a>.</li>

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

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

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

76)     </ol>

77) 

78)     <a id="Projects"></a>
79)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

80) 

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

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

88)     </p>

89) 

90)     <p>
91)     For a presentation summarizing many of these projects see...
92)     </p>
93) 
94)     <div id="ecosystem_presentation">

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

96)     </div>
97) 
98)     <br /></br />
99) 

100)     <table id="projects">
101)       <tr>
102)         <th>Name</th>
103)         <th>Category</th>
104)         <th>Language</th>
105)         <th>Activity</th>
106)         <th>Contributors</th>
107)       </tr>

108) 

109)       <tr>
110)         <td><a href="#project-tor">Tor</a></td>
111)         <td>Core</td>
112)         <td>C</td>
113)         <td>Heavy</td>

114)         <td>nickm, athena, arma, dgoulet, asn, teor</td>

115)       </tr>

116) 

117)       <tr>

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

119)         <td>Bundle</td>

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

121)         <td>Heavy</td>

122)         <td>mikeperry, Pearl Crescent, GeKo</td>

123)       </tr>
124) 

125)       <tr>

126)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
127)         <td>Browser Add-on</td>
128)         <td>Javascript</td>

129)         <td>Moderate</td>

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

131)       </tr>

132) 

133)       <tr>

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

135)         <td>User Interface</td>
136)         <td>Python, Curses</td>

137)         <td>Moderate</td>

138)         <td>atagar</td>
139)       </tr>

140) 

141)       <tr>

142)         <td><a href="#project-orbot">Orbot</a></td>
143)         <td>User Interface</td>
144)         <td>Java</td>

145)         <td>Moderate</td>

146)         <td>n8fr8</td>

147)       </tr>

148) 

149)       <tr>

150)         <td><a href="#project-tails">Tails</a></td>
151)         <td>OS image</td>
152)         <td>Sys Admin</td>
153)         <td>Heavy</td>
154)         <td><a href="https://tails.boum.org/">#tails</a></td>

155)       </tr>

156) 

157)       <tr>

158)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
159)         <td>OS image</td>
160)         <td>Sys Admin</td>

161)         <td>Light</td>

162)         <td>blueness</td>
163)       </tr>
164) 

165)       <tr>

166)         <td><a href="#project-torsocks">Torsocks</a></td>
167)         <td>Usability</td>
168)         <td>C</td>

169)         <td>Light</td>

170)         <td>David Goulet</td>

171)       </tr>
172) 

173)       <tr>
174)         <td><a href="#project-tormessenger">Tor Messenger</a></td>
175)         <td>Bundle</td>
176)         <td>JavaScript, XUL, Scripting</td>
177)         <td>Heavy</td>
178)         <td>arlolra, boklm, sukhe</td>
179)       </tr>
180) 

181)       <tr>

182)         <td><a href="#project-torbirdy">TorBirdy</a></td>
183)         <td>Browser Add-on</td>
184)         <td>JavaScript</td>

185)         <td>Light</td>
186)         <td>sukhe</td>

187)       </tr>

188) 

189)       <tr>

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

191)         <td>Simulator</td>

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

193)         <td>Moderate</td>

194)         <td>robgjansen</td>
195)       </tr>

196) 

197)       <tr>
198)         <td><a href="#project-chutney">Chutney</a></td>
199)         <td>Simulator</td>
200)         <td>Python</td>
201)         <td>Light</td>

202)         <td>teor</td>

203)       </tr>
204) 

205)       <tr>

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

207)         <td>Library</td>
208)         <td>Python</td>

209)         <td>Heavy</td>

210)         <td>atagar</td>

211)       </tr>

212) 

213)       <tr>

214)         <td><a href="#project-txtorcon">Txtorcon</a></td>
215)         <td>Library</td>
216)         <td>Python, Twisted</td>

217)         <td>Moderate</td>

218)         <td>meejah</td>
219)       </tr>

220) 

221)       <tr>
222)         <td><a href="#project-metrics-lib">metrics-lib</a></td>
223)         <td>Library</td>
224)         <td>Java</td>
225)         <td>Moderate</td>
226)         <td>karsten, iwakeh</td>
227)       </tr>
228) 

229)       <tr>

230)         <td><a href="#project-metrics">Metrics</a></td>
231)         <td>Client Service</td>
232)         <td>Java</td>

233)         <td>Heavy</td>

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

235)       </tr>

236) 

237)       <tr>

238)         <td><a href="#project-atlas">Relay Search</a></td>

239)         <td>Client Service</td>
240)         <td>JavaScript</td>

241)         <td>Light</td>

242)         <td>irl</td>

243)       </tr>

244) 

245)       <tr>

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

248)         <td>Java</td>

249)         <td>Heavy</td>
250)         <td>karsten, iwakeh</td>

251)       </tr>
252) 

253)       <tr>
254)         <td><a href="#project-exitmap">ExitMap</a></td>
255)         <td>Backend Service</td>
256)         <td>Python</td>

257)         <td>None</td>

258)         <td>phw</td>
259)       </tr>
260) 

261)       <tr>
262)         <td><a href="#project-doctor">DocTor</a></td>
263)         <td>Backend Service</td>
264)         <td>Python</td>

265)         <td>Light</td>

266)         <td>atagar</td>
267)       </tr>
268) 

269)       <tr>

270)         <td><a href="#project-gettor">GetTor</a></td>
271)         <td>Client Service</td>
272)         <td>Python</td>

273)         <td>None</td>

274)         <td>ilv</td>

275)       </tr>

276) 

277)       <tr>

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

280)         <td>Go</td>

281)         <td>None</td>

282)         <td>Arlo</td>

283)       </tr>

284) 

285)       <tr>

286)         <td><a href="#project-bridgedb">BridgeDB</a></td>
287)         <td>Backend Service</td>
288)         <td>Python</td>

289)         <td>Light</td>

290)         <td>isis</td>

291)       </tr>

292) 

293)       <tr>

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

295)         <td>Scanner</td>
296)         <td>Python</td>

297)         <td>Heavy</td>

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

299)       </tr>
300) 

301)       <tr>
302)         <td><a href="#project-torps">TorPS</a></td>
303)         <td>Backend Service</td>
304)         <td>Python</td>

305)         <td>None</td>

306)         <td>Aaron Johnson</td>
307)       </tr>
308) 

309)       <tr>

310)         <td><a href="#project-torflow">TorFlow</a></td>
311)         <td>Backend Service</td>
312)         <td>Python</td>

313)         <td>None</td>

314)         <td>aagbsn</td>

315)       </tr>

316) 

317)       <tr>
318)         <td><a href="#project-collector">CollecTor</a></td>
319)         <td>Backend Service</td>
320)         <td>Java</td>

321)         <td>Moderate</td>

322)         <td>karsten, iwakeh</td>
323)       </tr>
324) 
325)       <tr>
326)         <td><a href="#project-exonerator">ExoneraTor</a></td>
327)         <td>Client Service</td>
328)         <td>Java</td>
329)         <td>Light</td>
330)         <td>karsten, iwakeh</td>
331)       </tr>

332) 
333)       <tr>
334)         <td><a href="#project-anonbib">Anonbib</a></td>
335)         <td>Website</td>
336)         <td>Python</td>
337)         <td>None</td>
338)         <td>arma, nickm</td>
339)       </tr>

340)     </table>

341) 

342)     <sub>
343)     * Project is still in an alpha state.
344)     </sub>

345) 

346)     <br /><br />

347) 

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

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

351)     tracker</a>)</h3>

352) 

353)     <p>
354)     Central project, providing the core software for using and participating in
355)     the Tor network. Numerous people contribute to the project to varying
356)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
357)     </p>

358) 

359)     <p>
360)     <b>Project Ideas:</b><br />

361)     <i><a href="#improveOnionServices">Help improve Tor onion services</a></i><br />

362)     <i><a href="#torFuzzing">Fuzzing coverage of Tor</a></i><br />
363)     <i><a href="#relayCryptoParallelism">Relay crypto parallelism</a></i><br />
364)     <i><a href="#anonymousLocalCountStatistics">Anonymous local count statistics</a></i><br />
365)     <i><a href="#improveSocks5Variant">Improved SOCKS5 variant</a></i><br />

366)     <i><a href="#onionServiceCryptoParallelism">Onion service crypto parallelism</a></i><br />

367)     <i><a href="#supportAllDNS">Support all kinds of DNS in Tor</a></i><br />
368)     <i><a href="#improveIpv6Support">Improve IPv6 support</a></i>

369)     </p>

370) 

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

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

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

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

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

377)     <p>

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

380)     to work together out of
381)     the box. The modified copy of Firefox aims to resolve the

382)     privacy and security issues in mainline version.

383)     </p>

384) 

385)     <p>
386)     <b>Project Ideas:</b><br />

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

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

390)     </p>
391) 

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

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

397) 

398)     <p>

399)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
400)     your communications with many major websites, making your browsing
401)     more secure.

402)     </p>

403) 

404)     <a id="project-nyx"></a>

405)     <h3><a href="https://nyx.torproject.org/">Nyx</a> (<a

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

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

408)     tracker</a>)</h3>

409) 

410)     <p>

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

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

416)     </p>

417) 

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

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

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

422)     tracker</a>)</h3>

423) 
424)     <p>

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

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

428)     </p>
429) 
430)     <a id="project-tails"></a>
431)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

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

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

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

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

437) 
438)     <p>
439)     The Amnesic Incognito Live System is a live CD/USB distribution
440)     preconfigured so that everything is safely routed through Tor and leaves no
441)     trace on the local system. This is a merger of the Amnesia and <a

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

443)     and still under very active development.
444)     </p>
445) 

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

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

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

450) 
451)     <p>

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

454)     </p>
455) 

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

457)     <h3>Torsocks (<a

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

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

460)     tracker</a>)</h3>
461) 

462)     <p>

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

466)     </p>

467) 

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

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

472) 
473)     <p>
474)     Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor.
475)     </p>
476) 

477)     <a id="project-torbirdy"></a>
478)     <h3>TorBirdy (<a

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

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

482) 

483)     <p>
484)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
485)     </p>

486) 

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

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

489)     href="https://github.com/shadow">code</a>, <a
490)     href="https://github.com/shadow/shadow/issues">bug
491)     tracker</a>)</h3>

492) 

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

497)     For another simulator, see <a

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

499)     </p>

500) 

501)     <a id="project-chutney"></a>
502)     <h3>Chutney (<a href="https://gitweb.torproject.org/chutney.git">code</a>,
503)     <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
504)     tracker</a>)</h3>
505) 
506)     <p>
507)     Integration test suite that spawns a local tor network, checking the
508)     interactions of its components.
509)     </p>
510) 

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

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

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

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

515)     tracker</a>)</h3>

516) 

517)     <p>

518)     Python controller library for scripts and controller applications using
519)     Tor.

520)     </p>

521) 

522)     <p>
523)     <b>Project Ideas:</b><br />
524)     <i><a href="#pythonTorClient">Python Tor Client</a></i>
525)     </p>
526) 

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

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

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

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

531) 

532)     <p>
533)     Twisted-based asynchronous Tor control protocol implementation. Includes
534)     unit-tests, examples, state-tracking code and configuration abstraction.
535)     Used by OONI and APAF.
536)     </p>

537) 

538)     <a id="project-metrics-lib"></a>
539)     <h3>metrics-lib
540)     (<a href="https://gitweb.torproject.org/metrics-lib.git">code</a>,
541)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2Fmetrics-lib&order=priority">bug tracker</a>)</h3>
542) 
543)     <p>metrics-lib is a Java library that processes Tor network data
544)     provided by <a href="#project-collector">CollecTor</a> or from other
545)     sources.</p>
546) 

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

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

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

550) 

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

554)     Karsten Loesing.

555)     </p>

556) 

557)     <a id="project-atlas"></a>

558)     <h3><a href="https://atlas.torproject.org/">Relay Search</a> (<a

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

560) 

561)     <p>

562)     Relay Search is a web application to discover Tor relays and bridges. It
563)     provides useful information on how relays are configured along with graphics
564)     about their past usage.

565)     </p>

566) 

567)     <p>

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

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

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

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

575)     </p>
576) 

577)     <a id="project-onionoo"></a>

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

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

581) 
582)     <p>
583)     Onionoo is a JSON based protocol to learn information about currently
584)     running Tor relays and bridges.
585)     </p>
586) 

587)     <a id="project-exitmap"></a>
588)     <h3><a href="http://www.cs.kau.se/philwint/spoiled_onions/">ExitMap</a> (<a
589)     href="https://github.com/NullHypothesis/exitmap">code</a>, <a
590)     href="https://github.com/NullHypothesis/exitmap/issues">bug tracker</a>)</h3>
591) 
592)     <p>

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

596)     Onions</a> research paper.
597)     </p>
598) 

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

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

603)     tracker</a>)</h3>
604) 
605)     <p>
606)     DocTor is a notification service that monitors newly published descriptor
607)     information for issues. This is primarily a service to help the tor
608)     directory authority operators, but it also checks for a handful of other
609)     issues like sybil attacks.
610)     </p>
611) 

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

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

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

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

616)     tracker</a>)</h3>

617) 

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

624) 

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

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

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

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

629)     tracker</a>)</h3>

630) 

631)     <p>
632)     E-mail autoresponder providing Tor's packages over SMTP. This has been
633)     relatively unchanged for quite a while.
634)     </p>

635) 

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

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

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

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

640)     tracker</a>)</h3>

641) 

642)     <p>

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

644)     </p>

645) 

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

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

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

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

650)     tracker</a>)</h3>

651) 

652)     <p>
653)     Backend bridge distributor, handling the various pools they're distributed
654)     in. This was actively developed until Fall of 2010.
655)     </p>

656) 
657)     <a id="project-ooni-probe"></a>

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

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

661)     tracker</a>)</h3>
662) 
663)     <p>
664)     Censorship scanner, checking your local connection for blocked or modified
665)     content.
666)     </p>
667) 

668)     <a id="project-torps"></a>
669)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
670) 
671)     <p>
672)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
673)     path selection in Tor. It chooses circuits and assigns user streams to
674)     those circuits in the same way that Tor does. TorPS is fast enough to
675)     perform thousands of simulations over periods of months.
676)     </p>
677) 

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

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

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

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

682)     tracker</a>)</h3>

683) 

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

692) 

693)     <a id="project-collector"></a>
694)     <h3><a href="https://collector.torproject.org/">CollecTor</a>
695)     (<a href="https://gitweb.torproject.org/collector.git">code</a>,
696)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FCollecTor&order=priority">bug tracker</a>)</h3>
697) 
698)     <p>CollecTor is the Tor network data archive that powers other
699)     services like <a href="#project-metrics">Metrics</a> and
700)     <a href="#project-onionoo">Onionoo</a>.</p>
701) 
702)     <a id="project-exonerator"></a>
703)     <h3><a href="https://exonerator.torproject.org/">ExoneraTor</a>
704)     (<a href="https://gitweb.torproject.org/exonerator.git">code</a>,
705)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FExoneraTor&order=priority">bug tracker</a>)</h3>
706) 
707)     <p>ExoneraTor is a service that answers the question whether there was
708)     a Tor relay running on a given IP address on a given date.</p>
709) 

710)     <a id="project-anonbib"></a>
711)     <h3><a
712)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
713)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
714) 
715)     <p>
716)     Anonbib is a list of important papers in the field of anonymity. It's
717)     also a set of scripts to generate the website from Latex (bibtex). If
718)     we're missing any important papers, please let us know!
719)     </p>
720) 

721)     <a id="Coding"></a>
722)     <a id="Summer"></a>

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

724) 

725)     <p>

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

727)     about/gsoc>">Google Summer of Code</a> or the Tor Summer of Privacy. We have labelled each idea with

728)     which of our <a href="<page about/corepeople>">core developers</a> would be
729)     good mentors. If one or more of these ideas looks promising to you, please
730)     <a href="<page about/contact>">contact us</a> to discuss your plans rather
731)     than sending blind applications. You may also want to propose your own
732)     project idea &mdash; which often results in the best applications.

733)     </p>

734) 

735)     <ol>

736) 

737) 	#Keep old ids in case of incoming links.

738)     <a id="pythonTorClient"></a><a id="pythonTorClient"></a>
739)     <li>
740)     <b>Python Tor Client</b>
741)     <br>
742)     Language: <i>Python</i>
743)     <br>
744)     Likely Mentors: <i>Damian (atagar), Tim (teor)</i>
745)     <br><br>
746)     <p>
747) <b><a href="https://stem.torproject.org/">Stem</a></b> is our Python implementation of Tor's varous protocols. Traditionally this included <a href="https://stem.torproject.org/tutorials/the_little_relay_that_could.html">stem.control</a> for Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/control-spec.txt">ControlPort</a> and <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">stem.descriptor</a> to download from Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt">DirPort</a>. But recently we added a third to this family, <b><a href="https://lists.torproject.org/pipermail/tor-dev/2018-February/012905.html">stem.client</a></b>, that speaks Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">ORPort protocol</a>: the relay protocol for usage of the Tor network itself.
748)     </p>
749) 
750)     <p>
751) This opens interesting opportunities we've never had before such as...
752)     </p>
753) 
754)     <ul>
755)       <li>Construct a full three-hop circuit that can make GET requests and DNS lookups. If done right this might allow simple usage of the Tor network without even having Tor installed!</li>
756)       <li>Expand <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#where-can-i-get-the-current-descriptors">descriptor downloading</a> to use Tor's ORPort as an optional alternative for the DirPort. Following this we could adjust Tor so <a href="https://trac.torproject.org/projects/tor/ticket/19129">Fallback Directories no longer require a DirPort</a>.</li>

757)       <li>Download hidden service descriptors. Unlike relays, the descriptors for hidden services are only available over the ORPort. Once <a href="https://trac.torproject.org/projects/tor/ticket/17945">ticket 17945</a> is merged v3 HS descriptor downloads will require a multi-hop circuit. This requires an understanding of Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt">hidden service</a> specifications, particularly the HSDir hash ring.</li>
758)       <li>Authenticate our ORPort connection, checking that ORPorts we connect to have the right key fingerprint.</li>

759)       <li>Add protocol level integration test of Tor's ORPort, for instance exercising edge cases in circuit construction and extension.</li>

760)       <li>Connect to a hidden service to check if it's up or not.</li>

761)     </ul>
762) 
763)     <p>
764) And more! Applicants are encouraged to get a decent understanding of <a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">Tor's ORPort protocol</a> and come up with ideas of their own for neat directions that we can take this. To be clear this is <b>not</b> a particularly easy beginner project as it involves expanding stem.client to support more of Tor's ORPort protocol and crypto.
765)     </p>
766) 
767)     <p>
768) <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>
769)     </p>
770)     </li>
771) 

772)     <a id="improveOnionServices"></a><a id="improveHiddenServices"></a>

773)     <li>

774)     <b>Help improve Tor onion services</b>

775)     <br>

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

777)     <br>

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

779)     <br><br>

780)     <p>

781) The onion services team is busy implementing <a

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

783) 224</a> but we are always open to mentoring fun and exciting onion

784) service projects.

785)     </p>
786) 
787)     <p>

788) In the past, we've mentored a wide variety of projects related to onion

789) services, ranging from <a
790) href="https://lists.torproject.org/pipermail/tor-dev/2016-April/010832.html">onion
791) search engines</a>, <a
792) href="https://lists.torproject.org/pipermail/tor-talk/2015-May/037966.html">to

793) scaling techniques for onion services</a>,

794) and also various approaches
795) of making onion services more <a
796) href="https://lists.torproject.org/pipermail/tor-dev/2012-June/003588.html">usable</a>
797) <a href="https://lists.torproject.org/pipermail/tor-dev/2015-May/008826.html">by
798) common people</a>.

799)     </p>
800) 
801)     <p>

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

806)     </p>
807)     </li>
808) 

809)     <a id="torFuzzing"></a>
810)     <li>
811)     <b>Fuzzing coverage of Tor</b>
812)     <br>
813)     Likely Mentors: <i>Nick (nickm), ahf, teor</i>
814)     <br><br>
815)     <p>
816) Starting in 0.3.0.x, Tor supports a few fuzzing systems to check our
817) code for bugs.  But as of now, we only support a few possible entry
818) points to Tor.  It would be great to add fuzzing support for more of
819) our codebase -- ideally to include our whole network-facing interface.
820) That way, we could find more bugs in our code faster, and fix them
821) before they can get out of hand.
822)     </p>
823) 
824)     <p>
825) This won't be so easy, however: to fuzz effectively, we need to
826) refactor or mock the target function so that it doesn't change any
827) global state, or verify any signatures, or take too long to run.  With
828) lots of our network code, that's not so easy.  Make sure you
829) understand how our mocking system works, and what the challenges are,
830) before you apply for this one.
831)     </p>
832)     </li>
833) 
834)     <a id="relayCryptoParallelism"></a>
835)     <li>
836)     <b>Relay crypto parallelism</b>
837)     <br>
838)     Likely Mentors: <i>Isis, Nick (nickm)</i>
839)     <br><br>
840)     <p>
841) Tor relays spend a lot of time encrypting and decrypting relay
842) traffic, doing SHA1 and AES-CTR operations.  But right now, all of
843) this is done in the main thread!  It would be cool to split this
844) across multiple cores instead.
845)     </p>
846) 
847)     <p>
848) This won't be so easy though.  The code today is written to expect
849) immediate results from its encryption operations, so you would need to
850) do some pretty tricky refactoring in order get performance and
851) correctness here.  Make sure you understand how circuit crypto is
852) invoked today, and what the challenges are, before you apply for this
853) one.
854)     </p>
855) 
856)     <p>
857) For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>.
858)     </p>
859)     </li>
860) 
861)     <a id="anonymousLocalCountStatistics"></a>
862)     <li>
863)     <b>Anonymous local count statistics</b>
864)     <br>
865)     Likely Mentors: <i>Nick (nickm), teor</i>
866)     <br><br>
867)     <p>
868) There are some places in Tor where we count things (like distinct IPs)
869) to later report anonymized statistics.  But if the local Tor instance
870) were compromised, this data would be exposed.  There are statistical
871) methods which insteasd allow us to record this data in a way that's
872) already anonymous, before we ever summarize it.  Interested?
873)     </p>
874) 
875)     <p>
876) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7532">see its ticket</a>.
877)     </p>
878)     </li>
879) 
880)     <a id="improveSocks5Variant"></a>
881)     <li>
882)     <b>Improved SOCKS5 variant</b>
883)     <br>
884)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i>
885)     <br><br>
886)     <p>
887) In proposal 229, we describe a bunch of additional SOCKS extensions
888) that Tor-aware applications could use to get more fine-grained control
889) over how Tor handles their streams.  It would be cool to implement
890) this!  If there's time remaining, you might want to add support to one
891) or more applications.  Or maybe to torsocks?
892)     </p>
893) 
894)     <p>
895) For more information <a href="https://trac.torproject.org/projects/tor/ticket/12456">see its ticket</a>.
896)     </p>
897)     </li>
898) 

899) 	#Keep old ids in case of incoming links.
900)     <a id="onionServiceCryptoParallelism"></a><a id="hiddenServiceCryptoParallelism"></a>

901)     <li>

902)     <b>Onion service crypto parallelism</b>

903)     <br>
904)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i>
905)     <br><br>
906)     <p>

907) Onion services, onion service clients, onion service directories,

908) and introduction points all need to do a few public-key operations as
909) they operate.  But right now, these operations are all done on the
910) main thread.  It would be good to have these run across multiple cores.
911)     </p>
912) 
913)     <p>

914) This could probably be done in a way similar to how we currently handle

915) circuit extension handshakes in onion.c and cpuworker.c, but we'd need

916) to extend the state machine for onion services to add an additional
917) state.  It could help onion services operate much more efficiently.

918)     </p>
919) 
920)     <p>
921) For more information <a href="https://trac.torproject.org/projects/tor/ticket/13738">see its ticket</a>.
922)     </p>
923)     </li>
924) 
925)     <a id="supportAllDNS"></a>
926)     <li>
927)     <b>Support all kinds of DNS in Tor</b>
928)     <br>
929)     Likely Mentors: <i>Nick (nickm), George (asn)</i>
930)     <br><br>
931)     <p>
932) Right now Tor can query for the kind of DNS information you'd find in
933) A records, AAAA records, and PTR records.  It would be neat to be able
934) to support more general DNS queries to allow things like MX loopups,
935) DNSSEC lookups, and so on.  We have a design proposal (number 219) for
936) this, but it might need some clean-up.
937)     </p>
938) 
939)     <p>
940) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>.
941)     </p>
942)     </li>
943) 
944)     <a id="improveIpv6Support"></a>
945)     <li>
946)     <b>Improve IPv6 support</b>
947)     <br>
948)     Likely Mentors: <i>ahf, teor</i>
949)     <br><br>
950)     <p>
951) Tor works over IPv6, but require some manual configuration.
952) Clients and relays could automatically detect IPv6 availability,
953) and configure themselves appropriately. Implementing a
954) "happy eyeballs"-like algorithm is a challenge in an anonymity
955) network: are you up for it?
956)     </p>
957) 
958)     <ul>
959)       <li><a href="https://trac.torproject.org/projects/tor/ticket/6939">Missing IPv6 ORPort reachability check</a></li>
960)       <li><a href="https://trac.torproject.org/projects/tor/ticket/4847">Bridges binding only to an IPv6 address doesn't work</a></li>
961)       <li><a href="https://trac.torproject.org/projects/tor/ticket/5940">Figure out own IPv6 address</a></li>
962)       <li><a href="https://trac.torproject.org/projects/tor/ticket/17011">Teach chutney to verify over IPv6</a></li>
963)     </ul>
964) 
965)     <p>
966) For more information <a href="https://trac.torproject.org/projects/tor/ticket/17811">see its ticket</a>.
967)     </p>
968)     </li>
969) 

970)     <a id="feedbackExtension"></a>
971)     <li>
972)     <b>Feedback Extension for Tor Browser</b>
973)     <br>
974)     Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
975)     <p>
976)     Design and implement an extension for Tor Browser that can be used to gather
977)     end-user UI/UX feedback on an opt-in basis. While the design and
978)     implementation is left as an exercise for the applicant (and also serves as
979)     the qualification task), examples of the information we are looking to gather
980)     can include troubleshooting network connectivity issues, testing the various
981)     pluggable transports, or gathering information about the network of the users.
982)     </p>
983) 
984)     <p>
985)     Please propose the extension design in a way that the information is strictly
986)     on an opt-in basis and scrubs any information that can be used to identify a
987)     user, and also come up with a way to send the gathered information to a
988)     central server, whether to an onion address (if the user has Tor running), or
989)     otherwise. To start with, we are looking to gather only text as part of the
990)     feedback process.
991)     </p>
992)     </li>
993) 
994)     <a id="torBrowserCrashReport"></a>
995)     <li>
996)     <b>Crash Reporter for Tor Browser</b>
997)     <br>
998)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
999)     <p>
1000)     Currently Tor Browser disables the Crash Reporter. We would like to
1001)     build it reproducible, enable it, and configure it to report crashes
1002)     containing non-detailed and impersonal information to Tor, on a .onion
1003)     submission platform that would allow us to view and explore the
1004)     crashes.
1005)     </p>
1006) 
1007)     <p>
1008)     The project will entail enabling the Crash Report on Tor Browser and
1009)     creating a backend to receive reports from it. Once created, the crash
1010)     reporter data will be analyzed and modified to fit Tor's requirements
1011)     for personal data collection. As time permits, we will update the
1012)     build system to ensure the crash reporter is built reproducibly and
1013)     add data analysis tools for the crash report database to visualize top
1014)     crashers and similar statistics.
1015)     </p>
1016)     </li>
1017) 
1018)     <a id="fasterTorBrowser"></a>
1019)     <li>
1020)     <b>Make Tor Browser Faster</b>
1021)     <br>
1022)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
1023)     <p>
1024)     This project will enable and take advantage of HTTP/2, the Alt-Srv
1025)     header, and tor's new single hop .onion mode to enable websites to
1026)     transparently move their traffic to a .onion address. In addition to
1027)     improvements in security, we will benchmark page load and paint times
1028)     under normal HTTP/1.1, HTTP/2, and when taking advantage of features
1029)     such as Server Push.
1030)     </p>
1031)     </li>
1032) 

1033)     <a id="ahmiaSearch"></a>
1034)     <li>

1035)     <b>Ahmia - Onion Service Search</b>

1036)     <br>
1037)     Language: <i>Python, Django</i>
1038)     <br>
1039)     Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i>
1040)     <p>

1041)     Ahmia is open-source search engine software for Tor onion service deep

1042)     dark web sites. You can test the running search engine at ahmia.fi. For
1043)     more information see our <a
1044)     href="https://blog.torproject.org/category/tags/ahmiafi">blog post about
1045)     Ahmia's GSoC2014 development</a>.
1046)     </p>
1047) 
1048)     <p>
1049)     Ahmia is a working search engine that indexes, searches, and catalogs

1050)     content published on Tor Onion Services. Furthermore, it is an environment

1051)     to share meaningful insights, statistics, insights, and news about the Tor
1052)     network itself. In this context, there is a lot of work to do.
1053)     </p>
1054) 
1055)     <p>
1056)     The Ahmia web service is written using the Django web framework. As a
1057)     result, the server-side language is Python. On the client-side, most of the
1058)     pages are plain HTML. There are some pages that require JavaScript, but the
1059)     search itself works without client-side JavaScript.
1060)     </p>
1061) 
1062)     <p>
1063)     There are several possible directions for this project, including...
1064)     </p>
1065) 
1066)     <ol>
1067)       <li>Automate blacklisting (very important)<br />
1068)         <ul>
1069)           <li>Fetch a list of child abuse media sites</li>
1070)           <li>Remove these sites from the search results</li>
1071)         </ul>
1072)       </li>

1073)       <li>Add onion services function (very important)<br />

1074)         <ul>
1075)           <li>You can add onions using HTML form</li>
1076)           <li>Call the crawler immidiately when a new site is added</li>
1077)         </ul>
1078)       </li>
1079)       <li>Elasticsearch<br />
1080)         <ul>
1081)           <li>Must be updated to 5.X.X sooner or later</li>
1082)           <li>Adjust the settings</li>
1083)           <li>Automatically remove data older than, for instance, 90 days</li>
1084)         </ul>
1085)       </li>
1086)       <li>Maintainance<br />
1087)         <ul>
1088)           <li>Update all software dependencies</li>
1089)           <li>Automate crash recovery for Tor, Elasticsearch and crawler</li>
1090)         </ul>
1091)       </li>
1092)     </ol>
1093)     </li>
1094) 

1095) <!--
1096)     <a id=""></a>
1097)     <li>
1098)     <b></b>
1099)     <br>

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

1101)     <br>
1102)     Likely Mentors: <i>Damian (atagar)</i>

1103)     <br><br>

1104)     <p>
1105) 
1106)     </p>
1107) 
1108)     <p>
1109) 
1110)     </p>
1111)     </li>
1112) -->
1113) 

1114)     <li>
1115)     <b>Bring up new ideas!</b>

1116)     <br>

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

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

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

1120)     and find out what you think needs fixing.

1121)     Some of the <a href="<specblob>proposals">current proposals</a>

1122)     might also be short on developers.
1123)     </li>

1124) 

1125)     </ol>
1126)   </div>
1127)   <!-- END MAINCOL -->
1128)   <div id = "sidecol">
1129) #include "side.wmi"
1130) #include "info.wmi"
1131)   </div>
1132)   <!-- END SIDECOL -->
1133) </div>
1134) <!-- END CONTENT -->