tor-webwml.git

de/volunteer.wml         1) ## translation metadata

de/volunteer.wml         2) # Based-On-Revision: 18921

de/volunteer.wml         3) # Last-Translator: mail 11 oliverknapp 22 de

de/volunteer.de.html     4) 

de/volunteer.wml         5) #include "head.wmi" TITLE="Tor: Mithelfen" CHARSET="UTF-8"

de/contribute.de.html    6) 
de/contribute.de.html    7) <div class="main-column">
de/contribute.de.html    8) 
de/contribute.de.html    9) <!-- PUT CONTENT AFTER THIS TAG -->
de/contribute.de.html   10) 

de/volunteer.wml        11) <h2>Einige Dinge, die jeder tun kann</h2>

de/contribute.de.html   12) 

de/volunteer.de.html    13) <ol>

de/volunteer.wml        14)   <li>Bitte überlege dir,

de/volunteer.wml        15)     einen <a href="<page docs/tor-doc-relay>">Server zu

de/volunteer.wml        16)     betreiben</a>, damit das Netzwerk weiter wächst.</li>
de/volunteer.wml        17)   <li>Erzähl es deinen Freunden! Bringe sie dazu, auch Server zu

de/volunteer.de.html    18)     betreiben.  Bringe sie dazu, auch versteckte Services zu
de/volunteer.de.html    19)     betreiben. Bringe sie dazu, es wieder ihren Freunden zu

de/volunteer.wml        20)     erzählen.</li>

de/volunteer.wml        21)   <li>Wenn du die Ziele von Tor magst, bitte nimm dir einen Moment

de/volunteer.wml        22)   Zeit, um für das <a href="<page donate>">Projekt zu spenden</a>. Wir

de/volunteer.wml        23)   sind auch auf der Suche nach weiteren Sponsoren — wenn du

de/volunteer.wml        24)   Firmen, NGOs oder andere Organisationen kennst, die Anonymität,
de/volunteer.wml        25)   Privatsphäre und die Sicherheit der Kommunikation schätzen, dann

de/volunteer.wml        26)   lass sie von uns wissen.</li>
de/volunteer.wml        27)   <li>Wir suchen nach weiteren <a href="<page torusers>">guten

de/volunteer.wml        28)   Beispielen für Nutzer von Tor oder von Anwendungsfällen</a>. Falls
de/volunteer.wml        29)   du Tor für ein bestimmtes Szenario verwendest und uns davon erzählen
de/volunteer.wml        30)   möchtest, freuen wir uns, darüber zu hören.</li>

de/volunteer.wml        31)   </ol>
de/volunteer.wml        32) 

de/volunteer.wml        33) <a id="Usability"></a>

de/volunteer.wml        34) <h2><a class="anchor" href="#Usability">unterstützende Anwendungen</a></h2>

de/volunteer.de.html    35) 
de/volunteer.de.html    36) <ol>

de/volunteer.wml        37)   <li>Wir brauchen mehr und bessere Methoden, um DNS-Abfragen abzufangen, damit diese

de/volunteer.wml        38)   nicht an einen lokalen Beobachter dringen, während wir versuchen, anonym zu

de/volunteer.wml        39)   bleiben. (Dies passiert, weil die Anwendung selbst DNS-Anfragen

de/volunteer.wml        40)   stellt, anstatt diese über Tor zu leiten.).

de/volunteer.wml        41)   <ul>

de/volunteer.wml        42)     <li>Wir müssen <a

de/volunteer.wml        43)     href="https://wiki.torproject.org/noreply/TheOnionRouter/TSocksPatches">all

de/volunteer.wml        44)     unsere Patches für tsocks</a> einspielen und einen Fork
de/volunteer.wml        45)     betreuen. Wir würden diesen auch auf unserem Server mit anbieten, wenn
de/volunteer.wml        46)     du möchtest.</li>

de/volunteer.wml        47)     <li>Wir sollten das Programm dsocks von Dug Song patchen, so dass es
de/volunteer.wml        48)     das Kommando <code>mapaddress</code> von der Controllerschnittstelle
de/volunteer.wml        49)     nutzt. Somit verschwenden wir nicht einen gesamten Round-trip

de/volunteer.wml        50)     innerhalb von Tor, um die Auflösung vor der Verbindung zu

de/volunteer.wml        51)     machen.</li>

de/volunteer.wml        52)     <li>Wir müssen unser <kbd>torify</kbd>-Skript so umgestalten, dass

de/volunteer.wml        53)     es erkennt, welches tsocks oder dsocks installiert ist und dieses
de/volunteer.wml        54)     dann richtig aufruft. Das bedeutet wahrscheinlich, dass deren

de/volunteer.wml        55)     Schnittstellen vereinheitlicht werden müssen und führt wahrscheinlich

de/volunteer.wml        56)     dazu, dass Code zwischen beiden geteilt werden muss oder dass eines
de/volunteer.wml        57)     komplett nicht mehr benutzt wird.</li>
de/volunteer.wml        58)   </ul></li>

de/volunteer.de.html    59)   <li>Leute, die einen Server betreiben, teilen uns immer wieder mit,

de/volunteer.wml        60)     dass sie <var>BandwidthRate</var> in Abhängigkeit von der Uhrzeit setzen

de/volunteer.wml        61)     wollen. Anstatt das

de/volunteer.de.html    62)     direkt in Tor zu implementieren, sollten wir lieber ein kleines

de/volunteer.wml        63)     Skript haben, das über die <a href="<page gui/index>">Torschnittstelle</a>
de/volunteer.wml        64)     spricht und ein <code>setconf</code> macht, um die Änderungen
de/volunteer.wml        65)     herbeizuführen. Natürlich würde es durch Cron ausgeführt oder es
de/volunteer.wml        66)     schläft eine bestimmte Zeit und macht dann die Änderungen. Kann
de/volunteer.wml        67)     das jemand für uns schreiben und wir packen das dann
de/volunteer.wml        68)     nach <a href="<svnsandbox>contrib/">contrib</a>? Das wäre
de/volunteer.wml        69)   eine gute Möglichkeit für den <a href="<page gui/index>">Tor GUI

de/volunteer.wml        70)   Wettbewerb</a>.</li>

de/volunteer.wml        71)   <li>Wenn wir gerade bei Geolocation sind, wäre es schön, wenn

de/volunteer.de.html    72)     jemand eine Karte anfertigt, die die Standorte der Torserver

de/volunteer.wml        73)     anzeigt. Bonuspunkte gibt es, wenn es sich bei Änderungen am

de/volunteer.wml        74)     Netzwerk auf den neuesten Stand bringt. Der leichteste Weg, um

de/volunteer.wml        75)   dies zu erreichen, wäre alle Daten zu Google zu schicken und diese
de/volunteer.wml        76)   machen dann die Karte für uns. Wie sehr beeinflusst dies die
de/volunteer.wml        77)   Privatsphäre und haben wir noch andere gute Optionen?</li>

de/volunteer.wml        78) </ol>
de/volunteer.wml        79) 
de/volunteer.wml        80) <a id="Advocacy"></a>
de/volunteer.wml        81) <h2><a class="anchor" href="#Advocacy">Tor-Botschafter</a></h2>
de/volunteer.wml        82) <ol>
de/volunteer.wml        83) <li>Baue ein Communitylogo unter einer Creative Commons Lizenz, das alle benutzen und verändern dürfen</li>
de/volunteer.wml        84) <li>Mache eine Präsentation die weltweit für Talks und Diskusionen über Tor verwendet werden kann.</li>
de/volunteer.wml        85) <li>Dreh ein Video über deine positiven Einsätze von Tor. Es haben schon ein paar auf Seesmic angefangen.</li>
de/volunteer.wml        86) <li>Entwickle ein Poster oder ein Set von Postern rund um ein Thema wie z.B. "Freiheit dank Tor!"</li>

de/volunteer.de.html    87) </ol>
de/volunteer.de.html    88) 

de/volunteer.wml        89) <a id="Documentation"></a>
de/volunteer.wml        90) <h2><a class="anchor" href="#Documentation">Dokumentation</a></h2>

de/volunteer.de.html    91) 
de/volunteer.de.html    92) <ol>

de/volunteer.wml        93)   <li>Bitte hilf Matt Edman mit der Dokumentation und HOWTOs für

de/volunteer.wml        94)   seinen <a href="http://vidalia-project.net/">Vidalia</a>.</li>

de/volunteer.wml        95)   <li>Kommentiere und dokumentiere unsere <a

de/volunteer.wml        96)     href="https://wiki.torproject.org/wiki/TheOnionRouter/TorifyHOWTO">Liste

de/volunteer.wml        97)     von Programmen, die durch Tor geroutet werden können</a>.</li>
de/volunteer.wml        98)   <li>Wir brauchen bessere Dokumentation für Programme, die dynamisch
de/volunteer.wml        99)     in Verbindungen eingreifen und diese durch Tor schicken. Für Linux

de/volunteer.wml       100)     und Windows scheinen tsocks (Linux), dsocks (BSD), und freecap gute Kandidaten.</li>

de/volunteer.de.html   101)   <li>Wir haben eine riesige

de/volunteer.wml       102)     Liste <a href="<page support>">potentiell nützlicher Programme,

de/volunteer.de.html   103)     die eine Schnittstelle zu Tor haben</a>. Welche sind in welchen
de/volunteer.de.html   104)     Situationen gut? Bitte hilf uns, diese zu testen und dokumentiere

de/volunteer.wml       105)     die Ergebnisse.</li>
de/volunteer.wml       106)   <li>Hilf, die Webseite und die Dokumentation in andere Sprachen zu

de/volunteer.wml       107)   übersetzen. Schaue dir die <a href="<page translation>">Richtlinien
de/volunteer.wml       108)   zur Übersetzung</a> an, wenn du gern helfen möchtest. Wir brauchen
de/volunteer.wml       109)   auch Leute, um die Seiten in Arabisch oder Farsi zu übersetzen. Einen
de/volunteer.wml       110)   Überblick gibt

de/volunteer.wml       111)   es bei der <a href="<page translation-status>">Statusseite der

de/volunteer.wml       112)   Übersetzungen</a>.</li>

de/volunteer.de.html   113)   </ol>
de/volunteer.de.html   114) 

de/volunteer.wml       115) <a id="Coding"></a>

