tor-webwml.git

it/volunteer.wml         1) ## translation metadata

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

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>Alcune cose che puoi fare subito:</h2>

it/volunteer.wml        11) <ol>

it/volunteer.wml        12) <li>Puoi <a href="<page docs/tor-doc-relay>">installare

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>Se condividi gli obiettivi di Tor, per favore <a href="<page donate>">fai una donazione
it/volunteer.wml        17) e sostieni lo sviluppo futuro di Tor</a>. Cerchiamo anche
it/volunteer.wml        18) pi&ugrave; sponsor &mdash; se conosci aziende, ONG, enti od
it/volunteer.wml        19) altre organizzazioni interessate ad anonimato / privacy / sicurezza delle
it/volunteer.wml        20) comunicazioni, fagli conoscere il nostro progetto.</li>
it/volunteer.wml        21) <li>Cerchiamo altri <a href="<page torusers>">buoni esempi sull'uso di Tor
it/volunteer.wml        22) e sui suoi utenti</a>. Se usi Tor in una situazione o per scopi non ancora
it/volunteer.wml        23) descritti su questa pagina e se sei disposto a condividere queste informazioni con noi, ci
it/volunteer.wml        24) piacerebbe sentire la tua storia.</li>

it/volunteer.wml        25) </ol>

it/contribute.it.html   26) 

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

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

it/volunteer.wml        29) <ol>

it/volunteer.wml        30) <li>Servono dei migliori e nuovi metodi per intercettare le richieste DNS in modo che non siano svelate

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

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

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

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

it/volunteer.wml        35) <ul>
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>A proposito di geolocalizzazione, qualcuno potrebbe disegnare un mappamondo

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

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

it/volunteer.wml        60) </ol>

it/contribute.it.html   61) 

it/volunteer.wml        62) <a id="Advocacy"></a>
it/volunteer.wml        63) <h2><a class="anchor" href="#Advocacy">Divulgazione</a></h2>
it/volunteer.wml        64) <ol>
it/volunteer.wml        65) <li>Creare un logotipo sotto licenza Creative Commons che tutti possano usare e modificare</li>
it/volunteer.wml        66) <li>Creare una presentazione utilizzabile nei vari incontri e convegni di utenti in giro per il mondo</li>
it/volunteer.wml        67) <li>Creare un video sugli usi positivi di Tor. Ce ne sono gi&agrave; alcuni iniziati su Seesmic.</li>
it/volunteer.wml        68) <li>Creare un poster, od una serie di posters, attorno ad un tema, come "Tor per la libert&agrave;!"</li>
it/volunteer.wml        69) </ol>
it/volunteer.wml        70) 

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

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

it/volunteer.wml        75) Tor controller,

it/volunteer.wml        76) <a href="<page vidalia/index>">Vidalia</a>.</li>

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

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

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

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

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

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

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

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

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

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

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

it/volunteer.wml        96) <a id="Summer"></a>
it/volunteer.wml        97) <a id="Projects"></a>
it/volunteer.wml        98) <h2><a class="anchor" href="#Projects">Progetti di siluppo software</a></h2>
it/volunteer.wml        99) 
it/volunteer.wml       100) <p>

it/volunteer.wml       101) You may find some of these projects to be good <a href="<page
it/volunteer.wml       102) gsoc>">Google Summer of Code 2009</a> ideas. We have labelled each idea
it/volunteer.wml       103) with how useful it would be to the overall Tor project (priority), how
it/volunteer.wml       104) much work we expect it would be (effort level), how much clue you should
it/volunteer.wml       105) start with (skill level), and which of our <a href="<page
it/volunteer.wml       106) people>#Core">core developers</a> would be good mentors.
it/volunteer.wml       107) If one or more of these ideas looks promising to you, please <a
it/volunteer.wml       108) href="<page contact>">contact us</a> to discuss your plans rather than
it/volunteer.wml       109) sending blind applications. You may also want to propose your own project
it/volunteer.wml       110) idea which often results in the best applications.

it/volunteer.wml       111) </p>
it/volunteer.wml       112) <p>
it/volunteer.wml       113) (NdT: Le  schede di alcuni progetti sono in inglese e verranno tradotte man mano.)
it/volunteer.wml       114) </p>
it/volunteer.wml       115) <ol>

it/volunteer.wml       116) 
it/volunteer.wml       117) <li>
it/volunteer.wml       118) <b>Tor Browser Bundle for Linux/Mac OS X</b>
it/volunteer.wml       119) <br />
it/volunteer.wml       120) Priority: <i>High</i>
it/volunteer.wml       121) <br />
it/volunteer.wml       122) Effort Level: <i>High</i>
it/volunteer.wml       123) <br />
it/volunteer.wml       124) Skill Level: <i>Medium</i>
it/volunteer.wml       125) <br />
it/volunteer.wml       126) Likely Mentors: <i>Steven, Andrew</i>
it/volunteer.wml       127) <br />
it/volunteer.wml       128) The Tor Browser bundle incorporates Tor, Firefox, and the Vidalia user
it/volunteer.wml       129) interface (and optionally Pidgin IM). Components are pre-configured to
it/volunteer.wml       130) operate in a secure way, and it has very few dependencies on the
it/volunteer.wml       131) installed operating system. It has therefore become one of the most
it/volunteer.wml       132) easy to use, and popular, ways to use Tor on Windows.
it/volunteer.wml       133) <br />
it/volunteer.wml       134) However, there is currently no comparable package for Linux and Mac OS
it/volunteer.wml       135) X, so this project would be to implement Tor Browser Bundle for these
it/volunteer.wml       136) platforms. This will involve modifications to Vidalia (C++), possibly
it/volunteer.wml       137) Firefox (C) then creating and testing the launcher on a range of
it/volunteer.wml       138) operating system versions and configurations to verify portability.
it/volunteer.wml       139) <br />
it/volunteer.wml       140) Students should be familiar with application development on one or
it/volunteer.wml       141) preferably both of Linux and Mac OS X, and be comfortable with C/C++
it/volunteer.wml       142) and shell scripting.
it/volunteer.wml       143) <br />
it/volunteer.wml       144) Part of this project could be usability testing of Tor Browser Bundle,
it/volunteer.wml       145) ideally amongst our target demographic.
it/volunteer.wml       146) That would help a lot in knowing what needs to be done in terms of bug
it/volunteer.wml       147) fixes or new features. We get this informally at the moment, but a more
it/volunteer.wml       148) structured process would be better.
it/volunteer.wml       149) </li>
it/volunteer.wml       150) 
it/volunteer.wml       151) <li>
it/volunteer.wml       152) <b>Translation wiki for our website</b>
it/volunteer.wml       153) <br />
it/volunteer.wml       154) Priority: <i>High</i>
it/volunteer.wml       155) <br />
it/volunteer.wml       156) Effort Level: <i>Medium</i>
it/volunteer.wml       157) <br />
it/volunteer.wml       158) Skill Level: <i>Medium</i>
it/volunteer.wml       159) <br />
it/volunteer.wml       160) Likely Mentors: <i>Jacob</i>
it/volunteer.wml       161) <br />
it/volunteer.wml       162) The Tor Project has been working over the past year to set up web-based
it/volunteer.wml       163) tools to help volunteers translate our applications into other languages.
it/volunteer.wml       164) We finally hit upon Pootle, and we have a fine web-based translation engine
it/volunteer.wml       165) in place for Vidalia, Torbutton, and Torcheck. However, Pootle only
it/volunteer.wml       166) translates strings that are in the "po" format, and our website uses wml
it/volunteer.wml       167) files. This project is about finding a way to convert our wml files into po
it/volunteer.wml       168) strings and back, so they can be handled by Pootle.
it/volunteer.wml       169) </li>
it/volunteer.wml       170) 
it/volunteer.wml       171) 
it/volunteer.wml       172) <li>
it/volunteer.wml       173) <b>Help track the overall Tor Network status</b>
it/volunteer.wml       174) <br />
it/volunteer.wml       175) Priority: <i>Medium to High</i>
it/volunteer.wml       176) <br />
it/volunteer.wml       177) Effort Level: <i>Medium</i>
it/volunteer.wml       178) <br />
it/volunteer.wml       179) Skill Level: <i>Medium</i>
it/volunteer.wml       180) <br />
it/volunteer.wml       181) Likely Mentors: <i>Karsten, Roger</i>
it/volunteer.wml       182) <br />
it/volunteer.wml       183) It would be great to set up an automated system for tracking network
it/volunteer.wml       184) health over time, graphing it, etc. Part of this project would involve
it/volunteer.wml       185) inventing better metrics for assessing network health and growth. Is the
it/volunteer.wml       186) average uptime of the network increasing? How many relays are qualifying
it/volunteer.wml       187) for Guard status this month compared to last month? What's the turnover
it/volunteer.wml       188) in terms of new relays showing up and relays shutting off? Periodically
it/volunteer.wml       189) people collect brief snapshots, but where it gets really interesting is
it/volunteer.wml       190) when we start tracking data points over time.
it/volunteer.wml       191) <br />
it/volunteer.wml       192) Data could be collected from the Tor Network Scanners in <a
it/volunteer.wml       193) href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from
it/volunteer.wml       194) the server descriptors that each relay publishes, and from other
it/volunteer.wml       195) sources. Results over time could be integrated into one of the <a
it/volunteer.wml       196) href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
it/volunteer.wml       197) kept separate. Speaking of the Tor Status pages, take a look at Roger's
it/volunteer.wml       198) <a href="http://archives.seul.org/or/talk/Jan-2008/msg00300.html">Tor
it/volunteer.wml       199) Status wish list</a>.
it/volunteer.wml       200) </li>
it/volunteer.wml       201) 
it/volunteer.wml       202) <li>
it/volunteer.wml       203) <b>Improving Tor's ability to resist censorship</b>
it/volunteer.wml       204) <br />
it/volunteer.wml       205) Priority: <i>Medium to High</i>
it/volunteer.wml       206) <br />
it/volunteer.wml       207) Effort Level: <i>Medium</i>
it/volunteer.wml       208) <br />
it/volunteer.wml       209) Skill Level: <i>High</i>
it/volunteer.wml       210) <br />
it/volunteer.wml       211) Likely Mentors: <i>Nick, Roger, Steven</i>
it/volunteer.wml       212) <br />
it/volunteer.wml       213) The Tor 0.2.0.x series makes <a

