[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] r25560: {website} Reverting Arturo's mass whitespace changes Arturo stripped a (website/trunk/getinvolved/en)
Author: atagar
Date: 2012-03-20 15:12:10 +0000 (Tue, 20 Mar 2012)
New Revision: 25560
Modified:
website/trunk/getinvolved/en/volunteer.wml
Log:
Reverting Arturo's mass whitespace changes
Arturo stripped all trailing whitespace from the volunteer page wml while he
added his project. This bugs me and, since I make 95% of the changes to this
file, I'm gonna put it back the way I prefer.
Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml 2012-03-20 03:14:24 UTC (rev 25559)
+++ website/trunk/getinvolved/en/volunteer.wml 2012-03-20 15:12:10 UTC (rev 25560)
@@ -8,7 +8,7 @@
<a href="<page index>">Home » </a>
<a href="<page getinvolved/volunteer>">Volunteer</a>
</div>
- <div id="maincol">
+ <div id="maincol">
<!-- PUT CONTENT AFTER THIS TAG -->
<h1>A few things everyone can do now:</h1>
<ol>
@@ -30,7 +30,7 @@
yet described on that page, and you're comfortable sharing it with us,
we'd love to hear from you.</li>
</ol>
-
+
<a id="Documentation"></a>
<h2><a class="anchor" href="#Documentation">Documentation</a></h2>
<ol>
@@ -46,7 +46,7 @@
programs that interface to Tor</a>. Which ones are useful in which
situations? Please help us test them out and document your results.</li>
</ol>
-
+
<a id="Advocacy"></a>
<h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
<ol>
@@ -57,16 +57,16 @@
href="https://media.torproject.org/video/";>Tor's Media server</a>,
<a
href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy";>Howcast</a>,
- and <a href="http://www.youtube.com/thetorproject";>YouTube</a>.</li>
+ and <a href="http://www.youtube.com/thetorproject";>YouTube</a>.</li>
<li>Create a poster, or a set of posters, around a theme,
such as "Tor for Freedom!".</li>
<li>Create a t-shirt design that incorporates "Congratulations!
You are using Tor!" in any language.</li>
</ol>
-
+
<a id="Projects"></a>
<h2><a class="anchor" href="#Projects">Projects</a></h2>
-
+
<p>
Below are a list of Tor related projects we're developing and/or
maintaining. Most discussions happen on IRC so if you're interested in any
@@ -75,7 +75,7 @@
to ask questions, and don't hesitate to ask even if the main contributors
aren't active at that moment.
</p>
-
+
<table id="projects">
<tr>
<th>Name</th>
@@ -84,7 +84,7 @@
<th>Activity</th>
<th>Contributors</th>
</tr>
-
+
<tr>
<td><a href="#project-tor">Tor</a></td>
<td>Core</td>
@@ -92,7 +92,7 @@
<td>Heavy</td>
<td>nickm, arma, Sebastian</td>
</tr>
-
+
<tr class="alt">
<td>*<a href="#project-jtor">JTor</a></td>
<td>Core</td>
@@ -100,7 +100,7 @@
<td>None</td>
<td></td>
</tr>
-
+
<tr>
<td><a href="#project-tbb">TBB</a></td>
<td>Usability</td>
@@ -108,7 +108,7 @@
<td>Moderate</td>
<td>Erinn</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-tails">Tails</a></td>
<td>Usability</td>
@@ -116,7 +116,7 @@
<td>Heavy</td>
<td><a href="https://tails.boum.org/chat/";>#tails</a></td>
</tr>
-
+
<tr>
<td><a href="#project-torsocks">Torsocks</a></td>
<td>Usability</td>
@@ -124,7 +124,7 @@
<td>None</td>
<td>mwenge</td>
</tr>
-
+
<tr class="alt">
<td>*<a href="#project-torouter">Torouter</a></td>
<td>Usability</td>
@@ -132,7 +132,7 @@
<td>Light</td>
<td>ioerror, Runa</td>
</tr>
-
+
<tr>
<td><a href="#project-vidalia">Vidalia</a></td>
<td>User Interface</td>
@@ -140,7 +140,7 @@
<td>Light</td>
<td>chiiph</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-arm">Arm</a></td>
<td>User Interface</td>
@@ -148,7 +148,7 @@
<td>Light</td>
<td>atagar</td>
</tr>
-
+
<tr>
<td><a href="#project-orbot">Orbot</a></td>
<td>User Interface</td>
@@ -156,7 +156,7 @@
<td>Moderate</td>
<td>n8fr8</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-torbutton">Torbutton</a></td>
<td>Browser Add-on</td>
@@ -164,7 +164,7 @@
<td>Moderate</td>
<td>mikeperry</td>
</tr>
-
+
<tr>
<td><a href="#project-obfsproxy">Obfsproxy</a></td>
<td>Client Add-on</td>
@@ -172,7 +172,7 @@
<td>Moderate</td>
<td>nickm, asn</td>
</tr>
-
+
<tr class="alt">
<td>*<a href="#project-thandy">Thandy</a></td>
<td>Updater</td>
@@ -180,7 +180,7 @@
<td>Light</td>
<td>chiiph, Erinn, nickm</td>
</tr>
-
+
<tr>
<td>*<a href="#project-ooni-probe">Ooni Probe</a></td>
<td>Scanner</td>
@@ -188,7 +188,7 @@
<td>Moderate</td>
<td>hellais, ioerror</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-shadow">Shadow</a></td>
<td>Experimentation</td>
@@ -196,7 +196,7 @@
<td>Moderate</td>
<td>robgjansen</td>
</tr>
-
+
<tr>
<td><a href="#project-torctl">TorCtl</a></td>
<td>Library</td>
@@ -204,7 +204,7 @@
<td>Light</td>
<td>mikeperry</td>
</tr>
-
+
<tr class="alt">
<td>*<a href="#project-stem">Stem</a></td>
<td>Library</td>
@@ -212,7 +212,7 @@
<td>Heavy</td>
<td>atagar</td>
</tr>
-
+
<tr>
<td><a href="#project-metrics">Metrics</a></td>
<td>Client Service</td>
@@ -220,7 +220,7 @@
<td>Heavy</td>
<td>karsten</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-atlas">Atlas</a></td>
<td>Client Service</td>
@@ -228,7 +228,7 @@
<td>Moderate</td>
<td>hellais</td>
</tr>
-
+
<tr>
<td><a href="#project-torstatus">TorStatus</a></td>
<td>Client Service</td>
@@ -236,7 +236,7 @@
<td>None</td>
<td></td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-weather">Weather</a></td>
<td>Client Service</td>
@@ -244,7 +244,7 @@
<td>None</td>
<td>kaner</td>
</tr>
-
+
<tr>
<td><a href="#project-gettor">GetTor</a></td>
<td>Client Service</td>
@@ -252,7 +252,7 @@
<td>None</td>
<td>kaner</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-torcheck">TorCheck</a></td>
<td>Client Service</td>
@@ -260,7 +260,7 @@
<td>None</td>
<td></td>
</tr>
-
+
<tr>
<td><a href="#project-onionoo">Onionoo</a></td>
<td>Backend Service</td>
@@ -268,7 +268,7 @@
<td>Moderate</td>
<td>karsten</td>
</tr>
-
+
<tr class="alt">
<td><a href="#project-bridgedb">BridgeDB</a></td>
<td>Backend Service</td>
@@ -276,7 +276,7 @@
<td>None</td>
<td>kaner, nickm</td>
</tr>
-
+
<tr>
<td><a href="#project-torflow">TorFlow</a></td>
<td>Backend Service</td>
@@ -284,7 +284,7 @@
<td>Moderate</td>
<td>mikeperry</td>
</tr>
-
+
<tr class="alt">
<td>*<a href="#project-torbel">TorBEL</a></td>
<td>Backend Service</td>
@@ -293,24 +293,24 @@
<td>Sebastian</td>
</tr>
</table>
-
+
<sub>
* Project is still in an alpha state.
</sub>
-
+
<br /><br />
-
+
<a id="project-tor"></a>
<h3>Tor (<a href="https://gitweb.torproject.org/tor.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Client&component=Tor+Relay&component=vidalia&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Central project, providing the core software for using and participating in
the Tor network. Numerous people contribute to the project to varying
extents, but the chief architects are Nick Mathewson and Roger Dingledine.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#resistCensorship">Improving Tor's ability to resist
@@ -318,43 +318,43 @@
<i><a href="#user-space-transport">Integrating Tor with user-space
transport protocol libraries</a></i>
</p>
-
+
<a id="project-jtor"></a>
<h3><a href="https://github.com/brl/JTor/wiki";>JTor</a> (<a
href="https://github.com/brl/JTor";>code</a>, <a
href="https://github.com/brl/JTor/issues";>bug
tracker</a>)</h3>
-
+
<p>
Java implementation of Tor and successor to <a
href="http://onioncoffee.sourceforge.net/";>OnionCoffee</a>. This project
isn't yet complete, and has been inactive since Fall 2010.
</p>
-
+
<a id="project-tbb"></a>
<h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
href="https://gitweb.torproject.org/torbrowser.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+bundles/installation&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
and Firefox preconfigured to work together out of the box. This is actively
being worked on by Erinn Clark.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
<i><a href="#usabilityTesting">Usability testing of Tor</a></i>
</p>
-
+
<a id="project-tails"></a>
<h3><a href="https://tails.boum.org/";>The Amnesic Incognito Live System</a> (<a
href="http://git.immerda.ch/?p=amnesia.git;a=summary";>code</a>, <a
href="https://tails.boum.org/bugs/";>bug
tracker</a>)</h3>
-
+
<p>
The Amnesic Incognito Live System is a live CD/USB distribution
preconfigured so that everything is safely routed through Tor and leaves no
@@ -362,7 +362,7 @@
href="http://www.anonymityanywhere.com/incognito/";>Incognito</a> projects,
and still under very active development.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#tailsHiddenServicePetnames">Petname system for Tor hidden
@@ -370,68 +370,68 @@
<i><a href="#tailsServer">Tails server: Self-hosted services behind
Tails-powered Tor hidden services</a></i>
</p>
-
+
<a id="project-torsocks"></a>
<h3><a href="http://code.google.com/p/torsocks/";>Torsocks</a> (<a
href="https://gitweb.torproject.org/torsocks.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Utility for adapting other applications to work with Tor. Development has
slowed and compatibility issues remain with some platforms, but it's
otherwise feature complete.
</p>
-
+
<!--
<p>
<b>Project Ideas:</b><br />
<i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
</p>
-->
-
+
<a id="project-torouter"></a>
<h3><a
href="<wiki>doc/Torouter">Torouter</a> (<a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Project to provide an easy-to-use, embedded Tor instance for routers. This
had high activity in late 2010, but has since been rather quiet.
</p>
-
+
<a id="project-vidalia"></a>
<h3><a href="<page projects/vidalia>">Vidalia</a> (<a
href="https://gitweb.torproject.org/vidalia.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
The most commonly used user interface for Tor. Matt Edman started the
project in 2006 and brought it to its current stable state. Development
slowed for several years, though TomÃs Touceda has since taken a lead with
pushing the project forward.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i><br />
<i><a href="#vidalia-hidden-service-panel">Torrc plugin and improved hidden service configuration panel</a></i>
</p>
-
+
<a id="project-arm"></a>
<h3><a href="http://www.atagar.com/arm/";>Arm</a> (<a
href="https://gitweb.torproject.org/arm.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=arm&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Command-line monitor for Tor. This has been under very active development
by its author, Damian Johnson, since early 2009 to make it a better
general-purpose controller for *nix environments.
</p>
-
+
<!--
<p>
<b>Project Ideas:</b><br />
@@ -439,18 +439,18 @@
<i><a href="#armGui">GUI for Arm</a></i>
</p>
-->
-
+
<a id="project-orbot"></a>
<h3><a href="https://guardianproject.info/apps/orbot/";>Orbot</a> (<a
href="https://gitweb.torproject.org/orbot.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Orbot&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Provides Tor on the Android platform. This was under very active
development up through Fall 2010, after which things have been quiet.
</p>
-
+
<!--
<p>
<b>Project Ideas:</b><br />
@@ -459,13 +459,13 @@
<i><a href="#orbot-optimisation">Core Tor mobile optimisation</a></i>
</p>
-->
-
+
<a id="project-torbutton"></a>
<h3><a href="<page torbutton/index>">Torbutton</a> (<a
href="https://gitweb.torproject.org/torbutton.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Firefox addon that addresses many of the client-side threats to browsing
the Internet anonymously. Mike has since continued to adapt it to new
@@ -473,90 +473,90 @@
href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting";>Chrome
as well</a>.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#torbuttonForThunderbird">Torbutton equivalent for Thunderbird</a></i>
</p>
-
+
<a id="project-obfsproxy"></a>
<h3><a href="https://gitweb.torproject.org/obfsproxy.git/tree/HEAD:/doc";>Obfsproxy</a> (<a
href="https://gitweb.torproject.org/obfsproxy.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Pluggable+transport&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
A proxy that shapes Tor traffic, making it harder for censors to detect and
block Tor.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br />
<i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br />
<i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i>
</p>
-
+
<a id="project-thandy"></a>
<h3>Thandy (<a
href="https://gitweb.torproject.org/thandy.git";>code</a>)</h3>
-
+
<p>
Updater for Tor. The project began in the Summer of 2008 but wasn't
completed. Recently interest in it has been rekindled and many aspects of
its design (including the language it'll be in) are currently in flux.
</p>
-
+
<a id="project-ooni-probe"></a>
<h3>Ooni Probe (<a
href="https://gitweb.torproject.org/ooni-probe.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Ooni&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Censorship scanner, checking your local connection for blocked or modified
content.
</p>
-
+
<a id="project-shadow"></a>
<h3><a href="https://shadow.cs.umn.edu/";>Shadow</a> (<a
href="https://github.com/shadow";>code</a>, <a
href="https://github.com/shadow/shadow/issues";>bug
tracker</a>)</h3>
-
+
<p>
Shadow is a discrete-event network simulator that runs the real
Tor software as a plug-in. Shadow is open-source software that enables
accurate, efficient, controlled, and repeatable Tor experimentation.
</p>
-
+
<a id="project-torctl"></a>
<h3>TorCtl (<a
href="https://gitweb.torproject.org/pytorctl.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Python bindings and utilities for using the Tor control port. It has been
stable for several years, with only minor revisions.
</p>
-
+
<a id="project-stem"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/stem";>Stem</a> (<a
href="https://gitweb.torproject.org/stem.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Stem&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Python controller library with a similar scope to TorCtl, but with better
testing, documentation, and API. This project is not yet feature complete.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#stemPathsupport">Stem PathSupport Capabilities</a></i>
</p>
-
+
<a id="project-metrics"></a>
<h3><a href="https://metrics.torproject.org/";>Metrics</a> (code: <a
href="https://gitweb.torproject.org/metrics-db.git";>db</a>, <a
@@ -564,32 +564,32 @@
href="https://gitweb.torproject.org/metrics-web.git";>web</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Processing and analytics of consensus data, provided to users via the
metrics portal. This has been under active development for several years by
Karsten Loesing.
</p>
-
+
<p>
<b>Project Ideas:</b><br />
<i><a href="#metricsSearch">Searchable Tor descriptor and Metrics data archive</a></i> (Python/Django?)
</p>
-
+
<a id="project-atlas"></a>
<h3><a href="https://atlas.torproject.org/";>Atlas</a> (<a
href="https://gitweb.torproject.org/atlas.git";>code</a>)</h3>
-
+
<p>
Atlas is a web application to discover Tor relays and bridges. It provides
useful information on how relays are configured along with graphics about
their past usage. This is the third evolution of the TorStatus application.
</p>
-
+
<a id="project-torstatus"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorStatus";>TorStatus</a> (<a
href="https://gitweb.torproject.org/torstatus.git";>code</a>)</h3>
-
+
<p>
Portal providing an overview of the Tor network, and details on any of its
current relays. Though very actively used, this project has been
@@ -598,68 +598,68 @@
codebase</a> was written in PHP, and students from Wesleyan wrote the new
Django counterpart.
</p>
-
+
<a id="project-weather"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Weather";>Weather</a> (<a
href="https://gitweb.torproject.org/weather.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Weather&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Provides automatic notification to subscribed relay operators when their
relay's unreachable. This underwent a rewrite by the <a
href="http://hfoss.wesleyan.edu/";>Wesleyan HFOSS team</a>, which went live
in early 2011.
</p>
-
+
<a id="project-gettor"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/GetTor";>GetTor</a> (<a
href="https://gitweb.torproject.org/gettor.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=GetTor&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
E-mail autoresponder providing Tor's packages over SMTP. This has been
relatively unchanged for quite a while.
</p>
-
+
<a id="project-torcheck"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorCheck";>TorCheck</a> (<a
href="https://svn.torproject.org/svn/check/trunk/";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Check&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Provides a simple site for determining if the visitor is using Tor or not.
This has been relatively unchanged for quite a while.
</p>
-
+
<a id="project-onionoo"></a>
<h3><a href="<page projects/onionoo>">Onionoo</a> (<a
href="https://gitweb.torproject.org/onionoo.git";>code</a>)</h3>
-
+
<p>
Onionoo is a JSON based protocol to learn information about currently
running Tor relays and bridges.
</p>
-
+
<a id="project-bridgedb"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/BridgeDB";>BridgeDB</a> (<a
href="https://gitweb.torproject.org/bridgedb.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=BridgeDB&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Backend bridge distributor, handling the various pools they're distributed
in. This was actively developed until Fall of 2010.
</p>
-
+
<a id="project-torflow"></a>
<h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorFlow";>TorFlow</a> (<a
href="https://gitweb.torproject.org/torflow.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torflow&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
Library and collection of services for actively monitoring the Tor network.
These include the Bandwidth Scanners (measuring throughput of relays) and
@@ -668,14 +668,14 @@
months later. Both have been under active use since then, but development
has stopped.
</p>
-
+
<a id="project-torbel"></a>
<h3><a
href="https://blog.torproject.org/blog/torbel-tor-bulk-exit-list-tools";>TorBEL</a> (<a
href="https://gitweb.torproject.org/torbel.git";>code</a>, <a
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=TorDNSEL/TorBEL&order=priority";>bug
tracker</a>)</h3>
-
+
<p>
The Tor Bulk Exitlist provides a method of identifying if IPs belong to
exit nodes or not. This is a replacement for TorDNSEL which is a stable
@@ -683,11 +683,11 @@
version of TorBEL was started in GSOC 2010 but since then the project has
been inactive.
</p>
-
+
<a id="Coding"></a>
<a id="Summer"></a>
<h2><a class="anchor" href="#Coding">Project Ideas</a></h2>
-
+
<p>
You may find some of these projects to be good <a href="<page
about/gsoc>">Google Summer of Code</a> ideas. We have labelled each idea
@@ -700,9 +700,9 @@
sending blind applications. You may also want to propose your own project
idea — which often results in the best applications.
</p>
-
+
<ol>
-
+
<a id="auditTBB"></a>
<li>
<b>Audit Tor Browser Bundles for data leaks</b>
@@ -727,7 +727,7 @@
application development on one or preferably all of Windows, Linux,
and Mac OS X, and be comfortable with C/C++ and shell scripting.</p>
</li>
-
+
<a id="firewallProbeTool"></a>
<li>
<b>Develop a fully automatic firewall-probing system</b>
@@ -757,7 +757,7 @@
DTLS, etc.).</li>
</ul>
</li>
-
+
<!--
<a id="orbot-torbutton"></a>
<li>
@@ -780,7 +780,7 @@
on this so far.</p>
</li>
-->
-
+
<a id="obfsproxy-new-transports"></a>
<li>
<b>New and innovative pluggable transports</b>
@@ -796,18 +796,18 @@
interesting. Other ideas like bittorrent transports might be relevant,
but you will have to provide security proofs on why they are harder to
detect and block than other less-sophisticated transports.</p>
-
+
<p>The whole point of this project, though, is to come up with new
transports that we haven't already thought of. Be creative.</p>
-
+
<p>Bonus points if your idea is interesting and still implementable
through the summer period.</p>
-
+
<p>More bonus points if it's implemented on top of obfsproxy, or if your
implementation has a pluggable transport interface on top of it (as
specified <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt";>here</a>).</p>
</li>
-
+
<a id="obfsproxy-scanning-measures"></a>
<li>
<b>Defensive bridge active scanning measures</b>
@@ -822,13 +822,13 @@
<p>Involves providing good answers to <a
href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html";>this
thread</a> as well as concrete implementation plans for it.</p>
-
+
<p>This also involves implementing proposals <a
href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt";>189</a>
and <a
href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt";>190</a>.</p>
</li>
-
+
<a id="stemPathsupport"></a>
<li>
<b>Stem PathSupport Capabilities</b>
@@ -848,26 +848,26 @@
protocol</a> to help developers program against the tor process, enabling
them to build things similar to <a href="#project-vidalia">Vidalia</a> and
<a href="#project-arm">arm</a>.</p>
-
+
<p>While TorCtl provided a fine first draft for this sort of functionality,
it has not proved to be extensible nor maintainable. Stem is a rewrite of
TorCtl with a heavy focus on testing, documentation, and providing a
developer friendly API.</p>
-
+
<p>At the moment stem is still very much incomplete, missing several pieces
of functionality that TorCtl provides. This is a project to fix that by
porting TorCtl's <a
href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py";>PathSupport
module</a> to stem, writing tests for it, and migrate a couple clients to
use it.</p>
-
+
<p>PathSupport provides applications with programmatic control over how
tor's circuits are built, for instance letting you exit from particular
relays. This is used by projects like <a href="#project-torbel">TorBEL</a>,
<a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>.</p>
-
+
<p>This project can be broken into three parts...</p>
-
+
<ol style="list-style-type: decimal">
<li><p>Look at PathSupport's clients to figure out how it is used and
come up with the API that we will use for stem. Note that the goal if
@@ -885,7 +885,7 @@
API as we discover issues. A particularly good client to start with would
be TorBEL.</p></li>
</ol>
-
+
<!--
<a id="orbot-userInterface"></a>
<li>
@@ -913,7 +913,7 @@
Tablet.</p>
</li>
-->
-
+
<a id="user-space-transport"></a>
<li>
<b>Integrating Tor with user-space transport protocol libraries</b>
@@ -942,7 +942,7 @@
<p>Excellent C programming skills are needed, and knowledge of Tor
internals are highly desirable.</p>
</li>
-
+
<a id="resistCensorship"></a>
<li>
<b>Improving Tor's ability to resist censorship</b>
@@ -983,7 +983,7 @@
then trading off censorship resistance with usability and
robustness.</p>
</li>
-
+
<a id="tailsHiddenServicePetnames"></a>
<li>
<b>Petname system for Tor hidden services</b>
@@ -1026,7 +1026,7 @@
Development methods. Either in Ruby using Cucumber and RSpec, or in
Python using similar tools.</p>
</li>
-
+
<a id="tailsServer"></a>
<li>
<b>Tails server: Self-hosted services behind Tails-powered Tor hidden services</b>
@@ -1061,7 +1061,7 @@
amnesia property and limited support for persistent encrypted data
allows to protect content, to a great degree, even in such contexts.</p>
<p>In short, setting up a new Tails server would be done by:</p>
-
+
<ol style="list-style-type: decimal">
<li>Alice plugs a USB stick into a running desktop Tails system.</li>
<li>Alice uses a GUI to easily configure the needed services.</li>
@@ -1077,12 +1077,12 @@
services</b> project would be very complementary to this one, by the
way.)</li>
</ol>
-
+
<p>Tails server should content itself with hardware that is a bit old
(such as a PIII-450 laptop with 256MB of RAM) and/or half broken (e.g.
non-functional hard-disk, screen or keyboard).</p>
<p>The challenges behind this project are:</p>
-
+
<ul>
<li>Design and write the services configuration GUI [keywords: edit
configuration files, upgrade between major Debian versions,
@@ -1095,7 +1095,7 @@
encryption passphrase without X, and possibly with a broken keyboard
and/or screen [keywords: local network, SSL/TLS?, certificate?].</li>
</ul>
-
+
<p>This project can easily grow quite large, so the first task would
probably be to clarify what it would need to get an initial (minimal
but working) implementation ready to be shipped to users.</p>
@@ -1113,7 +1113,7 @@
would be most welcome.</p>
<p>For more information see https://tails.boum.org/todo/server_edition/</p>
</li>
-
+
<a id="geoIPUpgrade"></a>
<li>
<b>Improve our GeoIP file format</b>
@@ -1138,7 +1138,7 @@
designing the IPv6 format, this is not likely to be a good GSoC
project.</p>
</li>
-
+
<!--
<a id="armClientMode"></a>
<li>
@@ -1158,10 +1158,10 @@
operators. However, this doesn't need to be the case. This project would be
to expand and simplify arm to make it useful for Tor's client users
too.</p>
-
+
<p>This would include UI design, experimenting, and a lot of python
hacking. Here's some ideas for client functionality arm could provide:</p>
-
+
<ul>
<li>A panel for client connections, showing each hop of the user's
circuits with the ISP, country, and jurisdiction where those relays
@@ -1171,35 +1171,35 @@
information can be fetched safely (for instance, scraping rdns and whois
lookups could give hints about a relay's ISP, but we'd need to do it on
all Tor relays to avoid leaking our connections to the resolver).</li>
-
+
<li>Options to let the user request new circuits (the "New
Identity" feature in Vidalia), select the exit country, etc.</li>
-
+
<li>A panel showing Internet application and if their connections are
being routed through Tor or not (giving a warning if there's leaks).</li>
-
+
<li>The status of the bridges we're configured to use (ie, are they up?).
This would include adding control port functionality to Tor for <a
href="https://trac.torproject.org/projects/tor/ticket/2068";>ticket
2068</a>.</li>
-
+
<li>A one click option to set Tor to be a client, relay, or bridge. The
goal would be to make it trivial for users to voluntarily contribute to
the Tor network.</li>
-
+
<li>Menus as an alternative to hotkeys to make the interface more
intuitive and usable for beginners (<a
href="http://gnosis.cx/publish/programming/charming_python_6.html";>example</a>).</li>
-
+
<li>Look at Vidalia and TorK for ideas and solicit input from the Tor community.</li>
</ul>
-
+
<p>
More information is available in the following sections of arm's dev notes: <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#ConnectionListingExpansion";>Connection Listing Expansion</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#CircuitDetails";>Circuit Details</a>, and <a href="https://trac.torproject.org/projects/tor/wiki/doc/arm#ClientModeUseCases";>Client Mode Use Cases</a>
</p>
</li>
-->
-
+
<a id="vidalia-hidden-service-panel"></a>
<li>
<b>Torrc plugin and improved hidden service configuration panel</b>
@@ -1215,18 +1215,18 @@
every Tor option is saved in the torrc file. With that change, the
Hidden Service configuration panel was removed due to its specificity
and its multiple bugs.</p>
-
+
<p>The idea would be to provide the new Torrc class' functionality to the
Plugin Engine and with that, create a better Hidden Service
configuration panel as a plugin.</p>
-
+
<p>A person undertaking this project should have good UI design, layout
skills and some C++ development experience. Previous experience with Qt
and Qt's Designer will be very helpful, but are not required. Javascript
knowledge is a plus, but it shouldn't be a problem if the person
complies with the previous requirements.</p>
</li>
-
+
<a id="metricsSearch"></a>
<li>
<b>Searchable Tor descriptor and Metrics data archive</b>
@@ -1239,13 +1239,13 @@
<br>
Likely Mentors: <i>Karsten</i>
<p>The <a href="https://metrics.torproject.org/data.html";>Metrics data archive</a> of Tor relay descriptors and other Tor-related network data has grown to over 100G in size, bz2-compressed. We have developed two search interfaces: the <a href="https://metrics.torproject.org/relay-search.html";>relay search</a> finds relays by nickname, fingerprint, or IP address in a given month; <a href="https://metrics.torproject.org/exonerator-beta.html";>ExoneraTor</a> finds whether a given IP address was a relay on a given day.</p>
-
+
<p>We'd like to have a more general search application for Tor descriptors and metrics data. There are more <a href="https://metrics.torproject.org/formats.html";>descriptor types</a> that we'd like to include in the search. The search application should handle most of them and understand some semantics like what's a timestamp, what's an IP address, and what's a link to another descriptor. Users should then be able to search for arbitrary strings or limit their search to given time periods or IP address ranges. Descriptors that reference other descriptors should contain links, and descriptors should be able to say from where they are linked. The goal is to make the archive easily browsable.</p>
-
+
<p>The search application shall be separate from the metrics website and shouldn't rely on the metrics website codebase. The search application will contain hourly updated descriptor data from the metrics website via rsync. Programming language and database system are not specified yet, though there's a slight preference for Python/Django and Postgres for maintenance reasons. If there are good reasons to pick something else, e.g, some NoSQL variant or some search application framework, that's fine, too. Further requirements are that lookups should be really fast and that changes to the search application can be implemented in reasonable time.</p>
-
+
<p>Applications for this project should come with a design of the proposed search application, ideally with a proof-of-concept based on a subset of the available data to show that it will be able to handle the 100G+ of data.</p>
-
+
<!--
<a id="unitTesting"></a>
<li>
@@ -1274,7 +1274,7 @@
changes in performance on machines in different roles automatically.</p>
</li>
-->
-
+
<!--
<a id="simulateSlowConnections"></a>
<li>
@@ -1294,7 +1294,7 @@
difficult to improve the situation without being able to repeat the
problems in the lab.
</p>
-
+
<p>
This project would be to build a simulation environment which
replicates the poor connectivity so that the effect on Tor performance
@@ -1302,7 +1302,7 @@
establish what are the properties of connections available, and to
measure the effect of performance-improving modifications to Tor.
</p>
-
+
<p>
The tools used would be up to the student, but dummynet (for FreeBSD)
and nistnet (for Linux) are two potential components on which this
@@ -1312,7 +1312,7 @@
</p>
</li>
-->
-
+
<a id="torbuttonForThunderbird"></a>
<li>
<b>Torbutton equivalent for Thunderbird</b>
@@ -1332,7 +1332,7 @@
push to build a Thunderbird extension similar to Torbutton.
</p>
</li>
-
+
<a id="usabilityTesting"></a>
<li>
<b>Usability testing of Tor</b>
@@ -1350,13 +1350,13 @@
fixes or new features. We get this informally at the moment, but a more
structured process would be better.
</p>
-
+
<p>
Please note that since this isn't a coding project, it isn't suitable for
Google Summer of Code.
</p>
</li>
-
+
<!--
<a id="torsocksForOSX"></a>
<li>
@@ -1389,7 +1389,7 @@
</p>
</li>
-->
-
+
<a id="vidaliaStatusEventInterface"></a>
<li>
<b>Tor Controller Status Event Interface for Vidalia</b>
@@ -1430,7 +1430,7 @@
be understandable by non-technical users. Bonus points for some graphic
design/Photoshop fu, since we might want/need some shiny new icons too.</p>
</li>
-
+
<!--
<a id="orbot-optimisation"></a>
<li>
@@ -1451,7 +1451,7 @@
available (such as wireless network status) that could be taken
advantage of.
</p>
-
+
<p>
It should be noted, that even without optimisation, Tor is handling the
mobile network environment very well, automatically detecting change in
@@ -1461,13 +1461,13 @@
experience, and not any detailed study of what exactly is happening, and
what threats might exist because of this constantly changing network state.
</p>
-
+
<p>
Finally, the build process needs to be moved to the Android NDK from the
custom GCC toolchain we are now using, and compatibility with Android
2.3 and 3.x Honeycomb OS need to be verified.
</p>
-
+
<p>
For more information see the <a
href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/BUILD";>Orbot
@@ -1475,7 +1475,7 @@
</p>
</li>
-->
-
+
<!--
<a id="orbot-orlibAndOutreach"></a>
<li>
@@ -1502,7 +1502,7 @@
</p>
</li>
-->
-
+
<!--
<a id="vidaliaNetworkMap"></a>
<li>
@@ -1528,7 +1528,7 @@
more Tor exit relays and say, "I want my connections to exit
from here."
</p>
-
+
<p>
This project will first involve getting familiar with Vidalia
and the Marble widget's API. One will then integrate the widget
@@ -1536,7 +1536,7 @@
such as making circuits clickable, storing cached map data in Vidalia's
own data directory, and customizing some of the widget's dialogs.
</p>
-
+
<p>
A person undertaking this project should have good C++ development
experience. Previous experience with Qt and CMake is helpful, but not
@@ -1544,7 +1544,7 @@
</p>
</li>
-->
-
+
<a id="obfsproxy-fuzzer"></a>
<li>
<b>Fuzzer for the Tor protocol</b>
@@ -1558,12 +1558,12 @@
Likely Mentors: <i>asn</i>
<p>Involves researching good and smart ways to fuzz stateful network
protocols, and also implementing the fuzzer.</p>
-
+
<p>We are mostly looking for a fuzzer that fuzzes the Tor protocol
itself, and not the Tor directory protocol.</p>
-
+
<p>Bonus points if it's extremely modular. Relevant research:</p>
-
+
<ul>
<li>PROTOS - Security Testing of Protocol Implementations</li>
<li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li>
@@ -1575,7 +1575,7 @@
"symbolic execution" to get inspired.</li>
</ul>
</li>
-
+
<!--
<a id="armGui"></a>
<li>
@@ -1597,7 +1597,7 @@
users. This project would be to build a GTK or Qt frontend for the
controller, providing similar features set but with a windowed interface.
</p>
-
+
<p>
The vast majority of arm's more interesting functionality lies in its
backend <a href="https://gitweb.torproject.org/arm.git/tree/HEAD:/src/util";>utilities</a>, so
@@ -1608,7 +1608,7 @@
</p>
</li>
-->
-
+
<a id="APAF"></a>
<li>
<b>APAF: Anonymous Python Application Framework</b>
@@ -1621,24 +1621,25 @@
<br>
Likely Mentors: <i>Arturo (hellais)</i>
<p>
- The goal of APAF is to create a build framework for creating a binary package for multiple
- platforms (.app/dmg, .exe, .deb, etc.) that includes the python interpreter (cpython), the Tor
- binary and all the UI necessary to make users be able to easily run the bundled Tor Hidden
- Service.
+ The goal of APAF is to create a build framework for creating a binary
+ package for multiple platforms (.app/dmg, .exe, .deb, etc.) that includes
+ the python interpreter (cpython), the Tor binary and all the UI necessary
+ to make users be able to easily run the bundled Tor Hidden Service.
</p>
-
+
<p>
- For GSoC the student is expected to create the build system capable of building a simple
- web application that serves static files. It should also include a web UI for a wizard setup,
- checking the status of the HS and configuring it.
+ For GSoC the student is expected to create the build system capable of
+ building a simple web application that serves static files. It should also
+ include a web UI for a wizard setup, checking the status of the HS and
+ configuring it.
</p>
-
+
<p>
- For more details on this: check out <a href="https://pad.riseup.net/p/1zA8FI4nrYlq";>https://pad.riseup.net/p/1zA8FI4nrYlq</a>
+ For more details on this: check out <a
+ href="https://pad.riseup.net/p/1zA8FI4nrYlq";>https://pad.riseup.net/p/1zA8FI4nrYlq</a>
</p>
</li>
-
-
+
<li>
<b>Bring up new ideas!</b>
<br>
@@ -1649,9 +1650,9 @@
Some of the <a href="<spectree>proposals">current proposals</a>
might also be short on developers.
</li>
-
+
</ol>
-
+
<a id="OtherCoding"></a>
<h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
<ol>
@@ -1667,13 +1668,13 @@
the new libevent interface. Christian King made a
<a href="https://svn.torproject.org/svn/libevent-urz/trunk/";>good
start</a> on this in the summer of 2007.</li>
-
+
<li>We need to actually start building our <a href="<page
docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
fleshing out the design, modifying many different pieces of Tor, adapting
<a href="<page projects/vidalia>">Vidalia</a> so it supports the
new features, and planning for deployment.</li>
-
+
<li>We need a flexible simulator framework for studying end-to-end
traffic confirmation attacks. Many researchers have whipped up ad hoc
simulators to support their intuition either that the attacks work
@@ -1683,18 +1684,18 @@
See the entry <a href="#Research">below</a> on confirmation attacks for
details on the research side of this task — who knows, when it's
done maybe you can help write a paper or three also.</li>
-
+
<li>Tor 0.1.1.x and later include support for hardware crypto
accelerators via OpenSSL. It has been lightly tested and is
possibly very buggy. We're looking for more rigorous testing,
performance analysis, and optimally, code fixes to OpenSSL and
Tor if needed.</li>
-
+
<li>Perform a security analysis of Tor with <a
href="https://secure.wikimedia.org/wikipedia/en/wiki/Fuzz_testing";>"fuzz"</a>. Determine
if there are good fuzzing libraries out there for what we want. Win fame by
getting credit when we put out a new release because of you!</li>
-
+
<li>Tor uses TCP for transport and TLS for link
encryption. This is nice and simple, but it means all cells
on a link are delayed when a single packet gets dropped, and
@@ -1705,24 +1706,24 @@
href="<specblob>proposals/100-tor-spec-udp.txt">specification
for Tor and
UDP</a> — please let us know what's wrong with it.</li>
-
+
<li>We're not that far from having IPv6 support for destination addresses
(at exit nodes). If you care strongly about IPv6, that's probably the
first place to start.</li>
-
+
<li>We need a way to generate the website diagrams (for example, the "How
Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
from source, so we can translate them as UTF-8 text rather than edit
them by hand with Gimp. We might want to
integrate this as an wml file so translations are easy and images are
generated in multiple languages whenever we build the website.</li>
-
+
<li>How can we make the various LiveCD/USB systems easier
to maintain, improve, and document? One example is <a
href="https://tails.boum.org/";>The Amnesic Incognito Live
System</a>.
</li>
-
+
<li>
Another anti-censorship project is to try to make Tor
more scanning-resistant. Right now, an adversary can identify <a
@@ -1735,9 +1736,9 @@
To start, check out Shane Pope's <a
href="http://dl.dropbox.com/u/37735/index.html";>thesis and prototype</a>.
</li>
-
+
</ol>
-
+
<a id="Research"></a>
<h2><a class="anchor" href="#Research">Research</a></h2>
<ol>
@@ -1861,7 +1862,7 @@
connected?
</li>
</ol>
-
+
<p>
<a href="<page about/contact>">Let us know</a> if you've made progress on any
of these!
@@ -1875,4 +1876,4 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
+#include <foot.wmi>
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits