tor-webwml.git

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18613

+# Based-On-Revision: 19084

 # Last-Translator: mail ed oliverknapp.de

 #include "head.wmi" TITLE="Tor: Spende!" CHARSET="UTF-8"

@@ -74,7 +74,7 @@ href="http://paypal.com/">PayPal-Konto</a>):<br />

 <input type="hidden" name="cmd" value="_xclick-subscriptions" />

 <input type="hidden" name="business" value="donations@torproject.org" />

 <input type="hidden" name="item_name" value="Tor Project Membership" />

-<input type="hidden" name="return" value="https://www.torproject.org/">

+<input type="hidden" name="return" value="https://www.torproject.org/donate#funds">

 <input type="hidden" name="cancel_return" value="https://www.torproject.org/donate">

 </p>

 </form>

@@ -97,7 +97,7 @@ href="http://paypal.com/">PayPal-Konto</a>):<br />

 <input type="hidden" name="cmd" value="_xclick" />

 <input type="hidden" name="business" value="donations@torproject.org" />

 <input type="hidden" name="item_name" value="Tor" />

-<input type="hidden" name="return" value="https://www.torproject.org/">

+<input type="hidden" name="return" value="https://www.torproject.org/donate#funds">

 <input type="hidden" name="cancel_return" value="https://www.torproject.org/donate">

 </p>

 </form>

@@ -166,10 +166,11 @@ die Adresse des Spenders stehen.

 <h3><a class="anchor" href="#funds">Was passiert mit meiner

 Spende?</a></h3>

-<p>Deine Spende wird in unseren allgemeinen Fond eingezahlt. Du zählst

-damit zu den <a href="<page sponsors>">vielen Spendern</a> für die

-Zukunft von Tor und der Onlineanonymität. Im Jahr 2008 wurden die

-Spenden wie folgt ausgegeben und eingenommen:</p>

+<p>Wenn du gerade gespendet hast, vielen Dank für deinen Beitrag!Deine Spende

+wird in unseren allgemeinen Fond eingezahlt. Du zählst damit zu den <a

+href="<page sponsors>">vielen Spendern</a> für die Zukunft von Tor und der

+Onlineanonymität. Im Jahr 2008 wurden die Spenden wie folgt ausgegeben und

+eingenommen:</p>

 <p><img src="images/2008-funding-chart.png" alt="Wer spendet an das Tor-Projekt?"/>

 <img src="images/2008-expenses-chart.png" alt="Wie werden die Gelder ausgegeben?"/></p>

@@ -1,8 +1,8 @@

 ## translation metadata

-# Based-On-Revision: 18918

+# Based-On-Revision: 19103

 # Last-Translator: mail a-t oliverknapp .de

-#include "head.wmi" TITLE="Tor: Download" CHARSET="UTF-8"

+#include "head.wmi" TITLE="Tor: Download" CHARSET="UTF-8" ANNOUNCE_RSS="yes"

 <div class="main-column">

@@ -54,6 +54,21 @@ Wie das geht?</a>):</p>

     <li><a href="<package-osx-bundle-stable-sig>">Signatur des OS X Installationspakets</a></li>

   </ul></li>

+<p>Um über neueste Sicherheitshinweise und neue stabile Versionen informiert

+zu sein, abonniere die <a href="http://archives.seul.org/or/announce/">

+or-announce Mailingliste (Engl.)</a> (Du wirst per Mail um eine Bestätigung

+gebeten). Du kannst auch den RSS-Feed der Liste <a

+href="http://rss.gmane.org/gmane.network.onion-routing.announce">

+beobachten</a>. </p>

+

+<form action="http://freehaven.net/cgi-bin/majordomo.cgi">

+<input type="hidden" name="mlist" value="or-announce">

+<input type="hidden" name="subscribe" value="1">

+<input type="hidden" name="host" value="freehaven.net">

+<input name="email" size="15">

+<input type="submit" value="or-announce abonnieren">

+</form>

+

 <li><p>Du brauchst mehr Auswahl? <a href="<page download>">Hier gibt es unserer

 Downloadseite für fortgeschrittene Anwender</a>.</p></li>

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18909

+# Based-On-Revision: 18972

 # Last-Translator: mail et oliverknapp INSERT_DOT de

 #include "head.wmi" TITLE="Tor: Google Summer of Code 2009" CHARSET="UTF-8"

@@ -31,14 +31,16 @@ Bewerbung</a> ist der <b>7. April 2008</b> um 17 Uhr Pacific time. </p>-->

 arbeiten können. Wir haben eine spannende Community von interessierten

 Entwicklern im IRC und auf Mailinglisten und arbeiten gerne mit dir zusammen,

 diskutieren mit dir über Designvorschläge und vieles mehr, aber du musst dich

-und deine Zeit selbst einteilen können und solltest bereits wissen, wie die

+und deine Zeit selbst einteilen können und solltest bereits ungefähr wissen, wie die

 Entwicklung freier Software über das Internet funktioniert. </p>

 <p> Es geht aber nicht nur darum, ein bisschen Entwicklungsarbeit für Tor

 fertig zu bekommen. Google und Tor wollen auch Studenten so in die Entwicklung

 einbinden, dass sie nach dem Sommer weiter dabei bleiben. Aus diesem Grund

 bevorzugen wir Studenten die bereits andauerndes Interesse und Bereitschaft

-gezeigt haben. </p>

+gezeigt haben. Wir fordern von unseren Studenten öffentliche Statusreports für

+unsere Community, entweder gebloggt oder per Mail. Wir wollen, dass die

+Studenten und die Tor-Gemeinschaft voneinander profitieren können.</p>

 <p>

 Die Arbeit an Tor lohnt sich, da:

@@ -65,7 +67,7 @@ href="http://freehaven.net/anonbib/">anonymen Systeme</a> aufgeworfen.</li>

 <p>Dieses Jahr haben wir zwei Ideen: Eine Sache wäre es <a href="<page

 volunteer>#Projects">bei der Entwicklung von Tor zu helfen</a>, die andere

 Idee ist, bei der Entwicklung des

-<a href="http://www.eff.org/testyourisp/switzerland">Switzerland Werkzeugs der

+<a href="http://switzerland.wiki.sourceforge.net/Projects">Switzerland Werkzeugs der

 EFF zu helfen.</a>.</p>

 <a id="Template"></a>

@@ -87,7 +89,7 @@ und uns davon überzeugen, dass du planst es fertig zu bekommen.</li>

 <li>Zeig uns ein Code-Beispiel: Etwas Schickes und Sauberes, damit wir sehen

 dass du weißt was du so treibst, am Besten von einem bestehenden Projekt.</li>

-<li>Warum willst du gerade beim Tor Projekt helfen?</li>

+<li>Warum willst du gerade beim Tor Projekt / Switzerland helfen?</li>

 <li>Erzähl uns von deinen Erfahrungen bei der Entwicklung freier Software. Wir

 würden auch gerne hören, wie du mit anderen zusammengearbeitet hast und nicht

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18763

+# Based-On-Revision: 18968

 # Last-Translator: mail [a-t] oliverknapp .de, jens @kubieziel.de

 #include "head.wmi" TITLE="Tor: Anonymität online" CHARSET="UTF-8"

@@ -71,31 +71,34 @@ href="<page donate>">spende auch du</a>!</p>

 <a id="News"></a>

 <h2><a class="anchor" href="#News">Neues</a></h2>

-<ul>

-<li>09. Februar 2009:  Tor 0.2.0.34 wurde als neue stabile Version veröffentlicht. Lies die <a

+<ul> <li>12. März 2009: Tor startet den Plan und die Kampagne für

+Geschwindigkeitsverbesserungen. Lies die <a href="<page

+press/2009-03-12-performance-roadmap-press-release>">Pressemitteilung</a> für

+weitere Informationen.</li>

+<li>09. Februar 2009: Tor 0.2.0.34 wurde als neue

+stabile Version veröffentlicht. Lies die <a

 href="http://archives.seul.org/or/announce/Feb-2009/msg00000.html">Meldung</a>

 für weitere Informationen. Diese Version behebt ein Sicherheitsproblem!</li>

 <li>21. Januar 2009: Tor 0.2.0.33 als neue stabile Version veröffentlicht.

 Schaue dir die <a

 href="http://archives.seul.org/or/announce/Jan-2009/msg00000.html">Meldung</a>

-für Genaueres an.</li>

-<li>19. Dezember 2008: Tor veröffentlicht einen Drei-Jahres-Plan für die weitere

-Entwicklung. Bitte lies die <a href="<page

+für Genaueres an.</li> <li>19. Dezember 2008: Tor veröffentlicht einen

+Drei-Jahres-Plan für die weitere Entwicklung. Bitte lies die <a href="<page

 press/2008-12-19-roadmap-press-release>">Pressemeldung</a> für mehr

 Informationen.</li>

 <li><strong>Wir suchen aktiv nach neuen Sponsoren und Geldgebern.</strong>

 Wenn deine Organisation ein Interesse an einem schnellen und gut zu

-  benutzenden Tor-Netzwerk hat, <a href="<page people>">kontaktiere

-  uns</a>. Alle <a href="<page sponsors>">Sponsoren von Tor</a>

-  bekommen persönliche Aufmerksamkeit, bessere Unterstützung und

-  öffentliche Aufmerksamkeit (wenn sie es wollen). Weiterhin erhalten

-  sie auch Einfluss auf die Richtung unserer Forschung und

-  Weiterentwicklung! Bitte <a href="<page donate>">spende</a>.</li>

-

+benutzenden Tor-Netzwerk hat, <a href="<page people>">kontaktiere uns</a>.

+Alle <a href="<page sponsors>">Sponsoren von Tor</a> bekommen persönliche

+Aufmerksamkeit, bessere Unterstützung und öffentliche Aufmerksamkeit (wenn sie

+es wollen). Weiterhin erhalten sie auch Einfluss auf die Richtung unserer

+Forschung und Weiterentwicklung! Bitte <a href="<page donate>">spende</a>.</li>

 </ul>

-<p><a href="<page news>">Mehr Neuigkeiten</a></p>

-  </div><!-- #main -->

+

+<p><a href="<page news>">Mehr Neuigkeiten</a>&nbsp;|&nbsp;<a href="<page

+press/index>">Veröffentlichungen für die Presse</a>&nbsp;|&nbsp;<a href="<page

+tormedia>">Tor in den Nachrichten</a></p> </div><!-- #main -->

 #include <foot.wmi>

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18547

+# Based-On-Revision: 19108

 # Last-Translator: mail -at- oliverknapp .de, jens @kubieziel.de

 #include "head.wmi" TITLE="Tor: Neuigkeiten" CHARSET="UTF-8"

@@ -12,7 +12,10 @@

 <h2><a class="anchor" href="#News">Tor: Neuigkeiten</a></h2>

 <hr />

-<ul>

+<ul><li>12. März 2009: Tor startet den Plan und die Kampagne für

+Geschwindigkeitsverbesserungen. Lies die <a href="<page

+press/2009-03-12-performance-roadmap-press-release>">Pressemitteilung</a> für

+weitere Informationen.</li>

 <li>09. Februar 2009:  Tor 0.2.0.34 wurde als neue stabile Version veröffentlicht. Lies die <a

 href="http://archives.seul.org/or/announce/Feb-2009/msg00000.html">Meldung</a>

 für weitere Informationen. Diese Version behebt ein Sicherheitsproblem!</li>

