tor-webwml.git

it/volunteer.wml         1) ## translation metadata

it/volunteer.wml         2) # Based-On-Revision: 13989

it/volunteer.wml         3) # Last-Translator: jan at seul dot org

it/contribute.it.html    4) 

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

it/contribute.it.html    6) 
it/contribute.it.html    7) <div class="main-column">
it/contribute.it.html    8) 

it/volunteer.wml         9) <!-- PUT CONTENT AFTER THIS TAG -->

it/volunteer.wml        10) <h2>Tre cose che puoi fare subito:</h2>

it/volunteer.wml        11) <ol>

it/volunteer.wml        12) <li>Puoi <a href="<page docs/tor-doc-relay>">realizzare
it/volunteer.wml        13) un relay</a> per aiutare a far crescere la rete Tor.</li>
it/volunteer.wml        14) <li>Parla coi tuoi amici! Fagli realizzare un relay. Fagli aprire degli hidden

it/volunteer.wml        15) services. Falli parlare di Tor coi loro amici.</li>

it/volunteer.wml        16) <li>Cerchiamo finanziamenti e sponsor. Se ne apprezzi gli obiettivi, per favore

it/volunteer.wml        17)   <a href="<page donate>">fai una donazione per sostenere

it/volunteer.wml        18) lo sviluppo di Tor</a>. Se conosci qualche azienda, ente o

it/volunteer.wml        19) associazione che ha bisogno di sicurezza nelle
it/volunteer.wml        20) comunicazioni, fagli conoscere il progetto Tor.</li>
it/volunteer.wml        21) </ol>

it/contribute.it.html   22) 

it/volunteer.wml        23) <a id="Usability"></a>

it/volunteer.wml        24) <h2><a class="anchor" href="#Usability">Applicazioni di supporto</a></h2>

it/volunteer.wml        25) <ol>

it/volunteer.wml        26) <li>Servono altri buoni metodi per intercettare le richieste DNS in modo che non siano svelate

it/volunteer.wml        27) a un osservatore locale mentre cerchiamo di essere anonimi. (Ciò

it/volunteer.wml        28) succede se l'applicazione esegue la risoluzione DNS prima di rivolgersi

it/volunteer.wml        29) al proxy SOCKS.)</li>

it/volunteer.wml        30) <li>Tsocks/dsocks:

it/volunteer.wml        31) <ul>
it/volunteer.wml        32) <li>C'&egrave; bisogno di <a

it/volunteer.wml        33) href="https://wiki.torproject.org/noreply/TheOnionRouter/TSocksPatches">applicare

it/volunteer.wml        34) tutte le nostre patch a tsocks</a> e mantenerne un nuovo fork. Lo possiamo ospitare sul
it/volunteer.wml        35) nostro server se vuoi.</li>
it/volunteer.wml        36) <li>Bisognerebbe applicate le patch al programma "dsocks" di Dug Song in modo che usi
it/volunteer.wml        37) i comandi <i>mapaddress</i> di Tor dall'interfaccia di controllo, cos&igrave;
it/volunteer.wml        38) da non sprecare un intero ciclo in Tor per fare la risoluzione prima di
it/volunteer.wml        39) connettersi.</li>
it/volunteer.wml        40) <li>Dobbiamo fare in modo che il nostro script <i>torify</i> distingua se siano installati tsocks o
it/volunteer.wml        41) dsocks, e li chiami di conseguenza. Ci&ograve; significa probabilemnte
it/volunteer.wml        42) unificarne le interfacce e potrebbe essere necessario condividere del codice tra di essi
it/volunteer.wml        43) o scartarne uno direttamente.</li>
it/volunteer.wml        44) </ul>

it/volunteer.wml        45) </li>

it/volunteer.wml        46) <li>Chi gestisce un relay spesso vuole avere un BandwidthRate
it/volunteer.wml        47) durante parte della giornata, e un altro BandwidthRate nell'altra
it/volunteer.wml        48) parte del giorno. Invece di programmarlo dentro Tor, sarebbe bello avere
it/volunteer.wml        49) un piccolo script che parla tramite la <a href="<page gui/index>">Tor
it/volunteer.wml        50) Controller Interface</a> e fa un setconf per modificare la banda disponibile.
it/volunteer.wml        51) Ce n'&egrave; gi&agrave; uno per Unix e Mac (usa bash e cron),
it/volunteer.wml        52) ma gli utenti Windows hanno ancora bisogno di una soluzione.

it/volunteer.wml        53) </li>

it/volunteer.wml        54) <li>Tor pu&ograve; <a

it/volunteer.wml        55) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ChooseEntryExit">uscire dalla

it/volunteer.wml        56) rete Tor network da un particolare exit node</a>, ma dovremmo riuscire a
it/volunteer.wml        57) specificare solo una certa nazione e  fare scegliere l'exit node automaticamente. La
it/volunteer.wml        58) cosa migliore sembra prendere la directory Blossom e usare un client Blossom
it/volunteer.wml        59) locale che recuperi la directory in modo sicuro (via Tor e verificandone la
it/volunteer.wml        60) firma), intercetti i <tt>.country.blossom</tt> hostname, e faccia
it/volunteer.wml        61) la cosa giusta.</li>

it/volunteer.wml        62) <li>A proposito di geolocalizzazione, qualcuno potrebbe disegnare un mappamondo

it/volunteer.wml        63) indicante tutti i relay Tor. Un premio se si aggiorna man mano che

it/volunteer.wml        64) la rete cresce e cambia. Purtroppo la maniera più semplice per farlo implica
it/volunteer.wml        65) inviare tutti i dati a Google che disegni la mappa per te. Che
it/volunteer.wml        66) conseguenze ha per la privacy? Ci sono altre buone soluzioni?</li>
it/volunteer.wml        67) 

it/volunteer.wml        68) </ol>

it/contribute.it.html   69) 

it/volunteer.wml        70) <a id="Documentation"></a>
it/volunteer.wml        71) <h2><a class="anchor" href="#Documentation">Documentazione</a></h2>
it/volunteer.wml        72) <ol>

it/volunteer.wml        73) <li>Aiuta Matt Edman con la documentazione e con le guide del suo

it/volunteer.wml        74) Tor controller,
it/volunteer.wml        75) <a href="http://vidalia-project.net/">Vidalia</a>.</li>

it/volunteer.wml        76) <li>Analizzare e documentare

it/volunteer.wml        77) <a href="https://wiki.torproject.org/wiki/TheOnionRouter/TorifyHOWTO">la

it/volunteer.wml        78) nostra lista di programmi</a> configurabili per essere usati con Tor.</li>
it/volunteer.wml        79) <li>Abbiamo bisogno di una documentazione migliore per intercettare dinamicamente
it/volunteer.wml        80) le connessioni e inviarle via Tor. tsocks (Linux), dsocks (BSD),

it/volunteer.wml        81) e freecap (Windows) sembrano dei buoni candidati, come pure un miglior uso
it/volunteer.wml        82) della nosta nuova funzione TransPort.</li>
it/volunteer.wml        83) 

it/volunteer.wml        84) <li>C'&egrave; una lista immensa di <a href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">programmi potenzialmente

it/volunteer.wml        85) utili che si interfacciano con Tor</a>. In quali situazioni sono utili?
it/volunteer.wml        86) Aiutaci a testarli e a documentare i risultati.</li>

it/volunteer.wml        87) <li>Aiuta a tradurre e migliorare le pagine web e la documentazione in altre

it/volunteer.wml        88) lingue. Vedi le <a href="<page translation>">linee guida per

it/volunteer.wml        89) la traduzione</a> se vuoi dare una mano. Servono in particolare traduzioni in

it/volunteer.wml        90) Arabo e Farsi, per i tanti utenti Tor in aree dove vige la censura.
it/volunteer.wml        91) Serve anche aiuto per correggere e migliorare questa traduzione italiana.</li>

it/volunteer.wml        92) </ol>
it/volunteer.wml        93) 
it/volunteer.wml        94) <a id="Coding"></a>

