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="https://www.youtube.com/user/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, Rust</td>

113)         <td>Heavy</td>

114)         <td>nickm, 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>None</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="#pythonTorClient">Python Tor Client</a></i><br />

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

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

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

370)     </p>

371) 

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

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

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

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

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

378)     <p>

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

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

383)     privacy and security issues in mainline version.

384)     </p>

385) 

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

388)     <i><a href="#metadataremoval">Remove metadata from Tor Browser uploads</a></i><br />

389)     </p>
390) 

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

395)     tracker</a>)</h3>

396) 

397)     <p>

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

401)     </p>

402) 

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

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

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

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

407)     tracker</a>)</h3>

408) 

409)     <p>

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

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

415)     </p>

416) 

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

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

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

421)     tracker</a>)</h3>

422) 
423)     <p>

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

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

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

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

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

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

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

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

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

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

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

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

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

449) 
450)     <p>

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

453)     </p>
454) 

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

456)     <h3>Torsocks (<a

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

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

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

461)     <p>

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

465)     </p>

466) 

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

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

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

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

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

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

481) 

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

485) 

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

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

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

491) 

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

496)     For another simulator, see <a

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

498)     </p>

499) 

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

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

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

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

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

514)     tracker</a>)</h3>

515) 

516)     <p>

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

519)     </p>

520) 

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

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

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

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

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

530) 

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

536) 

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

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

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

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

549) 

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

553)     Karsten Loesing.

554)     </p>

555) 

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

557)     <h3><a href="https://metrics.torproject.org/rs.html">Relay Search</a> (<a

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

559) 

560)     <p>

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

564)     </p>

565) 

566)     <p>

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

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

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

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

574)     </p>
575) 

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

577)     <h3><a href="https://metrics.torproject.org/onionoo.html">Onionoo</a> (<a

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

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

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

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

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

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

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

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

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

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

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

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

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

615)     tracker</a>)</h3>

616) 

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

623) 

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

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

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

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

628)     tracker</a>)</h3>

629) 

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

634) 

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

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

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

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

639)     tracker</a>)</h3>

640) 

641)     <p>

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

643)     </p>

644) 

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

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

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

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

649)     tracker</a>)</h3>

650) 

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

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

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

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

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

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

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

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

679)     href="https://gitweb.torproject.org/torflow.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=Metrics%2FTorflow&order=priority">bug

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

682) 

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

691) 

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

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

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

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

723) 

724)     <p>

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

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

727)     which of our <a href="<page about/corepeople>">core developers</a> would be
728)     good mentors. If one or more of these ideas looks promising to you, please

729)     <a href="mailto:tor-sop@lists.torproject.org">contact us</a>  to discuss your plans rather

730)     than sending blind applications. You may also want to propose your own
731)     project idea — which often results in the best applications.

732)     </p>

733) 

734)     <ol>

735) 

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

737)     <a id="metadataremoval"></a>
738)     <li>
739)     <b>Remove metadata from Tor Browser uploads</b>
740)     <br>
741)     Likely Mentors: <i>Arthur D. Edelstein (arthuredelstein)</i>
742)     <p>
743)     Tor Browser is a privacy-preserving web browser used by millions of
744)     users around the world. We are looking for a programmer fluent in JS
745)     and C++ to implement new features to work closely with the Tor Browser
746)     team.

747)     </p>
748)     <p>

749)     Image files, especially photos taken by smartphones,
750)     often carry hidden privacy-violating metadata, typically specified by
751)     the EXIF format. Such metadata can include the user's geolocation and
752)     various unique identifiers. In order to protect the user's identity,
753)     we would like the intern to modify the file-upload feature in Tor
754)     Browser such that metadata in image files is automatically removed
755)     before the image is uploaded to a server. Ideally, the  summer intern would
756)     implement this feature for both desktop and mobile Tor Browser. If
757)     there is time, we can envision sanitizing other kinds of uploaded
758)     files, including movies, audio, PDFs and Office documents.
759)     </p>
760)     <p>
761)     For more information <a href="https://trac.torproject.org/projects/tor/ticket/24965">see its ticket</a>.

762)     Please also see <a href="https://mat.boum.org">the Metadata Anonymisation Toolkit (MAT)</a> for a
763)     similar project that could serve as inspiration.

764)     </p>
765)     </li>
766) 

767)     <a id="pythonTorClient"></a><a id="pythonTorClient"></a>
768)     <li>
769)     <b>Python Tor Client</b>
770)     <br>
771)     Language: <i>Python</i>
772)     <br>

773)     Likely Mentors: <i>Damian (atagar), teor</i>