it/volunteer.wml       214) href="<svnprojects>design-paper/blocking.html">significant

it/volunteer.wml       215) improvements</a> in resisting national and organizational censorship.
it/volunteer.wml       216) But Tor still needs better mechanisms for some parts of its
it/volunteer.wml       217) anti-censorship design.  For example, current Tors can only listen on a
it/volunteer.wml       218) single address/port combination at a time.  There's

it/volunteer.wml       219) <a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a

it/volunteer.wml       220) proposal to address this limitation</a> and allow clients to connect
it/volunteer.wml       221) to any given Tor on multiple addresses and ports, but it needs more
it/volunteer.wml       222) work.  Another anti-censorship project (far more difficult) is to try
it/volunteer.wml       223) to make Tor more scanning-resistant.  Right now, an adversary can identify

it/volunteer.wml       224) <a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>

it/volunteer.wml       225) just by trying to connect to them, following the Tor protocol, and
it/volunteer.wml       226) seeing if they respond.  To solve this, bridges could

it/volunteer.wml       227) <a href="<svnprojects>design-paper/blocking.html#tth_sEc9.3">act like

it/volunteer.wml       228) webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
it/volunteer.wml       229) and not act like bridges until the user provides a bridge-specific key.
it/volunteer.wml       230) <br />
it/volunteer.wml       231) This project involves a lot of research and design. One of the big
it/volunteer.wml       232) challenges will be identifying and crafting approaches that can still
it/volunteer.wml       233) resist an adversary even after the adversary knows the design, and
it/volunteer.wml       234) then trading off censorship resistance with usability and robustness.
it/volunteer.wml       235) </li>
it/volunteer.wml       236) 
it/volunteer.wml       237) <li>
it/volunteer.wml       238) <b>Tuneup Tor!</b>
it/volunteer.wml       239) <br />
it/volunteer.wml       240) Priority: <i>Medium to High</i>
it/volunteer.wml       241) <br />
it/volunteer.wml       242) Effort Level: <i>Medium to High</i>
it/volunteer.wml       243) <br />
it/volunteer.wml       244) Skill Level: <i>High</i>
it/volunteer.wml       245) <br />
it/volunteer.wml       246) Likely Mentors: <i>Nick, Roger, Mike, Karsten</i>
it/volunteer.wml       247) <br />
it/volunteer.wml       248) Right now, Tor relays measure and report their own bandwidth, and Tor
it/volunteer.wml       249) clients choose which relays to use in part based on that bandwidth.
it/volunteer.wml       250) This approach is vulnerable to
it/volunteer.wml       251) <a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where
it/volunteer.wml       252) relays lie about their bandwidth</a>;
it/volunteer.wml       253) to address this, Tor currently caps the maximum bandwidth
it/volunteer.wml       254) it's willing to believe any relay provides.  This is a limited fix, and
it/volunteer.wml       255) a waste of bandwidth capacity to boot.  Instead,
it/volunteer.wml       256) Tor should possibly measure bandwidth in a more distributed way, perhaps
it/volunteer.wml       257) as described in the
it/volunteer.wml       258) <a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for
it/volunteer.wml       259) Tor"</a> paper
it/volunteer.wml       260) by Snader and Borisov. One could use current testing code to
it/volunteer.wml       261) double-check this paper's findings and verify the extent to which they
it/volunteer.wml       262) dovetail with Tor as deployed in the wild, and determine good ways to
it/volunteer.wml       263) incorporate them into their suggestions Tor network without adding too
it/volunteer.wml       264) much communications overhead between relays and directory
it/volunteer.wml       265) authorities.
it/volunteer.wml       266) </li>
it/volunteer.wml       267)  
it/volunteer.wml       268) <li>
it/volunteer.wml       269) <b>Improving Polipo on Windows</b>
it/volunteer.wml       270) <br />
it/volunteer.wml       271) Priority: <i>Medium to High</i>
it/volunteer.wml       272) <br />
it/volunteer.wml       273) Effort Level: <i>Medium</i>
it/volunteer.wml       274) <br />
it/volunteer.wml       275) Skill Level: <i>Medium</i>
it/volunteer.wml       276) <br />
it/volunteer.wml       277) Likely Mentors: <i>Martin</i>
it/volunteer.wml       278) <br />
it/volunteer.wml       279) Help port <a
it/volunteer.wml       280) href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to
it/volunteer.wml       281) Windows. Example topics to tackle include:
it/volunteer.wml       282) 1) the ability to asynchronously
it/volunteer.wml       283) query name servers, find the system nameservers, and manage netbios
it/volunteer.wml       284) and dns queries.
it/volunteer.wml       285) 2) manage events and buffers
it/volunteer.wml       286) natively (i.e. in Unix-like OSes, Polipo defaults to 25% of ram, in
it/volunteer.wml       287) Windows it's whatever the config specifies). 3) some sort of GUI config
it/volunteer.wml       288) and reporting tool, bonus if it has a systray icon with right clickable
it/volunteer.wml       289) menu options. Double bonus if it's cross-platform compatible.
it/volunteer.wml       290) 4) allow the software to use the Windows Registry and handle proper
it/volunteer.wml       291) Windows directory locations, such as "C:\Program Files\Polipo"
it/volunteer.wml       292) </li>
it/volunteer.wml       293) 
it/volunteer.wml       294) <li>
it/volunteer.wml       295) <b>Implement a torrent-based scheme for downloading Thandy packages</b>
it/volunteer.wml       296) <br />
it/volunteer.wml       297) Priority: <i>Medium to High</i>
it/volunteer.wml       298) <br />
it/volunteer.wml       299) Effort Level: <i>High</i>
it/volunteer.wml       300) <br />
it/volunteer.wml       301) Skill Level: <i>Medium to High</i>
it/volunteer.wml       302) <br />
it/volunteer.wml       303) Likely Mentors: <i>Martin, Nick</i>
it/volunteer.wml       304) <br />
it/volunteer.wml       305) <a

it/volunteer.wml       306) href="https://git.torproject.org/checkout/thandy/master/specs/thandy-spec.txt">Thandy</a>