de/volunteer.wml       116)   <p>Die untenstehenden Angaben wurden in der Originalsprache

de/volunteer.wml       117)   belassen. Da diese sich ausschließlich auf englischsprachige

de/volunteer.wml       118)   Bewerber beziehen.</p>
de/volunteer.wml       119) 
de/volunteer.wml       120)   <a id="Summer"></a>
de/volunteer.wml       121) <a id="Projects"></a>
de/volunteer.wml       122) <h2><a class="anchor" href="#Projects">Good Coding Projects</a></h2>
de/volunteer.wml       123) 
de/volunteer.wml       124) <p>

de/volunteer.wml       125) Here is a list of ideas that were proposed for the <a href="<page gsoc>">Google Summer of Code 2009</a>

de/volunteer.wml       126) but have not been put into practice. Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a> 
de/volunteer.wml       127) might also be short on developers. If you think you can help out, <a href="<page contact>"> let us know!</a> 

de/volunteer.wml       128) </p>
de/volunteer.wml       129) 
de/volunteer.wml       130) <ol>

de/volunteer.wml       131) <!-- Mike is already working on this

de/volunteer.wml       132) <li>
de/volunteer.wml       133) <b>Tor Node Scanner improvements</b>
de/volunteer.wml       134) <br />

de/volunteer.wml       135) Similar to the SoaT exit scanner (or perhaps even during exit scanning),

de/volunteer.wml       136) statistics can be gathered about the reliability of nodes. Nodes that
de/volunteer.wml       137) fail too high a percentage of their circuits should not be given
de/volunteer.wml       138) Guard status. Perhaps they should have their reported bandwidth
de/volunteer.wml       139) penalized by some ratio as well, or just get marked as Invalid. In
de/volunteer.wml       140) addition, nodes that exhibit a very low average stream capacity but
de/volunteer.wml       141) advertise a very high node bandwidth can also be marked as Invalid.
de/volunteer.wml       142) Much of this statistics gathering is already done, it just needs to be
de/volunteer.wml       143) transformed into something that can be reported to the Directory
de/volunteer.wml       144) Authorities to blacklist/penalize nodes in such a way that clients
de/volunteer.wml       145) will listen.
de/volunteer.wml       146) <br />
de/volunteer.wml       147) In addition, these same statistics can be gathered about the traffic
de/volunteer.wml       148) through a node. Events can be added to the <a

de/volunteer.wml       149) href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor Control

de/volunteer.wml       150) Protocol</a> to
de/volunteer.wml       151) report if a circuit extend attempt through the node succeeds or fails, and
de/volunteer.wml       152) passive statistics can be gathered on both bandwidth and reliability
de/volunteer.wml       153) of other nodes via a node-based monitor using these events. Such a
de/volunteer.wml       154) scanner would also report information on oddly-behaving nodes to
de/volunteer.wml       155) the Directory Authorities, but a communication channel for this
de/volunteer.wml       156) currently does not exist and would need to be developed as well.
de/volunteer.wml       157) </li>

de/volunteer.wml       158)  -->
de/volunteer.wml       159)  

de/volunteer.wml       160) <li>
de/volunteer.wml       161) <b>Help track the overall Tor Network status</b>
de/volunteer.wml       162) <br />

de/volunteer.wml       163) Priority: <i>Medium to High</i>
de/volunteer.wml       164) <br />
de/volunteer.wml       165) Effort Level: <i>Medium</i>
de/volunteer.wml       166) <br />
de/volunteer.wml       167) Skill Level: <i>Medium</i>
de/volunteer.wml       168) <br />
de/volunteer.wml       169) Likely Mentors: <i>Karsten</i>
de/volunteer.wml       170) <br />

de/volunteer.wml       171) It would be great to set up an automated system for tracking network
de/volunteer.wml       172) health over time, graphing it, etc. Part of this project would involve
de/volunteer.wml       173) inventing better metrics for assessing network health and growth. Is the
de/volunteer.wml       174) average uptime of the network increasing? How many relays are qualifying
de/volunteer.wml       175) for Guard status this month compared to last month? What's the turnover
de/volunteer.wml       176) in terms of new relays showing up and relays shutting off? Periodically
de/volunteer.wml       177) people collect brief snapshots, but where it gets really interesting is
de/volunteer.wml       178) when we start tracking data points over time.
de/volunteer.wml       179) <br />

de/volunteer.wml       180) Data could be collected from the "Tor Node Scanner" in
de/volunteer.wml       181) <a href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from

de/volunteer.wml       182) the server descriptors that each relay publishes, and from other
de/volunteer.wml       183) sources. Results over time could be integrated into one of the <a
de/volunteer.wml       184) href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
de/volunteer.wml       185) kept separate. Speaking of the Tor Status pages, take a look at Roger's
de/volunteer.wml       186) <a href="http://archives.seul.org/or/talk/Jan-2008/msg00300.html">Tor
de/volunteer.wml       187) Status wish list</a>.
de/volunteer.wml       188) </li>
de/volunteer.wml       189) 

de/volunteer.wml       190) <!-- Is this still a useful project? If so, move it to another section.

de/volunteer.wml       191) <li>
de/volunteer.wml       192) <b>Better Debian/Ubuntu Packaging for Tor+Vidalia</b>
de/volunteer.wml       193) <br />
de/volunteer.wml       194) Vidalia currently doesn't play nicely on Debian and Ubuntu with the
de/volunteer.wml       195) default Tor packages. The current Tor packages automatically start Tor
de/volunteer.wml       196) as a daemon running as the debian-tor user and (sensibly) do not have a
de/volunteer.wml       197) <a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
de/volunteer.wml       198) in the default torrc. Consequently, Vidalia will try
de/volunteer.wml       199) to start its own Tor process since it could not connect to the existing
de/volunteer.wml       200) Tor, and Vidalia's Tor process will then exit with an error message
de/volunteer.wml       201) the user likely doesn't understand since Tor cannot bind its listening
de/volunteer.wml       202) ports &mdash; they're already in use by the original Tor daemon.
de/volunteer.wml       203) <br />
de/volunteer.wml       204) The current solution involves either telling the user to stop the
de/volunteer.wml       205) existing Tor daemon and let Vidalia start its own Tor process, or
de/volunteer.wml       206) explaining to the user how to set a control port and password in their
de/volunteer.wml       207) torrc. A better solution on Debian would be to use Tor's ControlSocket,
de/volunteer.wml       208) which allows Vidalia to talk to Tor via a Unix domain socket, and could
de/volunteer.wml       209) possibly be enabled by default in Tor's Debian packages. Vidalia can
de/volunteer.wml       210) then authenticate to Tor using filesystem-based (cookie) authentication
de/volunteer.wml       211) if the user running Vidalia is also in the debian-tor group.
de/volunteer.wml       212) <br />
de/volunteer.wml       213) This project will first involve adding support for Tor's ControlSocket
de/volunteer.wml       214) to Vidalia. The student will then develop and test Debian and Ubuntu
de/volunteer.wml       215) packages for Vidalia that conform to Debian's packaging standards and
de/volunteer.wml       216) make sure they work well with the existing Tor packages. We can also
de/volunteer.wml       217) set up an apt repository to host the new Vidalia packages.
de/volunteer.wml       218) <br />
de/volunteer.wml       219) The next challenge would be to find an intuitive usable way for Vidalia
de/volunteer.wml       220) to be able to change Tor's configuration (torrc) even though it is
de/volunteer.wml       221) located in <code>/etc/tor/torrc</code> and thus immutable. The best
de/volunteer.wml       222) idea we've come up with so far is to feed Tor a new configuration via
de/volunteer.wml       223) the ControlSocket when Vidalia starts, but that's bad because Tor starts
de/volunteer.wml       224) each boot with a different configuration than the user wants. The second
de/volunteer.wml       225) best idea
de/volunteer.wml       226) we've come up with is for Vidalia to write out a temporary torrc file
de/volunteer.wml       227) and ask the user to manually move it to <code>/etc/tor/torrc</code>,
de/volunteer.wml       228) but that's bad because users shouldn't have to mess with files directly.
de/volunteer.wml       229) <br />

de/volunteer.wml       230) A person undertaking this project should have prior knowledge of

de/volunteer.wml       231) Debian package management and some C++ development experience. Previous
de/volunteer.wml       232) experience with Qt is helpful, but not required.
de/volunteer.wml       233) </li>

de/volunteer.wml       234) -->
de/volunteer.wml       235) 	 

de/volunteer.wml       236) <li>
de/volunteer.wml       237) <b>Improving Tor's ability to resist censorship</b>
de/volunteer.wml       238) <br />

de/volunteer.wml       239) Priority: <i>High</i>
de/volunteer.wml       240) <br />
de/volunteer.wml       241) Effort Level: <i>High</i>
de/volunteer.wml       242) <br />
de/volunteer.wml       243) Skill Level: <i>High</i>
de/volunteer.wml       244) <br />
de/volunteer.wml       245) Likely Mentors: <i>Nick</i>
de/volunteer.wml       246) <br />

de/volunteer.wml       247) The Tor 0.2.0.x series makes <a
de/volunteer.wml       248) href="<svnsandbox>doc/design-paper/blocking.html">significant
de/volunteer.wml       249) improvements</a> in resisting national and organizational censorship.
de/volunteer.wml       250) But Tor still needs better mechanisms for some parts of its
de/volunteer.wml       251) anti-censorship design.  For example, current Tors can only listen on a
de/volunteer.wml       252) single address/port combination at a time.  There's
de/volunteer.wml       253) <a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
de/volunteer.wml       254) proposal to address this limitation</a> and allow clients to connect
de/volunteer.wml       255) to any given Tor on multiple addresses and ports, but it needs more
de/volunteer.wml       256) work.  Another anti-censorship project (far more difficult) is to try
de/volunteer.wml       257) to make Tor more scanning-resistant.  Right now, an adversary can identify
de/volunteer.wml       258) <a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
de/volunteer.wml       259) just by trying to connect to them, following the Tor protocol, and
de/volunteer.wml       260) seeing if they respond.  To solve this, bridges could
de/volunteer.wml       261) <a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
de/volunteer.wml       262) webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
de/volunteer.wml       263) and not act like bridges until the user provides a bridge-specific key.
de/volunteer.wml       264) <br />
de/volunteer.wml       265) This project involves a lot of research and design. One of the big
de/volunteer.wml       266) challenges will be identifying and crafting approaches that can still
de/volunteer.wml       267) resist an adversary even after the adversary knows the design, and
de/volunteer.wml       268) then trading off censorship resistance with usability and robustness.
de/volunteer.wml       269) </li>
de/volunteer.wml       270) 

de/volunteer.wml       271) <!-- This should be mostly done.

de/volunteer.wml       272) <li>
de/volunteer.wml       273) <b>Tor/Polipo/Vidalia Auto-Update Framework</b>
de/volunteer.wml       274) <br />
de/volunteer.wml       275) We're in need of a good authenticated-update framework.
de/volunteer.wml       276) Vidalia already has the ability to notice when the user is running an
de/volunteer.wml       277) outdated or unrecommended version of Tor, using signed statements inside
de/volunteer.wml       278) the Tor directory information. Currently, Vidalia simply pops
de/volunteer.wml       279) up a little message box that lets the user know they should manually
de/volunteer.wml       280) upgrade. The goal of this project would be to extend Vidalia with the
de/volunteer.wml       281) ability to also fetch and install the updated Tor software for the
de/volunteer.wml       282) user. We should do the fetches via Tor when possible, but also fall back
de/volunteer.wml       283) to direct fetches in a smart way. Time permitting, we would also like
de/volunteer.wml       284) to be able to update other
de/volunteer.wml       285) applications included in the bundled installers, such as Polipo and
de/volunteer.wml       286) Vidalia itself.
de/volunteer.wml       287) <br />
de/volunteer.wml       288) To complete this project, the student will first need to first investigate
de/volunteer.wml       289) the existing auto-update frameworks (e.g., Sparkle on OS X) to evaluate
de/volunteer.wml       290) their strengths, weaknesses, security properties, and ability to be
de/volunteer.wml       291) integrated into Vidalia. If none are found to be suitable, the student
de/volunteer.wml       292) will design their own auto-update framework, document the design, and
de/volunteer.wml       293) then discuss the design with other developers to assess any security
de/volunteer.wml       294) issues. The student will then implement their framework (or integrate
de/volunteer.wml       295) an existing one) and test it.
de/volunteer.wml       296) <br />

de/volunteer.wml       297) A person undertaking this project should have good C++ development
de/volunteer.wml       298) experience. Previous experience with Qt is helpful, but not required. One
de/volunteer.wml       299) should also have a good understanding of common security

de/volunteer.wml       300) practices, such as package signature verification. Good writing ability
de/volunteer.wml       301) is also important for this project, since a vital step of the project

de/volunteer.wml       302) will be producing a design document to review and discuss
de/volunteer.wml       303) with others prior to implementation.

de/volunteer.wml       304) </li>

de/volunteer.wml       305) -->

de/volunteer.wml       306) 

de/volunteer.wml       307) <li>
de/volunteer.wml       308) <b>An Improved and More Usable Network Map in Vidalia</b>
de/volunteer.wml       309) <br />

de/volunteer.wml       310) Priority: <i>Medium</i>
de/volunteer.wml       311) <br />
de/volunteer.wml       312) Effort Level: <i>Medium</i>
de/volunteer.wml       313) <br />
de/volunteer.wml       314) Skill Level: <i>Medium</i>
de/volunteer.wml       315) <br />
de/volunteer.wml       316) Likely Mentors: <i>Matt</i>
de/volunteer.wml       317) <br />

de/volunteer.wml       318) One of Vidalia's existing features is a network map that shows the user
de/volunteer.wml       319) the approximate geographic location of relays in the Tor network and
de/volunteer.wml       320) plots the paths the user's traffic takes as it is tunneled through the
de/volunteer.wml       321) Tor network. The map is currently not very interactive and has rather

de/volunteer.wml       322) poor graphics. Instead, we implemented KDE's Marble widget such
de/volunteer.wml       323) that it gives us a better quality map and enables improved interactivity,

de/volunteer.wml       324) such as allowing the user to click on individual relays or circuits to

de/volunteer.wml       325) display additional information. We want to add the ability

de/volunteer.wml       326) for users to click on a particular relay or a country containing one or

de/volunteer.wml       327) more Tor exit relays and say, "I want my connections to exit

de/volunteer.wml       328) from here."
de/volunteer.wml       329) <br />

de/volunteer.wml       330) This project will first involve getting familiar with Vidalia
de/volunteer.wml       331) and the Marble widget's API. One will then integrate the widget

de/volunteer.wml       332) into Vidalia and customize Marble to be better suited for our application,
de/volunteer.wml       333) such as making circuits clickable, storing cached map data in Vidalia's
de/volunteer.wml       334) own data directory, and customizing some of the widget's dialogs.
de/volunteer.wml       335) <br />

de/volunteer.wml       336) A person undertaking this project should have good C++ development

de/volunteer.wml       337) experience. Previous experience with Qt and CMake is helpful, but not
de/volunteer.wml       338) required.
de/volunteer.wml       339) </li>
de/volunteer.wml       340) 
de/volunteer.wml       341) <li>
de/volunteer.wml       342) <b>Tor Controller Status Event Interface</b>
de/volunteer.wml       343) <br />

de/volunteer.wml       344) Priority: <i>Medium</i>
de/volunteer.wml       345) <br />
de/volunteer.wml       346) Effort Level: <i>Medium</i>
de/volunteer.wml       347) <br />
de/volunteer.wml       348) Skill Level: <i>Medium</i>
de/volunteer.wml       349) <br />
de/volunteer.wml       350) Likely Mentors: <i>Matt</i>
de/volunteer.wml       351) <br />

de/volunteer.wml       352) There are a number of status changes inside Tor of which the user may need
de/volunteer.wml       353) to be informed. For example, if the user is trying to set up his Tor as a
de/volunteer.wml       354) relay and Tor decides that its ports are not reachable from outside
de/volunteer.wml       355) the user's network, we should alert the user. Currently, all the user
de/volunteer.wml       356) gets is a couple log messages in Vidalia's 'message log' window, which they
de/volunteer.wml       357) likely never see since they don't receive a notification that something
de/volunteer.wml       358) has gone wrong. Even if the user does actually look at the message log,
de/volunteer.wml       359) most of the messages make little sense to the novice user.
de/volunteer.wml       360) <br />
de/volunteer.wml       361) Tor has the ability to inform Vidalia of many such status changes, and
de/volunteer.wml       362) we recently implemented support for a couple of these events. Still,
de/volunteer.wml       363) there are many more status events the user should be informed of and we
de/volunteer.wml       364) need a better UI for actually displaying them to the user.
de/volunteer.wml       365) <br />
de/volunteer.wml       366) The goal of this project then is to design and implement a UI for
de/volunteer.wml       367) displaying Tor status events to the user. For example, we might put a
de/volunteer.wml       368) little badge on Vidalia's tray icon that alerts the user to new status
de/volunteer.wml       369) events they should look at. Double-clicking the icon could bring up a
de/volunteer.wml       370) dialog that summarizes recent status events in simple terms and maybe
de/volunteer.wml       371) suggests a remedy for any negative events if they can be corrected by

de/volunteer.wml       372) the user. Of course, this is just an example and one is free to

de/volunteer.wml       373) suggest another approach.
de/volunteer.wml       374) <br />

de/volunteer.wml       375) A person undertaking this project should have good UI design and layout

de/volunteer.wml       376) and some C++ development experience. Previous experience with Qt and
de/volunteer.wml       377) Qt's Designer will be very helpful, but are not required. Some
de/volunteer.wml       378) English writing ability will also be useful, since this project will
de/volunteer.wml       379) likely involve writing small amounts of help documentation that should
de/volunteer.wml       380) be understandable by non-technical users. Bonus points for some graphic
de/volunteer.wml       381) design/Photoshop fu, since we might want/need some shiny new icons too.
de/volunteer.wml       382) </li>
de/volunteer.wml       383) 

de/volunteer.wml       384) <!-- Jake already did most of this.

de/volunteer.wml       385) <li>
de/volunteer.wml       386) <b>Improvements on our active browser configuration tester</b> -
de/volunteer.wml       387) <a href="https://check.torproject.org/">https://check.torproject.org/</a>
de/volunteer.wml       388) <br />
de/volunteer.wml       389) We currently have a functional web page to detect if Tor is working. It
de/volunteer.wml       390) has a few places where it falls short. It requires improvements with
de/volunteer.wml       391) regard to default languages and functionality. It currently only responds
de/volunteer.wml       392) in English. In addition, it is a hack of a perl script that should have
de/volunteer.wml       393) never seen the light of day. It should probably be rewritten in python
de/volunteer.wml       394) with multi-lingual support in mind. It currently uses the <a
de/volunteer.wml       395) href="http://exitlist.torproject.org/">Tor DNS exit list</a>
de/volunteer.wml       396) and should continue to do so in the future. It currently result in certain
de/volunteer.wml       397) false positives and these should be discovered, documented, and fixed
de/volunteer.wml       398) where possible. Anyone working on this project should be interested in
de/volunteer.wml       399) DNS, basic perl or preferably python programming skills, and will have
de/volunteer.wml       400) to interact minimally with Tor to test their code.
de/volunteer.wml       401) <br />
de/volunteer.wml       402) If you want to make the project more exciting
de/volunteer.wml       403) and involve more design and coding, take a look at <a
de/volunteer.wml       404) href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
de/volunteer.wml       405) 131-verify-tor-usage.txt</a>.
de/volunteer.wml       406) </li>

de/volunteer.wml       407) -->

de/volunteer.wml       408) 

de/volunteer.wml       409) <!-- If we decide to switch to the exit list in TorStatus, this is obsolete.

de/volunteer.wml       410) <li>
de/volunteer.wml       411) <b>Improvements on our DNS Exit List service</b> -
de/volunteer.wml       412) <a href="http://exitlist.torproject.org/">http://exitlist.torproject.org/</a>
de/volunteer.wml       413) <br />
de/volunteer.wml       414) The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>
de/volunteer.wml       415) is written by our fabulous anonymous
de/volunteer.wml       416) contributer Tup. It's a DNS server written in Haskell that supports part of our <a

de/volunteer.wml       417) href="<svnsandbox>doc/contrib/torel-design.txt">exitlist

de/volunteer.wml       418) design document</a>. Currently, it is functional and it is used by
de/volunteer.wml       419) check.torproject.org and other users. The issues that are outstanding
de/volunteer.wml       420) are mostly aesthetic. This wonderful service could use a much better
de/volunteer.wml       421) website using the common Tor theme. It would be best served with better
de/volunteer.wml       422) documentation for common services that use an RBL. It could use more
de/volunteer.wml       423) publicity. A person working on this project should be interested in DNS,
de/volunteer.wml       424) basic RBL configuration for popular services, and writing documentation.
de/volunteer.wml       425) The person would require minimal Tor interaction &mdash; testing their
de/volunteer.wml       426) own documentation at the very least. Furthermore, it would be useful
de/volunteer.wml       427) if they were interested in Haskell and wanted to implement more of the
de/volunteer.wml       428) torel-design.txt suggestions.
de/volunteer.wml       429) </li>

de/volunteer.wml       430) -->

de/volunteer.wml       431) 

de/volunteer.wml       432) <!-- Nobody wanted to keep this.

de/volunteer.wml       433) <li>
de/volunteer.wml       434) <b>Testing integration of Tor with web browsers for our end users</b>
de/volunteer.wml       435) <br />
de/volunteer.wml       436) The Tor project currently lacks a solid test suite to ensure that a
de/volunteer.wml       437) user has a properly and safely configured web browser. It should test for as
de/volunteer.wml       438) many known issues as possible. It should attempt to decloak the
de/volunteer.wml       439) user in any way possible. Two current webpages that track these
de/volunteer.wml       440) kinds of issues are run by Greg Fleischer and HD Moore. Greg keeps a nice <a
de/volunteer.wml       441) href="http://pseudo-flaw.net/tor/torbutton/">list of issues along
de/volunteer.wml       442) with their proof of concept code, bug issues, etc</a>. HD Moore runs

de/volunteer.wml       443) the <a href="http://www.decloak.net/">metasploit

de/volunteer.wml       444) decloak website</a>. A person interested in defending Tor could start

de/volunteer.wml       445) by collecting as many workable and known methods for decloaking a
de/volunteer.wml       446) Tor user. (<a href="https://torcheck.xenobite.eu/">This page</a> may

de/volunteer.wml       447) be helpful as a start.) One should be familiar with the common pitfalls but

de/volunteer.wml       448) possibly have new methods in mind for implementing decloaking issues. The
de/volunteer.wml       449) website should ensure that it tells a user what their problem is. It
de/volunteer.wml       450) should help them to fix the problem or direct them to the proper support

de/volunteer.wml       451) channels. The person should also be closely familiar with using Tor and how

de/volunteer.wml       452) to prevent Tor information leakage.
de/volunteer.wml       453) </li>

de/volunteer.wml       454) -->

de/volunteer.wml       455) 

de/volunteer.wml       456) <!-- Nick did quite some work here. Is this project still required then?

de/volunteer.wml       457) <li>
de/volunteer.wml       458) <b>Libevent and Tor integration improvements</b>
de/volunteer.wml       459) <br />
de/volunteer.wml       460) Tor should make better use of the more recent features of Niels
de/volunteer.wml       461) Provos's <a href="http://monkey.org/~provos/libevent/">Libevent</a>
de/volunteer.wml       462) library.  Tor already uses Libevent for its low-level asynchronous IO
de/volunteer.wml       463) calls, and could also use Libevent's increasingly good implementations
de/volunteer.wml       464) of network buffers and of HTTP.  This wouldn't be simply a matter of
de/volunteer.wml       465) replacing Tor's internal calls with calls to Libevent: instead, we'll
de/volunteer.wml       466) need to refactor Tor to use Libevent calls that do not follow the
de/volunteer.wml       467) same models as Tor's existing backends. Also, we'll need to add
de/volunteer.wml       468) missing functionality to Libevent as needed &mdash; most difficult likely
de/volunteer.wml       469) will be adding OpenSSL support on top of Libevent's buffer abstraction.
de/volunteer.wml       470) Also tricky will be adding rate-limiting to Libevent.
de/volunteer.wml       471) </li>

de/volunteer.wml       472) -->

de/volunteer.wml       473) 
de/volunteer.wml       474) <li>
de/volunteer.wml       475) <b>Tuneup Tor!</b>
de/volunteer.wml       476) <br />

de/volunteer.wml       477) Priority: <i>Medium</i>
de/volunteer.wml       478) <br />
de/volunteer.wml       479) Effort Level: <i>Medium</i>
de/volunteer.wml       480) <br />
de/volunteer.wml       481) Skill Level: <i>Medium to High</i>
de/volunteer.wml       482) <br />
de/volunteer.wml       483) Likely Mentors: <i>Nick, Roger, Mike</i>
de/volunteer.wml       484) <br />

de/volunteer.wml       485) Right now, Tor relays measure and report their own bandwidth, and Tor
de/volunteer.wml       486) clients choose which relays to use in part based on that bandwidth.
de/volunteer.wml       487) This approach is vulnerable to
de/volunteer.wml       488) <a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where
de/volunteer.wml       489) relays lie about their bandwidth</a>;
de/volunteer.wml       490) to address this, Tor currently caps the maximum bandwidth
de/volunteer.wml       491) it's willing to believe any relay provides.  This is a limited fix, and
de/volunteer.wml       492) a waste of bandwidth capacity to boot.  Instead,
de/volunteer.wml       493) Tor should possibly measure bandwidth in a more distributed way, perhaps
de/volunteer.wml       494) as described in the
de/volunteer.wml       495) <a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for
de/volunteer.wml       496) Tor"</a> paper

de/volunteer.wml       497) by Snader and Borisov. One could use current testing code to

de/volunteer.wml       498) double-check this paper's findings and verify the extent to which they
de/volunteer.wml       499) dovetail with Tor as deployed in the wild, and determine good ways to
de/volunteer.wml       500) incorporate them into their suggestions Tor network without adding too
de/volunteer.wml       501) much communications overhead between relays and directory
de/volunteer.wml       502) authorities.
de/volunteer.wml       503) </li>
de/volunteer.wml       504) 
de/volunteer.wml       505) <!--
de/volunteer.wml       506) <li>
de/volunteer.wml       507) <b>Improving the Tor QA process: Continuous Integration for Windows builds</b>
de/volunteer.wml       508) <br />
de/volunteer.wml       509) It would be useful to have automated build processes for Windows and
de/volunteer.wml       510) probably other platforms. The purpose of having a continuous integration
de/volunteer.wml       511) build environment is to ensure that Windows isn't left behind for any of
de/volunteer.wml       512) the software projects used in the Tor project or its accompanying.<br />
de/volunteer.wml       513) Buildbot may be a good choice for this as it appears to support all of
de/volunteer.wml       514) the platforms Tor does. See the
de/volunteer.wml       515) <a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for
de/volunteer.wml       516) buildbot</a>.<br />
de/volunteer.wml       517) There may be better options and the person undertaking this task should
de/volunteer.wml       518) evaluate other options. Any person working on this automatic build
de/volunteer.wml       519) process should have experience or be willing to learn how to build all
de/volunteer.wml       520) of the respective Tor related code bases from scratch. Furthermore, the
de/volunteer.wml       521) person should have some experience building software in Windows
de/volunteer.wml       522) environments as this is the target audience we want to ensure we do not
de/volunteer.wml       523) leave behind. It would require close work with the Tor source code but
de/volunteer.wml       524) probably only in the form of building, not authoring.<br />
de/volunteer.wml       525) Additionally, we need to automate our performance testing for all platforms.
de/volunteer.wml       526) We've got buildbot (except on Windows &mdash; as noted above) to automate
de/volunteer.wml       527) our regular integration and compile testing already,
de/volunteer.wml       528) but we need to get our network simulation tests (as built in torflow)
de/volunteer.wml       529) updated for more recent versions of Tor, and designed to launch a test
de/volunteer.wml       530) network either on a single machine, or across several, so we can test
de/volunteer.wml       531) changes in performance on machines in different roles automatically.
de/volunteer.wml       532) </li>
de/volunteer.wml       533) -->
de/volunteer.wml       534) 
de/volunteer.wml       535) <li>
de/volunteer.wml       536) <b>Improve our unit testing process</b>
de/volunteer.wml       537) <br />

de/volunteer.wml       538) Priority: <i>Medium</i>
de/volunteer.wml       539) <br />
de/volunteer.wml       540) Effort Level: <i>Medium</i>
de/volunteer.wml       541) <br />
de/volunteer.wml       542) Skill Level: <i>Medium</i>
de/volunteer.wml       543) <br />
de/volunteer.wml       544) Likely Mentors: <i>Nick</i>
de/volunteer.wml       545) <br />

de/volunteer.wml       546) Tor needs to be far more tested. This is a multi-part effort. To start
de/volunteer.wml       547) with, our unit test coverage should rise substantially, especially in
de/volunteer.wml       548) the areas outside the utility functions. This will require significant
de/volunteer.wml       549) refactoring of some parts of Tor, in order to dissociate as much logic
de/volunteer.wml       550) as possible from globals.
de/volunteer.wml       551) <br />
de/volunteer.wml       552) Additionally, we need to automate our performance testing. We've got
de/volunteer.wml       553) buildbot to automate our regular integration and compile testing already
de/volunteer.wml       554) (though we need somebody to set it up on Windows),

de/volunteer.wml       555) but we need to get our network simulation tests (as built in <a
de/volunteer.wml       556) href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)

de/volunteer.wml       557) updated for more recent versions of Tor, and designed to launch a test
de/volunteer.wml       558) network either on a single machine, or across several, so we can test
de/volunteer.wml       559) changes in performance on machines in different roles automatically.
de/volunteer.wml       560) </li>
de/volunteer.wml       561) 
de/volunteer.wml       562) <li>
de/volunteer.wml       563) <b>Help revive an independent Tor client implementation</b>
de/volunteer.wml       564) <br />

de/volunteer.wml       565) Priority: <i>Medium</i>
de/volunteer.wml       566) <br />
de/volunteer.wml       567) Effort Level: <i>High</i>
de/volunteer.wml       568) <br />
de/volunteer.wml       569) Skill Level: <i>Medium to High</i>
de/volunteer.wml       570) <br />
de/volunteer.wml       571) Likely Mentors: <i>Karsten, Nick</i>
de/volunteer.wml       572) <br />

de/volunteer.wml       573) Reanimate one of the approaches to implement a Tor client in Java,
de/volunteer.wml       574) e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee
de/volunteer.wml       575) project</a>, and make it run on <a
de/volunteer.wml       576) href="http://code.google.com/android/">Android</a>. The first step
de/volunteer.wml       577) would be to port the existing code and execute it in an Android
de/volunteer.wml       578) environment. Next, the code should be updated to support the newer Tor
de/volunteer.wml       579) protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
de/volunteer.wml       580) directory protocol</a>. Further, support for requesting or even
de/volunteer.wml       581) providing Tor hidden services would be neat, but not required.
de/volunteer.wml       582) <br />

de/volunteer.wml       583) A prospective developer should be able to understand and write new Java
de/volunteer.wml       584) code, including

de/volunteer.wml       585) a Java cryptography API. Being able to read C code would be helpful,

de/volunteer.wml       586) too. One should be willing to read the existing documentation,

de/volunteer.wml       587) implement code based on it, and refine the documentation
de/volunteer.wml       588) when things are underdocumented. This project is mostly about coding and
de/volunteer.wml       589) to a small degree about design.
de/volunteer.wml       590) </li>
de/volunteer.wml       591) 
de/volunteer.wml       592) <li>
de/volunteer.wml       593) <b>Bring moniTor to life</b>
de/volunteer.wml       594) <br />

de/volunteer.wml       595) Priority: <i>Medium</i>
de/volunteer.wml       596) <br />
de/volunteer.wml       597) Effort Level: <i>Medium</i>
de/volunteer.wml       598) <br />
de/volunteer.wml       599) Skill Level: <i>Low to Medium</i>
de/volunteer.wml       600) <br />
de/volunteer.wml       601) Likely Mentors: <i>Karsten, Jacob</i>
de/volunteer.wml       602) <br />

de/volunteer.wml       603) Implement a <a href="http://www.ss64.com/bash/top.html">top-like</a>
de/volunteer.wml       604) management tool for Tor relays. The purpose of such a tool would be
de/volunteer.wml       605) to monitor a local Tor relay via its control port and include useful
de/volunteer.wml       606) system information of the underlying machine. When running this tool, it
de/volunteer.wml       607) would dynamically update its content like top does for Linux processes.
de/volunteer.wml       608) <a href="http://archives.seul.org/or/dev/Jan-2008/msg00005.html">This
de/volunteer.wml       609) or-dev post</a> might be a good first read.
de/volunteer.wml       610) <br />

de/volunteer.wml       611) A person interested in this should be familiar

de/volunteer.wml       612) with or willing to learn about administering a Tor relay and configuring
de/volunteer.wml       613) it via its control port. As an initial prototype is written in Python,
de/volunteer.wml       614) some knowledge about writing Python code would be helpful, too. This
de/volunteer.wml       615) project is one part about identifying requirements to such a
de/volunteer.wml       616) tool and designing its interface, and one part lots of coding.
de/volunteer.wml       617) </li>
de/volunteer.wml       618) 

de/volunteer.wml       619) <!-- Removed, unless Mike still wants this to be in.

de/volunteer.wml       620) <li>
de/volunteer.wml       621) <b>Torbutton improvements</b>
de/volunteer.wml       622) <br />
de/volunteer.wml       623) Torbutton has a number of improvements that can be made in the post-1.2
de/volunteer.wml       624) timeframe. Most of these are documented as feature requests in the <a
de/volunteer.wml       625) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">Torbutton
de/volunteer.wml       626) flyspray section</a>. Good examples include: stripping off node.exit on http
de/volunteer.wml       627) headers, more fine-grained control over formfill blocking, improved referrer
de/volunteer.wml       628) spoofing based on the domain of the site (a-la <a
de/volunteer.wml       629) href="https://addons.mozilla.org/en-US/firefox/addon/953">refcontrol extension</a>),
de/volunteer.wml       630) tighter integration with Vidalia for reporting Tor status, a New Identity
de/volunteer.wml       631) button with Tor integration and multiple identity management, and anything
de/volunteer.wml       632) else you might think of.
de/volunteer.wml       633) <br />
de/volunteer.wml       634) This work would be independent coding in Javascript and the fun world of <a
de/volunteer.wml       635) href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
de/volunteer.wml       636) with not too much involvement in the Tor internals.
de/volunteer.wml       637) </li>

de/volunteer.wml       638) -->

de/volunteer.wml       639) 

de/volunteer.wml       640) <li>

de/volunteer.wml       641) <b>Improving Polipo on Windows</b>
de/volunteer.wml       642) <br />
de/volunteer.wml       643) Priority: <i>Medium</i>
de/volunteer.wml       644) <br />
de/volunteer.wml       645) Effort Level: <i>Low</i>
de/volunteer.wml       646) <br />
de/volunteer.wml       647) Skill Level: <i>Medium</i>
de/volunteer.wml       648) <br />
de/volunteer.wml       649) Likely Mentors: <i>Martin</i>

de/volunteer.wml       650) <br />
de/volunteer.wml       651) Help port <a
de/volunteer.wml       652) href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to
de/volunteer.wml       653) Windows. Example topics to tackle include:

de/volunteer.wml       654) 1) the ability to asynchronously

de/volunteer.wml       655) query name servers, find the system nameservers, and manage netbios

de/volunteer.wml       656) and dns queries.
de/volunteer.wml       657) 2) manage events and buffers

de/volunteer.wml       658) natively (i.e. in Unix-like OSes, Polipo defaults to 25% of ram, in

de/volunteer.wml       659) Windows it's whatever the config specifies). 3) some sort of GUI config

de/volunteer.wml       660) and reporting tool, bonus if it has a systray icon with right clickable
de/volunteer.wml       661) menu options. Double bonus if it's cross-platform compatible.

de/volunteer.wml       662) 3) allow the software to use the Windows Registry and handle proper Windows directory locations, such as "C:\Program Files\Polipo"

de/volunteer.wml       663) </li>
de/volunteer.wml       664) 

de/volunteer.wml       665) <!-- Is Blossom development still happening?

de/volunteer.wml       666) <li>
de/volunteer.wml       667) <b>Rework and extend Blossom</b>
de/volunteer.wml       668) <br />
de/volunteer.wml       669) Rework and extend Blossom (a tool for monitoring and
de/volunteer.wml       670) selecting appropriate Tor circuits based upon exit node requirements
de/volunteer.wml       671) specified by the user) to gather data in a self-contained way, with
de/volunteer.wml       672) parameters easily configurable by the user.  Blossom is presently
de/volunteer.wml       673) implemented as a single Python script that interfaces with Tor using the
de/volunteer.wml       674) Controller interface and depends upon metadata about Tor nodes obtained
de/volunteer.wml       675) via external processes, such as a webpage indicating status of the nodes
de/volunteer.wml       676) plus publically available data from DNS, whois, etc.  This project has
de/volunteer.wml       677) two parts: (1) Determine which additional metadata may be useful and
de/volunteer.wml       678) rework Blossom so that it cleanly obtains the metadata on its own rather
de/volunteer.wml       679) than depend upon external scripts (this may, for example, involve
de/volunteer.wml       680) additional threads or inter-process communication), and (2) develop a
de/volunteer.wml       681) means by which the user can easily configure Blossom, starting with a
de/volunteer.wml       682) configuration file and possibly working up to a web configuration engine.
de/volunteer.wml       683) Knowledge of Tor and Python are important; knowledge of
de/volunteer.wml       684) TCP, interprocess communication, and Perl will also be helpful.  An
de/volunteer.wml       685) interest in network neutrality is important as well, since the
de/volunteer.wml       686) principles of evaluating and understanding internet inconsistency are at
de/volunteer.wml       687) the core of the Blossom effort.
de/volunteer.wml       688) </li>
de/volunteer.wml       689) 
de/volunteer.wml       690) <li>
de/volunteer.wml       691) <b>Improve Blossom: Allow users to qualitatively describe exit nodes they desire</b>
de/volunteer.wml       692) <br />
de/volunteer.wml       693) Develop and implement a means of affording Blossom
de/volunteer.wml       694) users the ability to qualitatively describe the exit node that they
de/volunteer.wml       695) want.  The Internet is an inconsistent place: some Tor exit nodes see
de/volunteer.wml       696) the world differently than others.  As presently implemented, Blossom (a
de/volunteer.wml       697) tool for monitoring and selecting appropriate Tor circuits based upon
de/volunteer.wml       698) exit node requirements specified by the user) lacks a sufficiently rich
de/volunteer.wml       699) language to describe how the different vantage points are different.
de/volunteer.wml       700) For example, some exit nodes may have an upstream network that filters
de/volunteer.wml       701) certain kinds of traffic or certain websites.  Other exit nodes may
de/volunteer.wml       702) provide access to special content as a result of their location, perhaps
de/volunteer.wml       703) as a result of discrimination on the part of the content providers
de/volunteer.wml       704) themselves.  This project has two parts: (1) develop a language for
de/volunteer.wml       705) describing characteristics of networks in which exit nodes reside, and
de/volunteer.wml       706) (2) incorporate this language into Blossom so that users can select Tor
de/volunteer.wml       707) paths based upon the description.
de/volunteer.wml       708) Knowledge of Tor and Python are important; knowledge of
de/volunteer.wml       709) TCP, interprocess communication, and Perl will also be helpful.  An
de/volunteer.wml       710) interest in network neutrality is important as well, since the
de/volunteer.wml       711) principles of evaluating and understanding internet inconsistency are at
de/volunteer.wml       712) the core of the Blossom effort.
de/volunteer.wml       713) </li>

de/volunteer.wml       714) -->

de/volunteer.wml       715) 

de/volunteer.wml       716) <li>
de/volunteer.wml       717) <b>Implement a torrent-based scheme for downloading Thandy packages</b>
de/volunteer.wml       718) <br />

de/volunteer.wml       719) Priority: <i>Medium</i>
de/volunteer.wml       720) <br />
de/volunteer.wml       721) Effort Level: <i>High</i>
de/volunteer.wml       722) <br />
de/volunteer.wml       723) Skill Level: <i>Medium to High</i>
de/volunteer.wml       724) <br />
de/volunteer.wml       725) Likely Mentors: <i>Martin, Nick</i>
de/volunteer.wml       726) <br />