@@ -92,7 +95,7 @@ mit installierst. Schaue dir die englischsprachige

 href="http://archives.seul.org/or/announce/Oct-2007/msg00000.html">Ankündigung</a>

 für weitere Details an.</li>

-<li>Oct 2007: Wie viele wissen, wurde The Tor Project im Februar eine <a

+<li>Okt 2007: Wie viele wissen, wurde The Tor Project im Februar eine <a

 href="<page people>">unabhängige, offizielle Nonprofit-Organisation</a>. Wir

 haben das gemacht, um Zuwendungen von Gruppen erhalten zu können, die nur an

 NGOs spenden. Damit können Spender Spendenquittungen von uns erhalten.

@@ -106,11 +109,9 @@ Weiterhin haben sie auch unsere Wandlung in eine Nonprofit-Organisation

 betreut.</a>

 <li>Sep 2007: Falls du eine E-Mail erhalten hast, die behauptet von Tor zu

-stammen, dann war diese nicht von uns.

-Die <a href="<page download>">offiziellen Tor-Pakete</a> können über deren

-<a

-href="http://wiki.noreply.org/noreply/TheOnionRouter/VerifyingSignatures">Signatur

-als authentisch</a> bewertet werden.</li>

+stammen, dann war diese nicht von uns. Die <a href="<page download>">

+offiziellen Tor-Pakete</a> können über deren <a href="<page