it/volunteer.wml       307) is a relatively new software to allow assisted updates of Tor and related
it/volunteer.wml       308) software. Currently, there are very few users, but we expect Thandy to be
it/volunteer.wml       309) used by almost every Tor user in the future. To avoid crashing servers on
it/volunteer.wml       310) the day of a Tor update, we need new ways to distribute new packages
it/volunteer.wml       311) efficiently, and using libtorrent seems to be a possible solution. If you
it/volunteer.wml       312) think of other good ideas, great - please do let us know!<br />
it/volunteer.wml       313) We also need to investigate how to include our mirrors better. If possible,
it/volunteer.wml       314) there should be an easy way for them to help distributing the packages.
it/volunteer.wml       315) </li>
it/volunteer.wml       316) 
it/volunteer.wml       317) <li>
it/volunteer.wml       318) <b>Tor Controller Status Event Interface</b>
it/volunteer.wml       319) <br />
it/volunteer.wml       320) Priority: <i>Medium</i>
it/volunteer.wml       321) <br />
it/volunteer.wml       322) Effort Level: <i>Medium</i>
it/volunteer.wml       323) <br />
it/volunteer.wml       324) Skill Level: <i>Low to Medium</i>
it/volunteer.wml       325) <br />
it/volunteer.wml       326) Likely Mentors: <i>Matt</i>
it/volunteer.wml       327) <br />
it/volunteer.wml       328) There are a number of status changes inside Tor of which the user may need
it/volunteer.wml       329) to be informed. For example, if the user is trying to set up his Tor as a
it/volunteer.wml       330) relay and Tor decides that its ports are not reachable from outside
it/volunteer.wml       331) the user's network, we should alert the user. Currently, all the user
it/volunteer.wml       332) gets is a couple log messages in Vidalia's 'message log' window, which they
it/volunteer.wml       333) likely never see since they don't receive a notification that something
it/volunteer.wml       334) has gone wrong. Even if the user does actually look at the message log,
it/volunteer.wml       335) most of the messages make little sense to the novice user.
it/volunteer.wml       336) <br />
it/volunteer.wml       337) Tor has the ability to inform Vidalia of many such status changes, and
it/volunteer.wml       338) we recently implemented support for a couple of these events. Still,
it/volunteer.wml       339) there are many more status events the user should be informed of and we
it/volunteer.wml       340) need a better UI for actually displaying them to the user.
it/volunteer.wml       341) <br />
it/volunteer.wml       342) The goal of this project then is to design and implement a UI for
it/volunteer.wml       343) displaying Tor status events to the user. For example, we might put a
it/volunteer.wml       344) little badge on Vidalia's tray icon that alerts the user to new status
it/volunteer.wml       345) events they should look at. Double-clicking the icon could bring up a
it/volunteer.wml       346) dialog that summarizes recent status events in simple terms and maybe
it/volunteer.wml       347) suggests a remedy for any negative events if they can be corrected by
it/volunteer.wml       348) the user. Of course, this is just an example and one is free to
it/volunteer.wml       349) suggest another approach.
it/volunteer.wml       350) <br />
it/volunteer.wml       351) A person undertaking this project should have good UI design and layout
it/volunteer.wml       352) and some C++ development experience. Previous experience with Qt and
it/volunteer.wml       353) Qt's Designer will be very helpful, but are not required. Some
it/volunteer.wml       354) English writing ability will also be useful, since this project will
it/volunteer.wml       355) likely involve writing small amounts of help documentation that should
it/volunteer.wml       356) be understandable by non-technical users. Bonus points for some graphic
it/volunteer.wml       357) design/Photoshop fu, since we might want/need some shiny new icons too.
it/volunteer.wml       358) </li>
it/volunteer.wml       359)  
it/volunteer.wml       360) <li>
it/volunteer.wml       361) <b>Improve our unit testing process</b>
it/volunteer.wml       362) <br />
it/volunteer.wml       363) Priority: <i>Medium</i>
it/volunteer.wml       364) <br />
it/volunteer.wml       365) Effort Level: <i>Medium</i>
it/volunteer.wml       366) <br />
it/volunteer.wml       367) Skill Level: <i>Medium</i>
it/volunteer.wml       368) <br />
it/volunteer.wml       369) Likely Mentors: <i>Nick, Roger</i>
it/volunteer.wml       370) <br />
it/volunteer.wml       371) Tor needs to be far more tested. This is a multi-part effort. To start
it/volunteer.wml       372) with, our unit test coverage should rise substantially, especially in
it/volunteer.wml       373) the areas outside the utility functions. This will require significant
it/volunteer.wml       374) refactoring of some parts of Tor, in order to dissociate as much logic
it/volunteer.wml       375) as possible from globals.
it/volunteer.wml       376) <br />
it/volunteer.wml       377) Additionally, we need to automate our performance testing. We've got
it/volunteer.wml       378) buildbot to automate our regular integration and compile testing already
it/volunteer.wml       379) (though we need somebody to set it up on Windows),
it/volunteer.wml       380) but we need to get our network simulation tests (as built in <a
it/volunteer.wml       381) href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
it/volunteer.wml       382) updated for more recent versions of Tor, and designed to launch a test
it/volunteer.wml       383) network either on a single machine, or across several, so we can test
it/volunteer.wml       384) changes in performance on machines in different roles automatically.
it/volunteer.wml       385) </li>
it/volunteer.wml       386) 
it/volunteer.wml       387) <li>
it/volunteer.wml       388) <b>Help revive an independent Tor client implementation</b>
it/volunteer.wml       389) <br />
it/volunteer.wml       390) Priority: <i>Medium</i>
it/volunteer.wml       391) <br />
it/volunteer.wml       392) Effort Level: <i>High</i>
it/volunteer.wml       393) <br />
it/volunteer.wml       394) Skill Level: <i>Medium to High</i>
it/volunteer.wml       395) <br />
it/volunteer.wml       396) Likely Mentors: <i>Karsten, Nick</i>
it/volunteer.wml       397) <br />
it/volunteer.wml       398) Reanimate one of the approaches to implement a Tor client in Java,
it/volunteer.wml       399) e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee
it/volunteer.wml       400) project</a>, and make it run on <a
it/volunteer.wml       401) href="http://code.google.com/android/">Android</a>. The first step
it/volunteer.wml       402) would be to port the existing code and execute it in an Android
it/volunteer.wml       403) environment. Next, the code should be updated to support the newer Tor

it/volunteer.wml       404) protocol versions like the <a href="<gitblob>doc/spec/dir-spec.txt">v3