de/volunteer.wml       727) <a
de/volunteer.wml       728) href="http://git.torproject.org/checkout/thandy/master/specs/thandy-spec.txt">Thandy</a>

de/volunteer.wml       729) is a relatively new software to allow assisted updates of Tor and related

de/volunteer.wml       730) software. Currently, there are very few users, but we expect Thandy to be
de/volunteer.wml       731) used by almost every Tor user in the future. To avoid crashing servers on
de/volunteer.wml       732) the day of a Tor update, we need new ways to distribute new packages
de/volunteer.wml       733) efficiently, and using libtorrent seems to be a possible solution. If you
de/volunteer.wml       734) think of other good ideas, great - please do let us know!<br />
de/volunteer.wml       735) We also need to investigate how to include our mirrors better. If possible,
de/volunteer.wml       736) there should be an easy way for them to help distributing the packages.
de/volunteer.wml       737) </li>
de/volunteer.wml       738) 
de/volunteer.wml       739) <li>
de/volunteer.wml       740) <b>Torbutton equivalent for Thunderbird</b>
de/volunteer.wml       741) <br />

de/volunteer.wml       742) Priority: <i>Medium</i>
de/volunteer.wml       743) <br />
de/volunteer.wml       744) Effort Level: <i>High</i>
de/volunteer.wml       745) <br />
de/volunteer.wml       746) Skill Level: <i>High</i>
de/volunteer.wml       747) <br />
de/volunteer.wml       748) Likely Mentors: <i>Mike</i>
de/volunteer.wml       749) <br />

de/volunteer.wml       750) We're hearing from an increasing number of users that they want to use
de/volunteer.wml       751) Thunderbird with Tor. However, there are plenty of application-level
de/volunteer.wml       752) concerns, for example, by default Thunderbird will put your hostname in
de/volunteer.wml       753) the outgoing mail that it sends. At some point we should start a new
de/volunteer.wml       754) push to build a Thunderbird extension similar to Torbutton.
de/volunteer.wml       755) </li>
de/volunteer.wml       756) 
de/volunteer.wml       757) <li>
de/volunteer.wml       758) <b>New Torbutton Features</b>

de/volunteer.wml       759) <br />
de/volunteer.wml       760) Priority: <i>Medium</i>
de/volunteer.wml       761) <br />
de/volunteer.wml       762) Effort Level: <i>High</i>
de/volunteer.wml       763) <br />
de/volunteer.wml       764) Skill Level: <i>High</i>
de/volunteer.wml       765) <br />
de/volunteer.wml       766) Likely Mentors: <i>Mike</i>

de/volunteer.wml       767) <br/>
de/volunteer.wml       768) There are several <a

de/volunteer.wml       769) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5&type=2">good

de/volunteer.wml       770) feature requests</a> on the Torbutton Flyspray section. In particular, <a

de/volunteer.wml       771) href="https://bugs.torproject.org/flyspray/index.php?do=details&id=523">Integrating

de/volunteer.wml       772) 'New Identity' with Vidalia</a>,

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

de/volunteer.wml       774) managing multiple cookie jars/identities</a>, <a

de/volunteer.wml       775) href="https://bugs.torproject.org/flyspray/index.php?do=details&id=637">preserving
de/volunteer.wml       776) specific cookies</a> when cookies are cleared,

de/volunteer.wml       777) <a

de/volunteer.wml       778) href="https://bugs.torproject.org/flyspray/index.php?do=details&id=524">better

de/volunteer.wml       779) referrer spoofing</a>, <a

de/volunteer.wml       780) href="https://bugs.torproject.org/flyspray/index.php?do=details&id=564">correct

de/volunteer.wml       781) Tor status reporting</a>, and <a

de/volunteer.wml       782) href="https://bugs.torproject.org/flyspray/index.php?do=details&id=462">"tor://"

de/volunteer.wml       783) and "tors://" urls</a> are all interesting
de/volunteer.wml       784) features that could be added.
de/volunteer.wml       785) <br />
de/volunteer.wml       786) This work would be independent coding in Javascript and the fun world of <a
de/volunteer.wml       787) href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
de/volunteer.wml       788) with not too much involvement in the Tor internals.
de/volunteer.wml       789) </li>
de/volunteer.wml       790) 
de/volunteer.wml       791) <li>
de/volunteer.wml       792) <b>Usability testing of Tor</b>
de/volunteer.wml       793) <br />

de/volunteer.wml       794) Priority: <i>Medium</i>
de/volunteer.wml       795) <br />
de/volunteer.wml       796) Effort Level: <i>Medium</i>
de/volunteer.wml       797) <br />
de/volunteer.wml       798) Skill Level: <i>Low to Medium</i>
de/volunteer.wml       799) <br />
de/volunteer.wml       800) Likely Mentors: <i>Andrew</i>
de/volunteer.wml       801) <br />

de/volunteer.wml       802) Especially the browser bundle, ideally amongst our target demographic.
de/volunteer.wml       803) That would help a lot in knowing what needs to be done in terms of bug
de/volunteer.wml       804) fixes or new features. We get this informally at the moment, but a more
de/volunteer.wml       805) structured process would be better.
de/volunteer.wml       806) </li>
de/volunteer.wml       807) 
de/volunteer.wml       808) <li>
de/volunteer.wml       809) <b>Translation wiki for our website</b>
de/volunteer.wml       810) <br />

de/volunteer.wml       811) Priority: <i>High</i>
de/volunteer.wml       812) <br />
de/volunteer.wml       813) Effort Level: <i>Medium</i>
de/volunteer.wml       814) <br />
de/volunteer.wml       815) Skill Level: <i>Medium</i>
de/volunteer.wml       816) <br />
de/volunteer.wml       817) Likely Mentors: <i>Jacob</i>
de/volunteer.wml       818) <br />

de/volunteer.wml       819) The Tor Project has been working over the past year to set up web-based
de/volunteer.wml       820) tools to help volunteers translate our applications into other languages.
de/volunteer.wml       821) We finally hit upon Pootle, and we have a fine web-based translation engine
de/volunteer.wml       822) in place for Vidalia, Torbutton, and Torcheck. However, Pootle only
de/volunteer.wml       823) translates strings that are in the "po" format, and our website uses wml
de/volunteer.wml       824) files. This project is about finding a way to convert our wml files into po
de/volunteer.wml       825) strings and back, so they can be handled by Pootle.
de/volunteer.wml       826) </li>

de/volunteer.wml       827) 

de/volunteer.wml       828) <li>
de/volunteer.wml       829) <b>New Thandy Features</b>
de/volunteer.wml       830) <br />
de/volunteer.wml       831) Priority: <i>Medium</i>
de/volunteer.wml       832) <br />
de/volunteer.wml       833) Effort Level: <i>Medium</i>
de/volunteer.wml       834) <br />
de/volunteer.wml       835) Skill Level: <i>Medium to High</i>
de/volunteer.wml       836) <br />
de/volunteer.wml       837) Likely Mentors: <i>Martin</i>
de/volunteer.wml       838) <br />
de/volunteer.wml       839) Additional capabilities are needed for assisted updates of all the Tor
de/volunteer.wml       840) related software for Windows and other operating systems. Some of the
de/volunteer.wml       841) features to consider include:
de/volunteer.wml       842) 1) Integration of the <a
de/volunteer.wml       843) href="http://chandlerproject.org/Projects/MeTooCrypto">MeTooCrypto
de/volunteer.wml       844) Python library</a>
de/volunteer.wml       845) for authenticated HTTPS downloads. 2) Adding a level of indirection
de/volunteer.wml       846) between the timestamp signatures and the package files included in an
de/volunteer.wml       847) update. See the "Thandy attacks / suggestions" thread on or-dev.
de/volunteer.wml       848) 3) Support locale specific installation and configuration of assisted
de/volunteer.wml       849) updates based on preference, host, or user account language settings.
de/volunteer.wml       850) Familiarity with Windows codepages, unicode, and other character sets
de/volunteer.wml       851) is helpful in addition to general win32 and posix API experience and
de/volunteer.wml       852) Python proficiency.
de/volunteer.wml       853) </li>
de/volunteer.wml       854) 
de/volunteer.wml       855) <li>
de/volunteer.wml       856) <b>Intermediate Level Network Device Driver</b>
de/volunteer.wml       857) <br />
de/volunteer.wml       858) Priority: <i>Low</i>
de/volunteer.wml       859) <br />
de/volunteer.wml       860) Effort Level: <i>High</i>
de/volunteer.wml       861) <br />
de/volunteer.wml       862) Skill Level: <i>High</i>
de/volunteer.wml       863) <br />
de/volunteer.wml       864) Likely Mentors: <i>Martin</i>
de/volunteer.wml       865) <br />
de/volunteer.wml       866) The WinPCAP device driver used by Tor VM for bridged networking does
de/volunteer.wml       867) not support a number of wireless and non-Ethernet network adapters.
de/volunteer.wml       868) Implementation of a intermediate level network device driver for win32
de/volunteer.wml       869) and 64bit would provide a way to intercept and route traffic over such
de/volunteer.wml       870) networks. This project will require knowledge of and experience with
de/volunteer.wml       871) Windows kernel device driver development and testing. Familiarity with
de/volunteer.wml       872) Winsock and Qemu would also be helpful.
de/volunteer.wml       873) </li>
de/volunteer.wml       874) 
de/volunteer.wml       875) <li>
de/volunteer.wml       876) <b>Tor Browser Bundle for Linux/Mac OS X</b>
de/volunteer.wml       877) <br />
de/volunteer.wml       878) Priority: <i>High</i>
de/volunteer.wml       879) <br />
de/volunteer.wml       880) Effort Level: <i>High</i>
de/volunteer.wml       881) <br />
de/volunteer.wml       882) Skill Level: <i>Medium</i>
de/volunteer.wml       883) <br />
de/volunteer.wml       884) Likely Mentors: <i>Steven</i>
de/volunteer.wml       885) <br />
de/volunteer.wml       886) The Tor Browser bundle incorporates Tor, Firefox, and the Vidalia user
de/volunteer.wml       887) interface (and optionally Pidgin IM). Components are pre-configured to
de/volunteer.wml       888) operate in a secure way, and it has very few dependencies on the
de/volunteer.wml       889) installed operating system. It has therefore become one of the most
de/volunteer.wml       890) easy to use, and popular, ways to use Tor on Windows.
de/volunteer.wml       891) <br />
de/volunteer.wml       892) However, there is currently no comparable package for Linux and Mac OS
de/volunteer.wml       893) X, so this project would be to implement Tor Browser Bundle for these
de/volunteer.wml       894) platforms. This will involve modifications to Vidalia (C++), possibly
de/volunteer.wml       895) Firefox (C) then creating and testing the launcher on a range of
de/volunteer.wml       896) operating system versions and configurations to verify portability.
de/volunteer.wml       897) <br />
de/volunteer.wml       898) Students should be familiar with application development on one or
de/volunteer.wml       899) preferably both of Linux and Mac OS X, and be comfortable with C/C++
de/volunteer.wml       900) and shell scripting.
de/volunteer.wml       901) </li>
de/volunteer.wml       902) 
de/volunteer.wml       903) <li>
de/volunteer.wml       904) <b>Simulator for slow Internet connections</b>
de/volunteer.wml       905) <br />
de/volunteer.wml       906) Priority: <i>Medium</i>
de/volunteer.wml       907) <br />
de/volunteer.wml       908) Effort Level: <i>Medium</i>
de/volunteer.wml       909) <br />
de/volunteer.wml       910) Skill Level: <i>Medium</i>
de/volunteer.wml       911) <br />
de/volunteer.wml       912) Likely Mentors: <i>Steven</i>
de/volunteer.wml       913) <br />
de/volunteer.wml       914) Many users of Tor have poor-quality Internet connections, giving low
de/volunteer.wml       915) bandwidth, high latency, and high packet loss/re-ordering. User
de/volunteer.wml       916) experience is that Tor reacts badly to these conditions, but it is
de/volunteer.wml       917) difficult to improve the situation without being able to repeat the
de/volunteer.wml       918) problems in the lab.
de/volunteer.wml       919) <br />
de/volunteer.wml       920) This project would be to build a simulation environment which
de/volunteer.wml       921) replicates the poor connectivity so that the effect on Tor performance
de/volunteer.wml       922) can be measured. Other components would be a testing utility to
de/volunteer.wml       923) establish what are the properties of connections available, and to
de/volunteer.wml       924) measure the effect of performance-improving modifications to Tor.
de/volunteer.wml       925) <br />
de/volunteer.wml       926) The tools used would be up to the student, but dummynet (for FreeBSD)
de/volunteer.wml       927) and nistnet (for Linux) are two potential components on which this
de/volunteer.wml       928) project could be built. Students should be experienced with network
de/volunteer.wml       929) programming/debugging and TCP/IP, and preferably familiar with C and a
de/volunteer.wml       930) scripting language.
de/volunteer.wml       931) </li>
de/volunteer.wml       932) 

