it/contribute.it.html (1d9f60bd1) - tor-webwml.git

contribute.it.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
  <title>Tor: Contribuisci</title>
  <meta name="Author" content="Roger Dingledine" />
  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
  <link rel="stylesheet" type="text/css" href="stylesheet.css" />
  <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" />
</head>
<body>

<table class="banner" border="0" cellpadding="0" cellspacing="0">
    <tr>
        <td class="banner-left"></td>
        <td class="banner-middle">
            <a href="index.it.html">Home</a>
          | <a href="howitworks.it.html">Come Funziona</a>
          | <a href="download.it.html">Scarica</a>
          | <a href="documentation.it.html">Docs</a>
          | <a href="users.it.html">Utenti</a>
          | <a href="faq.it.html">Faq</a>
          | <a class="current">Contribuire</a>
          | <a href="developers.it.html">Sviluppo</a>
          | <a href="research.it.html">Ricerca</a>
          | <a href="people.it.html">Persone</a>
        </td>
        <td class="banner-right"></td>
    </tr>
</table>

<p>Questa traduzione non &egrave; stata controllata dagli sviluppatori di Tor
e da EFF. Pu&ograve; risultare non attuale o sbagliata. Il sito ufficiale di
Tor &egrave; in Inglese, all'indirizzo http://tor.eff.org/</p>
<p>Necessit&agrave; presenti:</p>
<h2>Tor: Contribuire</h2>
<hr />
<p>Cosa abbiamo bisogno:</p>
<ul>
<li>Utenti come te per testare Tor, e permettere agli sviluppatori di 
malfunzionamenti o nuovi modi di .</li>
<li>Ti invitiamo a<a href="cvs/tor/doc/tor-doc.html#server">
creare un server</a> per contribuire alla crescita della rete Tor.</li> 
<li>Uno speciale bisogno di programmatori Windows per il debug della 
piattaforma Windows.</li>
<li>Avvia un <a href="cvs/tor/doc/tor-doc.html#hidden-service">Tor hidden
service</a> e mettici dei contenuti interessanti all'interno..</li>
<li>Informa i tuoi amici! Invitali a installare servers. Invitali a offrire
hidden service. Invitali a passar parola ai loro amici.</li>
<li>Cosa va documentato? Che cosa &egrave; mal documentato?</li>
<li>Entra a far parte dell'<a href="http://secure.eff.org/tor">Electronic
Frontier Foundation</a>. Un maggior numero di donazioni a EFF equivale a un 
maggior grado di libert&agrave; nel mondo e a un ulteriore sviluppo 
della rete Tor.</li>
</ul>

<p>Siamo in continua attivit&agrave;: se qualcuno si occupasse di task a breve termine 
sarebbe di grande aiuto a noi che possiamo cos&igrave; focalizzarci su Tor.
</p>

<p>Attivit&agrave; di scrittura:</p>
<ul>
<li>Volontari per manutenere il sito web, o che aiutino alla 
documentazione, o in aiuto per gestire i nostri TODO e nella gestione dei bug reports?</li>
<li>Abbiamo <i>molta</i> documentazione. Non &egrave; centralizzata e a volte
in duplicati. Puoi aiutarci a ordinarla?</li>
<li>Aiutaci nella traduzione delle pagine web e della documentazione
in altre lingue. Leggi la <a href="translation.html">guida alla traduzione</a> 
se vuoi cimentarti. (Esempi:
<a href="http://membres.lycos.fr/geolemalin/anonymat_garantit.htm">Francese</a>
, <a href="http://tor.freesuperhost.com/">Persiano</a> e 
<a href="http://www.gamevn.com/forum/showthread.php?t=103346">Vietnamita</a>.)</li>
<li>Sistemare <a
href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">le FAQ Wiki</a>,
e se conosci la risposta di qualche "FAQ senza risposta" non esitare a rispondere.</li>
</ul>

<p>Attivit&agrave; di Packaging:</p>
<ul>
<li>Siamo alla costante ricerca di un installer migliore per Windows. Specialmente,
sarebbe di grande aiuto se qualcuno estendesse il nostro windows installer NSIS-based
per includere FreeCap e Privoxy.</li>
<li>Il nostro OS X installer non riesce nell'uninstall. Ci sar&agave; un benedetto OS X
packagers che ha le capacit&agrave; per l'uninstall? Sta diventando una noia crescente
.</li>
</ul>

<p>Attivit&agrave di organizzazione e testing:</p>
<ul>
<li>Esiste una lista di programmi potenzialmente interessanti con cui Tor
pu&ograve; funzionare <a href="users.html">qui</a>. Esiste anche il <a
href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify
howto</a>. Cerchiamo persone che le provino, ne semplifichino le spiegazione, le
amplino dove bisogna, le documentino meglio, e facciano in modo che sia tutto pi&ugrave; 
usabile.
</li>
</ul>