it/volunteer.wml       405) directory protocol</a>. Further, support for requesting or even
it/volunteer.wml       406) providing Tor hidden services would be neat, but not required.
it/volunteer.wml       407) <br />
it/volunteer.wml       408) A prospective developer should be able to understand and write new Java
it/volunteer.wml       409) code, including
it/volunteer.wml       410) a Java cryptography API. Being able to read C code would be helpful,
it/volunteer.wml       411) too. One should be willing to read the existing documentation,
it/volunteer.wml       412) implement code based on it, and refine the documentation
it/volunteer.wml       413) when things are underdocumented. This project is mostly about coding and
it/volunteer.wml       414) to a small degree about design.
it/volunteer.wml       415) </li>
it/volunteer.wml       416) 
it/volunteer.wml       417) <li>
it/volunteer.wml       418) <b>New Torbutton Features</b>
it/volunteer.wml       419) <br />
it/volunteer.wml       420) Priority: <i>Medium</i>
it/volunteer.wml       421) <br />
it/volunteer.wml       422) Effort Level: <i>High</i>
it/volunteer.wml       423) <br />
it/volunteer.wml       424) Skill Level: <i>High</i>
it/volunteer.wml       425) <br />
it/volunteer.wml       426) Likely Mentors: <i>Mike</i>
it/volunteer.wml       427) <br/>
it/volunteer.wml       428) There are several <a
it/volunteer.wml       429) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5&amp;type=2">good
it/volunteer.wml       430) feature requests</a> on the Torbutton Flyspray section. In particular, <a
it/volunteer.wml       431) href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=523">Integrating
it/volunteer.wml       432) 'New Identity' with Vidalia</a>,
it/volunteer.wml       433) <a href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=940">ways of
it/volunteer.wml       434) managing multiple cookie jars/identities</a>, <a
it/volunteer.wml       435) href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=637">preserving
it/volunteer.wml       436) specific cookies</a> when cookies are cleared,
it/volunteer.wml       437) <a
it/volunteer.wml       438) href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=524">better
it/volunteer.wml       439) referrer spoofing</a>, <a
it/volunteer.wml       440) href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=564">correct
it/volunteer.wml       441) Tor status reporting</a>, and <a
it/volunteer.wml       442) href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=462">"tor://"
it/volunteer.wml       443) and "tors://" urls</a> are all interesting
it/volunteer.wml       444) features that could be added.
it/volunteer.wml       445) <br />
it/volunteer.wml       446) This work would be independent coding in Javascript and the fun world of <a
it/volunteer.wml       447) href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
it/volunteer.wml       448) with not too much involvement in the Tor internals.
it/volunteer.wml       449) </li>
it/volunteer.wml       450) 
it/volunteer.wml       451) <li>
it/volunteer.wml       452) <b>New Thandy Features</b>
it/volunteer.wml       453) <br />
it/volunteer.wml       454) Priority: <i>Medium</i>
it/volunteer.wml       455) <br />
it/volunteer.wml       456) Effort Level: <i>Medium</i>
it/volunteer.wml       457) <br />
it/volunteer.wml       458) Skill Level: <i>Medium to High</i>
it/volunteer.wml       459) <br />
it/volunteer.wml       460) Likely Mentors: <i>Martin</i>
it/volunteer.wml       461) <br />
it/volunteer.wml       462) Additional capabilities are needed for assisted updates of all the Tor
it/volunteer.wml       463) related software for Windows and other operating systems. Some of the
it/volunteer.wml       464) features to consider include:
it/volunteer.wml       465) 1) Integration of the <a
it/volunteer.wml       466) href="http://chandlerproject.org/Projects/MeTooCrypto">MeTooCrypto
it/volunteer.wml       467) Python library</a>
it/volunteer.wml       468) for authenticated HTTPS downloads. 2) Adding a level of indirection
it/volunteer.wml       469) between the timestamp signatures and the package files included in an
it/volunteer.wml       470) update. See the "Thandy attacks / suggestions" thread on or-dev.
it/volunteer.wml       471) 3) Support locale specific installation and configuration of assisted
it/volunteer.wml       472) updates based on preference, host, or user account language settings.
it/volunteer.wml       473) Familiarity with Windows codepages, unicode, and other character sets
it/volunteer.wml       474) is helpful in addition to general win32 and posix API experience and
it/volunteer.wml       475) Python proficiency.
it/volunteer.wml       476) </li>
it/volunteer.wml       477) 
it/volunteer.wml       478) <li>
it/volunteer.wml       479) <b>Simulator for slow Internet connections</b>
it/volunteer.wml       480) <br />
it/volunteer.wml       481) Priority: <i>Medium</i>
it/volunteer.wml       482) <br />
it/volunteer.wml       483) Effort Level: <i>Medium</i>
it/volunteer.wml       484) <br />
it/volunteer.wml       485) Skill Level: <i>Medium</i>
it/volunteer.wml       486) <br />
it/volunteer.wml       487) Likely Mentors: <i>Steven</i>
it/volunteer.wml       488) <br />
it/volunteer.wml       489) Many users of Tor have poor-quality Internet connections, giving low
it/volunteer.wml       490) bandwidth, high latency, and high packet loss/re-ordering. User
it/volunteer.wml       491) experience is that Tor reacts badly to these conditions, but it is
it/volunteer.wml       492) difficult to improve the situation without being able to repeat the
it/volunteer.wml       493) problems in the lab.
it/volunteer.wml       494) <br />
it/volunteer.wml       495) This project would be to build a simulation environment which
it/volunteer.wml       496) replicates the poor connectivity so that the effect on Tor performance
it/volunteer.wml       497) can be measured. Other components would be a testing utility to
it/volunteer.wml       498) establish what are the properties of connections available, and to
it/volunteer.wml       499) measure the effect of performance-improving modifications to Tor.
it/volunteer.wml       500) <br />
it/volunteer.wml       501) The tools used would be up to the student, but dummynet (for FreeBSD)
it/volunteer.wml       502) and nistnet (for Linux) are two potential components on which this
it/volunteer.wml       503) project could be built. Students should be experienced with network
it/volunteer.wml       504) programming/debugging and TCP/IP, and preferably familiar with C and a
it/volunteer.wml       505) scripting language.
it/volunteer.wml       506) </li>
it/volunteer.wml       507)  
it/volunteer.wml       508) <li>
it/volunteer.wml       509) <b>An Improved and More Usable Network Map in Vidalia</b>
it/volunteer.wml       510) <br />
it/volunteer.wml       511) Priority: <i>Low to Medium</i>
it/volunteer.wml       512) <br />
it/volunteer.wml       513) Effort Level: <i>Medium</i>
it/volunteer.wml       514) <br />
it/volunteer.wml       515) Skill Level: <i>Medium</i>
it/volunteer.wml       516) <br />
it/volunteer.wml       517) Likely Mentors: <i>Matt</i>
it/volunteer.wml       518) <br />
it/volunteer.wml       519) One of Vidalia's existing features is a network map that shows the user
it/volunteer.wml       520) the approximate geographic location of relays in the Tor network and
it/volunteer.wml       521) plots the paths the user's traffic takes as it is tunneled through the
it/volunteer.wml       522) Tor network. The map is currently not very interactive and has rather
it/volunteer.wml       523) poor graphics. Instead, we implemented KDE's Marble widget such
it/volunteer.wml       524) that it gives us a better quality map and enables improved interactivity,
it/volunteer.wml       525) such as allowing the user to click on individual relays or circuits to
it/volunteer.wml       526) display additional information. We want to add the ability
it/volunteer.wml       527) for users to click on a particular relay or a country containing one or
it/volunteer.wml       528) more Tor exit relays and say, "I want my connections to exit
it/volunteer.wml       529) from here."
it/volunteer.wml       530) <br />
it/volunteer.wml       531) This project will first involve getting familiar with Vidalia
it/volunteer.wml       532) and the Marble widget's API. One will then integrate the widget
it/volunteer.wml       533) into Vidalia and customize Marble to be better suited for our application,
it/volunteer.wml       534) such as making circuits clickable, storing cached map data in Vidalia's
it/volunteer.wml       535) own data directory, and customizing some of the widget's dialogs.
it/volunteer.wml       536) <br />
it/volunteer.wml       537) A person undertaking this project should have good C++ development
it/volunteer.wml       538) experience. Previous experience with Qt and CMake is helpful, but not
it/volunteer.wml       539) required.
it/volunteer.wml       540) </li>
it/volunteer.wml       541) 
it/volunteer.wml       542) <li>
it/volunteer.wml       543) <b>Bring moniTor to life</b>
it/volunteer.wml       544) <br />
it/volunteer.wml       545) Priority: <i>Low</i>
it/volunteer.wml       546) <br />
it/volunteer.wml       547) Effort Level: <i>Medium</i>
it/volunteer.wml       548) <br />
it/volunteer.wml       549) Skill Level: <i>Low to Medium</i>
it/volunteer.wml       550) <br />
it/volunteer.wml       551) Likely Mentors: <i>Karsten, Jacob</i>
it/volunteer.wml       552) <br />
it/volunteer.wml       553) Implement a <a href="http://www.ss64.com/bash/top.html">top-like</a>
it/volunteer.wml       554) management tool for Tor relays. The purpose of such a tool would be
it/volunteer.wml       555) to monitor a local Tor relay via its control port and include useful
it/volunteer.wml       556) system information of the underlying machine. When running this tool, it
it/volunteer.wml       557) would dynamically update its content like top does for Linux processes.
it/volunteer.wml       558) <a href="http://archives.seul.org/or/dev/Jan-2008/msg00005.html">This
it/volunteer.wml       559) or-dev post</a> might be a good first read.
it/volunteer.wml       560) <br />
it/volunteer.wml       561) A person interested in this should be familiar
it/volunteer.wml       562) with or willing to learn about administering a Tor relay and configuring
it/volunteer.wml       563) it via its control port. As an initial prototype is written in Python,
it/volunteer.wml       564) some knowledge about writing Python code would be helpful, too. This
it/volunteer.wml       565) project is one part about identifying requirements to such a
it/volunteer.wml       566) tool and designing its interface, and one part lots of coding.
it/volunteer.wml       567) </li>
it/volunteer.wml       568) 
it/volunteer.wml       569) <li>
it/volunteer.wml       570) <b>Torbutton equivalent for Thunderbird</b>
it/volunteer.wml       571) <br />
it/volunteer.wml       572) Priority: <i>Low</i>
it/volunteer.wml       573) <br />
it/volunteer.wml       574) Effort Level: <i>High</i>
it/volunteer.wml       575) <br />
it/volunteer.wml       576) Skill Level: <i>High</i>
it/volunteer.wml       577) <br />
it/volunteer.wml       578) Likely Mentors: <i>Mike</i>
it/volunteer.wml       579) <br />
it/volunteer.wml       580) We're hearing from an increasing number of users that they want to use
it/volunteer.wml       581) Thunderbird with Tor. However, there are plenty of application-level
it/volunteer.wml       582) concerns, for example, by default Thunderbird will put your hostname in
it/volunteer.wml       583) the outgoing mail that it sends. At some point we should start a new
it/volunteer.wml       584) push to build a Thunderbird extension similar to Torbutton.
it/volunteer.wml       585) </li>
it/volunteer.wml       586) 
it/volunteer.wml       587) <li>
it/volunteer.wml       588) <b>Intermediate Level Network Device Driver</b>
it/volunteer.wml       589) <br />
it/volunteer.wml       590) Priority: <i>Low</i>
it/volunteer.wml       591) <br />
it/volunteer.wml       592) Effort Level: <i>High</i>
it/volunteer.wml       593) <br />
it/volunteer.wml       594) Skill Level: <i>High</i>
it/volunteer.wml       595) <br />
it/volunteer.wml       596) Likely Mentors: <i>Martin</i>
it/volunteer.wml       597) <br />
it/volunteer.wml       598) The WinPCAP device driver used by Tor VM for bridged networking does
it/volunteer.wml       599) not support a number of wireless and non-Ethernet network adapters.
it/volunteer.wml       600) Implementation of a intermediate level network device driver for win32
it/volunteer.wml       601) and 64bit would provide a way to intercept and route traffic over such
it/volunteer.wml       602) networks. This project will require knowledge of and experience with
it/volunteer.wml       603) Windows kernel device driver development and testing. Familiarity with
it/volunteer.wml       604) Winsock and Qemu would also be helpful.
it/volunteer.wml       605) </li>
it/volunteer.wml       606) 
it/volunteer.wml       607) <li>
it/volunteer.wml       608) <b>Improve Tor Weather</b>
it/volunteer.wml       609) <br />
it/volunteer.wml       610) Priority: <i>Medium</i>
it/volunteer.wml       611) <br />
it/volunteer.wml       612) Effort Level: <i>Medium</i>
it/volunteer.wml       613) <br />
it/volunteer.wml       614) Skill Level: <i>Medium</i>
it/volunteer.wml       615) <br />
it/volunteer.wml       616) Likely Mentors: <i>Jake, Roger</i>
it/volunteer.wml       617) <br />
it/volunteer.wml       618) <a href="https://weather.torproject.org/">Tor weather</a> is a tool
it/volunteer.wml       619) that allows signing up to receive notifications via email when the
it/volunteer.wml       620) tracked Tor relay is down. Currently, it isn't really useful for
it/volunteer.wml       621) people who use the hibernation feature of Tor, or for those who
it/volunteer.wml       622) have to shut down their relay regularly. During the project, Tor
it/volunteer.wml       623) weather could be extended to allow more flexible configurations.
it/volunteer.wml       624) Other enhancements are also possible: Weather could send out warnings
it/volunteer.wml       625) when your relay runs an out-of-date version of Tor, or when its
it/volunteer.wml       626) observed bandwith drops below a certain value. It might also be a
it/volunteer.wml       627) nice tool that allows for checking whether your relay has earned
it/volunteer.wml       628) you a <a href="<page tshirt>">T-Shirt</a>, or sending reminders to
it/volunteer.wml       629) directory authorities that
it/volunteer.wml       630) their keys are about to expire. Be creative, and consider how the
it/volunteer.wml       631) above project to track overall network status can help you get your job
it/volunteer.wml       632) done more quickly! See also its
it/volunteer.wml       633) <a href="https://svn.torproject.org/svn/weather/trunk/README">README</a>
it/volunteer.wml       634) and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
it/volunteer.wml       635) </li>
it/volunteer.wml       636) 
it/volunteer.wml       637) <li>
it/volunteer.wml       638) <b>Bring up new ideas!</b>
it/volunteer.wml       639) <br />
it/volunteer.wml       640) Don't like any of these? Look at the <a

it/volunteer.wml       641) href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development

it/volunteer.wml       642) roadmap</a> for more ideas.

it/volunteer.wml       643) Some of the <a href="<gittree>doc/spec/proposals/">current proposals</a>

it/volunteer.wml       644) might also be short on developers.
it/volunteer.wml       645) </li>
it/volunteer.wml       646) 

it/volunteer.wml       647) <!-- Mike is already working on this.
it/volunteer.wml       648) <li>Tor Node Scanner improvements</b>

it/volunteer.wml       649) <br />

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

it/volunteer.wml       651) statistics can be gathered about the reliability of nodes. Nodes that
it/volunteer.wml       652) fail too high a percentage of their circuits should not be given
it/volunteer.wml       653) Guard status. Perhaps they should have their reported bandwidth
it/volunteer.wml       654) penalized by some ratio as well, or just get marked as Invalid. In
it/volunteer.wml       655) addition, nodes that exhibit a very low average stream capacity but
it/volunteer.wml       656) advertise a very high node bandwidth can also be marked as Invalid.
it/volunteer.wml       657) Much of this statistics gathering is already done, it just needs to be
it/volunteer.wml       658) transformed into something that can be reported to the Directory
it/volunteer.wml       659) Authorities to blacklist/penalize nodes in such a way that clients
it/volunteer.wml       660) will listen.
it/volunteer.wml       661) <br />
it/volunteer.wml       662) In addition, these same statistics can be gathered about the traffic
it/volunteer.wml       663) through a node. Events can be added to the <a

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