+verifying-signatures>">Signatur als authentisch</a> bewertet werden.</li>

 <li>Aug 2007: <strong>Bitte bringe deine Tor-Software auf den aktuellsten

 Stand!</strong> Die letzten Versionen (stable: 0.1.2.17; development:

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18762

+# Based-On-Revision: 19085

 # Last-Translator: mail (a-t) oliverknapp .de

 #include "head.wmi" TITLE="The Tor Project in den Medien" CHARSET="UTF-8"

@@ -24,10 +24,15 @@ Beispiele:</p>

 </tr>

 </thead>

+<td>12. März 2009</td>

+<td>BBC World Service</td>

+<td><a href="http://bbcworldservicetrust.wordpress.com/2009/03/12/12-march-world-day-against-cyber-censorship/">Steven J Murdoch im Interview über Tor und Zensur</a></td>

+</tr>

+<tr>

 <tr>

 <td>2009 Feb 13</td>

 <td>Hearsay Culture</td>

-<td><a href="http://www.hearsayculture.com/">Hearsay Culture Radio Interview/Podcast</a></td>

+<td><a href="http://www.hearsayculture.com/?p=307">Hearsay Culture Radio Interview/Podcast</a></td>

 </tr>

 <tr style="background-color: #e5e5e5;">

 <td>2008 Dec 29</td>

@@ -112,7 +117,17 @@ Artikel.</p>

 <th>Thema</th>

 </tr>

 </thead>

-

+<tr>

+<td>18. März 2009</td>

+<td>Marie Claire</td>

+<td><a href="http://www.marieclaire.com/career-money/career-coach/manage-online--web-image">How to Manage Your Web Footprint</a></td>

+</tr>

+<tr>

+<td>13. März 2009</td>

+<td>Wall Street Journal</td>

+<td><a href="http://online.wsj.com/article/SB123567809587886053.html">The Kindness of Strangers</a>

+</tr>

+<tr style="background-color: #e5e5e5;">

 <tr>

 <td>2009 Mar 03</td>

 <td>Orf Austria</td>

@@ -1,5 +1,5 @@

 ## translation metadata

-# Based-On-Revision: 18921

+# Based-On-Revision: 18944

 # Last-Translator: mail 11 oliverknapp 22 de

 #include "head.wmi" TITLE="Tor: Mithelfen" CHARSET="UTF-8"

@@ -112,50 +112,82 @@

   Übersetzungen</a>.</li>

   </ol>

-<a id="Coding"></a>

-  <p>Die untenstehenden Angaben wurden in der Originalsprache

-  belassen. Da diese sich ausschließlich auf englischsprachige

-  Bewerber beziehen.</p>

+<a id="Coding"></a> <p>Die untenstehenden Angaben wurden in der

+Originalsprache belassen. Da diese sich ausschließlich auf Bewerber beziehen,

+die ausreichende Englischkenntnisse besitzen.</p>

   <a id="Summer"></a>

 <a id="Projects"></a>

 <h2><a class="anchor" href="#Projects">Good Coding Projects</a></h2>

 <p>

-Here is a list of ideas that were proposed for the <a href="<page gsoc>">Google Summer of Code 2009</a>

-but have not been put into practice. Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a> 

-might also be short on developers. If you think you can help out, <a href="<page contact>"> let us know!</a> 

+You may find some of these projects to be good <a href="<page

+gsoc>">Google Summer of Code 2009</a> ideas. We have labelled each idea

+with how useful it would be to the overall Tor project (priority), how

+much work we expect it would be (effort level), how much clue you should

+start with (skill level), and which of our <a href="<page

+people>#Core">core developers</a> would be good mentors.

+If one or more of these ideas looks promising to you, please <a

+href="<page contact>">contact us</a> to discuss your plans rather than

+sending blind applications. You may also want to propose your own project

+idea which often results in the best applications.

 </p>

 <ol>

-<!-- Mike is already working on this

+

 <li>

-<b>Tor Node Scanner improvements</b>

+<b>Tor Browser Bundle for Linux/Mac OS X</b>

 <br />

-Similar to the SoaT exit scanner (or perhaps even during exit scanning),

-statistics can be gathered about the reliability of nodes. Nodes that

-fail too high a percentage of their circuits should not be given

-Guard status. Perhaps they should have their reported bandwidth

-penalized by some ratio as well, or just get marked as Invalid. In

-addition, nodes that exhibit a very low average stream capacity but

-advertise a very high node bandwidth can also be marked as Invalid.

-Much of this statistics gathering is already done, it just needs to be

-transformed into something that can be reported to the Directory

-Authorities to blacklist/penalize nodes in such a way that clients

-will listen.

+Priority: <i>High</i>

 <br />

-In addition, these same statistics can be gathered about the traffic

-through a node. Events can be added to the <a

-href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor Control

-Protocol</a> to

-report if a circuit extend attempt through the node succeeds or fails, and

-passive statistics can be gathered on both bandwidth and reliability

-of other nodes via a node-based monitor using these events. Such a

-scanner would also report information on oddly-behaving nodes to

-the Directory Authorities, but a communication channel for this

-currently does not exist and would need to be developed as well.

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Steven, Andrew</i>

+<br />

+The Tor Browser bundle incorporates Tor, Firefox, and the Vidalia user

+interface (and optionally Pidgin IM). Components are pre-configured to

+operate in a secure way, and it has very few dependencies on the

+installed operating system. It has therefore become one of the most

+easy to use, and popular, ways to use Tor on Windows.

+<br />

+However, there is currently no comparable package for Linux and Mac OS

+X, so this project would be to implement Tor Browser Bundle for these

+platforms. This will involve modifications to Vidalia (C++), possibly

+Firefox (C) then creating and testing the launcher on a range of

+operating system versions and configurations to verify portability.

+<br />

+Students should be familiar with application development on one or

+preferably both of Linux and Mac OS X, and be comfortable with C/C++

+and shell scripting.

+<br />

+Part of this project could be usability testing of Tor Browser Bundle,

+ideally amongst our target demographic.

+That would help a lot in knowing what needs to be done in terms of bug

+fixes or new features. We get this informally at the moment, but a more

+structured process would be better.

+</li>

+

+<li>

+<b>Translation wiki for our website</b>

+<br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Jacob</i>

+<br />

+The Tor Project has been working over the past year to set up web-based

+tools to help volunteers translate our applications into other languages.

+We finally hit upon Pootle, and we have a fine web-based translation engine

+in place for Vidalia, Torbutton, and Torcheck. However, Pootle only

+translates strings that are in the "po" format, and our website uses wml

+files. This project is about finding a way to convert our wml files into po

+strings and back, so they can be handled by Pootle.

 </li>

- -->

 <li>

 <b>Help track the overall Tor Network status</b>

@@ -166,7 +198,7 @@ Effort Level: <i>Medium</i>

 <br />

 Skill Level: <i>Medium</i>

 <br />

-Likely Mentors: <i>Karsten</i>

+Likely Mentors: <i>Karsten, Roger</i>

 <br />

 It would be great to set up an automated system for tracking network

 health over time, graphing it, etc. Part of this project would involve

@@ -177,8 +209,8 @@ in terms of new relays showing up and relays shutting off? Periodically

 people collect brief snapshots, but where it gets really interesting is

 when we start tracking data points over time.

 <br />

-Data could be collected from the "Tor Node Scanner" in

-<a href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from

+Data could be collected from the Tor Network Scanners in <a

+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from

 the server descriptors that each relay publishes, and from other

 sources. Results over time could be integrated into one of the <a

 href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be

@@ -187,62 +219,16 @@ kept separate. Speaking of the Tor Status pages, take a look at Roger's

 Status wish list</a>.

 </li>

-<!-- Is this still a useful project? If so, move it to another section.

-<li>

-<b>Better Debian/Ubuntu Packaging for Tor+Vidalia</b>

-<br />

-Vidalia currently doesn't play nicely on Debian and Ubuntu with the

-default Tor packages. The current Tor packages automatically start Tor

-as a daemon running as the debian-tor user and (sensibly) do not have a

-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined

-in the default torrc. Consequently, Vidalia will try

-to start its own Tor process since it could not connect to the existing

-Tor, and Vidalia's Tor process will then exit with an error message

-the user likely doesn't understand since Tor cannot bind its listening

-ports — they're already in use by the original Tor daemon.

-<br />

-The current solution involves either telling the user to stop the

-existing Tor daemon and let Vidalia start its own Tor process, or

-explaining to the user how to set a control port and password in their

-torrc. A better solution on Debian would be to use Tor's ControlSocket,

-which allows Vidalia to talk to Tor via a Unix domain socket, and could

-possibly be enabled by default in Tor's Debian packages. Vidalia can

-then authenticate to Tor using filesystem-based (cookie) authentication

-if the user running Vidalia is also in the debian-tor group.

-<br />

-This project will first involve adding support for Tor's ControlSocket

-to Vidalia. The student will then develop and test Debian and Ubuntu

-packages for Vidalia that conform to Debian's packaging standards and

-make sure they work well with the existing Tor packages. We can also

-set up an apt repository to host the new Vidalia packages.

-<br />

-The next challenge would be to find an intuitive usable way for Vidalia

-to be able to change Tor's configuration (torrc) even though it is

-located in <code>/etc/tor/torrc</code> and thus immutable. The best

-idea we've come up with so far is to feed Tor a new configuration via

-the ControlSocket when Vidalia starts, but that's bad because Tor starts

-each boot with a different configuration than the user wants. The second

-best idea

-we've come up with is for Vidalia to write out a temporary torrc file

-and ask the user to manually move it to <code>/etc/tor/torrc</code>,

-but that's bad because users shouldn't have to mess with files directly.

-<br />

-A person undertaking this project should have prior knowledge of

-Debian package management and some C++ development experience. Previous

-experience with Qt is helpful, but not required.

-</li>

--->

-	 

 <li>

 <b>Improving Tor's ability to resist censorship</b>

 <br />

-Priority: <i>High</i>

+Priority: <i>Medium to High</i>

 <br />

-Effort Level: <i>High</i>

+Effort Level: <i>Medium</i>

 <br />

 Skill Level: <i>High</i>

 <br />

-Likely Mentors: <i>Nick</i>

+Likely Mentors: <i>Nick, Roger, Steven</i>

 <br />

 The Tor 0.2.0.x series makes <a

 href="<svnsandbox>doc/design-paper/blocking.html">significant

@@ -268,74 +254,83 @@ resist an adversary even after the adversary knows the design, and

 then trading off censorship resistance with usability and robustness.

 </li>

-<!-- This should be mostly done.

 <li>

-<b>Tor/Polipo/Vidalia Auto-Update Framework</b>

+<b>Tuneup Tor!</b>

 <br />

-We're in need of a good authenticated-update framework.

-Vidalia already has the ability to notice when the user is running an

-outdated or unrecommended version of Tor, using signed statements inside

-the Tor directory information. Currently, Vidalia simply pops

-up a little message box that lets the user know they should manually

-upgrade. The goal of this project would be to extend Vidalia with the

-ability to also fetch and install the updated Tor software for the

-user. We should do the fetches via Tor when possible, but also fall back

-to direct fetches in a smart way. Time permitting, we would also like

-to be able to update other

-applications included in the bundled installers, such as Polipo and

-Vidalia itself.

+Priority: <i>Medium to High</i>

 <br />

-To complete this project, the student will first need to first investigate

-the existing auto-update frameworks (e.g., Sparkle on OS X) to evaluate

-their strengths, weaknesses, security properties, and ability to be

-integrated into Vidalia. If none are found to be suitable, the student

-will design their own auto-update framework, document the design, and

-then discuss the design with other developers to assess any security

-issues. The student will then implement their framework (or integrate

-an existing one) and test it.

+Effort Level: <i>Medium to High</i>

 <br />

-A person undertaking this project should have good C++ development

-experience. Previous experience with Qt is helpful, but not required. One

-should also have a good understanding of common security

-practices, such as package signature verification. Good writing ability

-is also important for this project, since a vital step of the project

-will be producing a design document to review and discuss

-with others prior to implementation.

+Skill Level: <i>High</i>

+<br />

+Likely Mentors: <i>Nick, Roger, Mike, Karsten</i>

+<br />

+Right now, Tor relays measure and report their own bandwidth, and Tor

+clients choose which relays to use in part based on that bandwidth.

+This approach is vulnerable to

+<a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where

+relays lie about their bandwidth</a>;

+to address this, Tor currently caps the maximum bandwidth

+it's willing to believe any relay provides.  This is a limited fix, and

+a waste of bandwidth capacity to boot.  Instead,

+Tor should possibly measure bandwidth in a more distributed way, perhaps

+as described in the

+<a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for

+Tor"</a> paper

+by Snader and Borisov. One could use current testing code to

+double-check this paper's findings and verify the extent to which they

+dovetail with Tor as deployed in the wild, and determine good ways to

+incorporate them into their suggestions Tor network without adding too

+much communications overhead between relays and directory

+authorities.

 </li>

--->

 <li>

-<b>An Improved and More Usable Network Map in Vidalia</b>

+<b>Improving Polipo on Windows</b>

 <br />

-Priority: <i>Medium</i>

+Priority: <i>Medium to High</i>

 <br />

 Effort Level: <i>Medium</i>

 <br />

 Skill Level: <i>Medium</i>

 <br />

-Likely Mentors: <i>Matt</i>

+Likely Mentors: <i>Martin</i>

 <br />

-One of Vidalia's existing features is a network map that shows the user

-the approximate geographic location of relays in the Tor network and

-plots the paths the user's traffic takes as it is tunneled through the

-Tor network. The map is currently not very interactive and has rather

-poor graphics. Instead, we implemented KDE's Marble widget such

-that it gives us a better quality map and enables improved interactivity,

-such as allowing the user to click on individual relays or circuits to

-display additional information. We want to add the ability

-for users to click on a particular relay or a country containing one or

-more Tor exit relays and say, "I want my connections to exit

-from here."

+Help port <a

+href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to

+Windows. Example topics to tackle include:

+1) the ability to asynchronously