it/volunteer.wml        95) <a id="Summer"></a>
it/volunteer.wml        96) <a id="Projects"></a>
it/volunteer.wml        97) <h2><a class="anchor" href="#Projects">Progetti di siluppo software</a></h2>
it/volunteer.wml        98) 
it/volunteer.wml        99) <p>
it/volunteer.wml       100) Alcuni di questi progetti potrebbero essere dei buoni candidati per <a href="<page
it/volunteer.wml       101) +gsoc>">Google Summer of Code 2008</a>. Abbiamo classificato ogni idea
it/volunteer.wml       102) secondo l'utilit&agrave; complessiva al progetto Tor
it/volunteer.wml       103) (priorit&agrave;), quanto lavoro stimiamo sia necessario (livello d'impegno), quante
it/volunteer.wml       104) conoscenze servono per iniziare (livello di competenze), e quali dei nostri <a href="<page
it/volunteer.wml       105) +people>#Core">principali programmatori</a> potrebbero essere dei buoni mentori.
it/volunteer.wml       106) </p>
it/volunteer.wml       107) <p>
it/volunteer.wml       108) (NdT: Le  schede di alcuni progetti sono in inglese e verranno tradotte man mano.)
it/volunteer.wml       109) </p>
it/volunteer.wml       110) <ol>
it/volunteer.wml       111) 
it/volunteer.wml       112) <li>
it/volunteer.wml       113) <b>Framework per l'aggiornamento automatico di Tor/Polipo/Vidalia Framework</b>
it/volunteer.wml       114) <br />
it/volunteer.wml       115) Priorit&agrave;: <i>Alta</i>
it/volunteer.wml       116) <br />
it/volunteer.wml       117) Impegno: <i>Alto</i>
it/volunteer.wml       118) <br />
it/volunteer.wml       119) Competenze: <i>Alte</i>
it/volunteer.wml       120) <br />
it/volunteer.wml       121) Possibili mentori: <i>Matt, Jacob</i>
it/volunteer.wml       122) <br />
it/volunteer.wml       123) Ci seve un buon framework per l'aggiornamento autenticato.
it/volunteer.wml       124) Vidalia si accorge gi&agrave; se l'utente ha una versione obsoleta
it/volunteer.wml       125) o deprecata di Tor, tramite dei signed statement nelle informazioni
it/volunteer.wml       126) di directory Tor. Al momento Vidalia manda una semplice
it/volunteer.wml       127) finestra di avviso che informa l'utente che dovrebbe aggiornare manualmente.
it/volunteer.wml       128) Lo scopo del progetto &egrave; di estendere Vidalia aggiungendo la
it/volunteer.wml       129) possibilit&agrave; di scaricare e installare il software Tor aggiornato al
it/volunteer.wml       130) posto dell'utente. Il download dovrebbe avenire via Tor quando possibile, con un buon
it/volunteer.wml       131) meccanismo di fall back al download diretto. Tempo permettendo sarebbe bello
it/volunteer.wml       132) potere aggiornare altre applicazioni
it/volunteer.wml       133) contenute nei pacchetti di installazione, come Polipo e
it/volunteer.wml       134) Vidalia stessa.
it/volunteer.wml       135) <br />
it/volunteer.wml       136) Per portare a termine il progetto, lo studente dovr&agrave; anzitutto studiare
it/volunteer.wml       137) il framework di auto-update esistente (ad es., Sparkle su OS X) per valutarne
it/volunteer.wml       138) vantaggi, debolezze, fattori di sicurezza e possibilit&agrave; di venire
it/volunteer.wml       139) integrato in Vidalia. Se non se ne trovano di adatti, lo studente
it/volunteer.wml       140) disegner&agrave; uno proprio frameword di auto aggiornamento, documentando il disegno e
it/volunteer.wml       141) discutendolo con altri sviluppatori per verificarne gli aspetti di sicurezza.
it/volunteer.wml       142) Lo studente realizzer&agrave; poi il framework (o lo integrer&agrave; con
it/volunteer.wml       143) uno esistente) e lo sottoporr6agrave; a test.
it/volunteer.wml       144) <br />
it/volunteer.wml       145) Gli studenti interessati a questo progetto devono avere una buona esperienza di sviluppo
it/volunteer.wml       146) in C++. Utili, ma non obbligatorie, esperienze di Qt. Occorre anche
it/volunteer.wml       147) una buona comprensione delle comuni pratiche di sicurezza,
it/volunteer.wml       148) come la package signature verification. Importanti per il progetto anche buone
it/volunteer.wml       149) capacit&agrave; di comunicazione scritta, poich&eacute; una fase cruciale
it/volunteer.wml       150) sar&agrave; la produzione di un design document che altri valuteranno e discuteranno
it/volunteer.wml       151) con lo studente prima della realizzazione.
it/volunteer.wml       152) </li>
it/volunteer.wml       153) 
it/volunteer.wml       154) <li>
it/volunteer.wml       155) <b>Una Network Map per Vidalia migliore e pi&ugrave; usabile</b>
it/volunteer.wml       156) <br />
it/volunteer.wml       157) Priorit&agrave;: <i>Media</i>
it/volunteer.wml       158) <br />
it/volunteer.wml       159) Impegno: <i>Medio</i>
it/volunteer.wml       160) <br />
it/volunteer.wml       161) Competenze: <i>Medio-alte</i>
it/volunteer.wml       162) <br />
it/volunteer.wml       163) Possibili mentori: <i>Matt</i>
it/volunteer.wml       164) <br />
it/volunteer.wml       165) Vidalia ha una carta della rete che mostra all'utente la posizione
it/volunteer.wml       166) geografica approssimata dei nodi nella rete Tor e che
it/volunteer.wml       167) disegna il percorso del traffico dell'utente attraverso i tunnel stabiliti nella
it/volunteer.wml       168) rete Tor. The mappa per ora non &egrave; molto interattiva ed ha una grafica
it/volunteer.wml       169) spartana. Ci piacerebbe usare il widget KDE Marble che
it/volunteer.wml       170) crea mappe di miglior qualit&agrave; ed offre maggior einterattivit&agrave;,
it/volunteer.wml       171) permettendo all'utente di fare clic su singoli nodi o circuiti per ottenere
it/volunteer.wml       172) maggiori informazioni. Potremmo anche permettere all'utente di fare
it/volunteer.wml       173) clic su un particolare nodo o su un paese contenente uno o pi&ugrave;
it/volunteer.wml       174) Tor exit relay e dire, ad esempio: "Voglio che le mie connessioni a pippo.com
it/volunteer.wml       175) escano da qui."
it/volunteer.wml       176) <br />
it/volunteer.wml       177) Questo progetto richiede anzitutto che lo studente si familiarizzi con Vidalia
it/volunteer.wml       178) e le API del widget Marble. Lo studente integrer&agrave; poi il widget
it/volunteer.wml       179) in Vidalia e personalizzer&agrave; Marble per adattarlo meglio ai nostri bisogni,
it/volunteer.wml       180) ad esempio rendendo cliccabili i circuiti, memorizzando i dati di cache nella
it/volunteer.wml       181) data directory di Vidalia, e personalizzando alcuni messaggi di dialogo del widget.
it/volunteer.wml       182) <br />
it/volunteer.wml       183) Gli studenti impegnati in questo progettp devono avere una buona esperienza
it/volunteer.wml       184) di sviluppo C++. Utile, ma non obbligatorio, avere avuto esperienza con Qt e
it/volunteer.wml       185) Cmake.
it/volunteer.wml       186) </li>
it/volunteer.wml       187) 
it/volunteer.wml       188) <li>
it/volunteer.wml       189) <b>Better Debian Packaging for Tor+Vidalia</b>
it/volunteer.wml       190) <br />
it/volunteer.wml       191) Priority: <i>High</i>
it/volunteer.wml       192) <br />
it/volunteer.wml       193) Effort Level: <i>Medium</i>
it/volunteer.wml       194) <br />
it/volunteer.wml       195) Skill Level: <i>Medium</i>
it/volunteer.wml       196) <br />
it/volunteer.wml       197) Likely Mentors: <i>Peter, Matt</i>
it/volunteer.wml       198) <br />
it/volunteer.wml       199) Vidalia currently doesn't play nicely on Debian and Ubuntu with the
it/volunteer.wml       200) default Tor packages. The current Tor packages automatically start Tor
it/volunteer.wml       201) as a daemon running as the debian-tor user and (sensibly) do not have a
it/volunteer.wml       202) <a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
it/volunteer.wml       203) in the default torrc. Consequently, Vidalia will try
it/volunteer.wml       204) to start its own Tor process since it could not connect to the existing
it/volunteer.wml       205) Tor, and Vidalia's Tor process will then exit with an error message
it/volunteer.wml       206) the user likely doesn't understand since Tor cannot bind its listening
it/volunteer.wml       207) ports &mdash; they're already in use by the original Tor daemon.
it/volunteer.wml       208) <br />
it/volunteer.wml       209) The current solution involves either telling the user to stop the
it/volunteer.wml       210) existing Tor daemon and let Vidalia start its own Tor process, or
it/volunteer.wml       211) explaining to the user how to set a control port and password in their
it/volunteer.wml       212) torrc. A better solution on Debian would be to use Tor's ControlSocket,
it/volunteer.wml       213) which allows Vidalia to talk to Tor via a Unix domain socket, and could
it/volunteer.wml       214) possibly be enabled by default in Tor's Debian packages. Vidalia can
it/volunteer.wml       215) then authenticate to Tor using filesystem-based (cookie) authentication
it/volunteer.wml       216) if the user running Vidalia is also in the debian-tor group.
it/volunteer.wml       217) <br />
it/volunteer.wml       218) This project will first involve adding support for Tor's ControlSocket
it/volunteer.wml       219) to Vidalia. The student will then develop and test Debian and Ubuntu
it/volunteer.wml       220) packages for Vidalia that conform to Debian's packaging standards and
it/volunteer.wml       221) make sure they work well with the existing Tor packages. We can also
it/volunteer.wml       222) set up an apt repository to host the new Vidalia packages.
it/volunteer.wml       223) <br />
it/volunteer.wml       224) The next challenge would be to find an intuitive usable way for Vidalia
it/volunteer.wml       225) to be able to change Tor's configuration (torrc) even though it is
it/volunteer.wml       226) located in <code>/etc/tor/torrc</code> and thus immutable. The best
it/volunteer.wml       227) idea we've come up with so far is to feed Tor a new configuration via
it/volunteer.wml       228) the ControlSocket when Vidalia starts, but that's bad because Tor starts
it/volunteer.wml       229) each boot with a different configuration than the user wants. The second
it/volunteer.wml       230) best idea
it/volunteer.wml       231) we've come up with is for Vidalia to write out a temporary torrc file
it/volunteer.wml       232) and ask the user to manually move it to <code>/etc/tor/torrc</code>,
it/volunteer.wml       233) but that's bad because users shouldn't have to mess with files directly.
it/volunteer.wml       234) <br />
it/volunteer.wml       235) A student undertaking this project should have prior knowledge of
it/volunteer.wml       236) Debian package management and some C++ development experience. Previous
it/volunteer.wml       237) experience with Qt is helpful, but not required.
it/volunteer.wml       238) </li>
it/volunteer.wml       239) 
it/volunteer.wml       240) <li>
it/volunteer.wml       241) <b>Tor Controller Status Event Interface</b>
it/volunteer.wml       242) <br />
it/volunteer.wml       243) Priority: <i>Medium</i>
it/volunteer.wml       244) <br />
it/volunteer.wml       245) Effort Level: <i>Medium</i>
it/volunteer.wml       246) <br />
it/volunteer.wml       247) Skill Level: <i>Medium</i>
it/volunteer.wml       248) <br />
it/volunteer.wml       249) Likely Mentors: <i>Matt, Roger</i>
it/volunteer.wml       250) <br />
it/volunteer.wml       251) There are a number of status changes inside Tor of which the user may need
it/volunteer.wml       252) to be informed. For example, if the user is trying to set up his Tor as a
it/volunteer.wml       253) relay and Tor decides that its ports are not reachable from outside
it/volunteer.wml       254) the user's network, we should alert the user. Currently, all the user
it/volunteer.wml       255) gets is a couple log messages in Vidalia's 'message log' window, which they
it/volunteer.wml       256) likely never see since they don't receive a notification that something
it/volunteer.wml       257) has gone wrong. Even if the user does actually look at the message log,
it/volunteer.wml       258) most of the messages make little sense to the novice user.
it/volunteer.wml       259) <br />
it/volunteer.wml       260) Tor has the ability to inform Vidalia of many such status changes, and
it/volunteer.wml       261) we recently implemented support for a couple of these events. Still,
it/volunteer.wml       262) there are many more status events the user should be informed of and we
it/volunteer.wml       263) need a better UI for actually displaying them to the user.
it/volunteer.wml       264) <br />
it/volunteer.wml       265) The goal of this project then is to design and implement a UI for
it/volunteer.wml       266) displaying Tor status events to the user. For example, we might put a
it/volunteer.wml       267) little badge on Vidalia's tray icon that alerts the user to new status
it/volunteer.wml       268) events they should look at. Double-clicking the icon could bring up a
it/volunteer.wml       269) dialog that summarizes recent status events in simple terms and maybe
it/volunteer.wml       270) suggests a remedy for any negative events if they can be corrected by
it/volunteer.wml       271) the user. Of course, this is just an example and the student is free to
it/volunteer.wml       272) suggest another approach.
it/volunteer.wml       273) <br />
it/volunteer.wml       274) A student undertaking this project should have good UI design and layout
it/volunteer.wml       275) and some C++ development experience. Previous experience with Qt and 
it/volunteer.wml       276) Qt's Designer will be very helpful, but are not required. Some
it/volunteer.wml       277) English writing ability will also be useful, since this project will
it/volunteer.wml       278) likely involve writing small amounts of help documentation that should
it/volunteer.wml       279) be understandable by non-technical users. Bonus points for some graphic
it/volunteer.wml       280) design/Photoshop fu, since we might want/need some shiny new icons too.
it/volunteer.wml       281) </li>
it/volunteer.wml       282) 
it/volunteer.wml       283) <li>
it/volunteer.wml       284) <b>Translation Wiki</b>
it/volunteer.wml       285) <br />
it/volunteer.wml       286) Priority: <i>High</i>
it/volunteer.wml       287) <br />
it/volunteer.wml       288) Effort Level: <i>Medium</i>
it/volunteer.wml       289) <br />
it/volunteer.wml       290) Skill Level: <i>Medium</i>
it/volunteer.wml       291) <br />
it/volunteer.wml       292) Likely Mentors: <i>Jacob</i>
it/volunteer.wml       293) <br />
it/volunteer.wml       294) We need a way to edit and translate sections of the website. Currently
it/volunteer.wml       295) the website is made up of a bunch of <a href="<svnsandbox>website/en/">wml
it/volunteer.wml       296) files</a>, and <a href="<page translation>">translators</a> fetch these
it/volunteer.wml       297) wml files, translate them in an editor, and either send us the translation
it/volunteer.wml       298) or use svn to commit them back. The current "cost" of publication of
it/volunteer.wml       299) website changes is quite high even for English language users. For a
it/volunteer.wml       300) single word change or any type of
it/volunteer.wml       301) minor change, the page may never be corrected or translated. It would
it/volunteer.wml       302) be nice to have a wiki that was specifically geared towards translation
it/volunteer.wml       303) and would somehow track the upstream (English) versions to indicate when
it/volunteer.wml       304) a fresh translation is needed, like our current
it/volunteer.wml       305) <a href="<page translation-status>">translation status page</a>. This
it/volunteer.wml       306) seems mostly like a job for a wiki
it/volunteer.wml       307) integrator or wiki software author. Certainly the person would need to
it/volunteer.wml       308) be interested in human languages and translation. They should at least
it/volunteer.wml       309) be minimally familiar with what Tor is; but they would not have to interact
it/volunteer.wml       310) with the software, only the documentation and the website.
it/volunteer.wml       311) </li>
it/volunteer.wml       312) 
it/volunteer.wml       313) <li>
it/volunteer.wml       314) <b>Improvements on our active browser configuration tester</b> - 
it/volunteer.wml       315) <a href="https://check.torproject.org/">https://check.torproject.org/</a>
it/volunteer.wml       316) <br />
it/volunteer.wml       317) Priority: <i>Medium</i>
it/volunteer.wml       318) <br />
it/volunteer.wml       319) Effort Level: <i>Low</i>
it/volunteer.wml       320) <br />
it/volunteer.wml       321) Skill Level: <i>Low to Medium</i>
it/volunteer.wml       322) <br />
it/volunteer.wml       323) Likely Mentors: <i>Jacob, Steven</i>
it/volunteer.wml       324) <br />
it/volunteer.wml       325) We currently have a functional web page to detect if Tor is working. It
it/volunteer.wml       326) has a few places where it falls short. It requires improvements with
it/volunteer.wml       327) regard to default languages and functionality. It currently only responds
it/volunteer.wml       328) in English. In addition, it is a hack of a perl script that should have
it/volunteer.wml       329) never seen the light of day. It should probably be rewritten in python
it/volunteer.wml       330) with multi-lingual support in mind. It currently uses the <a
it/volunteer.wml       331) href="http://exitlist.torproject.org/">Tor DNS exit list</a>
it/volunteer.wml       332) and should continue to do so in the future. It currently result in certain
it/volunteer.wml       333) false positives and these should be discovered, documented, and fixed
it/volunteer.wml       334) where possible. Anyone working on this project should be interested in
it/volunteer.wml       335) DNS, basic perl or preferably python programming skills, and will have
it/volunteer.wml       336) to interact minimally with Tor to test their code.
it/volunteer.wml       337) <br />
it/volunteer.wml       338) If you want to make the project more exciting
it/volunteer.wml       339) and involve more design and coding, take a look at <a
it/volunteer.wml       340) href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
it/volunteer.wml       341) 131-verify-tor-usage.txt</a>.
it/volunteer.wml       342) </li>
it/volunteer.wml       343) 
it/volunteer.wml       344) <li>
it/volunteer.wml       345) <b>Improvements on our DNS Exit List service</b> - 
it/volunteer.wml       346) <a href="http://exitlist.torproject.org/">http://exitlist.torproject.org/</a>
it/volunteer.wml       347) <br />
it/volunteer.wml       348) Priority: <i>Medium</i>
it/volunteer.wml       349) <br />
it/volunteer.wml       350) Effort Level: <i>Low</i>
it/volunteer.wml       351) <br />
it/volunteer.wml       352) Skill Level: <i>Low</i>
it/volunteer.wml       353) <br />
it/volunteer.wml       354) Likely Mentors: <i>Jacob, Tup</i>
it/volunteer.wml       355) <br />
it/volunteer.wml       356) The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>
it/volunteer.wml       357) is written by our fabulous anonymous
it/volunteer.wml       358) contributer Tup. It's a DNS server written in Haskell that supports part of our <a
it/volunteer.wml       359) href="https://www.torproject.org/svn/trunk/doc/contrib/torel-design.txt">exitlist
it/volunteer.wml       360) design document</a>. Currently, it is functional and it is used by
it/volunteer.wml       361) check.torproject.org and other users. The issues that are outstanding
it/volunteer.wml       362) are mostly aesthetic. This wonderful service could use a much better
it/volunteer.wml       363) website using the common Tor theme. It would be best served with better
it/volunteer.wml       364) documentation for common services that use an RBL. It could use more
it/volunteer.wml       365) publicity. A person working on this project should be interested in DNS,
it/volunteer.wml       366) basic RBL configuration for popular services, and writing documentation.
it/volunteer.wml       367) The person would require minimal Tor interaction &mdash; testing their
it/volunteer.wml       368) own documentation at the very least. Furthermore, it would be useful
it/volunteer.wml       369) if they were interested in Haskell and wanted to implement more of the
it/volunteer.wml       370) torel-design.txt suggestions.
it/volunteer.wml       371) </li>
it/volunteer.wml       372) 
it/volunteer.wml       373) <li>
it/volunteer.wml       374) <b>Testing integration of Tor with web browsers for our end users</b>
it/volunteer.wml       375) <br />
it/volunteer.wml       376) Priority: <i>Medium</i>
it/volunteer.wml       377) <br />
it/volunteer.wml       378) Effort Level: <i>Medium</i>
it/volunteer.wml       379) <br />
it/volunteer.wml       380) Skill Level: <i>Medium</i>
it/volunteer.wml       381) <br />
it/volunteer.wml       382) Likely Mentors: <i>Jacob, Mike, Greg</i>
it/volunteer.wml       383) <br />
it/volunteer.wml       384) The Tor project currently lacks a solid test suite to ensure that a
it/volunteer.wml       385) user has a properly and safely configured web browser. It should test for as
it/volunteer.wml       386) many known issues as possible. It should attempt to decloak the
it/volunteer.wml       387) user in any way possible. Two current webpages that track these
it/volunteer.wml       388) kinds of issues are run by Greg Fleischer and HD Moore. Greg keeps a nice <a
it/volunteer.wml       389) href="http://pseudo-flaw.net/tor/torbutton/">list of issues along
it/volunteer.wml       390) with their proof of concept code, bug issues, etc</a>. HD Moore runs
it/volunteer.wml       391) the <a href="http://metasploit.com/research/projects/decloak/">metasploit
it/volunteer.wml       392) decloak website</a>. A student interested in defending Tor could start
it/volunteer.wml       393) by collecting as many workable and known methods for decloaking a
it/volunteer.wml       394) Tor user. (<a href="https://torcheck.xenobite.eu/">This page</a> may
it/volunteer.wml       395) be helpful as a start.) The student should be familiar with the common
it/volunteer.wml       396) pitfalls but
it/volunteer.wml       397) possibly have new methods in mind for implementing decloaking issues. The
it/volunteer.wml       398) website should ensure that it tells a user what their problem is. It
it/volunteer.wml       399) should help them to fix the problem or direct them to the proper support
it/volunteer.wml       400) channels. The student should be closely familiar with using Tor and how
it/volunteer.wml       401) to prevent Tor information leakage.
it/volunteer.wml       402) </li>
it/volunteer.wml       403) 
it/volunteer.wml       404) <li>
it/volunteer.wml       405) <b>Improving Tor's ability to resist censorship</b>
it/volunteer.wml       406) <br />
it/volunteer.wml       407) Priority: <i>High</i>
it/volunteer.wml       408) <br />
it/volunteer.wml       409) Effort Level: <i>High</i>
it/volunteer.wml       410) <br />
it/volunteer.wml       411) Skill Level: <i>High</i>
it/volunteer.wml       412) <br />
it/volunteer.wml       413) Likely Mentors: <i>Nick</i>
it/volunteer.wml       414) <br />
it/volunteer.wml       415) The Tor 0.2.0.x series makes <a
it/volunteer.wml       416) href="<svnsandbox>doc/design-paper/blocking.html">significant
it/volunteer.wml       417) improvements</a> in resisting national and organizational censorship.
it/volunteer.wml       418) But Tor still needs better mechanisms for some parts of its
it/volunteer.wml       419) anti-censorship design.  For example, current Tors can only listen on a
it/volunteer.wml       420) single address/port combination at a time.  There's
it/volunteer.wml       421) <a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
it/volunteer.wml       422) proposal to address this limitation</a> and allow clients to connect
it/volunteer.wml       423) to any given Tor on multiple addresses and ports, but it needs more
it/volunteer.wml       424) work.  Another anti-censorship project (far more difficult) is to try
it/volunteer.wml       425) to make Tor more scanning-resistant.  Right now, an adversary can identify
it/volunteer.wml       426) <a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
it/volunteer.wml       427) just by trying to connect to them, following the Tor protocol, and 
it/volunteer.wml       428) seeing if they respond.  To solve this, bridges could
it/volunteer.wml       429) <a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
it/volunteer.wml       430) webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
it/volunteer.wml       431) and not act like bridges until the user provides a bridge-specific key.
it/volunteer.wml       432) <br />
it/volunteer.wml       433) This project involves a lot of research and design. One of the big
it/volunteer.wml       434) challenges will be identifying and crafting approaches that can still
it/volunteer.wml       435) resist an adversary even after the adversary knows the design, and
it/volunteer.wml       436) then trading off censorship resistance with usability and robustness.
it/volunteer.wml       437) </li>
it/volunteer.wml       438)  
it/volunteer.wml       439) <li>
it/volunteer.wml       440) <b>Libevent and Tor integration improvements</b>
it/volunteer.wml       441) <br />
it/volunteer.wml       442) Priority: <i>Medium</i>
it/volunteer.wml       443) <br />
it/volunteer.wml       444) Effort Level: <i>High</i>
it/volunteer.wml       445) <br />
it/volunteer.wml       446) Skill Level: <i>Medium to High</i>
it/volunteer.wml       447) <br />
it/volunteer.wml       448) Likely Mentors: <i>Nick</i>
it/volunteer.wml       449) <br />
it/volunteer.wml       450) Tor should make better use of the more recent features of Niels
it/volunteer.wml       451) Provos's <a href="http://monkey.org/~provos/libevent/">Libevent</a>
it/volunteer.wml       452) library.  Tor already uses Libevent for its low-level asynchronous IO
it/volunteer.wml       453) calls, and could also use Libevent's increasingly good implementations
it/volunteer.wml       454) of network buffers and of HTTP.  This wouldn't be simply a matter of
it/volunteer.wml       455) replacing Tor's internal calls with calls to Libevent: instead, we'll
it/volunteer.wml       456) need to refactor Tor to use Libevent calls that do not follow the
it/volunteer.wml       457) same models as Tor's existing backends. Also, we'll need to add
it/volunteer.wml       458) missing functionality to Libevent as needed &mdash; most difficult likely
it/volunteer.wml       459) will be adding OpenSSL support on top of Libevent's buffer abstraction.
it/volunteer.wml       460) Also tricky will be adding rate-limiting to Libevent.
it/volunteer.wml       461) </li>
it/volunteer.wml       462) 
it/volunteer.wml       463) <li>
it/volunteer.wml       464) <b>Tuneup Tor!</b>
it/volunteer.wml       465) <br />
it/volunteer.wml       466) Priority: <i>Medium</i>
it/volunteer.wml       467) <br />
it/volunteer.wml       468) Effort Level: <i>Medium</i>
it/volunteer.wml       469) <br />
it/volunteer.wml       470) Skill Level: <i>Medium to High</i>
it/volunteer.wml       471) <br />
it/volunteer.wml       472) Likely Mentors: <i>Nick, Roger, Mike</i>
it/volunteer.wml       473) <br />
it/volunteer.wml       474) Right now, Tor relays measure and report their own bandwidth, and Tor
it/volunteer.wml       475) clients choose which relays to use in part based on that bandwidth.
it/volunteer.wml       476) This approach is vulnerable to
it/volunteer.wml       477) <a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where
it/volunteer.wml       478) relays lie about their bandwidth</a>;
it/volunteer.wml       479) to address this, Tor currently caps the maximum bandwidth
it/volunteer.wml       480) it's willing to believe any relay provides.  This is a limited fix, and
it/volunteer.wml       481) a waste of bandwidth capacity to boot.  Instead,
it/volunteer.wml       482) Tor should possibly measure bandwidth in a more distributed way, perhaps
it/volunteer.wml       483) as described in the
it/volunteer.wml       484) <a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for
it/volunteer.wml       485) Tor"</a> paper
it/volunteer.wml       486) by Snader and Borisov. A student could use current testing code to
it/volunteer.wml       487) double-check this paper's findings and verify the extent to which they
it/volunteer.wml       488) dovetail with Tor as deployed in the wild, and determine good ways to
it/volunteer.wml       489) incorporate them into their suggestions Tor network without adding too
it/volunteer.wml       490) much communications overhead between relays and directory
it/volunteer.wml       491) authorities.
it/volunteer.wml       492) </li>
it/volunteer.wml       493) 
it/volunteer.wml       494) <!--
it/volunteer.wml       495) <li>
it/volunteer.wml       496) <b>Improving the Tor QA process: Continuous Integration for Windows builds</b>
it/volunteer.wml       497) <br />
it/volunteer.wml       498) Priority: <i>High</i>
it/volunteer.wml       499) <br />
it/volunteer.wml       500) Effort Level: <i>Medium</i>
it/volunteer.wml       501) <br />
it/volunteer.wml       502) Skill Level: <i>Medium</i>
it/volunteer.wml       503) <br />
it/volunteer.wml       504) Likely Mentors: <i>Jacob, Andrew</i>
it/volunteer.wml       505) <br />
it/volunteer.wml       506) It would be useful to have automated build processes for Windows and
it/volunteer.wml       507) probably other platforms. The purpose of having a continuous integration
it/volunteer.wml       508) build environment is to ensure that Windows isn't left behind for any of
it/volunteer.wml       509) the software projects used in the Tor project or its accompanying.<br />
it/volunteer.wml       510) Buildbot may be a good choice for this as it appears to support all of
it/volunteer.wml       511) the platforms Tor does. See the 
it/volunteer.wml       512) <a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for
it/volunteer.wml       513) buildbot</a>.<br />
it/volunteer.wml       514) There may be better options and the person undertaking this task should
it/volunteer.wml       515) evaluate other options. Any person working on this automatic build
it/volunteer.wml       516) process should have experience or be willing to learn how to build all
it/volunteer.wml       517) of the respective Tor related code bases from scratch. Furthermore, the
it/volunteer.wml       518) person should have some experience building software in Windows
it/volunteer.wml       519) environments as this is the target audience we want to ensure we do not
it/volunteer.wml       520) leave behind. It would require close work with the Tor source code but
it/volunteer.wml       521) probably only in the form of building, not authoring.<br />
it/volunteer.wml       522) Additionally, we need to automate our performance testing for all platforms.
it/volunteer.wml       523) We've got buildbot (except on Windows &mdash; as noted above) to automate 
it/volunteer.wml       524) our regular integration and compile testing already,
it/volunteer.wml       525) but we need to get our network simulation tests (as built in torflow)
it/volunteer.wml       526) updated for more recent versions of Tor, and designed to launch a test
it/volunteer.wml       527) network either on a single machine, or across several, so we can test
it/volunteer.wml       528) changes in performance on machines in different roles automatically.
it/volunteer.wml       529) </li>
it/volunteer.wml       530) -->
it/volunteer.wml       531) 
it/volunteer.wml       532) <li>
it/volunteer.wml       533) <b>Improve our unit testing process</b>
it/volunteer.wml       534) <br />
it/volunteer.wml       535) Priority: <i>Medium</i>
it/volunteer.wml       536) <br />
it/volunteer.wml       537) Effort Level: <i>Medium</i>
it/volunteer.wml       538) <br />
it/volunteer.wml       539) Skill Level: <i>Medium</i>
it/volunteer.wml       540) <br />
it/volunteer.wml       541) Likely Mentors: <i>Nick</i>
it/volunteer.wml       542) <br />
it/volunteer.wml       543) Tor needs to be far more tested. This is a multi-part effort. To start
it/volunteer.wml       544) with, our unit test coverage should rise substantially, especially in
it/volunteer.wml       545) the areas outside the utility functions. This will require significant
it/volunteer.wml       546) refactoring of some parts of Tor, in order to dissociate as much logic
it/volunteer.wml       547) as possible from globals.
it/volunteer.wml       548) <br />
it/volunteer.wml       549) Additionally, we need to automate our performance testing. We've got
it/volunteer.wml       550) buildbot to automate our regular integration and compile testing already
it/volunteer.wml       551) (though we need somebody to set it up on Windows),
it/volunteer.wml       552) but we need to get our network simulation tests (as built in TorFlow: see
it/volunteer.wml       553) the "Tor Node Scanner improvements" item)
it/volunteer.wml       554) updated for more recent versions of Tor, and designed to launch a test
it/volunteer.wml       555) network either on a single machine, or across several, so we can test
it/volunteer.wml       556) changes in performance on machines in different roles automatically.
it/volunteer.wml       557) </li>
it/volunteer.wml       558)  
it/volunteer.wml       559) <li>
it/volunteer.wml       560) <b>Help revive an independent Tor client implementation</b>
it/volunteer.wml       561) <br />
it/volunteer.wml       562) Priority: <i>Medium</i>
it/volunteer.wml       563) <br />
it/volunteer.wml       564) Effort Level: <i>High</i>
it/volunteer.wml       565) <br />
it/volunteer.wml       566) Skill Level: <i>Medium to High</i>
it/volunteer.wml       567) <br />
it/volunteer.wml       568) Likely Mentors: <i>Karsten, Nick</i>
it/volunteer.wml       569) <br />
it/volunteer.wml       570) Reanimate one of the approaches to implement a Tor client in Java,
it/volunteer.wml       571) e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee
it/volunteer.wml       572) project</a>, and make it run on <a
it/volunteer.wml       573) href="http://code.google.com/android/">Android</a>. The first step
it/volunteer.wml       574) would be to port the existing code and execute it in an Android
it/volunteer.wml       575) environment. Next, the code should be updated to support the newer Tor
it/volunteer.wml       576) protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
it/volunteer.wml       577) directory protocol</a>. Further, support for requesting or even
it/volunteer.wml       578) providing Tor hidden services would be neat, but not required.
it/volunteer.wml       579) <br />
it/volunteer.wml       580) The student should be able to understand and write new Java code, including
it/volunteer.wml       581) a Java cryptography API. Being able to read C code would be helpful,
it/volunteer.wml       582) too. The student should be willing to read the existing documentation,
it/volunteer.wml       583) implement code based on it, and refine the documentation
it/volunteer.wml       584) when things are underdocumented. This project is mostly about coding and
it/volunteer.wml       585) to a small degree about design.
it/volunteer.wml       586) </li>
it/volunteer.wml       587) 
it/volunteer.wml       588) <li>
it/volunteer.wml       589) <b>Automatic system tests and automatically starting private Tor networks</b>
it/volunteer.wml       590) <br />
it/volunteer.wml       591) Priority: <i>Medium</i>
it/volunteer.wml       592) <br />
it/volunteer.wml       593) Effort Level: <i>Medium</i>
it/volunteer.wml       594) <br />
it/volunteer.wml       595) Skill Level: <i>Medium</i>
it/volunteer.wml       596) <br />
it/volunteer.wml       597) Likely Mentors: <i>Karsten, Nick, Roger</i>
it/volunteer.wml       598) <br />
it/volunteer.wml       599) Write a tool that runs automatic system tests in addition
it/volunteer.wml       600) to the existing unit tests. The Java-based Tor simulator <a
it/volunteer.wml       601) href="https://tor-svn.freehaven.net/svn/puppetor/trunk/">PuppeTor</a>
it/volunteer.wml       602) might be a good start for starting up a private Tor network, using it
it/volunteer.wml       603) for a while, and verifying that at least parts of it are working. This
it/volunteer.wml       604) project requires to conceive a blueprint for performing system tests
it/volunteer.wml       605) of private Tor networks, before starting to code. Typical types of
it/volunteer.wml       606) tests range from performing single requests over the private network to
it/volunteer.wml       607) manipulating exchanged messages and see if nodes handle corrupt messages
it/volunteer.wml       608) appropriately.
it/volunteer.wml       609) <br />
it/volunteer.wml       610) The student should be able to obtain a good understanding
it/volunteer.wml       611) of how Tor works and what problems and bugs could arise to design good
it/volunteer.wml       612) test cases. Understanding the existing Tor code structure and documentation is
it/volunteer.wml       613) vital. If PuppeTor is used, the student should also be able to understand
it/volunteer.wml       614) and possibly extend an existing Java application. This project is partly
it/volunteer.wml       615) about design and partly about coding.
it/volunteer.wml       616) </li>
it/volunteer.wml       617) 
it/volunteer.wml       618) <li>
it/volunteer.wml       619) <b>Bring moniTor to life</b>
it/volunteer.wml       620) <br />
it/volunteer.wml       621) Priority: <i>Medium</i>
it/volunteer.wml       622) <br />
it/volunteer.wml       623) Effort Level: <i>Medium</i>
it/volunteer.wml       624) <br />
it/volunteer.wml       625) Skill Level: <i>Low to Medium</i>
it/volunteer.wml       626) <br />
it/volunteer.wml       627) Likely Mentors: <i>Karsten, Jacob</i>
it/volunteer.wml       628) <br />
it/volunteer.wml       629) Implement a <a href="http://www.ss64.com/bash/top.html">top-like</a>
it/volunteer.wml       630) management tool for Tor relays. The purpose of such a tool would be
it/volunteer.wml       631) to monitor a local Tor relay via its control port and include useful
it/volunteer.wml       632) system information of the underlying machine. When running this tool, it
it/volunteer.wml       633) would dynamically update its content like top does for Linux processes.
it/volunteer.wml       634) <a href="http://archives.seul.org/or/dev/Jan-2008/msg00005.html">This
it/volunteer.wml       635) or-dev post</a> might be a good first read.
it/volunteer.wml       636) <br />
it/volunteer.wml       637) The student should be familiar
it/volunteer.wml       638) with or willing to learn about administering a Tor relay and configuring
it/volunteer.wml       639) it via its control port. As an initial prototype is written in Python,
it/volunteer.wml       640) some knowledge about writing Python code would be helpful, too. This
it/volunteer.wml       641) project is one part about identifying requirements to such a
it/volunteer.wml       642) tool and designing its interface, and one part lots of coding.
it/volunteer.wml       643) </li>
it/volunteer.wml       644) 
it/volunteer.wml       645) <li>
it/volunteer.wml       646) <b>Tor Exit Scanner improvements</b>
it/volunteer.wml       647) <br />
it/volunteer.wml       648) Priority: <i>High</i>
it/volunteer.wml       649) <br />
it/volunteer.wml       650) Effort Level: <i>High</i>
it/volunteer.wml       651) <br />
it/volunteer.wml       652) Skill Level: <i>High</i>
it/volunteer.wml       653) <br />
it/volunteer.wml       654) Likely Mentors: <i>Mike</i>
it/volunteer.wml       655) <br />
it/volunteer.wml       656) The Tor exit node scanner 'SoaT', part of the <a
it/volunteer.wml       657) href="<svnsandbox>torflow/">Torflow project</a>, makes connections out
it/volunteer.wml       658) of each Tor exit node and compares the content it gets back with what it
it/volunteer.wml       659) "should" get back. The goal is to notice misconfigured, broken, and even
it/volunteer.wml       660) malicious exit relays. Alas, the code is
it/volunteer.wml       661) currently written in rather rickety perl and relies on MD5sums of
it/volunteer.wml       662) entire documents in order to determine if exit nodes are modifying
it/volunteer.wml       663) content. The problem with this is threefold: 1) Perl sucks at life.
it/volunteer.wml       664) 2) The scanner can't verify pages that are dynamic, and attackers can
it/volunteer.wml       665) focus malicious content injection on only those dynamic pages. 3)
it/volunteer.wml       666) Pages change after a while (or based on GeoIP) and begin generating
it/volunteer.wml       667) false positives.
it/volunteer.wml       668) <br />
it/volunteer.wml       669) Ideally, soat.pl would be reimplemented in a sane language with a
it/volunteer.wml       670) robust html parser library (since the rest of Torflow is in Python
it/volunteer.wml       671) that would be nice, but it is not required), and calculate signatures only for
it/volunteer.wml       672) tags and content likely to be targeted by a malicious attacker (script
it/volunteer.wml       673) tags, object links, images, css). It should also be robust in the face of
it/volunteer.wml       674) changes to content outside of Tor, and ultimately even GeoIP localized
it/volunteer.wml       675) content.
it/volunteer.wml       676) <br />
it/volunteer.wml       677) This scanner would likely be run by the Directory Authorities and
it/volunteer.wml       678) report its results to the control port via the AuthDirBadExit config
it/volunteer.wml       679) setting.
it/volunteer.wml       680) <br />
it/volunteer.wml       681) </li>
it/volunteer.wml       682) 
it/volunteer.wml       683) <li>
it/volunteer.wml       684) <b>Tor Node Scanner improvements</b>
it/volunteer.wml       685) <br />
it/volunteer.wml       686) Priority: <i>High</i>
it/volunteer.wml       687) <br />
it/volunteer.wml       688) Effort Level: <i>Medium to High</i>
it/volunteer.wml       689) <br />
it/volunteer.wml       690) Skill Level: <i>Medium to High</i>
it/volunteer.wml       691) <br />
it/volunteer.wml       692) Likely Mentors: <i>Mike</i>
it/volunteer.wml       693) <br />
it/volunteer.wml       694) Similar to the exit scanner (or perhaps even during exit scanning),
it/volunteer.wml       695) statistics can be gathered about the reliability of nodes. Nodes that
it/volunteer.wml       696) fail too high a percentage of their circuits should not be given
it/volunteer.wml       697) Guard status. Perhaps they should have their reported bandwidth
it/volunteer.wml       698) penalized by some ratio as well, or just get marked as Invalid. In
it/volunteer.wml       699) addition, nodes that exhibit a very low average stream capacity but
it/volunteer.wml       700) advertise a very high node bandwidth can also be marked as Invalid.
it/volunteer.wml       701) Much of this statistics gathering is already done, it just needs to be
it/volunteer.wml       702) transformed into something that can be reported to the Directory
it/volunteer.wml       703) Authorities to blacklist/penalize nodes in such a way that clients
it/volunteer.wml       704) will listen.
it/volunteer.wml       705) <br />
it/volunteer.wml       706) In addition, these same statistics can be gathered about the traffic
it/volunteer.wml       707) through a node. Events can be added to the <a
it/volunteer.wml       708) href="https://www.torproject.org/svn/torctl/doc/howto.txt">Tor Control
it/volunteer.wml       709) Protocol</a> to
it/volunteer.wml       710) report if a circuit extend attempt through the node succeeds or fails, and
it/volunteer.wml       711) passive statistics can be gathered on both bandwidth and reliability
it/volunteer.wml       712) of other nodes via a node-based monitor using these events. Such a
it/volunteer.wml       713) scanner would also report information on oddly-behaving nodes to
it/volunteer.wml       714) the Directory Authorities, but a communication channel for this
it/volunteer.wml       715) currently does not exist and would need to be developed as well.
it/volunteer.wml       716) </li>
it/volunteer.wml       717) 
it/volunteer.wml       718) <li>
it/volunteer.wml       719) <b>Help track the overall Tor Network status</b>
it/volunteer.wml       720) <br />
it/volunteer.wml       721) Priority: <i>High</i>
it/volunteer.wml       722) <br />
it/volunteer.wml       723) Effort Level: <i>Medium</i>
it/volunteer.wml       724) <br />
it/volunteer.wml       725) Skill Level: <i>Medium</i>
it/volunteer.wml       726) <br />
it/volunteer.wml       727) Likely Mentors: <i>Roger, Nick, Mike</i>
it/volunteer.wml       728) <br />
it/volunteer.wml       729) It would be great to set up an automated system for tracking network
it/volunteer.wml       730) health over time, graphing it, etc. Part of this project would involve
it/volunteer.wml       731) inventing better metrics for assessing network health and growth. Is the
it/volunteer.wml       732) average uptime of the network increasing? How many relays are qualifying
it/volunteer.wml       733) for Guard status this month compared to last month? What's the turnover
it/volunteer.wml       734) in terms of new relays showing up and relays shutting off? Periodically
it/volunteer.wml       735) people collect brief snapshots, but where it gets really interesting is
it/volunteer.wml       736) when we start tracking data points over time.
it/volunteer.wml       737) <br />
it/volunteer.wml       738) Data could be collected from the "Tor Node Scanner" item above, from
it/volunteer.wml       739) the server descriptors that each relay publishes, and from other
it/volunteer.wml       740) sources. Results over time could be integrated into one of the <a
it/volunteer.wml       741) href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
it/volunteer.wml       742) kept separate. Speaking of the Tor Status pages, take a look at Roger's
it/volunteer.wml       743) <a href="http://archives.seul.org/or/talk/Jan-2008/msg00300.html">Tor
it/volunteer.wml       744) Status wish list</a>.
it/volunteer.wml       745) </li>
it/volunteer.wml       746) 
it/volunteer.wml       747) <li>
it/volunteer.wml       748) <b>Tor path selection improvements</b>
it/volunteer.wml       749) <br />
it/volunteer.wml       750) Priority: <i>High</i>
it/volunteer.wml       751) <br />
it/volunteer.wml       752) Effort Level: <i>Low to Medium</i>
it/volunteer.wml       753) <br />
it/volunteer.wml       754) Skill Level: <i>High</i>
it/volunteer.wml       755) <br />
it/volunteer.wml       756) Likely Mentors: <i>Roger, Nick, Mike</i>
it/volunteer.wml       757) <br />
it/volunteer.wml       758) Some simple improvements can be made to Tor's path selection to vastly
it/volunteer.wml       759) improve Tor speed. For instance, some of the (unofficial) <a
it/volunteer.wml       760) href="http://wiki.noreply.org/noreply/TheOnionRouter/FireFoxTorPerf">Tor
it/volunteer.wml       761) Performance Recommendations</a> on the wiki are to increase the number of
it/volunteer.wml       762) guards and decrease the CircuitBuildTimeout. Ideally, the client would
it/volunteer.wml       763) <a href="http://archives.seul.org/or/talk/Feb-2008/msg00012.html">learn
it/volunteer.wml       764) these values by gathering statistics on circuit construction
it/volunteer.wml       765) time</a> (and/or using values gained from Torflow), and set the timeouts
it/volunteer.wml       766) low enough such that some high percentile (75%, 90%, 1-stddev?) of
it/volunteer.wml       767) circuits succeed, yet extremely slow nodes are avoided. This would
it/volunteer.wml       768) involve some statistics gathering+basic research, and some changes to 
it/volunteer.wml       769) Tor path selection code.
it/volunteer.wml       770) <br />
it/volunteer.wml       771) In addition, to improve path security, some elements from the <a
it/volunteer.wml       772) href="http://www.torproject.org/svn/trunk/doc/spec/proposals/115-two-hop-paths.txt">Two
it/volunteer.wml       773) Hop Paths proposal</a> could be done as part of this (since it will
it/volunteer.wml       774) likely touch the same code anyways), regardless of the adoption of
it/volunteer.wml       775) that proposal. In particular, clients probably should avoid guards that
it/volunteer.wml       776) seem to fail an excessive percentage of their circuits through them,
it/volunteer.wml       777) and non-firewalled clients should issue a warning if they are only able
it/volunteer.wml       778) to connect to a limited set of guard nodes. See also
it/volunteer.wml       779) <a href="http://archives.seul.org/or/dev/Feb-2008/msg00003.html">this
it/volunteer.wml       780) or-dev post</a>.
it/volunteer.wml       781) </li>
it/volunteer.wml       782) 
it/volunteer.wml       783) <li>
it/volunteer.wml       784) <b>Torbutton improvements</b>
it/volunteer.wml       785) <br />
it/volunteer.wml       786) Priority: <i>Medium</i>
it/volunteer.wml       787) <br />
it/volunteer.wml       788) Effort Level: <i>High</i>
it/volunteer.wml       789) <br />
it/volunteer.wml       790) Skill Level: <i>High</i>
it/volunteer.wml       791) <br />
it/volunteer.wml       792) Likely Mentors: <i>Mike</i>
it/volunteer.wml       793) <br/>
it/volunteer.wml       794) Torbutton has a number of improvements that can be made in the post-1.2
it/volunteer.wml       795) timeframe. Most of these are documented as feature requests in the <a
it/volunteer.wml       796) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">Torbutton
it/volunteer.wml       797) flyspray section</a>. Good examples include: stripping off node.exit on http
it/volunteer.wml       798) headers, more fine-grained control over formfill blocking, improved referrer
it/volunteer.wml       799) spoofing based on the domain of the site (a-la <a
it/volunteer.wml       800) href="http://addons.mozilla.org/firefox/addon/4513">refspoof extension</a>),
it/volunteer.wml       801) tighter integration with Vidalia for reporting Tor status, a New Identity
it/volunteer.wml       802) button with Tor integration and multiple identity management, and anything
it/volunteer.wml       803) else you might think of.
it/volunteer.wml       804) <br />
it/volunteer.wml       805) This work would be independent coding in Javascript and the fun world of <a
it/volunteer.wml       806) href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
it/volunteer.wml       807) with not too much involvement in the Tor internals.
it/volunteer.wml       808) </li>
it/volunteer.wml       809) 
it/volunteer.wml       810) <li>
it/volunteer.wml       811) <b>Porting Polipo to Windows</b>
it/volunteer.wml       812) <br />
it/volunteer.wml       813) Priority: <i>Medium</i>
it/volunteer.wml       814) <br />
it/volunteer.wml       815) Effort Level: <i>Medium</i>
it/volunteer.wml       816) <br />
it/volunteer.wml       817) Skill Level: <i>Medium to High</i>
it/volunteer.wml       818) <br />
it/volunteer.wml       819) Likely Mentors: <i>Andrew, Steven, Roger</i>
it/volunteer.wml       820) <br />
it/volunteer.wml       821) Help port <a
it/volunteer.wml       822) href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to
it/volunteer.wml       823) Windows. Example topics to tackle include:
it/volunteer.wml       824) 1) handle spaces in path names and understand the filesystem
it/volunteer.wml       825) namespace &mdash; that is, where application data, personal data,
it/volunteer.wml       826) and program data typically reside in various versions of Windows. 2) the
it/volunteer.wml       827) ability to handle ipv6 communications. 3) the ability to asynchronously
it/volunteer.wml       828) query name servers, find the system nameservers, and manage netbios
it/volunteer.wml       829) and dns queries. 4) use native regex capabilities of Windows, rather
it/volunteer.wml       830) than using 3rd party GNU regex libraries. 5) manage events and buffers
it/volunteer.wml       831) natively (i.e. in Unix-like OSes, Polipo defaults to 25% of ram, in
it/volunteer.wml       832) Windows it's whatever the config specifies). 6) some sort of GUI config
it/volunteer.wml       833) and reporting tool, bonus if it has a systray icon with right clickable
it/volunteer.wml       834) menu options. Double bonus if it's cross-platform compatible.
it/volunteer.wml       835) </li>
it/volunteer.wml       836) 
it/volunteer.wml       837) <li>
it/volunteer.wml       838) <b>Make our diagrams beautiful and automated</b>
it/volunteer.wml       839) <br />
it/volunteer.wml       840) Priority: <i>Medium</i>
it/volunteer.wml       841) <br />
it/volunteer.wml       842) Effort Level: <i>Low</i>
it/volunteer.wml       843) <br />
it/volunteer.wml       844) Skill Level: <i>Low</i>
it/volunteer.wml       845) <br />
it/volunteer.wml       846) Likely Mentors: <i>Andrew</i>
it/volunteer.wml       847) <br />
it/volunteer.wml       848) We need a way to generate the website diagrams (for example, the "How
it/volunteer.wml       849) Tor Works" pictures on the <a href="<page overview>">overview page</a>
it/volunteer.wml       850) from source, so we can translate them as UTF-8 text rather than edit
it/volunteer.wml       851) them by hand with Gimp. We might want to
it/volunteer.wml       852) integrate this as an wml file so translations are easy and images are
it/volunteer.wml       853) generated in multiple languages whenever we build the website. See the
it/volunteer.wml       854) "Translation Wiki" idea above.
it/volunteer.wml       855) </li>
it/volunteer.wml       856) 
it/volunteer.wml       857) <li>
it/volunteer.wml       858) <b>Improve the LiveCD offerings for the Tor community</b>
it/volunteer.wml       859) <br />
it/volunteer.wml       860) Priority: <i>Low</i>
it/volunteer.wml       861) <br />
it/volunteer.wml       862) Effort Level: <i>Low</i>
it/volunteer.wml       863) <br />
it/volunteer.wml       864) Skill Level: <i>Medium to High</i>
it/volunteer.wml       865) <br />
it/volunteer.wml       866) Likely Mentors: <i>Anonym, Jacob, Roger</i>
it/volunteer.wml       867) <br />
it/volunteer.wml       868) How can we make the <a
it/volunteer.wml       869) href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a>
it/volunteer.wml       870) easier to maintain, improve, and document?
it/volunteer.wml       871) </li>
it/volunteer.wml       872) 
it/volunteer.wml       873) <li>
it/volunteer.wml       874) <b>Contribuisci con delle nuove idee!</b>
it/volunteer.wml       875) <br />
it/volunteer.wml       876) Nessuna di queste proposte ti piace? Dai un'occhiata alla <a
it/volunteer.wml       877) href="<svnsandbox>doc/design-paper/roadmap-future.pdf">Tor development
it/volunteer.wml       878) roadmap</a> per avere altri spunti.
it/volunteer.wml       879) </li>
it/volunteer.wml       880) 
it/volunteer.wml       881) </ol>
it/volunteer.wml       882) 