it/volunteer.wml       665) Protocol</a> to
it/volunteer.wml       666) report if a circuit extend attempt through the node succeeds or fails, and
it/volunteer.wml       667) passive statistics can be gathered on both bandwidth and reliability
it/volunteer.wml       668) of other nodes via a node-based monitor using these events. Such a
it/volunteer.wml       669) scanner would also report information on oddly-behaving nodes to
it/volunteer.wml       670) the Directory Authorities, but a communication channel for this
it/volunteer.wml       671) currently does not exist and would need to be developed as well.
it/volunteer.wml       672) </li>

it/volunteer.wml       673) -->

it/volunteer.wml       674) 

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

it/volunteer.wml       676) <li>
it/volunteer.wml       677) <b>Una migliore gestione dei pacchetti Debian/Ubuntu per Tor e Vidalia</b>
it/volunteer.wml       678) <br />
it/volunteer.wml       679) Vidalia al momento non funziona bene su Debian e Ubuntu con i pacchetti
it/volunteer.wml       680) standard di Tor. Gli attuali pacchetti Tor fanno partire automaticamente Tor
it/volunteer.wml       681) come demone sotto l'utente debian-tor e (giustamente) senza una

it/volunteer.wml       682) <a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> definita

it/volunteer.wml       683) del file torrc. Di conseguenza, Vidalia cerca di far 
it/volunteer.wml       684) partire il suo processo Tor, dato che non riesce a connettersi a un processo
it/volunteer.wml       685) Tor esistente, col risulato che il processo Tor di Vidalia termina con un messaggio di errore
it/volunteer.wml       686) che l'utente probabilmente non capisce, dato che non può collegarsi alle sue
it/volunteer.wml       687) porte in ascolto — che sono già utilizzate dal demone Tor originale.
it/volunteer.wml       688) <br />
it/volunteer.wml       689) La soluzione attuale prevede o di dire all'utente di fermare il demone
it/volunteer.wml       690) Tor esistente e farne partire uno da Vidalia, oppure di spiegare all'utente
it/volunteer.wml       691) come definire una port e una password nel file di configurazione
it/volunteer.wml       692) torrc. Su Debian una soluzione migliore sarebbe usare il ControlSocket di Tor,
it/volunteer.wml       693) che permetterebbe a Vidalia di parlare con Tor attraverso un Unix domain socket, e potrebbe
it/volunteer.wml       694) essere abilitata di default nei pacchetti Debian di Tor. Vidalia potrebbe 
it/volunteer.wml       695) quindi autenticarsi a Tor con una autenticazione basata sul filesystem (cookie),
it/volunteer.wml       696) usa Vidalia fa parte del gruppo debian-tor.
it/volunteer.wml       697) <br />
it/volunteer.wml       698) Questo progetto richiede di aggiungere a Vidalia il supporto per ControlSocket
it/volunteer.wml       699) di Tor. Lo studente svilupper&agrave; e tester&agrave; i pacchetti Vidalia
it/volunteer.wml       700) per Debian e Ubuntu in conformit&agrave; agli standard di pacchetto Debian,
it/volunteer.wml       701) e verificher&agrave; che essi funzionino bene con  i pacchetti Tor esistenti. Possiamo anche
it/volunteer.wml       702) creare un repository apt per ospitare i nuovi pacchetti Vidalia.
it/volunteer.wml       703) <br />
it/volunteer.wml       704) Il prossimo passo sar&agrave; trovare un metodo intuitivo e facile perch&eacute; Vidalia
it/volunteer.wml       705) possa modificare la configurazione di Tor (torrc) anche se si trova
it/volunteer.wml       706) in <code>/etc/tor/torrc</code> ed &egrave; quindi non modificabile. Finora la cosa
it/volunteer.wml       707) migliore che abbiamo pensato &egrave; fornire a Tor una nuova configurazione tramite
it/volunteer.wml       708) il ControlSocket quando Vidalia si avvia, ma ha il difetto di far partire Tor
it/volunteer.wml       709) ad ogni boot con una configurazione diversa da quella desiderata dall'utente. L'alternativa
it/volunteer.wml       710) che
it/volunteer.wml       711) ci &egrave; venuta in mente &egrave; che Vidalia scriva un file torrc temporaneo
it/volunteer.wml       712) e chieda all'utente di spostarlo manualmente in <code>/etc/tor/torrc</code>,
it/volunteer.wml       713) ha il difetto di fare interagire l'utente direttamente con i file.
it/volunteer.wml       714) <br />

it/volunteer.wml       715) Le persone interessate a questo progetto dovrebbero conoscere bene il

it/volunteer.wml       716) Debian package management ed avere qualche esperienza di sviluppo in C++. Apprezzata,
it/volunteer.wml       717) ma non obbligatoria, dell'esperienza con Qt.
it/volunteer.wml       718) </li>
it/volunteer.wml       719) 

it/volunteer.wml       720) -->

it/volunteer.wml       721) 

it/volunteer.wml       722) <!-- This should be mostly done.

it/volunteer.wml       723) <li>
it/volunteer.wml       724) <b>Framework per l'aggiornamento automatico di Tor/Polipo/Vidalia Framework</b>
it/volunteer.wml       725) <br />
it/volunteer.wml       726) Ci seve un buon framework per l'aggiornamento autenticato.
it/volunteer.wml       727) Vidalia si accorge gi&agrave; se l'utente ha una versione obsoleta
it/volunteer.wml       728) o deprecata di Tor, tramite dei signed statement nelle informazioni
it/volunteer.wml       729) di directory Tor. Al momento Vidalia manda una semplice
it/volunteer.wml       730) finestra di avviso che informa l'utente che dovrebbe aggiornare manualmente.
it/volunteer.wml       731) Lo scopo del progetto &egrave; di estendere Vidalia aggiungendo la
it/volunteer.wml       732) possibilit&agrave; di scaricare e installare il software Tor aggiornato al
it/volunteer.wml       733) posto dell'utente. Il download dovrebbe avenire via Tor quando possibile, con un buon
it/volunteer.wml       734) meccanismo di fall back al download diretto. Tempo permettendo sarebbe bello
it/volunteer.wml       735) potere aggiornare altre applicazioni
it/volunteer.wml       736) contenute nei pacchetti di installazione, come Polipo e
it/volunteer.wml       737) Vidalia stessa.
it/volunteer.wml       738) <br />
it/volunteer.wml       739) Per portare a termine il progetto, lo studente dovr&agrave; anzitutto studiare
it/volunteer.wml       740) il framework di auto-update esistente (ad es., Sparkle su OS X) per valutarne
it/volunteer.wml       741) vantaggi, debolezze, fattori di sicurezza e possibilit&agrave; di venire
it/volunteer.wml       742) integrato in Vidalia. Se non se ne trovano di adatti, lo studente
it/volunteer.wml       743) disegner&agrave; uno proprio frameword di auto aggiornamento, documentando il disegno e
it/volunteer.wml       744) discutendolo con altri sviluppatori per verificarne gli aspetti di sicurezza.
it/volunteer.wml       745) Lo studente realizzer&agrave; poi il framework (o lo integrer&agrave; con
it/volunteer.wml       746) uno esistente) e lo sottoporr6agrave; a test.
it/volunteer.wml       747) <br />

it/volunteer.wml       748) Le persone interessate a questo progetto devono avere una buona esperienza di sviluppo

it/volunteer.wml       749) in C++. Utili, ma non obbligatorie, esperienze di Qt. Occorre anche
it/volunteer.wml       750) una buona comprensione delle comuni pratiche di sicurezza,
it/volunteer.wml       751) come la package signature verification. Importanti per il progetto anche buone
it/volunteer.wml       752) capacità di comunicazione scritta, poiché una fase cruciale

it/volunteer.wml       753) sarà la produzione di un design document da valutare e discutere
it/volunteer.wml       754) prima della realizzazione.

it/volunteer.wml       755) </li>

it/volunteer.wml       756) -->

it/volunteer.wml       757) 

it/volunteer.wml       758) 

it/volunteer.wml       759) 

it/volunteer.wml       760) <!-- Jake already did most of this.

it/volunteer.wml       761) <li>

it/volunteer.wml       762) <b>Migliorare il nostro test di configurazione del browser</b> - 

it/volunteer.wml       763) <a href="https://check.torproject.org/">https://check.torproject.org/</a>
it/volunteer.wml       764) <br />

it/volunteer.wml       765) Abbiamo in funzione una pagina web che rileva se Tor funziona. Ha
it/volunteer.wml       766) un po' di difetti e richiede migliorie sulle lingue e sulle 
it/volunteer.wml       767) funzionalità di default, dato che per ora risponde 
it/volunteer.wml       768) solo in inglese. Inoltre è un'accozzaglia di script in perl che
it/volunteer.wml       769) non dovrebbe essere mai nata. Probabilmente bisognerebbe riscriverla in python
it/volunteer.wml       770) con supporto multilingue. Al momento usa la <a

it/volunteer.wml       771) href="http://exitlist.torproject.org/">Tor DNS exit list</a>