774)     <br><br>
775)     <p>
776) <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.
777)     </p>
778) 
779)     <p>
780) This opens interesting opportunities we've never had before such as...
781)     </p>
782) 
783)     <ul>
784)       <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>
785)       <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>

786)       <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>
787)       <li>Authenticate our ORPort connection, checking that ORPorts we connect to have the right key fingerprint.</li>

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

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

790)     </ul>
791) 
792)     <p>
793) 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.
794)     </p>
795) 
796)     <p>
797) <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>
798)     </p>
799)     </li>

800) <!--

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

802)     <li>

803)     <b>Help improve Tor onion 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 onion 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 onion

813) service projects.

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

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

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 onion 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="torFuzzing"></a>
839)     <li>
840)     <b>Fuzzing coverage of Tor</b>
841)     <br>
842)     Likely Mentors: <i>Nick (nickm), ahf, teor</i>
843)     <br><br>
844)     <p>
845) Starting in 0.3.0.x, Tor supports a few fuzzing systems to check our
846) code for bugs.  But as of now, we only support a few possible entry
847) points to Tor.  It would be great to add fuzzing support for more of
848) our codebase -- ideally to include our whole network-facing interface.
849) That way, we could find more bugs in our code faster, and fix them
850) before they can get out of hand.
851)     </p>
852) 
853)     <p>
854) This won't be so easy, however: to fuzz effectively, we need to
855) refactor or mock the target function so that it doesn't change any
856) global state, or verify any signatures, or take too long to run.  With
857) lots of our network code, that's not so easy.  Make sure you
858) understand how our mocking system works, and what the challenges are,
859) before you apply for this one.
860)     </p>
861)     </li>

862) 

863)     <a id="relayCryptoParallelism"></a>
864)     <li>
865)     <b>Relay crypto parallelism</b>
866)     <br>
867)     Likely Mentors: <i>Isis, Nick (nickm)</i>
868)     <br><br>
869)     <p>
870) Tor relays spend a lot of time encrypting and decrypting relay
871) traffic, doing SHA1 and AES-CTR operations.  But right now, all of
872) this is done in the main thread!  It would be cool to split this
873) across multiple cores instead.
874)     </p>
875) 
876)     <p>
877) This won't be so easy though.  The code today is written to expect
878) immediate results from its encryption operations, so you would need to
879) do some pretty tricky refactoring in order get performance and
880) correctness here.  Make sure you understand how circuit crypto is
881) invoked today, and what the challenges are, before you apply for this
882) one.
883)     </p>
884) 
885)     <p>
886) For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>.
887)     </p>
888)     </li>

889) 

890)     <a id="anonymousLocalCountStatistics"></a>
891)     <li>
892)     <b>Anonymous local count statistics</b>
893)     <br>
894)     Likely Mentors: <i>Nick (nickm), teor</i>
895)     <br><br>
896)     <p>
897) There are some places in Tor where we count things (like distinct IPs)
898) to later report anonymized statistics.  But if the local Tor instance
899) were compromised, this data would be exposed.  There are statistical
900) methods which insteasd allow us to record this data in a way that's
901) already anonymous, before we ever summarize it.  Interested?
902)     </p>
903) 
904)     <p>
905) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7532">see its ticket</a>.
906)     </p>
907)     </li>
908) 
909)     <a id="improveSocks5Variant"></a>
910)     <li>
911)     <b>Improved SOCKS5 variant</b>
912)     <br>

913)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet), meejah</i>

914)     <br><br>
915)     <p>
916) In proposal 229, we describe a bunch of additional SOCKS extensions
917) that Tor-aware applications could use to get more fine-grained control
918) over how Tor handles their streams.  It would be cool to implement
919) this!  If there's time remaining, you might want to add support to one
920) or more applications.  Or maybe to torsocks?
921)     </p>
922) 
923)     <p>
924) For more information <a href="https://trac.torproject.org/projects/tor/ticket/12456">see its ticket</a>.
925)     </p>
926)     </li>
927) 

928) 

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

931)     <li>

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

933)     <br>
934)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i>
935)     <br><br>
936)     <p>

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

938) and introduction points all need to do a few public-key operations as
939) they operate.  But right now, these operations are all done on the
940) main thread.  It would be good to have these run across multiple cores.
941)     </p>
942) 
943)     <p>

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

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

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

948)     </p>
949) 
950)     <p>
951) For more information <a href="https://trac.torproject.org/projects/tor/ticket/13738">see its ticket</a>.
952)     </p>
953)     </li>
954) 
955)     <a id="supportAllDNS"></a>
956)     <li>
957)     <b>Support all kinds of DNS in Tor</b>
958)     <br>
959)     Likely Mentors: <i>Nick (nickm), George (asn)</i>
960)     <br><br>
961)     <p>
962) Right now Tor can query for the kind of DNS information you'd find in
963) A records, AAAA records, and PTR records.  It would be neat to be able
964) to support more general DNS queries to allow things like MX loopups,
965) DNSSEC lookups, and so on.  We have a design proposal (number 219) for
966) this, but it might need some clean-up.
967)     </p>
968) 
969)     <p>
970) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>.
971)     </p>
972)     </li>