it/volunteer.wml       883) <h2><a class="anchor" href="#Coding">Programmazione e design</a></h2>
it/volunteer.wml       884) <ol>

it/volunteer.wml       885) <li>I relay Tor non funzionano bene su Windows XP. Su

it/volunteer.wml       886) Windows, Tor usa la normale chiamata di sistema <tt>select()</tt>,

it/volunteer.wml       887) che usa spazio nel pool non-page. Ciò significa
it/volunteer.wml       888) che un server Tor di medie dimensioni esaurir&agrave; il non-page pool, <a

it/volunteer.wml       889) href="https://wiki.torproject.org/noreply/TheOnionRouter/WindowsBufferProblems">causando

it/volunteer.wml       890) confusione e crash del sistema</a>. Probabilmente dovremmo usare overlapped IO.

it/volunteer.wml       891) Una soluzione sarebbe far usare a <a
it/volunteer.wml       892) href="http://www.monkey.org/~provos/libevent/">libevent</a> l'
it/volunteer.wml       893) overlapped IO invece di select() su Windows, per poi adattare Tor

it/volunteer.wml       894) alla nuova interfaccia libevent. Christian King ha dato un
it/volunteer.wml       895) <a href="https://tor-svn.freehaven.net/svn/libevent-urz/trunk/">buon inizio