+query name servers, find the system nameservers, and manage netbios

+and dns queries.

+2) manage events and buffers

+natively (i.e. in Unix-like OSes, Polipo defaults to 25% of ram, in

+Windows it's whatever the config specifies). 3) some sort of GUI config

+and reporting tool, bonus if it has a systray icon with right clickable

+menu options. Double bonus if it's cross-platform compatible.

+4) allow the software to use the Windows Registry and handle proper Windows directory locations, such as "C:\Program Files\Polipo"

+</li>

+

+<li>

+<b>Implement a torrent-based scheme for downloading Thandy packages</b>

 <br />

-This project will first involve getting familiar with Vidalia

-and the Marble widget's API. One will then integrate the widget

-into Vidalia and customize Marble to be better suited for our application,

-such as making circuits clickable, storing cached map data in Vidalia's

-own data directory, and customizing some of the widget's dialogs.

+Priority: <i>Medium to High</i>

 <br />

-A person undertaking this project should have good C++ development

-experience. Previous experience with Qt and CMake is helpful, but not

-required.

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Martin, Nick</i>

+<br />

+<a

+href="http://git.torproject.org/checkout/thandy/master/specs/thandy-spec.txt">Thandy</a>

+is a relatively new software to allow assisted updates of Tor and related

+software. Currently, there are very few users, but we expect Thandy to be

+used by almost every Tor user in the future. To avoid crashing servers on

+the day of a Tor update, we need new ways to distribute new packages