<p>Attivit&agrave; di programmazione e sviluppo:</p>
<ul>
<li>We need somebody to code up a GUI or other
controller program, to do configuration, etc. See our <a
href="cvs/tor/doc/control-spec.txt">control specification</a> for details,
and the <a href="cvs/tor/contrib/TorControl.py">rudimentary demonstration
Python control script</a>. No, we don't know what the interface should look
like.  You can use any license you want, but we'd recommend 3-clause BSD or
maybe GPL; and we can only help out if your license conforms to the
<a href="http://www.debian.org/social_contract.html#guidelines">DFSG</a>.</li>
<li>Periodically people running servers tells us they want to have one
BandwidthRate during some part of the day, and a different BandwidthRate
at other parts of the day. Rather than coding this inside Tor, we should
have a little script that speaks via the Tor Controller Interface, and does
a setconf to change the bandwidth rate. Perhaps it would run out of cron,
or perhaps it would sleep until appropriate times and then do its tweak
(that's probably more portable). Can somebody write one for us and we'll
put it inside <a href="cvs/tor/contrib/">tor/contrib/</a>?</li>
<li>Does somebody want to do up a patch so we can be an NT service? Or
so we can go in the system tray?</li>
<li>A good (portable, fast, clean, BSD-free) asynchronous DNS library
would be really handy, so we don't have to keep forking DNS worker
threads to do gethostbyname.</li>
<li>Can somebody take a look at Martin's <a
href="http://wiki.noreply.org/wiki/TheOnionRouter/SquidProxy">Squid
and Tor</a> page, and update it to reflect Tor's
<a href="http://tor.eff.org/tor-manual.html">RedirectExit</a> config
option?</li>
<li>See the <a href="cvs/tor/doc/TODO">TODO</a> and
<a href="cvs/tor/doc/HACKING">HACKING</a> files in the Tor distribution
for more ideas.</li>
</ul>

<p>Security project-lets: We need people to attack the implementation
and clean it up, and also to attack the design and experiment with
defenses.</p>
<ul>
<li>We need somebody to <a
href="http://en.wikipedia.org/wiki/Fuzz_testing">fuzz</a> Tor. Are there
good libraries out there for what we want? What are the first steps? Win
fame by getting credit when we put out a new release because of you!</li>
<li>Website volume fingerprinting attacks (<a
href="http://freehaven.net/anonbib/#back01">Back et al</a>, <a
href="http://freehaven.net/anonbib/#hintz02">Hintz</a>).
Defenses include a large cell size, <a
href="http://freehaven.net/anonbib/#timing-fc2004">defensive dropping</a>,
etc. How well does each approach work?</li>
<li>The end-to-end traffic confirmation attack. We need to study
long-range dummies more, along with traffic shaping. How much traffic
of what sort of distribution is needed before the adversary is confident
he has won?</li>
<li>It's not that hard to DoS Tor servers or dirservers. Are puzzles
the right answer? What other practical approaches are there?</li>
<li>What sensitive info squeaks by privoxy? Are other html scrubbers
better?</li>
</ul>

<p>Designer project-lets:</p>
<ul>
<li>Server CPU load is high because clients keep asking to make new
circuits, which uses public key crypto. Possible defenses include:
using helper nodes (fixed entry nodes); rate limiting the number of
create cells handled per second; having clients retry failed extensions
a few times; implementing ssl sessions; and using hardware crypto when
available.</li>
<li>We fear we might not work very well when servers have asymmetric
bandwidth. Because Tor has separate TCP connections between each hop,
if the incoming bytes are arriving just fine and the outgoing bytes
are all getting dropped on the floor, the TCP push-back mechanisms
don't really transmit this information back to the incoming streams.
Perhaps Tor should detect when it's dropping a lot of outgoing packets,
and rate-limit incoming streams to regulate this itself? We need somebody
who's good with networks to simulate this and help design solutions.</li>
<li>Right now the hidden service descriptors are being stored on the
dirservers, but any reliable distributed storage system would do (for
example, a DHT that allows authenticated updates). Can somebody figure
out our best options and decide if they're good enough?</li>
<li>How hard is it to patch bind or a DNS proxy to redirect requests
to Tor via our tor-resolve socks extension? What about to convert UDP
DNS requests to TCP requests and send them through Tor?</li>
<li>Tor provides anonymous connections, but if you want to keep multiple
pseudonyms in practice (say, in case you frequently go to two websites
and if anybody knew about both of them they would conclude it's you),
we don't support that well yet. We should find a good approach and
interface for handling pseudonymous profiles in Tor. See <a
href="http://archives.seul.org/or/talk/Dec-2004/msg00086.html">this
post</a> and <a
href="http://archives.seul.org/or/talk/Jan-2005/msg00007.html">followup</a>
for details.</li>
</ul>

<p>Drop by <a href="irc://irc.oftc.net/tor">the #tor IRC channel at irc.oftc.net</a> or
<a href="mailto:tor-volunteer@freehaven.net">email
tor-volunteer@freehaven.net</a> if you want to help out!</p>

</div>
</div>
  <div class="bottom" id="bottom">
     <i><a href="mailto:tor-webmaster@freehaven.net" class="smalllink">Webmaster</a></i> -
     $Id$
  </div>
</body>
</html>

tor-webwml.git

Updated it html docs.