it/volunteer.wml       896) al lavoro</a> nell'estate 2007.</li>

it/volunteer.wml       897) <li>Dobbiamo iniziare a realizzare il nostro <a href="<page
it/volunteer.wml       898) documentation>#DesignDoc">blocking-resistance design</a>. Occorre
it/volunteer.wml       899) ideare il design, modificare varie parti di Tor, adattare
it/volunteer.wml       900) <a href="http://vidalia-project.net/">Vidalia</a> perch&eacute; supporti le
it/volunteer.wml       901) nuove funzionalit&agrave; e progettarne lo sviluppo.</li>
it/volunteer.wml       902) <li>Serve un framework flessibile di simulazione per studiare gli attacchi
it/volunteer.wml       903) end-to-end di conferma del traffico. Molti ricercatori hanno creato dei sumulatori
it/volunteer.wml       904) ad hoc a sostegno delle loro intuizioni sul funzionamento degli attacchi
it/volunteer.wml       905) o di certe difese e contromisure. Possiamo costruire un simulatore
it/volunteer.wml       906) ben documentato e aperto che possa fornire a ciascuno risposte
it/volunteer.wml       907) adeguare? Questo potrebbe contribuire a molte nuove ricerche.
it/volunteer.wml       908) Vedi la voce <a href="#Research">qui sotto</a> sui confirmation attack per
it/volunteer.wml       909) maggior dettagli sulla ricerca in questo campo &mdash; chiss&agrave; forse al
it/volunteer.wml       910) termine  potresti scrivere qualche paper sull'argomento.</li>