+efficiently, and using libtorrent seems to be a possible solution. If you

+think of other good ideas, great - please do let us know!<br />

+We also need to investigate how to include our mirrors better. If possible,

+there should be an easy way for them to help distributing the packages.

 </li>

 <li>

@@ -345,7 +340,7 @@ Priority: <i>Medium</i>

 <br />

 Effort Level: <i>Medium</i>

 <br />

-Skill Level: <i>Medium</i>

+Skill Level: <i>Low to Medium</i>

 <br />

 Likely Mentors: <i>Matt</i>

 <br />

@@ -381,167 +376,16 @@ be understandable by non-technical users. Bonus points for some graphic

 design/Photoshop fu, since we might want/need some shiny new icons too.

 </li>

-<!-- Jake already did most of this.

 <li>

-<b>Improvements on our active browser configuration tester</b> -

-<a href="https://check.torproject.org/">https://check.torproject.org/</a>

+<b>Improve our unit testing process</b>

 <br />

-We currently have a functional web page to detect if Tor is working. It

-has a few places where it falls short. It requires improvements with

-regard to default languages and functionality. It currently only responds

-in English. In addition, it is a hack of a perl script that should have

-never seen the light of day. It should probably be rewritten in python

-with multi-lingual support in mind. It currently uses the <a

-href="http://exitlist.torproject.org/">Tor DNS exit list</a>

-and should continue to do so in the future. It currently result in certain

-false positives and these should be discovered, documented, and fixed

-where possible. Anyone working on this project should be interested in

-DNS, basic perl or preferably python programming skills, and will have

-to interact minimally with Tor to test their code.

-<br />

-If you want to make the project more exciting

-and involve more design and coding, take a look at <a

-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal

-131-verify-tor-usage.txt</a>.

-</li>

--->

-

-<!-- If we decide to switch to the exit list in TorStatus, this is obsolete.

-<li>

-<b>Improvements on our DNS Exit List service</b> -

-<a href="http://exitlist.torproject.org/">http://exitlist.torproject.org/</a>

-<br />

-The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>

-is written by our fabulous anonymous

-contributer Tup. It's a DNS server written in Haskell that supports part of our <a

-href="<svnsandbox>doc/contrib/torel-design.txt">exitlist

-design document</a>. Currently, it is functional and it is used by

-check.torproject.org and other users. The issues that are outstanding

-are mostly aesthetic. This wonderful service could use a much better

-website using the common Tor theme. It would be best served with better

-documentation for common services that use an RBL. It could use more

-publicity. A person working on this project should be interested in DNS,

-basic RBL configuration for popular services, and writing documentation.

-The person would require minimal Tor interaction — testing their

-own documentation at the very least. Furthermore, it would be useful

-if they were interested in Haskell and wanted to implement more of the

-torel-design.txt suggestions.

-</li>

--->

-

-<!-- Nobody wanted to keep this.

-<li>

-<b>Testing integration of Tor with web browsers for our end users</b>

-<br />

-The Tor project currently lacks a solid test suite to ensure that a

-user has a properly and safely configured web browser. It should test for as

-many known issues as possible. It should attempt to decloak the

-user in any way possible. Two current webpages that track these

-kinds of issues are run by Greg Fleischer and HD Moore. Greg keeps a nice <a

-href="http://pseudo-flaw.net/tor/torbutton/">list of issues along

-with their proof of concept code, bug issues, etc</a>. HD Moore runs

-the <a href="http://www.decloak.net/">metasploit

-decloak website</a>. A person interested in defending Tor could start

-by collecting as many workable and known methods for decloaking a

-Tor user. (<a href="https://torcheck.xenobite.eu/">This page</a> may

-be helpful as a start.) One should be familiar with the common pitfalls but

-possibly have new methods in mind for implementing decloaking issues. The

-website should ensure that it tells a user what their problem is. It

-should help them to fix the problem or direct them to the proper support

-channels. The person should also be closely familiar with using Tor and how

-to prevent Tor information leakage.

-</li>

--->

-

-<!-- Nick did quite some work here. Is this project still required then?

-<li>

-<b>Libevent and Tor integration improvements</b>

-<br />

-Tor should make better use of the more recent features of Niels

-Provos's <a href="http://monkey.org/~provos/libevent/">Libevent</a>

-library.  Tor already uses Libevent for its low-level asynchronous IO

-calls, and could also use Libevent's increasingly good implementations

-of network buffers and of HTTP.  This wouldn't be simply a matter of

-replacing Tor's internal calls with calls to Libevent: instead, we'll

-need to refactor Tor to use Libevent calls that do not follow the

-same models as Tor's existing backends. Also, we'll need to add

-missing functionality to Libevent as needed — most difficult likely

-will be adding OpenSSL support on top of Libevent's buffer abstraction.

-Also tricky will be adding rate-limiting to Libevent.

-</li>

--->

-

-<li>

-<b>Tuneup Tor!</b>

-<br />

-Priority: <i>Medium</i>

-<br />

-Effort Level: <i>Medium</i>

-<br />

-Skill Level: <i>Medium to High</i>

-<br />

-Likely Mentors: <i>Nick, Roger, Mike</i>

-<br />

-Right now, Tor relays measure and report their own bandwidth, and Tor

-clients choose which relays to use in part based on that bandwidth.

-This approach is vulnerable to

-<a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where

-relays lie about their bandwidth</a>;

-to address this, Tor currently caps the maximum bandwidth

-it's willing to believe any relay provides.  This is a limited fix, and

-a waste of bandwidth capacity to boot.  Instead,

-Tor should possibly measure bandwidth in a more distributed way, perhaps

-as described in the

-<a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for

-Tor"</a> paper

-by Snader and Borisov. One could use current testing code to

-double-check this paper's findings and verify the extent to which they