it/volunteer.wml       772) e dovrebbe continuare ad usarla. Per ora genera dei falsi
it/volunteer.wml       773) positivi che andrebbero individuati, documentati e risolti ove
it/volunteer.wml       774) possibile. Gli interessati al progetto dovrebbero essere interessati anche nel
it/volunteer.wml       775) DNS, dovrebbero avere delle conoscenze di programmazione in perl o meglio python, e
it/volunteer.wml       776) dovrà interagire minimamente con Tor per testare il codice.
it/volunteer.wml       777) <br />
it/volunteer.wml       778) Se vuoi rendere più interessante il progetto con
it/volunteer.wml       779) un maggiore lavoro di design e sviluppo, dai  un'occhiata alla <a

it/volunteer.wml       780) href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal

it/volunteer.wml       781) 131-verify-tor-usage.txt</a>.
it/volunteer.wml       782) </li>

it/volunteer.wml       783) -->

it/volunteer.wml       784) 

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

it/volunteer.wml       786) <li>
it/volunteer.wml       787) <b>Improvements on our DNS Exit List service</b> - 
it/volunteer.wml       788) <a href="http://exitlist.torproject.org/">http://exitlist.torproject.org/</a>
it/volunteer.wml       789) <br />
it/volunteer.wml       790) The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>
it/volunteer.wml       791) is written by our fabulous anonymous
it/volunteer.wml       792) contributer Tup. It's a DNS server written in Haskell that supports part of our <a

it/volunteer.wml       793) href="<gitblob>doc/contrib/torel-design.txt">exitlist

it/volunteer.wml       794) design document</a>. Currently, it is functional and it is used by
it/volunteer.wml       795) check.torproject.org and other users. The issues that are outstanding
it/volunteer.wml       796) are mostly aesthetic. This wonderful service could use a much better
it/volunteer.wml       797) website using the common Tor theme. It would be best served with better
it/volunteer.wml       798) documentation for common services that use an RBL. It could use more
it/volunteer.wml       799) publicity. A person working on this project should be interested in DNS,
it/volunteer.wml       800) basic RBL configuration for popular services, and writing documentation.
it/volunteer.wml       801) The person would require minimal Tor interaction &mdash; testing their
it/volunteer.wml       802) own documentation at the very least. Furthermore, it would be useful
it/volunteer.wml       803) if they were interested in Haskell and wanted to implement more of the
it/volunteer.wml       804) torel-design.txt suggestions.
it/volunteer.wml       805) </li>

it/volunteer.wml       806) -->

it/volunteer.wml       807) 

it/volunteer.wml       808) <!-- Nobody wanted to keep this.

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

it/volunteer.wml       819) the <a href="http://www.decloak.net">metasploit
it/volunteer.wml       820) decloak website</a>. A person interested in defending Tor could start

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

it/volunteer.wml       823) be helpful as a start.) One should be familiar with the common

it/volunteer.wml       824) pitfalls but
it/volunteer.wml       825) possibly have new methods in mind for implementing decloaking issues. The
it/volunteer.wml       826) website should ensure that it tells a user what their problem is. It
it/volunteer.wml       827) should help them to fix the problem or direct them to the proper support
it/volunteer.wml       828) channels. The student should be closely familiar with using Tor and how
it/volunteer.wml       829) to prevent Tor information leakage.
it/volunteer.wml       830) </li>

it/volunteer.wml       831) -->

it/volunteer.wml       832) 

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

it/volunteer.wml       834) <li>
it/volunteer.wml       835) <b>Libevent and Tor integration improvements</b>
it/volunteer.wml       836) <br />
it/volunteer.wml       837) Tor should make better use of the more recent features of Niels
it/volunteer.wml       838) Provos's <a href="http://monkey.org/~provos/libevent/">Libevent</a>
it/volunteer.wml       839) library.  Tor already uses Libevent for its low-level asynchronous IO
it/volunteer.wml       840) calls, and could also use Libevent's increasingly good implementations
it/volunteer.wml       841) of network buffers and of HTTP.  This wouldn't be simply a matter of
it/volunteer.wml       842) replacing Tor's internal calls with calls to Libevent: instead, we'll
it/volunteer.wml       843) need to refactor Tor to use Libevent calls that do not follow the
it/volunteer.wml       844) same models as Tor's existing backends. Also, we'll need to add
it/volunteer.wml       845) missing functionality to Libevent as needed &mdash; most difficult likely
it/volunteer.wml       846) will be adding OpenSSL support on top of Libevent's buffer abstraction.
it/volunteer.wml       847) Also tricky will be adding rate-limiting to Libevent.
it/volunteer.wml       848) </li>

it/volunteer.wml       849) -->

it/volunteer.wml       850) 
it/volunteer.wml       851) 
it/volunteer.wml       852) <!--
it/volunteer.wml       853) <li>
it/volunteer.wml       854) <b>Improving the Tor QA process: Continuous Integration for Windows builds</b>
it/volunteer.wml       855) <br />
it/volunteer.wml       856) It would be useful to have automated build processes for Windows and
it/volunteer.wml       857) probably other platforms. The purpose of having a continuous integration
it/volunteer.wml       858) build environment is to ensure that Windows isn't left behind for any of
it/volunteer.wml       859) the software projects used in the Tor project or its accompanying.<br />
it/volunteer.wml       860) Buildbot may be a good choice for this as it appears to support all of
it/volunteer.wml       861) the platforms Tor does. See the 
it/volunteer.wml       862) <a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for
it/volunteer.wml       863) buildbot</a>.<br />
it/volunteer.wml       864) There may be better options and the person undertaking this task should
it/volunteer.wml       865) evaluate other options. Any person working on this automatic build
it/volunteer.wml       866) process should have experience or be willing to learn how to build all
it/volunteer.wml       867) of the respective Tor related code bases from scratch. Furthermore, the
it/volunteer.wml       868) person should have some experience building software in Windows
it/volunteer.wml       869) environments as this is the target audience we want to ensure we do not
it/volunteer.wml       870) leave behind. It would require close work with the Tor source code but
it/volunteer.wml       871) probably only in the form of building, not authoring.<br />
it/volunteer.wml       872) Additionally, we need to automate our performance testing for all platforms.
it/volunteer.wml       873) We've got buildbot (except on Windows &mdash; as noted above) to automate 
it/volunteer.wml       874) our regular integration and compile testing already,
it/volunteer.wml       875) but we need to get our network simulation tests (as built in torflow)
it/volunteer.wml       876) updated for more recent versions of Tor, and designed to launch a test
it/volunteer.wml       877) network either on a single machine, or across several, so we can test
it/volunteer.wml       878) changes in performance on machines in different roles automatically.
it/volunteer.wml       879) </li>
it/volunteer.wml       880) -->
it/volunteer.wml       881) 
it/volunteer.wml       882) 

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

it/volunteer.wml       884) <li>
it/volunteer.wml       885) <b>Torbutton improvements</b>
it/volunteer.wml       886) <br />
it/volunteer.wml       887) Torbutton has a number of improvements that can be made in the post-1.2
it/volunteer.wml       888) timeframe. Most of these are documented as feature requests in the <a

it/volunteer.wml       889) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">Torbutton

it/volunteer.wml       890) flyspray section</a>. Good examples include: stripping off node.exit on http
it/volunteer.wml       891) headers, more fine-grained control over formfill blocking, improved referrer
it/volunteer.wml       892) spoofing based on the domain of the site (a-la <a

it/volunteer.wml       893) href="https://addons.mozilla.org/en-US/firefox/addon/953">refcontrol extension</a>),

it/volunteer.wml       894) tighter integration with Vidalia for reporting Tor status, a New Identity
it/volunteer.wml       895) button with Tor integration and multiple identity management, and anything
it/volunteer.wml       896) else you might think of.
it/volunteer.wml       897) <br />
it/volunteer.wml       898) This work would be independent coding in Javascript and the fun world of <a
it/volunteer.wml       899) href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
it/volunteer.wml       900) with not too much involvement in the Tor internals.
it/volunteer.wml       901) </li>

it/volunteer.wml       902) -->

it/volunteer.wml       903) 
it/volunteer.wml       904) 

it/volunteer.wml       905) <!-- Is Blossom development still happening?

it/volunteer.wml       906) <li>
it/volunteer.wml       907) <b>Rework and extend Blossom</b>
it/volunteer.wml       908) <br />
it/volunteer.wml       909) Rework and extend Blossom (a tool for monitoring and
it/volunteer.wml       910) selecting appropriate Tor circuits based upon exit node requirements
it/volunteer.wml       911) specified by the user) to gather data in a self-contained way, with
it/volunteer.wml       912) parameters easily configurable by the user.  Blossom is presently
it/volunteer.wml       913) implemented as a single Python script that interfaces with Tor using the
it/volunteer.wml       914) Controller interface and depends upon metadata about Tor nodes obtained
it/volunteer.wml       915) via external processes, such as a webpage indicating status of the nodes
it/volunteer.wml       916) plus publically available data from DNS, whois, etc.  This project has
it/volunteer.wml       917) two parts: (1) Determine which additional metadata may be useful and
it/volunteer.wml       918) rework Blossom so that it cleanly obtains the metadata on its own rather
it/volunteer.wml       919) than depend upon external scripts (this may, for example, involve
it/volunteer.wml       920) additional threads or inter-process communication), and (2) develop a
it/volunteer.wml       921) means by which the user can easily configure Blossom, starting with a
it/volunteer.wml       922) configuration file and possibly working up to a web configuration engine.

it/volunteer.wml       923) Knowledge of Tor and Python are important; knowledge of 
it/volunteer.wml       924) TCP, interprocess communication, and Perl will also be helpful.  An
it/volunteer.wml       925) interest in network neutrality is important as well, since the
it/volunteer.wml       926) principles of evaluating and understanding internet inconsistency are at
it/volunteer.wml       927) the core of the Blossom effort.