it/volunteer.wml       911) <li>Tor 0.1.1.x e successivi includono il supporto per acceleratori crittografici hardware

it/volunteer.wml       912) tramite OpenSSL. Nessuno tuttavia lo ha ancora testato. C'è qualcuno che vuole

it/volunteer.wml       913) prendere una scheda e farci sapere come va?</li>
it/volunteer.wml       914) <li>Effettuare una analisi di sicurezza di Tor con <a
it/volunteer.wml       915) href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determinare
it/volunteer.wml       916) se esistono delle buone librerie di fuzzing adatte al nostro scopo. Guadagnati la fama
it/volunteer.wml       917) e il credito quando potremo fare una nuova release grazie a te!</li>
it/volunteer.wml       918) <li>Tor usa TCP per il trasporto e TLS per la cifratura del
it/volunteer.wml       919) collegamento. Funziona ed &egrave; semplice, ma significa che se un pacchetto
it/volunteer.wml       920) viene scartato tutte le cellule di un collegamento subiscono un ritardo; inoltre
it/volunteer.wml       921) significa che possiamo ragionrvolmente supportare solo flussi TCP. Abbiamo una <a

it/volunteer.wml       922) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">lista

it/volunteer.wml       923) di motivi per evitare il trasporto UDP</a>, ma sarebbe bello accorciare