-dovetail with Tor as deployed in the wild, and determine good ways to

-incorporate them into their suggestions Tor network without adding too

-much communications overhead between relays and directory

-authorities.

-</li>

-

-<!--

-<li>

-<b>Improving the Tor QA process: Continuous Integration for Windows builds</b>

-<br />

-It would be useful to have automated build processes for Windows and

-probably other platforms. The purpose of having a continuous integration

-build environment is to ensure that Windows isn't left behind for any of

-the software projects used in the Tor project or its accompanying.<br />

-Buildbot may be a good choice for this as it appears to support all of

-the platforms Tor does. See the

-<a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for

-buildbot</a>.<br />

-There may be better options and the person undertaking this task should

-evaluate other options. Any person working on this automatic build

-process should have experience or be willing to learn how to build all

-of the respective Tor related code bases from scratch. Furthermore, the

-person should have some experience building software in Windows

-environments as this is the target audience we want to ensure we do not

-leave behind. It would require close work with the Tor source code but

-probably only in the form of building, not authoring.<br />

-Additionally, we need to automate our performance testing for all platforms.

-We've got buildbot (except on Windows — as noted above) to automate

-our regular integration and compile testing already,

-but we need to get our network simulation tests (as built in torflow)

-updated for more recent versions of Tor, and designed to launch a test

-network either on a single machine, or across several, so we can test

-changes in performance on machines in different roles automatically.

-</li>

--->

-

-<li>

-<b>Improve our unit testing process</b>

-<br />

-Priority: <i>Medium</i>

+Priority: <i>Medium</i>

 <br />

 Effort Level: <i>Medium</i>

 <br />

 Skill Level: <i>Medium</i>

 <br />

-Likely Mentors: <i>Nick</i>

+Likely Mentors: <i>Nick, Roger</i>

 <br />

 Tor needs to be far more tested. This is a multi-part effort. To start

 with, our unit test coverage should rise substantially, especially in

@@ -590,12 +434,137 @@ to a small degree about design.

 </li>

 <li>

-<b>Bring moniTor to life</b>

+<b>New Torbutton Features</b>

+<br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>High</i>

+<br />

+Likely Mentors: <i>Mike</i>

+<br/>

+There are several <a

+href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5&type=2">good

+feature requests</a> on the Torbutton Flyspray section. In particular, <a

+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=523">Integrating

+'New Identity' with Vidalia</a>,

+<a href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=940">ways of

+managing multiple cookie jars/identities</a>, <a

+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=637">preserving

+specific cookies</a> when cookies are cleared,

+<a

+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=524">better

+referrer spoofing</a>, <a

+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=564">correct

+Tor status reporting</a>, and <a

+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=462">"tor://"

+and "tors://" urls</a> are all interesting

+features that could be added.

+<br />

+This work would be independent coding in Javascript and the fun world of <a

+href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,

+with not too much involvement in the Tor internals.

+</li>

+

+<li>

+<b>New Thandy Features</b>

+<br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Martin</i>

+<br />

+Additional capabilities are needed for assisted updates of all the Tor

+related software for Windows and other operating systems. Some of the

+features to consider include:

+1) Integration of the <a

+href="http://chandlerproject.org/Projects/MeTooCrypto">MeTooCrypto

+Python library</a>

+for authenticated HTTPS downloads. 2) Adding a level of indirection

+between the timestamp signatures and the package files included in an

+update. See the "Thandy attacks / suggestions" thread on or-dev.

+3) Support locale specific installation and configuration of assisted

+updates based on preference, host, or user account language settings.

+Familiarity with Windows codepages, unicode, and other character sets

+is helpful in addition to general win32 and posix API experience and

+Python proficiency.

+</li>

+

+<li>

+<b>Simulator for slow Internet connections</b>

 <br />

 Priority: <i>Medium</i>

 <br />

 Effort Level: <i>Medium</i>

 <br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Steven</i>

+<br />

+Many users of Tor have poor-quality Internet connections, giving low

+bandwidth, high latency, and high packet loss/re-ordering. User

+experience is that Tor reacts badly to these conditions, but it is

+difficult to improve the situation without being able to repeat the

+problems in the lab.

+<br />

+This project would be to build a simulation environment which

+replicates the poor connectivity so that the effect on Tor performance

+can be measured. Other components would be a testing utility to

+establish what are the properties of connections available, and to

+measure the effect of performance-improving modifications to Tor.

+<br />

+The tools used would be up to the student, but dummynet (for FreeBSD)

+and nistnet (for Linux) are two potential components on which this

+project could be built. Students should be experienced with network

+programming/debugging and TCP/IP, and preferably familiar with C and a

+scripting language.

+</li>

+

+<li>

+<b>An Improved and More Usable Network Map in Vidalia</b>

+<br />

+Priority: <i>Low to Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Matt</i>

+<br />

+One of Vidalia's existing features is a network map that shows the user

+the approximate geographic location of relays in the Tor network and

+plots the paths the user's traffic takes as it is tunneled through the

+Tor network. The map is currently not very interactive and has rather

+poor graphics. Instead, we implemented KDE's Marble widget such

+that it gives us a better quality map and enables improved interactivity,

+such as allowing the user to click on individual relays or circuits to

+display additional information. We want to add the ability

+for users to click on a particular relay or a country containing one or

+more Tor exit relays and say, "I want my connections to exit

+from here."

+<br />

+This project will first involve getting familiar with Vidalia

+and the Marble widget's API. One will then integrate the widget

+into Vidalia and customize Marble to be better suited for our application,

+such as making circuits clickable, storing cached map data in Vidalia's

+own data directory, and customizing some of the widget's dialogs.

+<br />

+A person undertaking this project should have good C++ development

+experience. Previous experience with Qt and CMake is helpful, but not