it/volunteer.wml       928) </li>
it/volunteer.wml       929) 
it/volunteer.wml       930) <li>
it/volunteer.wml       931) <b>Improve Blossom: Allow users to qualitatively describe exit nodes they desire</b>
it/volunteer.wml       932) <br />
it/volunteer.wml       933) Develop and implement a means of affording Blossom
it/volunteer.wml       934) users the ability to qualitatively describe the exit node that they
it/volunteer.wml       935) want.  The Internet is an inconsistent place: some Tor exit nodes see
it/volunteer.wml       936) the world differently than others.  As presently implemented, Blossom (a
it/volunteer.wml       937) tool for monitoring and selecting appropriate Tor circuits based upon
it/volunteer.wml       938) exit node requirements specified by the user) lacks a sufficiently rich
it/volunteer.wml       939) language to describe how the different vantage points are different.
it/volunteer.wml       940) For example, some exit nodes may have an upstream network that filters
it/volunteer.wml       941) certain kinds of traffic or certain websites.  Other exit nodes may
it/volunteer.wml       942) provide access to special content as a result of their location, perhaps
it/volunteer.wml       943) as a result of discrimination on the part of the content providers
it/volunteer.wml       944) themselves.  This project has two parts: (1) develop a language for
it/volunteer.wml       945) describing characteristics of networks in which exit nodes reside, and
it/volunteer.wml       946) (2) incorporate this language into Blossom so that users can select Tor
it/volunteer.wml       947) paths based upon the description.

it/volunteer.wml       948) Knowledge of Tor and Python are important; knowledge of
it/volunteer.wml       949) TCP, interprocess communication, and Perl will also be helpful.  An
it/volunteer.wml       950) interest in network neutrality is important as well, since the
it/volunteer.wml       951) principles of evaluating and understanding internet inconsistency are at
it/volunteer.wml       952) the core of the Blossom effort.

it/volunteer.wml       953) </li>

it/volunteer.wml       954) -->

it/volunteer.wml       955) 

it/volunteer.wml       956) <!-- not really suited for GSoC; integrated into TBB for Linux/Mac OS X

it/volunteer.wml       957) <li>

it/volunteer.wml       958) <b>Usability testing of Tor</b>

it/volunteer.wml       959) <br />

it/volunteer.wml       960) Priority: <i>Medium</i>
it/volunteer.wml       961) <br />
it/volunteer.wml       962) Effort Level: <i>Medium</i>
it/volunteer.wml       963) <br />
it/volunteer.wml       964) Skill Level: <i>Low to Medium</i>
it/volunteer.wml       965) <br />
it/volunteer.wml       966) Likely Mentors: <i>Andrew</i>
it/volunteer.wml       967) <br />
it/volunteer.wml       968) Especially the browser bundle, ideally amongst our target demographic.
it/volunteer.wml       969) That would help a lot in knowing what needs to be done in terms of bug
it/volunteer.wml       970) fixes or new features. We get this informally at the moment, but a more
it/volunteer.wml       971) structured process would be better.

it/volunteer.wml       972) </li>
it/volunteer.wml       973) 
it/volunteer.wml       974) </ol>
it/volunteer.wml       975) 

it/volunteer.wml       976) <a id="OtherCoding"></a>
it/volunteer.wml       977) <h2><a class="anchor" href="#OtherCoding">Altre idee di sviluppo e design</a></h2>

it/volunteer.wml       978) <ol>

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

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

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

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

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

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

it/volunteer.wml       988) alla nuova interfaccia libevent. Christian King ha dato un

it/volunteer.wml       989) <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">buon inizio

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

it/volunteer.wml       991) 

it/volunteer.wml       992) <li>Dobbiamo iniziare a realizzare il nostro <a href="<page
it/volunteer.wml       993) documentation>#DesignDoc">blocking-resistance design</a>. Occorre
it/volunteer.wml       994) ideare il design, modificare varie parti di Tor, adattare

it/volunteer.wml       995) <a href="<page vidalia/index>">Vidalia</a> perch&eacute; supporti le

it/volunteer.wml       996) nuove funzionalit&agrave; e progettarne lo sviluppo.</li>

it/volunteer.wml       997) 

it/volunteer.wml       998) <li>Serve un framework flessibile di simulazione per studiare gli attacchi
it/volunteer.wml       999) end-to-end di conferma del traffico. Molti ricercatori hanno creato dei sumulatori
it/volunteer.wml      1000) ad hoc a sostegno delle loro intuizioni sul funzionamento degli attacchi
it/volunteer.wml      1001) o di certe difese e contromisure. Possiamo costruire un simulatore
it/volunteer.wml      1002) ben documentato e aperto che possa fornire a ciascuno risposte
it/volunteer.wml      1003) adeguare? Questo potrebbe contribuire a molte nuove ricerche.
it/volunteer.wml      1004) Vedi la voce <a href="#Research">qui sotto</a> sui confirmation attack per
it/volunteer.wml      1005) maggior dettagli sulla ricerca in questo campo &mdash; chiss&agrave; forse al
it/volunteer.wml      1006) termine  potresti scrivere qualche paper sull'argomento.</li>

it/volunteer.wml      1007) 

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

it/volunteer.wml      1009) tramite OpenSSL. &Egrave; stato testato leggermente ed &egrave; verosimilmente pieno di bachi. Cerchiamo test pi&ugrave; rigorosi, analisi delle prestazioni e, idealmente, modifiche al codice di OpenSSL e Tor se necessario.</li>

it/volunteer.wml      1010) 

it/volunteer.wml      1011) <li>Effettuare una analisi di sicurezza di Tor con <a
it/volunteer.wml      1012) href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determinare
it/volunteer.wml      1013) se esistono delle buone librerie di fuzzing adatte al nostro scopo. Guadagnati la fama
it/volunteer.wml      1014) e il credito quando potremo fare una nuova release grazie a te!</li>

it/volunteer.wml      1015) 

it/volunteer.wml      1016) <li>Tor usa TCP per il trasporto e TLS per la cifratura del
it/volunteer.wml      1017) collegamento. Funziona ed &egrave; semplice, ma significa che se un pacchetto
it/volunteer.wml      1018) viene scartato tutte le cellule di un collegamento subiscono un ritardo; inoltre
it/volunteer.wml      1019) significa che possiamo ragionrvolmente supportare solo flussi TCP. Abbiamo una <a

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

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

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

it/volunteer.wml      1023) href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specifiche

it/volunteer.wml      1024) per Tor e

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

it/volunteer.wml      1026) 

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

it/volunteer.wml      1030) 
it/volunteer.wml      1031) <li>Ci serve un sistema per generare i diagrammi sul sito web (ad esempio, le immagini
it/volunteer.wml      1032) How Tor Works" nella <a href="<page overview>">pagina di panoramica</a>
it/volunteer.wml      1033) a partire daisorgenti, in modo da tradurli come testo UTF-8 invece di modificarli
it/volunteer.wml      1034) a mano con Gimp. Potremmo integrare ci&ograve;
it/volunteer.wml      1035) come file wml per i traduttori e generare cos&igrave; le immagine
it/volunteer.wml      1036) in pi&ugrave; lingue quando risostruiamo il sito web.</li>
it/volunteer.wml      1037) 
it/volunteer.wml      1038) <li>Come possiamo rendere il <a
it/volunteer.wml      1039) href="http://anonymityanywhere.com/incognito/">LiveCD Incognito</a>
it/volunteer.wml      1040) pi&ugrave; facile da mantenere, migliorare e documentare?</li>

it/volunteer.wml      1041) </ol>

it/contribute.it.html 1042) 

it/volunteer.wml      1043) <a id="Research"></a>
it/volunteer.wml      1044) <h2><a class="anchor" href="#Research">Ricerca</a></h2>
it/volunteer.wml      1045) <ol>
it/volunteer.wml      1046) <li>Attacco di tipo "website fingerprinting": fai un elenco di quanche
it/volunteer.wml      1047) centinaio di siti famosi, scaricane le pagine, crea una serie di
it/volunteer.wml      1048) "signature" per ciascun sito. Poi osserva il traffico di un client Tor. Mentre
it/volunteer.wml      1049) riceve dati, potresti indovinare se e quale di questi siti
it/volunteer.wml      1050) il client sta visitando. Per prima cosa, che possibilit&agrave; di successo
it/volunteer.wml      1051) ha questo attacco sull'installato Tor attuale? Poi, cerca delle difese
it/volunteer.wml      1052) possibili: ad esempio, potremmo cambiare le dimensioni delle cellule Tor da 512
it/volunteer.wml      1053) byte a 1024 byte, potremmo usare tecniche di padding come <a
it/volunteer.wml      1054) href="http://freehaven.net/anonbib/#timing-fc2004">il defensive dropping</a>,
it/volunteer.wml      1055) o potremmo aggiungere ritardi nel traffico. Che impatto avrebbe,
it/volunteer.wml      1056) che conseguenze avrebbe sull'usabilit&agrave; (con un metro di riferimento adeguato)
it/volunteer.wml      1057) l'uso di difese efficaci in ciascuno di questi casi?</li>
it/volunteer.wml      1058) <li>Attacco di tipo "end-to-end traffic confirmation":
it/volunteer.wml      1059) osservando il traffico dal lato di Alice e di Bob, si possono <a
it/volunteer.wml      1060) href="http://freehaven.net/anonbib/#danezis:pet2004">confrontare
it/volunteer.wml      1061) le signature del traffico e dedurre che si sta osservando lo stesso
it/volunteer.wml      1062) flusso</a>. Finora Tor si rassegna ad accettare questa situazione, assumendo
it/volunteer.wml      1063) che in ogni caso questo attacco &egrave; triviale. Ma &egrave; davvero cos&igrave;? Quanto
it/volunteer.wml      1064)  e quale traffico &egrave; necessario perch&eacute; un aversario
it/volunteer.wml      1065) sia certo di aver vinto? Ci sono situazioni che rallentano l'attacco (es. trasmissioni modeste)?
it/volunteer.wml      1066) Il traffic padding o il traffic shaping

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