de/volunteer.wml       933) <li>
de/volunteer.wml       934) <b>Bring up new ideas!</b>
de/volunteer.wml       935) <br />
de/volunteer.wml       936) Don't like any of these? Look at the <a

de/volunteer.wml       937) href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development

de/volunteer.wml       938) roadmap</a> for more ideas.

de/volunteer.wml       939) Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>
de/volunteer.wml       940) might also be short on developers.

de/volunteer.wml       941) </li>
de/volunteer.wml       942) 
de/volunteer.wml       943) </ol>
de/volunteer.wml       944) 

de/volunteer.wml       945) <a id="OtherCoding"></a>

de/volunteer.wml       946) <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
de/volunteer.wml       947) <ol>
de/volunteer.wml       948) <li>Tor relays don't work well on Windows XP. On
de/volunteer.wml       949) Windows, Tor uses the standard <tt>select()</tt> system
de/volunteer.wml       950) call, which uses space in the non-page pool. This means
de/volunteer.wml       951) that a medium sized Tor relay will empty the non-page pool, <a
de/volunteer.wml       952) href="https://wiki.torproject.org/noreply/TheOnionRouter/WindowsBufferProblems">causing
de/volunteer.wml       953) havoc and system crashes</a>. We should probably be using overlapped IO
de/volunteer.wml       954) instead. One solution would be to teach <a
de/volunteer.wml       955) href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
de/volunteer.wml       956) overlapped IO rather than select() on Windows, and then adapt Tor to
de/volunteer.wml       957) the new libevent interface. Christian King made a
de/volunteer.wml       958) <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
de/volunteer.wml       959) start</a> on this in the summer of 2007.</li>

de/volunteer.wml       960) 

de/volunteer.wml       961) <li>We need to actually start building our <a href="<page
de/volunteer.wml       962) documentation>#DesignDoc">blocking-resistance design</a>. This involves
de/volunteer.wml       963) fleshing out the design, modifying many different pieces of Tor, adapting
de/volunteer.wml       964) <a href="http://vidalia-project.net/">Vidalia</a> so it supports the
de/volunteer.wml       965) new features, and planning for deployment.</li>

de/volunteer.de.html   966) 

de/volunteer.wml       967) <li>We need a flexible simulator framework for studying end-to-end
de/volunteer.wml       968) traffic confirmation attacks. Many researchers have whipped up ad hoc
de/volunteer.wml       969) simulators to support their intuition either that the attacks work
de/volunteer.wml       970) really well or that some defense works great. Can we build a simulator
de/volunteer.wml       971) that's clearly documented and open enough that everybody knows it's
de/volunteer.wml       972) giving a reasonable answer? This will spur a lot of new research.
de/volunteer.wml       973) See the entry <a href="#Research">below</a> on confirmation attacks for
de/volunteer.wml       974) details on the research side of this task &mdash; who knows, when it's
de/volunteer.wml       975) done maybe you can help write a paper or three also.</li>
de/volunteer.wml       976) 
de/volunteer.wml       977) <li>Tor 0.1.1.x and later include support for hardware crypto accelerators
de/volunteer.wml       978) 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>
de/volunteer.wml       979) 
de/volunteer.wml       980) <li>Perform a security analysis of Tor with <a
de/volunteer.wml       981) href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
de/volunteer.wml       982) if there are good fuzzing libraries out there for what we want. Win fame by
de/volunteer.wml       983) getting credit when we put out a new release because of you!</li>
de/volunteer.wml       984) 
de/volunteer.wml       985) <li>Tor uses TCP for transport and TLS for link
de/volunteer.wml       986) encryption. This is nice and simple, but it means all cells
de/volunteer.wml       987) on a link are delayed when a single packet gets dropped, and
de/volunteer.wml       988) it means we can only reasonably support TCP streams. We have a <a
de/volunteer.wml       989) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
de/volunteer.wml       990) of reasons why we haven't shifted to UDP transport</a>, but it would
de/volunteer.wml       991) be great to see that list get shorter. We also have a proposed <a
de/volunteer.wml       992) href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
de/volunteer.wml       993) for Tor and
de/volunteer.wml       994) UDP</a> &mdash; please let us know what's wrong with it.</li>
de/volunteer.wml       995) 
de/volunteer.wml       996) <li>We're not that far from having IPv6 support for destination addresses
de/volunteer.wml       997) (at exit nodes). If you care strongly about IPv6, that's probably the
de/volunteer.wml       998) first place to start.</li>
de/volunteer.wml       999) 
de/volunteer.wml      1000) <li>We need a way to generate the website diagrams (for example, the "How
de/volunteer.wml      1001) Tor Works" pictures on the <a href="<page overview>">overview page</a>
de/volunteer.wml      1002) from source, so we can translate them as UTF-8 text rather than edit
de/volunteer.wml      1003) them by hand with Gimp. We might want to
de/volunteer.wml      1004) integrate this as an wml file so translations are easy and images are
de/volunteer.wml      1005) generated in multiple languages whenever we build the website.</li>
de/volunteer.wml      1006) 
de/volunteer.wml      1007) <li>How can we make the <a

de/volunteer.wml      1008) href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a>

de/volunteer.wml      1009) easier to maintain, improve, and document?</li>

de/volunteer.de.html  1010) </ol>

de/contribute.de.html 1011) 

de/volunteer.wml      1012) <a id="Research"></a>

de/volunteer.wml      1013) <h2><a class="anchor" href="#Research">Research</a></h2>

de/volunteer.de.html  1014) <ol>