+required.

+</li>

+

+<li>

+<b>Bring moniTor to life</b>

+<br />

+Priority: <i>Low</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

 Skill Level: <i>Low to Medium</i>

 <br />

 Likely Mentors: <i>Karsten, Jacob</i>

@@ -616,6 +585,285 @@ project is one part about identifying requirements to such a

 tool and designing its interface, and one part lots of coding.

 </li>

+<li>

+<b>Torbutton equivalent for Thunderbird</b>

+<br />

+Priority: <i>Low</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>High</i>

+<br />

+Likely Mentors: <i>Mike</i>

+<br />

+We're hearing from an increasing number of users that they want to use

+Thunderbird with Tor. However, there are plenty of application-level

+concerns, for example, by default Thunderbird will put your hostname in

+the outgoing mail that it sends. At some point we should start a new

+push to build a Thunderbird extension similar to Torbutton.

+</li>

+

+<li>

+<b>Intermediate Level Network Device Driver</b>

+<br />

+Priority: <i>Low</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>High</i>

+<br />

+Likely Mentors: <i>Martin</i>

+<br />

+The WinPCAP device driver used by Tor VM for bridged networking does

+not support a number of wireless and non-Ethernet network adapters.

+Implementation of a intermediate level network device driver for win32

+and 64bit would provide a way to intercept and route traffic over such

+networks. This project will require knowledge of and experience with

+Windows kernel device driver development and testing. Familiarity with

+Winsock and Qemu would also be helpful.

+</li>

+

+<li>

+<b>Bring up new ideas!</b>

+<br />

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

+href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development

+roadmap</a> for more ideas.

+Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>

+might also be short on developers.

+</li>

+

+<!-- Mike is already working on this.

+<li>

+<b>Tor Node Scanner improvements</b>

+<br />

+Similar to the SoaT exit scanner (or perhaps even during exit scanning),

+statistics can be gathered about the reliability of nodes. Nodes that

+fail too high a percentage of their circuits should not be given

+Guard status. Perhaps they should have their reported bandwidth

+penalized by some ratio as well, or just get marked as Invalid. In

+addition, nodes that exhibit a very low average stream capacity but

+advertise a very high node bandwidth can also be marked as Invalid.

+Much of this statistics gathering is already done, it just needs to be

+transformed into something that can be reported to the Directory

+Authorities to blacklist/penalize nodes in such a way that clients

+will listen.

+<br />

+In addition, these same statistics can be gathered about the traffic

+through a node. Events can be added to the <a

+href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor Control

+Protocol</a> to

+report if a circuit extend attempt through the node succeeds or fails, and

+passive statistics can be gathered on both bandwidth and reliability

+of other nodes via a node-based monitor using these events. Such a

+scanner would also report information on oddly-behaving nodes to

+the Directory Authorities, but a communication channel for this

+currently does not exist and would need to be developed as well.

+</li>

+-->

+

+<!-- Is this still a useful project? If so, move it to another section.

+<li>

+<b>Better Debian/Ubuntu Packaging for Tor+Vidalia</b>

+<br />

+Vidalia currently doesn't play nicely on Debian and Ubuntu with the

+default Tor packages. The current Tor packages automatically start Tor

+as a daemon running as the debian-tor user and (sensibly) do not have a

+<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined

+in the default torrc. Consequently, Vidalia will try

+to start its own Tor process since it could not connect to the existing

+Tor, and Vidalia's Tor process will then exit with an error message

+the user likely doesn't understand since Tor cannot bind its listening

+ports — they're already in use by the original Tor daemon.

+<br />

+The current solution involves either telling the user to stop the

+existing Tor daemon and let Vidalia start its own Tor process, or

+explaining to the user how to set a control port and password in their

+torrc. A better solution on Debian would be to use Tor's ControlSocket,

+which allows Vidalia to talk to Tor via a Unix domain socket, and could

+possibly be enabled by default in Tor's Debian packages. Vidalia can

+then authenticate to Tor using filesystem-based (cookie) authentication

+if the user running Vidalia is also in the debian-tor group.

+<br />

+This project will first involve adding support for Tor's ControlSocket

+to Vidalia. The student will then develop and test Debian and Ubuntu

+packages for Vidalia that conform to Debian's packaging standards and

+make sure they work well with the existing Tor packages. We can also

+set up an apt repository to host the new Vidalia packages.

+<br />

+The next challenge would be to find an intuitive usable way for Vidalia

+to be able to change Tor's configuration (torrc) even though it is

+located in <code>/etc/tor/torrc</code> and thus immutable. The best

+idea we've come up with so far is to feed Tor a new configuration via

+the ControlSocket when Vidalia starts, but that's bad because Tor starts

+each boot with a different configuration than the user wants. The second

+best idea

+we've come up with is for Vidalia to write out a temporary torrc file

+and ask the user to manually move it to <code>/etc/tor/torrc</code>,

+but that's bad because users shouldn't have to mess with files directly.

+<br />

+A person undertaking this project should have prior knowledge of

+Debian package management and some C++ development experience. Previous

+experience with Qt is helpful, but not required.

+</li>

+-->

+

+<!-- This should be mostly done.

+<li>

+<b>Tor/Polipo/Vidalia Auto-Update Framework</b>

+<br />

+We're in need of a good authenticated-update framework.

+Vidalia already has the ability to notice when the user is running an

+outdated or unrecommended version of Tor, using signed statements inside

+the Tor directory information. Currently, Vidalia simply pops

+up a little message box that lets the user know they should manually

+upgrade. The goal of this project would be to extend Vidalia with the

+ability to also fetch and install the updated Tor software for the

+user. We should do the fetches via Tor when possible, but also fall back

+to direct fetches in a smart way. Time permitting, we would also like