973) 

974)     <a id="improveIpv6Support"></a>
975)     <li>
976)     <b>Improve IPv6 support</b>
977)     <br>
978)     Likely Mentors: <i>ahf, teor</i>
979)     <br><br>
980)     <p>
981) Tor works over IPv6, but require some manual configuration.
982) Clients and relays could automatically detect IPv6 availability,
983) and configure themselves appropriately. Implementing a
984) "happy eyeballs"-like algorithm is a challenge in an anonymity
985) network: are you up for it?
986)     </p>
987) 
988)     <ul>
989)       <li><a href="https://trac.torproject.org/projects/tor/ticket/6939">Missing IPv6 ORPort reachability check</a></li>
990)       <li><a href="https://trac.torproject.org/projects/tor/ticket/4847">Bridges binding only to an IPv6 address doesn't work</a></li>
991)       <li><a href="https://trac.torproject.org/projects/tor/ticket/5940">Figure out own IPv6 address</a></li>
992)       <li><a href="https://trac.torproject.org/projects/tor/ticket/17011">Teach chutney to verify over IPv6</a></li>
993)     </ul>
994) 
995)     <p>
996) For more information <a href="https://trac.torproject.org/projects/tor/ticket/17811">see its ticket</a>.
997)     </p>
998)     </li>

999) <!--

1000)     <a id="feedbackExtension"></a>
1001)     <li>
1002)     <b>Feedback Extension for Tor Browser</b>
1003)     <br>
1004)     Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
1005)     <p>
1006)     Design and implement an extension for Tor Browser that can be used to gather
1007)     end-user UI/UX feedback on an opt-in basis. While the design and
1008)     implementation is left as an exercise for the applicant (and also serves as
1009)     the qualification task), examples of the information we are looking to gather
1010)     can include troubleshooting network connectivity issues, testing the various
1011)     pluggable transports, or gathering information about the network of the users.
1012)     </p>
1013) 
1014)     <p>
1015)     Please propose the extension design in a way that the information is strictly
1016)     on an opt-in basis and scrubs any information that can be used to identify a
1017)     user, and also come up with a way to send the gathered information to a
1018)     central server, whether to an onion address (if the user has Tor running), or
1019)     otherwise. To start with, we are looking to gather only text as part of the
1020)     feedback process.
1021)     </p>
1022)     </li>

1023) -->

1024) 

1025)     <a id="ahmiaSearch"></a>
1026)     <li>

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

1028)     <br>
1029)     Language: <i>Python, Django</i>
1030)     <br>
1031)     Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i>
1032)     <p>

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

1034)     dark web sites. You can test the running search engine at ahmia.fi. For
1035)     more information see our <a
1036)     href="https://blog.torproject.org/category/tags/ahmiafi">blog post about
1037)     Ahmia's GSoC2014 development</a>.
1038)     </p>
1039) 
1040)     <p>
1041)     Ahmia is a working search engine that indexes, searches, and catalogs

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

1043)     to share meaningful insights, statistics, insights, and news about the Tor
1044)     network itself. In this context, there is a lot of work to do.
1045)     </p>
1046) 
1047)     <p>
1048)     The Ahmia web service is written using the Django web framework. As a
1049)     result, the server-side language is Python. On the client-side, most of the
1050)     pages are plain HTML. There are some pages that require JavaScript, but the
1051)     search itself works without client-side JavaScript.
1052)     </p>
1053) 
1054)     </li>
1055) 

1056) <!--
1057)     <a id=""></a>
1058)     <li>
1059)     <b></b>
1060)     <br>

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

1062)     <br>
1063)     Likely Mentors: <i>Damian (atagar)</i>

1064)     <br><br>

1065)     <p>
1066) 
1067)     </p>
1068) 
1069)     <p>
1070) 
1071)     </p>
1072)     </li>
1073) -->
1074) 

1075)     <li>
1076)     <b>Bring up new ideas!</b>

1077)     <br>

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

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

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

1081)     and find out what you think needs fixing.

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

1083)     might also be short on developers.
1084)     </li>

1085) 

1086)     </ol>
1087)   </div>
1088)   <!-- END MAINCOL -->
1089)   <div id = "sidecol">
1090) #include "side.wmi"
1091) #include "info.wmi"
1092)   </div>
1093)   <!-- END SIDECOL -->
1094) </div>
1095) <!-- END CONTENT -->