it/volunteer.wml      1068) <li>Un altro problema collegato &egrave;: Creare un relay/bridge offre qualche 
it/volunteer.wml      1069) protezione in pi&ugrave; contro questi timing attacks? Un avversario esterno che non pu&ograve;
it/volunteer.wml      1070) leggere dentro i link TLS pu&ograve; riuscire a riconoscere i singoli flussi in modo affidabile?
it/volunteer.wml      1071) La quantit&agrave; di traffico trasportato limita in qualche modo questa eventualit&agrave;? Cosa accadrebbe se
it/volunteer.wml      1072) il client-relay ritardasse apposta il traffico upstream creando una coda
it/volunteer.wml      1073) che potrebbe essere usata per simulare il timing dal client downstream cos&igrave; da fingere
it/volunteer.wml      1074) che sia traffico relayed anch'esso? Questa stessa coda potrebbe essere usata per mascherare
it/volunteer.wml      1075) i timing nel traffico upstream monte dai client con tecniche di <a
it/volunteer.wml      1076) href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
it/volunteer.wml      1077) ma senza aver bisogno di traffico addizionale. Una simile miscela di
it/volunteer.wml      1078) traffico upstream monte dal client potrebbe forse offuscare il timing per un avversario esterno? Questa strategia
it/volunteer.wml      1079) deve essere modificata in caso di link asimmetrici? Ad esempio, su
it/volunteer.wml      1080) link asimmentrici si riesce a distinguere il traffico del client dai
it/volunteer.wml      1081) picchi naturali dovuti all'asimmetria della capacit&agrave; del link? Od &egrave; pi&ugrave;
it/volunteer.wml      1082) facile sui link asimmetrici, per qualche altro motivo?</li>

it/volunteer.wml      1083) <li>Ripetere l' <a
it/volunteer.wml      1084) href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attacco da
it/volunteer.wml      1085) Oakland 05</a> di Murdoch e Danezi sull'attuale rete Tor. Provare a capire perch&eacute;
it/volunteer.wml      1086) funziona bene contro alcuni nodi e non su altri. /La mia teoria &egrave; che
it/volunteer.wml      1087) i nodi veloci con capacit&agrave; aggiuntiva resistono meglio al'attacco) Se questo &egrave; vero
it/volunteer.wml      1088) allora bisogna provare con le opzioni RelayBandwidthRate e RelayBandwidthBurst
it/volunteer.wml      1089) per gestire un relay usato come client mentre si fa da relay al traffico
it/volunteer.wml      1090) dell'attaccante: riducendo RelayBandwidthRate, forse l'attacco

it/volunteer.wml      1091) diventa più difficile? Quale è il rapporto ideale tra RelayBandwidthRate e

it/volunteer.wml      1092) capacità reale? Ma è poi un rapporto? Già che ci siamo, un numero
it/volunteer.wml      1093) maggiore di potenziali relay aumenta forse il tasso di falsi positivi
it/volunteer.wml      1094) o altri fattori complessi per l'attacco? (La rete Tor oggi è di quasi due
it/volunteer.wml      1095) ordini di grandezza maggiore rispetto a quando fu scritto il paper.) Leggi anche
it/volunteer.wml      1096) <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
it/volunteer.wml      1097) Clog the Queue</a>.</li>

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

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

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

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

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

it/volunteer.wml      1129) Potremmo sperimentare finestre di ampiezza variabile, invece
it/volunteer.wml      1130) di finestre di ampiezza fissa? Questo sembrava funzionare bene in un <a
it/volunteer.wml      1131) href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">esperimento
it/volunteer.wml      1132) di throughput ssh</a>. Dovremmo misurare e provare, e forse applicare il metodo
it/volunteer.wml      1133) se i risultati fossero soddisfacenti.</li>

it/volunteer.wml      1134) <li>Uno degli obiettivi per resistere alla censura &egrave; impedire
it/volunteer.wml      1135) ad un attaccante che osservi il traffico Tor su una connessione di <a

it/volunteer.wml      1136) href="<svnprojects>design-paper/blocking.html#sec:network-fingerprint">distinguerlo

it/volunteer.wml      1137) dal normale traffico SSL</a>. Non possiamo ovviamente ottenere perfetta
it/volunteer.wml      1138) steganografia e al contempo essere ancora utilizzabili, ma come primo passo ci
it/volunteer.wml      1139) bloccare tutti quegli attacchi che funzionano solo osservando pochi pacchetti. Uno degli
it/volunteer.wml      1140) altri attacchi che non abbiamo esaminato ancora a fondo &egrave; che le celle Tor sono di 512
it/volunteer.wml      1141) byte, e quindi il traffico sulla connessione potrebbe essere di multipli di 512 byte.
it/volunteer.wml      1142) Batching e overhead nei record TLS modificano questo dato sulla connessione?
it/volunteer.wml      1143) Ci sono altre strategie di buffer flushing in Tor che influiscono su questo dato? Possiamo
it/volunteer.wml      1144) aspettarci dei risultati usando un po' di padding, o si tratta di un attacco che dobbiamo accettare cos&igrave; com'&egrave;?</li>

it/volunteer.wml      1145) <li>I circuiti Tor si stabiliscono un nodo alla volta, per cui potremmo
it/volunteer.wml      1146) fare uscire alcuni flussi dal secondo nodo, altri dal terzo e cos&igrave; via.
it/volunteer.wml      1147) Sembra una buona idea, dato che riduce i flussi in uscita

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

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

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

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

it/volunteer.wml      1155) <li>Programmi come <a

it/volunteer.wml      1156) href="<page torbutton/index>">Torbutton</a> cercano di nascondere

it/volunteer.wml      1157) la stringa UserAgent del tuo browser sostituendola con una risposta uniforme
it/volunteer.wml      1158) per ogni utente Tor. In questo modo un attaccante non può ridurre l'anonymity set
it/volunteer.wml      1159) in base a questo header. Torbutton cerca di usare una stringa comunemente usata anche
it/volunteer.wml      1160) da utenti non-Tor in modo da non dare nell'occhio. Prima domanda: quanto
it/volunteer.wml      1161) è dannoso aggiornare periodicamente la versione di Firefox che
it/volunteer.wml      1162) Torbutton dichiara? Se la aggiorniamo troppo spessp suddividiamo da soli
it/volunteer.wml      1163) l'anonymity set. se non l'aggiorniamo abbastanza spesso allora tutti gli
it/volunteer.wml      1164) utenti di Tor spiccano dato che dichiarano una versione obsoleta di
it/volunteer.wml      1165) Firefox. La risposta dipende probabilmente dalle versioni di Firefox osservabili
it/volunteer.wml      1166) dal vivo. Seconda domanda: ci viene regolarmente chiesto di ruotare N stringhe
it/volunteer.wml      1167) UserAgent invece di usarne una sola. È un approccio utile, dannoso
it/volunteer.wml      1168) o indifferente? Considera per esempio: uso di cookie e riconoscimento di utenti
it/volunteer.wml      1169) Torbutton dai loro UserAgent; siti web maliziosi che attaccano solo certi
it/volunteer.wml      1170) browser; e se le risposte alla domanda numero uno hanno in impatto sulla seconda domanda.
it/volunteer.wml      1171) </li>
it/volunteer.wml      1172) <li>Per ora i client Tor riutilizzano un circuito per dieci minuti
it/volunteer.wml      1173) da quando &egrave; stato stabilito. Lo scopo &egrave; di evitare il sovraccarico
it/volunteer.wml      1174) della rete con troppe operazioni di estensione di circuito, e di evitare al contempo
it/volunteer.wml      1175) che i client usino lo stesso circuito troppo a lungo, tanto da permettere a un exit node
it/volunteer.wml      1176) di realizzare un profilo pseudonimo utile su di essi. Purtroppo 10 minuti sono
it/volunteer.wml      1177) troppo, specie se vengono fatte sullo stesso circuto connessioni per protocolli multipli (come IM e
it/volunteer.wml      1178) web browsing). Se manteniamo fisso il numero totale di
it/volunteer.wml      1179) circuit extend che la rete deve compiere, esistono altri metodi
it/volunteer.wml      1180) pi&ugrave; efficienti o sicuri perch&eacute; i client allochino flussi ai circuiti,
it/volunteer.wml      1181) o perch&eacute; i client costruiscano preventivamente dei circuiti? Forse un punto di partenza in
it/volunteer.wml      1182) questa ricerca &egrave; la raccolta di informazioni su che genere di connessioni
it/volunteer.wml      1183) vengono tipicamente lanciate dai client, in modo da disporre di un quadro realistico su cui lavorare.
it/volunteer.wml      1184) </li>
it/volunteer.wml      1185) <li>Quanti bridge relay occorre conoscere per mantenere una raggiungibilit&agrave;
it/volunteer.wml      1186) ottimale? Bisognerebbe misurare il tasso di esaurimento dei nostri bridge. Se questo &egrave;
it/volunteer.wml      1187) alto, ci sono dei modi per mantenere meglio connessi gli utenti dei
it/volunteer.wml      1188) bridge?

it/volunteer.wml      1189) </li>
it/volunteer.wml      1190) 

it/volunteer.wml      1191) </ol>

it/contribute.it.html 1192) 

it/volunteer.wml      1193) <p>

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

it/volunteer.wml      1196) </p>

it/contribute.it.html 1197) 

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

it/volunteer.wml      1199) 
it/volunteer.wml      1200) #include <foot.wmi>