it/volunteer.wml       924) questa lista. Abbiamo proposto anche delle <a

it/volunteer.wml       925) href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specifiche
it/volunteer.wml       926) per Tor e

it/volunteer.wml       927) UDP</a> &mdash; facci sapere se presentano dei problemi.</li>

it/volunteer.wml       928) <li>Non ci manca molto per avere supporto IPv6 per indirizzi destinazione
it/volunteer.wml       929) (sugli exit node). Se per te IPv6 &egrave; molto importante, questo &egrave;
it/volunteer.wml       930) il punto da cui cominciare.</li>
it/volunteer.wml       931) </ol>

it/contribute.it.html  932) 

it/volunteer.wml       933) <a id="Research"></a>
it/volunteer.wml       934) <h2><a class="anchor" href="#Research">Ricerca</a></h2>
it/volunteer.wml       935) <ol>
it/volunteer.wml       936) <li>Attacco di tipo "website fingerprinting": fai un elenco di quanche
it/volunteer.wml       937) centinaio di siti famosi, scaricane le pagine, crea una serie di
it/volunteer.wml       938) "signature" per ciascun sito. Poi osserva il traffico di un client Tor. Mentre
it/volunteer.wml       939) riceve dati, potresti indovinare se e quale di questi siti
it/volunteer.wml       940) il client sta visitando. Per prima cosa, che possibilit&agrave; di successo
it/volunteer.wml       941) ha questo attacco sull'installato Tor attuale? Poi, cerca delle difese
it/volunteer.wml       942) possibili: ad esempio, potremmo cambiare le dimensioni delle cellule Tor da 512
it/volunteer.wml       943) byte a 1024 byte, potremmo usare tecniche di padding come <a
it/volunteer.wml       944) href="http://freehaven.net/anonbib/#timing-fc2004">il defensive dropping</a>,
it/volunteer.wml       945) o potremmo aggiungere ritardi nel traffico. Che impatto avrebbe,
it/volunteer.wml       946) che conseguenze avrebbe sull'usabilit&agrave; (con un metro di riferimento adeguato)
it/volunteer.wml       947) l'uso di difese efficaci in ciascuno di questi casi?</li>
it/volunteer.wml       948) <li>Attacco di tipo "end-to-end traffic confirmation":
it/volunteer.wml       949) osservando il traffico dal lato di Alice e di Bob, si possono <a
it/volunteer.wml       950) href="http://freehaven.net/anonbib/#danezis:pet2004">confrontare
it/volunteer.wml       951) le signature del traffico e dedurre che si sta osservando lo stesso
it/volunteer.wml       952) flusso</a>. Finora Tor si rassegna ad accettare questa situazione, assumendo
it/volunteer.wml       953) che in ogni caso questo attacco &egrave; triviale. Ma &egrave; davvero cos&igrave;? Quanto
it/volunteer.wml       954)  e quale traffico &egrave; necessario perch&eacute; un aversario
it/volunteer.wml       955) sia certo di aver vinto? Ci sono situazioni che rallentano l'attacco (es. trasmissioni modeste)?
it/volunteer.wml       956) Il traffic padding o il traffic shaping