de/volunteer.wml      1015) <li>The "website fingerprinting attack": make a list of a few
de/volunteer.wml      1016) hundred popular websites, download their pages, and make a set of
de/volunteer.wml      1017) "signatures" for each site. Then observe a Tor client's traffic. As
de/volunteer.wml      1018) you watch him receive data, you quickly approach a guess about which
de/volunteer.wml      1019) (if any) of those sites he is visiting. First, how effective is
de/volunteer.wml      1020) this attack on the deployed Tor codebase? Then start exploring
de/volunteer.wml      1021) defenses: for example, we could change Tor's cell size from 512
de/volunteer.wml      1022) bytes to 1024 bytes, we could employ padding techniques like <a
de/volunteer.wml      1023) href="http://freehaven.net/anonbib/#timing-fc2004">defensive dropping</a>,
de/volunteer.wml      1024) or we could add traffic delays. How much of an impact do these have,
de/volunteer.wml      1025) and how much usability impact (using some suitable metric) is there from
de/volunteer.wml      1026) a successful defense in each case?</li>
de/volunteer.wml      1027) <li>The "end-to-end traffic confirmation attack":
de/volunteer.wml      1028) by watching traffic at Alice and at Bob, we can <a
de/volunteer.wml      1029) href="http://freehaven.net/anonbib/#danezis:pet2004">compare
de/volunteer.wml      1030) traffic signatures and become convinced that we're watching the same
de/volunteer.wml      1031) stream</a>. So far Tor accepts this as a fact of life and assumes this
de/volunteer.wml      1032) attack is trivial in all cases. First of all, is that actually true? How
de/volunteer.wml      1033) much traffic of what sort of distribution is needed before the adversary
de/volunteer.wml      1034) is confident he has won? Are there scenarios (e.g. not transmitting much)
de/volunteer.wml      1035) that slow down the attack? Do some traffic padding or traffic shaping
de/volunteer.wml      1036) schemes work better than others?</li>
de/volunteer.wml      1037) <li>A related question is: Does running a relay/bridge provide additional
de/volunteer.wml      1038) protection against these timing attacks? Can an external adversary that can't
de/volunteer.wml      1039) see inside TLS links still recognize individual streams reliably?
de/volunteer.wml      1040) Does the amount of traffic carried degrade this ability any? What if the
de/volunteer.wml      1041) client-relay deliberately delayed upstream relayed traffic to create a queue
de/volunteer.wml      1042) that could be used to mimic timings of client downstream traffic to make it
de/volunteer.wml      1043) look like it was also relayed? This same queue could also be used for masking
de/volunteer.wml      1044) timings in client upstream traffic with the techniques from <a
de/volunteer.wml      1045) href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
de/volunteer.wml      1046) but without the need for additional traffic. Would such an interleaving of
de/volunteer.wml      1047) client upstream traffic obscure timings for external adversaries? Would the
de/volunteer.wml      1048) strategies need to be adjusted for asymmetric links? For example, on
de/volunteer.wml      1049) asymmetric links, is it actually possible to differentiate client traffic from
de/volunteer.wml      1050) natural bursts due to their asymmetric capacity? Or is it easier than
de/volunteer.wml      1051) symmetric links for some other reason?</li>
de/volunteer.wml      1052) <li>Repeat Murdoch and Danezis's <a
de/volunteer.wml      1053) href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
de/volunteer.wml      1054) Oakland 05</a> on the current Tor network. See if you can learn why it
de/volunteer.wml      1055) works well on some nodes and not well on others. (My theory is that the
de/volunteer.wml      1056) fast nodes with spare capacity resist the attack better.) If that's true,
de/volunteer.wml      1057) then experiment with the RelayBandwidthRate and RelayBandwidthBurst
de/volunteer.wml      1058) options to run a relay that is used as a client while relaying the
de/volunteer.wml      1059) attacker's traffic: as we crank down the RelayBandwidthRate, does the
de/volunteer.wml      1060) attack get harder? What's the right ratio of RelayBandwidthRate to
de/volunteer.wml      1061) actually capacity? Or is it a ratio at all? While we're at it, does a
de/volunteer.wml      1062) much larger set of candidate relays increase the false positive rate
de/volunteer.wml      1063) or other complexity for the attack? (The Tor network is now almost two
de/volunteer.wml      1064) orders of magnitude larger than it was when they wrote their paper.) Be
de/volunteer.wml      1065) sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
de/volunteer.wml      1066) Clog the Queue</a> too.</li>
de/volunteer.wml      1067) <li>The "routing zones attack": most of the literature thinks of
de/volunteer.wml      1068) the network path between Alice and her entry node (and between the
de/volunteer.wml      1069) exit node and Bob) as a single link on some graph. In practice,
de/volunteer.wml      1070) though, the path traverses many autonomous systems (ASes), and <a
de/volunteer.wml      1071) href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
de/volunteer.wml      1072) that the same AS appears on both the entry path and the exit path</a>.
de/volunteer.wml      1073) Unfortunately, to accurately predict whether a given Alice, entry,
de/volunteer.wml      1074) exit, Bob quad will be dangerous, we need to download an entire Internet
de/volunteer.wml      1075) routing zone and perform expensive operations on it. Are there practical
de/volunteer.wml      1076) approximations, such as avoiding IP addresses in the same /8 network?</li>
de/volunteer.wml      1077) <li>Other research questions regarding geographic diversity consider
de/volunteer.wml      1078) the tradeoff between choosing an efficient circuit and choosing a random
de/volunteer.wml      1079) circuit. Look at Stephen Rollyson's <a
de/volunteer.wml      1080) href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
de/volunteer.wml      1081) paper</a> on how to discard particularly slow choices without hurting
de/volunteer.wml      1082) anonymity "too much". This line of reasoning needs more work and more
de/volunteer.wml      1083) thinking, but it looks very promising.</li>
de/volunteer.wml      1084) <li>Tor doesn't work very well when relays have asymmetric bandwidth
de/volunteer.wml      1085) (e.g. cable or DSL). Because Tor has separate TCP connections between
de/volunteer.wml      1086) each hop, if the incoming bytes are arriving just fine and the outgoing
de/volunteer.wml      1087) bytes are all getting dropped on the floor, the TCP push-back mechanisms
de/volunteer.wml      1088) don't really transmit this information back to the incoming streams.
de/volunteer.wml      1089) Perhaps Tor should detect when it's dropping a lot of outgoing packets,
de/volunteer.wml      1090) and rate-limit incoming streams to regulate this itself? I can imagine
de/volunteer.wml      1091) a build-up and drop-off scheme where we pick a conservative rate-limit,
de/volunteer.wml      1092) slowly increase it until we get lost packets, back off, repeat. We
de/volunteer.wml      1093) need somebody who's good with networks to simulate this and help design
de/volunteer.wml      1094) solutions; and/or we need to understand the extent of the performance
de/volunteer.wml      1095) degradation, and use this as motivation to reconsider UDP transport.</li>
de/volunteer.wml      1096) <li>A related topic is congestion control. Is our
de/volunteer.wml      1097) current design sufficient once we have heavy use? Maybe
de/volunteer.wml      1098) we should experiment with variable-sized windows rather
de/volunteer.wml      1099) than fixed-size windows? That seemed to go well in an <a
de/volunteer.wml      1100) href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">ssh
de/volunteer.wml      1101) throughput experiment</a>. We'll need to measure and tweak, and maybe
de/volunteer.wml      1102) overhaul if the results are good.</li>
de/volunteer.wml      1103) <li>Our censorship-resistance goals include preventing
de/volunteer.wml      1104) an attacker who's looking at Tor traffic on the wire from <a
de/volunteer.wml      1105) href="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
de/volunteer.wml      1106) it from normal SSL traffic</a>. Obviously we can't achieve perfect
de/volunteer.wml      1107) steganography and still remain usable, but for a first step we'd like to
de/volunteer.wml      1108) block any attacks that can win by observing only a few packets. One of
de/volunteer.wml      1109) the remaining attacks we haven't examined much is that Tor cells are 512
de/volunteer.wml      1110) bytes, so the traffic on the wire may well be a multiple of 512 bytes.
de/volunteer.wml      1111) How much does the batching and overhead in TLS records blur this on the
de/volunteer.wml      1112) wire? Do different buffer flushing strategies in Tor affect this? Could
de/volunteer.wml      1113) a bit of padding help a lot, or is this an attack we must accept?</li>
de/volunteer.wml      1114) <li>Tor circuits are built one hop at a time, so in theory we have the
de/volunteer.wml      1115) ability to make some streams exit from the second hop, some from the
de/volunteer.wml      1116) third, and so on. This seems nice because it breaks up the set of exiting
de/volunteer.wml      1117) streams that a given relay can see. But if we want each stream to be safe,
de/volunteer.wml      1118) the "shortest" path should be at least 3 hops long by our current logic, so
de/volunteer.wml      1119) the rest will be even longer. We need to examine this performance / security
de/volunteer.wml      1120) tradeoff.</li>
de/volunteer.wml      1121) <li>It's not that hard to DoS Tor relays or directory authorities. Are client
de/volunteer.wml      1122) puzzles the right answer? What other practical approaches are there? Bonus
de/volunteer.wml      1123) if they're backward-compatible with the current Tor protocol.</li>
de/volunteer.wml      1124) <li>Programs like <a
de/volunteer.wml      1125) href="<page torbutton/index>">Torbutton</a> aim to hide
de/volunteer.wml      1126) your browser's UserAgent string by replacing it with a uniform answer for
de/volunteer.wml      1127) every Tor user. That way the attacker can't splinter Tor's anonymity set
de/volunteer.wml      1128) by looking at that header. It tries to pick a string that is commonly used
de/volunteer.wml      1129) by non-Tor users too, so it doesn't stand out. Question one: how badly
de/volunteer.wml      1130) do we hurt ourselves by periodically updating the version of Firefox
de/volunteer.wml      1131) that Torbutton claims to be? If we update it too often, we splinter the
de/volunteer.wml      1132) anonymity sets ourselves. If we don't update it often enough, then all the
de/volunteer.wml      1133) Tor users stand out because they claim to be running a quite old version
de/volunteer.wml      1134) of Firefox. The answer here probably depends on the Firefox versions seen
de/volunteer.wml      1135) in the wild. Question two: periodically people ask us to cycle through N
de/volunteer.wml      1136) UserAgent strings rather than stick with one. Does this approach help,
de/volunteer.wml      1137) hurt, or not matter? Consider: cookies and recognizing Torbutton users
de/volunteer.wml      1138) by their rotating UserAgents; malicious websites who only attack certain
de/volunteer.wml      1139) browsers; and whether the answers to question one impact this answer.
de/volunteer.wml      1140) </li>
de/volunteer.wml      1141) <li>Right now Tor clients are willing to reuse a given circuit for ten
de/volunteer.wml      1142) minutes after it's first used. The goal is to avoid loading down the
de/volunteer.wml      1143) network with too many circuit extend operations, yet to also avoid having
de/volunteer.wml      1144) clients use the same circuit for so long that the exit node can build a
de/volunteer.wml      1145) useful pseudonymous profile of them. Alas, ten minutes is probably way
de/volunteer.wml      1146) too long, especially if connections from multiple protocols (e.g. IM and
de/volunteer.wml      1147) web browsing) are put on the same circuit. If we keep fixed the overall
de/volunteer.wml      1148) number of circuit extends that the network needs to do, are there more
de/volunteer.wml      1149) efficient and/or safer ways for clients to allocate streams to circuits,
de/volunteer.wml      1150) or for clients to build preemptive circuits? Perhaps this research item
de/volunteer.wml      1151) needs to start with gathering some traces of what connections typical
de/volunteer.wml      1152) clients try to launch, so you have something realistic to try to optimize.
de/volunteer.wml      1153) </li>
de/volunteer.wml      1154) <li>How many bridge relays do you need to know to maintain
de/volunteer.wml      1155) reachability? We should measure the churn in our bridges. If there is
de/volunteer.wml      1156) lots of churn, are there ways to keep bridge users more likely to stay
de/volunteer.wml      1157) connected?
de/volunteer.wml      1158) </li>
de/volunteer.wml      1159) </ol>

de/contribute.de.html 1160) 

de/volunteer.wml      1161) <p><a href="<page contact>">Lass uns wissen</a>, wenn du bei einem
de/volunteer.wml      1162)   dieser Punkte Fortschritte gemacht hast.</p>

de/contribute.de.html 1163) 
de/contribute.de.html 1164) </div><!-- #main -->