it/volunteer.wml       957) funzionano meglio di altri sistemi?</li>

it/volunteer.wml       958) <li>Attacco di tipo "routing zones": gli studi attuali considerano
it/volunteer.wml       959) il percorso di rete tra Alice e il suo entry node (e tra
it/volunteer.wml       960) l'exit node e Bob) come un singolo collegamento in un grafico. In realt&agrave;
it/volunteer.wml       961) invece il percorso attraversa diversi autonomous system (AS), e <a
it/volunteer.wml       962) href="http://freehaven.net/anonbib/#feamster:wpes2004">non &egrave; infrequente che
it/volunteer.wml       963) lo stesso AS appaia sia nell'entry path che nell'exit path</a>.
it/volunteer.wml       964) Purtroppo, per calcolare se una certa configurazione tra Alice, entry,
it/volunteer.wml       965) exit e Bob sia pericolosa occorre scaricare una intera
it/volunteer.wml       966) routing zone Internet ed effettuare su di essa molte operazioni. Ci sono dei
it/volunteer.wml       967) rimedi pratici approssimativi, come ad esempio evitare gli indirizzi IP nella stessa rete /8?</li>

it/volunteer.wml       968) <li>Nella ricerca su Tor vi sono altre questioni riguardo la diversit&agrave; geografica:
it/volunteer.wml       969) considera il costo tra scegliere un circuito client efficienteicient e sceglierne uno
it/volunteer.wml       970) casuale. Leggi il <a
it/volunteer.wml       971) href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
it/volunteer.wml       972) paper</a> di Stephen Rollyson per come scartare alcuni circuiti particolarmente lenti senza ledere
it/volunteer.wml       973) "troppo" l'anonimato. Su questa linea di ricerca serve pi&ugrave; lavoro,
it/volunteer.wml       974) ma pare assai promettente.</li>

it/volunteer.wml       975) <li>Tor funziona male quando un relay dispone di banda asimmetrica

it/volunteer.wml       976) (come via cavo o DSL). Siccome Tor usa connessioni TCP separate per
it/volunteer.wml       977) ogni nodo, se i bye in arrivo giungono regolarmente e quelli in uscita
it/volunteer.wml       978) vengono tutti persi, il meccanismo di push-back del TCP non
it/volunteer.wml       979) ritrasmette questa informazione ai flussi in entrata.
it/volunteer.wml       980) Tor potrebbe rilevare se sta perdendo molti pacchetti in uscita ed eseguire
it/volunteer.wml       981) un rate-limit sui flussi in ingresso per autoregolarsi? Ho in mente
it/volunteer.wml       982) un sistema di accumulo e scarico in cui si sceglie un rate-limit prudente e
it/volunteer.wml       983) lo si incrementa lentamente finché non si perdono pacchetti, poi si decrementa etc.
it/volunteer.wml       984) Ci serve qualcuno esperto di reti per simulare il meccanismo e aiutarci a disegnare
it/volunteer.wml       985) una soluzione; oppure dovremmo capire quanto ne vengono degradate le
it/volunteer.wml       986) prestazioni, e decidere se riconsiderare il trasporto UDP.</li>
it/volunteer.wml       987) <li>Un argomento simile &egrave; il controllo delle congestioni. Il nostro sistema attuale

it/volunteer.wml       988) sarà sufficiente quando avremo un uso molto intenso?

it/volunteer.wml       989) Potremmo sperimentare finestre di ampiezza variabile, invece
it/volunteer.wml       990) di finestre di ampiezza fissa? Questo sembrava funzionare bene in un <a
it/volunteer.wml       991) href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">esperimento
it/volunteer.wml       992) di throughput ssh</a>. Dovremmo misurare e provare, e forse applicare il metodo
it/volunteer.wml       993) se i risultati fossero soddisfacenti.</li>
it/volunteer.wml       994) <li>Per permettere ai dissidenti in tutto il mondo di usare Tor senza essere
it/volunteer.wml       995) bloccati dai firewall del loro paese, serve un sistema per avere decine di migliaia
it/volunteer.wml       996) di relay, non qualche centinaio. Potremmo immaginare la GUI di un client Tor con

it/volunteer.wml       997) un pulsante "Tor for Freedom" che apre una porta e fa il relay di pochi

it/volunteer.wml       998) KB/s di traffico verso la rete Tor. (Pochi KB/s non dovrebbero essere un problema,
it/volunteer.wml       999) e ci sarebbero pochi abusi, dato che non sarebbero degli exit
it/volunteer.wml      1000) node.) Ma come si fa a distribuire automaticamente ai dissidenti
it/volunteer.wml      1001) la lista di questi client volontari ed ad impedire ai firewall nazionali di
it/volunteer.wml      1002) intercettarli ed enumerarli? Forse si dovrebbe lavorare a livello di

it/volunteer.wml      1003) fiducia personale. Vedi il nostro <a href="<page documentation>#DesignDoc">early

it/volunteer.wml      1004) blocking-resistance design document</a> e la nostra <a

it/volunteer.wml      1005) href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#BlockingResistance">FAQ

it/volunteer.wml      1006) </a> sull'argomento e poi leggi la <a
it/volunteer.wml      1007) href="http://freehaven.net/anonbib/topic.html#Communications_20Censorship">sezione
it/volunteer.wml      1008) di anonbib sulla resistenza alla censura</a>.</li>
it/volunteer.wml      1009) <li>I circuiti Tor si stabiliscono un nodo alla volta, per cui potremmo
it/volunteer.wml      1010) fare uscire alcuni flussi dal secondo nodo, altri dal terzo e cos&igrave; via.
it/volunteer.wml      1011) Sembra una buona idea, dato che riduce i flussi in uscita

it/volunteer.wml      1012) che ciascun relay può vedere. Se però vogliamo assicurare la sicurezza di ciascun flusso,

it/volunteer.wml      1013) il percorso più breve dovrebbe essere almeno di tre nodi, secondo i criteri correnti, e
it/volunteer.wml      1014) gli altri dovrebbero essere anche più lunghi. Dobbiamo valutare questo compromesso tra
it/volunteer.wml      1015) sicurezza e prestazioni.</li>

it/volunteer.wml      1016) <li>Non &egrave; difficile effettuare un DoS ai Tor relay o alle autorit&agrave di directory. I client

it/volunteer.wml      1017) puzzle sono la soluzione giusta? Quali altri approcci pratici esistono? Un premio
it/volunteer.wml      1018) se sono compatibili col protocollo Tor attuale.</li>
it/volunteer.wml      1019) </ol>

it/contribute.it.html 1020) 

it/volunteer.wml      1021) <p>

it/volunteer.wml      1022) <a href="<page contact>">Facci sapere</a> se hai fatto progressi in qualcuno di
it/volunteer.wml      1023) questi campi!

it/volunteer.wml      1024) </p>

it/contribute.it.html 1025) 

it/volunteer.wml      1026)   </div><!-- #main -->

it/volunteer.wml      1027) 
it/volunteer.wml      1028) #include <foot.wmi>