Runa A. Sandvik commited on 2010-08-13 21:10:35
Zeige 16 geänderte Dateien mit 185 Einfügungen und 406 Löschungen.
... | ... |
@@ -29,13 +29,12 @@ ni ninguna otra cosa."</p> |
29 | 29 |
|
30 | 30 |
<a id="onionlogo"></a> |
31 | 31 |
<h2>¿Puedo usar el logo de la cebolla Tor?</h2> |
32 |
-<p>If you're making non-commercial use of Tor software, you may also use the |
|
33 |
-Tor onion logo (as an illustration, not as a brand for your products). |
|
34 |
-Please don't modify the design or colors of the logo. You can use items |
|
35 |
-that look like the Tor onion logo to illustrate a point (e.g. an exploded |
|
36 |
-onion with layers, for instance), so long as they're not used as logos in |
|
37 |
-ways that would confuse people. As a general guideline, the Tor Project logo |
|
38 |
-should not be the dominant image on a page.</p> |
|
32 |
+<p>Si está haciendo un uso no comercial del sofware Tor, puede también usar el |
|
33 |
+logo de la cebolla Tor (como ilustración, no como marca para sus |
|
34 |
+productos). Por favor no modifique el diseño ni los colores del logo. Puede |
|
35 |
+usar items que se parezcan al logo de la cebolla Tor para ilustrar algo |
|
36 |
+(e.g. una cebolla abierta con capas, por ejemplo), mientras que no se usen |
|
37 |
+como logos de un modo que pueda confundir a la gente.</p> |
|
39 | 38 |
|
40 | 39 |
<a id="combining"></a> |
41 | 40 |
<h2>¿Puedo usar la palabra "Tor" como parte del nombre de mi producto o mi |
... | ... |
@@ -224,61 +224,6 @@ de conjuguer résistance à la censure avec facilité d'utilisation et |
224 | 224 |
robustesse. |
225 | 225 |
</li> |
226 | 226 |
|
227 |
- |
|
228 |
- |
|
229 |
-<!--<li> |
|
230 |
- |
|
231 |
-<b>Tuneup Tor!</b> |
|
232 |
-<br /> |
|
233 |
-Priority: <i>Medium to High</i> |
|
234 |
-<br /> |
|
235 |
-Effort Level: <i>Medium to High</i> |
|
236 |
-<br /> |
|
237 |
-Skill Level: <i>High</i> |
|
238 |
-<br /> |
|
239 |
-Likely Mentors: <i>Nick, Roger, Mike, Karsten</i> |
|
240 |
-<br /> |
|
241 |
-Right now, Tor relays measure and report their own bandwidth, and Tor |
|
242 |
-clients choose which relays to use in part based on that bandwidth. |
|
243 |
-This approach is vulnerable to |
|
244 |
-<a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where |
|
245 |
-relays lie about their bandwidth</a>; |
|
246 |
-to address this, Tor currently caps the maximum bandwidth |
|
247 |
-it's willing to believe any relay provides. This is a limited fix, and |
|
248 |
-a waste of bandwidth capacity to boot. Instead, |
|
249 |
-Tor should possibly measure bandwidth in a more distributed way, perhaps |
|
250 |
-as described in the |
|
251 |
-<a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for |
|
252 |
-Tor"</a> paper |
|
253 |
-by Snader and Borisov. One could use current testing code to |
|
254 |
-double-check this paper's findings and verify the extent to which they |
|
255 |
-dovetail with Tor as deployed in the wild, and determine good ways to |
|
256 |
-incorporate them into their suggestions Tor network without adding too |
|
257 |
-much communications overhead between relays and directory |
|
258 |
-authorities. |
|
259 |
-</li>--> |
|
260 |
-<li> |
|
261 |
-<b>Améliorer Polipo sous Windows</b> <br /> Priorité: <i>Moyenne à Haute</i> |
|
262 |
-<br /> Effort à fournir: <i>Moyen</i> <br /> Compétences requises: |
|
263 |
-<i>Moyennes</i> <br /> Tuteurs potentiels: <i>Chris</i> <br />Il faut nous |
|
264 |
-aider à porter <a |
|
265 |
-href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> sous |
|
266 |
-Windows. Quelques exemples de sujets à retenir: |
|
267 |
-<ol><li> la possibilité d'interroger de manière asynchrone les serveurs de noms, |
|
268 |
-trouver les serveurs de noms utilisés par le système et gérer les requêtes |
|
269 |
-netbios et dns.</li> |
|
270 |
-<li> gérer nativement les tampons et les évènement (i.e. sous les OS de type |
|
271 |
-Unix, Polipo occupe 25% de la ram, sous Windows, c'est selon la |
|
272 |
-configuration).</li> |
|
273 |
-<li> un outil graphique de configuration et de rapport, avec en bonus, une icône |
|
274 |
-de barre système avec un menu d'option par clic-droit. Double-bonus si c'est |
|
275 |
-multiplateforme.</li> |
|
276 |
-<li> permettre au logiciel d'utiliser le registre Windows et de gérer |
|
277 |
-correctement les emplacements de répertoire Windows tels que "C:\Program |
|
278 |
-Files\Polipo"</li> |
|
279 |
-</ol> |
|
280 |
-</li> |
|
281 |
- |
|
282 | 227 |
<li> |
283 | 228 |
<b>Interface de contrôle des évènements d'état de Tor</b> <br /> Priorité: |
284 | 229 |
<i>Moyenne</i> <br /> Effort à fournir: <i>Moyen</i> <br /> Compétences |
... | ... |
@@ -393,44 +338,31 @@ mobiles, détecte automatiquement le changement d'adresse IP, reconnecte les |
393 | 338 |
circuits et gère le passage d'un réseau 2G à 3G à Wifi. |
394 | 339 |
</li> |
395 | 340 |
|
396 |
- |
|
397 |
- |
|
398 |
- |
|
399 |
- |
|
400 |
-<!--<li> |
|
401 |
- |
|
402 |
-<b>New Torbutton Features</b> |
|
403 |
-<br /> |
|
404 |
-Priority: <i>Medium</i> |
|
405 |
-<br /> |
|
406 |
-Effort Level: <i>High</i> |
|
407 |
-<br /> |
|
408 |
-Skill Level: <i>High</i> |
|
409 |
-<br /> |
|
410 |
-Likely Mentors: <i>Mike</i> |
|
411 |
-<br/> |
|
412 |
-There are several <a |
|
413 |
-href="https://trac.torproject.org/projects/tor/report/14">good |
|
414 |
-feature requests</a> on the Torbutton Trac section. In particular, <a |
|
415 |
-href="https://trac.torproject.org/projects/tor/ticket/523">Integrating |
|
416 |
-'New Identity' with Vidalia</a>, |
|
417 |
-<a href="https://trac.torproject.org/projects/tor/ticket/940">ways of |
|
418 |
-managing multiple cookie jars/identities</a>, |
|
419 |
-<a href="https://trac.torproject.org/projects/tor/ticket/637">preserving |
|
420 |
-specific cookies</a> when cookies are cleared, |
|
421 |
-<a |
|
422 |
-href="https://trac.torproject.org/projects/tor/ticket/524">better |
|
423 |
-referrer spoofing</a>, <a |
|
424 |
-href="https://trac.torproject.org/projects/tor/ticket/564">correct |
|
425 |
-Tor status reporting</a>, and <a |
|
426 |
-href="https://trac.torproject.org/projects/tor/ticket/462">"tor://" |
|
427 |
-and "tors://" urls</a> are all interesting |
|
428 |
-features that could be added. |
|
429 |
-<br /> |
|
341 |
+<li> |
|
342 |
+<b>New Torbutton Features</b> <br /> Priority: <i>Medium</i> <br /> Effort |
|
343 |
+Level: <i>High</i> <br /> Skill Level: <i>High</i> <br /> Likely Mentors: |
|
344 |
+<i>Mike</i> <br/> There are several <a |
|
345 |
+href="https://trac.torproject.org/projects/tor/report/14">good feature |
|
346 |
+requests</a> on the Torbutton Trac section. In particular, <a |
|
347 |
+href="https://trac.torproject.org/projects/tor/ticket/523">Integrating 'New |
|
348 |
+Identity' with Vidalia</a>, <a |
|
349 |
+href="https://trac.torproject.org/projects/tor/ticket/940">ways of managing |
|
350 |
+multiple cookie jars/identities</a>, <a |
|
351 |
+href="https://trac.torproject.org/projects/tor/ticket/637">preserving |
|
352 |
+specific cookies</a> when cookies are cleared, <a |
|
353 |
+href="https://trac.torproject.org/projects/tor/ticket/524">better referrer |
|
354 |
+spoofing</a>, <a |
|
355 |
+href="https://trac.torproject.org/projects/tor/ticket/564">correct Tor |
|
356 |
+status reporting</a>, and <a |
|
357 |
+href="https://trac.torproject.org/projects/tor/ticket/462">"tor://" and |
|
358 |
+"tors://" urls</a> are all interesting features that could be added. <br /> |
|
430 | 359 |
This work would be independent coding in Javascript and the fun world of <a |
431 | 360 |
href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>, |
432 | 361 |
with not too much involvement in the Tor internals. |
433 |
-</li>--> |
|
362 |
+</li> |
|
363 |
+ |
|
364 |
+ |
|
365 |
+ |
|
434 | 366 |
<!-- <li> |
435 | 367 |
|
436 | 368 |
<b>New Thandy Features</b> |
... | ... |
@@ -516,28 +448,6 @@ nom d'hôte au mail sortant qu'il envoie. A un certain niveau, nous devrions |
516 | 448 |
pousser la réalisation d'une extension Thunderbird similaire à Torbutton. |
517 | 449 |
</li> |
518 | 450 |
|
519 |
- |
|
520 |
- |
|
521 |
-<!--<li> |
|
522 |
- |
|
523 |
-<b>Intermediate Level Network Device Driver</b> |
|
524 |
-<br /> |
|
525 |
-Priority: <i>Low</i> |
|
526 |
-<br /> |
|
527 |
-Effort Level: <i>High</i> |
|
528 |
-<br /> |
|
529 |
-Skill Level: <i>High</i> |
|
530 |
-<br /> |
|
531 |
-Likely Mentors: <i>Martin</i> |
|
532 |
-<br /> |
|
533 |
-The WinPCAP device driver used by Tor VM for bridged networking does |
|
534 |
-not support a number of wireless and non-Ethernet network adapters. |
|
535 |
-Implementation of a intermediate level network device driver for win32 |
|
536 |
-and 64bit would provide a way to intercept and route traffic over such |
|
537 |
-networks. This project will require knowledge of and experience with |
|
538 |
-Windows kernel device driver development and testing. Familiarity with |
|
539 |
-Winsock and Qemu would also be helpful. |
|
540 |
-</li>--> |
|
541 | 451 |
<li> |
542 | 452 |
<b>Améliorer Tor Weather</b> <br /> Priorité: <i>Moyenne</i> <br /> Effort à |
543 | 453 |
fournir: <i>Moyen</i> <br /> Compétences requises: <i>moyennes</i> <br /> |
... | ... |
@@ -601,91 +511,15 @@ disposer d'une certaine connaissance des règles d'empaquetage dans Debian et |
601 | 511 |
avoir une expérience en C++. Des compétences en QT seraient un vrai plus. |
602 | 512 |
</li> |
603 | 513 |
|
604 |
- |
|
605 |
- |
|
606 |
-<!--<li> |
|
607 |
- |
|
608 |
-<b>Tor/Polipo/Vidalia Auto-Update Framework</b> |
|
609 |
-<br /> |
|
610 |
-We're in need of a good authenticated-update framework. |
|
611 |
-Vidalia already has the ability to notice when the user is running an |
|
612 |
-outdated or unrecommended version of Tor, using signed statements inside |
|
613 |
-the Tor directory information. Currently, Vidalia simply pops |
|
614 |
-up a little message box that lets the user know they should manually |
|
615 |
-upgrade. The goal of this project would be to extend Vidalia with the |
|
616 |
-ability to also fetch and install the updated Tor software for the |
|
617 |
-user. We should do the fetches via Tor when possible, but also fall back |
|
618 |
-to direct fetches in a smart way. Time permitting, we would also like |
|
619 |
-to be able to update other |
|
620 |
-applications included in the bundled installers, such as Polipo and |
|
621 |
-Vidalia itself. |
|
622 |
-<br /> |
|
623 |
-To complete this project, the student will first need to first investigate |
|
624 |
-the existing auto-update frameworks (e.g., Sparkle on OS X) to evaluate |
|
625 |
-their strengths, weaknesses, security properties, and ability to be |
|
626 |
-integrated into Vidalia. If none are found to be suitable, the student |
|
627 |
-will design their own auto-update framework, document the design, and |
|
628 |
-then discuss the design with other developers to assess any security |
|
629 |
-issues. The student will then implement their framework (or integrate |
|
630 |
-an existing one) and test it. |
|
631 |
-<br /> |
|
632 |
-A person undertaking this project should have good C++ development |
|
633 |
-experience. Previous experience with Qt is helpful, but not required. One |
|
634 |
-should also have a good understanding of common security |
|
635 |
-practices, such as package signature verification. Good writing ability |
|
636 |
-is also important for this project, since a vital step of the project |
|
637 |
-will be producing a design document to review and discuss |
|
638 |
-with others prior to implementation. |
|
639 |
-</li>--> |
|
640 | 514 |
<li> |
641 |
-<b>Améliorer le processus qualité de Tor: Intégration continue de |
|
642 |
-compilation</b> <br /> Priorité: <i>Moyenne</i> <br /> Effort à fournir: |
|
643 |
-<i>Moyen</i> <br /> Compétences requises: <i>Moyennes</i> <br /> Tuteurs |
|
644 |
-potentiels: <i>Erinn</i> <br /> Il serait très utile d'avoir un processus de |
|
645 |
-compilation automatisée pour Windows et pour les autres plateformes. Le but |
|
646 |
-d'avoir un tel environnement est de s'assurer que Windows ne reste pas à la |
|
647 |
-traîne sur aucun des logiciels employés dans le projet Tor. <br />Buildbot |
|
648 |
-semble être un bon choix car il supporte toutes les plateformes |
|
649 |
-surlesquelles Tor fonctionne. Consultez <a |
|
650 |
-href="http://en.wikipedia.org/wiki/BuildBot">l'article Wikipedia sur |
|
651 |
-buildbot</a>.<br /> Il y a sans doute de meilleures options que la personne |
|
652 |
-désirant gérer cette tâche doit évaluer. Toute personne travaillant sur ce |
|
653 |
-processus de compilation automatique doit avoir de l'expérience ou le désir |
|
654 |
-d'apprendre comment compiler l'ensemble du code source en lien avec Tor à |
|
655 |
-partir de rien. De plus, cette personne doit disposer d'une expérience dans |
|
656 |
-la compilation de logiciels sous l'environnement Windows car c'est le coeur |
|
657 |
-de cible à ne pas rater de ce projet. Ce travail impose d'utiliser le code |
|
658 |
-source de Tor mais uniquement du point de vue compilation et non |
|
659 |
-d'écriture.<br /> Ensuite, nous avons besoin d'automatiser nos tests de |
|
660 |
-performance pour toutes les plateformes. Nous disposons là encore de builbot |
|
661 |
-(sauf sur Windows — comme indiqué ci-dessus) pour automatiser nos |
|
662 |
-intégrations régulières de code et nos tests de compilation mais nous avons |
|
663 |
-besoin de mettre à jour nos tests de simulation réseau pour les versions les |
|
664 |
-plus récente de Tor. Enfin, nous avons besoin de lancer des tests réseau à |
|
665 |
-la fois sur une seule machine et également à travers plusieurs autres de |
|
666 |
-manière à tester automatiquement les changement de performance avec des |
|
667 |
-rôles différents. |
|
515 |
+<b>Usability testing of Tor</b> <br /> Priority: <i>Medium</i> <br /> Effort |
|
516 |
+Level: <i>Medium</i> <br /> Skill Level: <i>Low to Medium</i> <br /> Likely |
|
517 |
+Mentors: <i>Andrew</i> <br /> Especially the browser bundle, ideally amongst |
|
518 |
+our target demographic. That would help a lot in knowing what needs to be |
|
519 |
+done in terms of bug fixes or new features. We get this informally at the |
|
520 |
+moment, but a more structured process would be better. |
|
668 | 521 |
</li> |
669 | 522 |
|
670 |
- |
|
671 |
- |
|
672 |
-<!--<li> |
|
673 |
- |
|
674 |
-<b>Usability testing of Tor</b> |
|
675 |
-<br /> |
|
676 |
-Priority: <i>Medium</i> |
|
677 |
-<br /> |
|
678 |
-Effort Level: <i>Medium</i> |
|
679 |
-<br /> |
|
680 |
-Skill Level: <i>Low to Medium</i> |
|
681 |
-<br /> |
|
682 |
-Likely Mentors: <i>Andrew</i> |
|
683 |
-<br /> |
|
684 |
-Especially the browser bundle, ideally amongst our target demographic. |
|
685 |
-That would help a lot in knowing what needs to be done in terms of bug |
|
686 |
-fixes or new features. We get this informally at the moment, but a more |
|
687 |
-structured process would be better. |
|
688 |
-</li>--> |
|
689 | 523 |
<li> |
690 | 524 |
<b>Un proxy IRC d'authentification</b> <br /> Priorité: <i>Basse</i> <br /> |
691 | 525 |
Effort à fournir: <i>Moyen à Important</i> <br /> Compétences requises: |
... | ... |
@@ -0,0 +1,109 @@ |
1 |
+ |
|
2 |
+ |
|
3 |
+ |
|
4 |
+ |
|
5 |
+ |
|
6 |
+ |
|
7 |
+## translation metadata |
|
8 |
+# Revision: $Revision$ |
|
9 |
+# Translation-Priority: 1-high |
|
10 |
+#include "head.wmi" TITLE="Tor: anonymity online" CHARSET="UTF-8" |
|
11 |
+<div class="main-column"> |
|
12 |
+ |
|
13 |
+ |
|
14 |
+ |
|
15 |
+<!-- PUT CONTENT AFTER THIS TAG --> |
|
16 |
+<h2>Tor: anonimitāte Internetā</h2> |
|
17 |
+ |
|
18 |
+ |
|
19 |
+<!-- BEGIN SIDEBAR --> |
|
20 |
+<div class="sidebar"> |
|
21 |
+<h3>Pārskats</h3> |
|
22 |
+<p></p> |
|
23 |
+<p><a href="<page overview>#overview">Kāpēc Tor?</a></p> |
|
24 |
+<p><a href="<page torusers>">Kas lieto Tor?</a></p> |
|
25 |
+<p><a href="<page overview>#thesolution">Kas ir Tor?</a></p> |
|
26 |
+<div class="underline"></div> |
|
27 |
+<div class="downloadbutton"> |
|
28 |
+<p><a href="<page easy-download>">Lejuplādēt Tor</a></p> |
|
29 |
+</div> |
|
30 |
+<div class="donatebutton"> |
|
31 |
+<p><a href="<page donate>">Ziedo un atbalsti Tor!</a></p> |
|
32 |
+</div> |
|
33 |
+</div> |
|
34 |
+ |
|
35 |
+ |
|
36 |
+<!-- END SIDEBAR --> |
|
37 |
+<div class="underline"></div> |
|
38 |
+ |
|
39 |
+<p>Tor ir bezmaksas programmatūra un atvērts tīkls, kas palīdz aizsargāties |
|
40 |
+pret tīkla komunikāciju uzraudzības veidu - <a href="<page |
|
41 |
+overview>">datplūsmas analīzi</a>, kas apdraud personisko brīvību un |
|
42 |
+privātumu, konfidenciālas biznesa aktivitātes un attiecības, valsts drošību.</p> |
|
43 |
+ |
|
44 |
+<p>Tor aizsargā tevi, pāradresējot tavas komunikācijas dalītā tīklā starp |
|
45 |
+brīvprātīgo darbinātiem retranslatoriem visā pasaule: tas liedz tiem, kas |
|
46 |
+novēro tavu Internet pieslēgumu, uzzināt, kādas tīmekļa vietnes tu apmeklē, |
|
47 |
+un tas liedz apmeklētajām tīmekļa vietnēm uzzināt tavu fizisko atrašanās |
|
48 |
+vietu. Tor strādā ar daudzām no tavām pašreizējām lietojumprogrammām - |
|
49 |
+tīmekļa pārlūkiem, tūlītējas ziņojumapmaiņas un attālās piekļuve klientiem, |
|
50 |
+kā arī citām lietojumprogrammām, kas izmanto TCP protokolu. |
|
51 |
+</p> |
|
52 |
+ |
|
53 |
+<p> Tūkstošiem cilvēku visā pasaulē izmanto Tor dažādu iemeslu dēļ: žurnālisti |
|
54 |
+un blogeri, cilvēktiesību aktīvisti, tiesībsargājošo iiestāžu darbinieki, |
|
55 |
+militārpersonas, uzņēmumi, iedzīvotāji valstīs ar represīvu režīmu un |
|
56 |
+vienkārši parasti pilsoņi. Apskati <a href="<page torusers>">Kas lieto |
|
57 |
+Tor?</a> lapu ar tipisku Tor lietotāju piemēriem. Apskati <a href="<page |
|
58 |
+overview>">pārskata lapu</a> ar detalizētāku izkaidrojumu, ko Tor dara, un |
|
59 |
+kāpēc lietotāju dažādība ir svarīga. |
|
60 |
+</p> |
|
61 |
+ |
|
62 |
+<p>Tor maģiski nenošifrē visas tavas aktivitātes Internetā. Tev <a href="<page |
|
63 |
+download>#Warning">jāsaprot, ko Tor dara un nedara tavā labā</a>.</p> |
|
64 |
+ |
|
65 |
+<p> |
|
66 |
+Tor drošība uzlabojas, pieaugot lietotāju skaitam un pieaugot cilvēku |
|
67 |
+skaitam, kas <a href="<page docs/tor-doc-relay>">darbina |
|
68 |
+retranslatorus</a>. (Aktivizēt retranslācijas funkciju nav tik sarežģīti, kā |
|
69 |
+tas varētu likties, un tas ievērojami <a |
|
70 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">uzlabo |
|
71 |
+tava paša drošību</a>). Ja retranslatora darbināšana nav domāta tev, mums ir |
|
72 |
+nepieciešama <a href="<page volunteer>">palīdzība citos projekta |
|
73 |
+aspektos</a>, un mums nepieciešami līdzekļi, lai turpinātu uzlabot Tor tīkla |
|
74 |
+ātrdarbību un izmantošanas vieglumu, saglabājot labu drošību.</p> |
|
75 |
+ |
|
76 |
+<p>Tor ir reģistrēta 501(c)(3) ASV bezpeļnas organizācija, kuras misija ir dot |
|
77 |
+tev iespēju pasargāt savu Internet datplūsmu no analīzes. Lūdzu, atbalsti to |
|
78 |
+un <a href="<page donate>">ziedo</a>. |
|
79 |
+</p> |
|
80 |
+ |
|
81 |
+<a id="News"></a> |
|
82 |
+<h2><a class="anchor" href="#News">Jaunumi</a></h2> |
|
83 |
+<div class="underline"></div> |
|
84 |
+ |
|
85 |
+<ul> |
|
86 |
+<li>2. maijs, 2010: Izlaista stabila Tor 0.2.1.26 versija. Ir izlabotas OpenSSL |
|
87 |
+savietojamības problēmas un pievienota aizsardzība retranslatoriem pasargāt |
|
88 |
+sevi no savienojumu plūdiem. Lasiet <a |
|
89 |
+href="https://blog.torproject.org/blog/tor-02126-stable-released">pilnu |
|
90 |
+paziņojumu</a> ar izmaiņu sarakstu.</li> |
|
91 |
+<li>29. marts 2010: Tor un Printfection paziņo par Tor veikala atvēršanu. Vairāk |
|
92 |
+informāčijas pieejams <a href="<page |
|
93 |
+press/2010-03-25-tor-store-press-release>">preses relīzē</a>.</li> |
|
94 |
+<li><b>Mēs aktīvi meklējam jaunus sponsorus un finansējumu.</b> Ja tavai |
|
95 |
+organizācijai ir interese uzturēt Tor tīklu lietojamu un ātru, lūdzu <a |
|
96 |
+href="<page contact>">sazinies ar mums</a>. <a href="<page sponsors>">Tor |
|
97 |
+sponsori</a> saņem personīgu uzmanību, labāku tehnisko atbalstu, publicitāti |
|
98 |
+(ja viņi to vēlas), un iespēju ietekmēt tālākus pētniecības un izstrādes |
|
99 |
+virzienus. <a href="<page donate>">Lūdzu, ziedo.</a></li> |
|
100 |
+ |
|
101 |
+</ul> |
|
102 |
+<p><a href="<page news>">Vairāk ziņu</a> | <a href="<page |
|
103 |
+press/index>">Preses relīzes</a> | <a href="<page tormedia>">Tor |
|
104 |
+ziņās</a></p> |
|
105 |
+ </div> |
|
106 |
+ |
|
107 |
+ |
|
108 |
+ |
|
109 |
+#include <foot.wmi> |
... | ... |
@@ -209,59 +209,6 @@ nawet po tym, jak atakujący pozna projekt, po czym równoważenie odporności |
209 | 209 |
na cenzurę z użytecznością i siłą. |
210 | 210 |
</li> |
211 | 211 |
|
212 |
- |
|
213 |
- |
|
214 |
-<!--<li> |
|
215 |
- |
|
216 |
-<b>Tuneup Tor!</b> |
|
217 |
-<br /> |
|
218 |
-Priority: <i>Medium to High</i> |
|
219 |
-<br /> |
|
220 |
-Effort Level: <i>Medium to High</i> |
|
221 |
-<br /> |
|
222 |
-Skill Level: <i>High</i> |
|
223 |
-<br /> |
|
224 |
-Likely Mentors: <i>Nick, Roger, Mike, Karsten</i> |
|
225 |
-<br /> |
|
226 |
-Right now, Tor relays measure and report their own bandwidth, and Tor |
|
227 |
-clients choose which relays to use in part based on that bandwidth. |
|
228 |
-This approach is vulnerable to |
|
229 |
-<a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where |
|
230 |
-relays lie about their bandwidth</a>; |
|
231 |
-to address this, Tor currently caps the maximum bandwidth |
|
232 |
-it's willing to believe any relay provides. This is a limited fix, and |
|
233 |
-a waste of bandwidth capacity to boot. Instead, |
|
234 |
-Tor should possibly measure bandwidth in a more distributed way, perhaps |
|
235 |
-as described in the |
|
236 |
-<a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for |
|
237 |
-Tor"</a> paper |
|
238 |
-by Snader and Borisov. One could use current testing code to |
|
239 |
-double-check this paper's findings and verify the extent to which they |
|
240 |
-dovetail with Tor as deployed in the wild, and determine good ways to |
|
241 |
-incorporate them into their suggestions Tor network without adding too |
|
242 |
-much communications overhead between relays and directory |
|
243 |
-authorities. |
|
244 |
-</li>--> |
|
245 |
-<li> |
|
246 |
-<b>Ulepszenie Polipo na Windows</b> <br /> Priorytet: <i>Średni do |
|
247 |
-Wysokiego</i> <br /> Poziom wysiłku: <i>Średni</i> <br /> Poziom |
|
248 |
-umiejętności: <i>Średni</i> <br /> Prawdopodobni opiekunowie: <i>Chris</i> |
|
249 |
-<br /> Pomóż przenieść <a |
|
250 |
-href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> na |
|
251 |
-Windows. Przykładowe tematy to: |
|
252 |
-<ol><li> zdolność do asynchronicznego wysyłania zapytań do serwerów nazw, znajdowania |
|
253 |
-systemowych serwerów nazw i zarządzanie zapytaniami NetBIOS i DNS.</li> |
|
254 |
-<li> natywna obsługa zdarzeń i buforów (tj. w systemach uniksopodobnych Polipo |
|
255 |
-domyślnie używa 25% pamięci RAM, a pod Windows jest to cokolwiek wpisane w |
|
256 |
-plik konfiguracyjny).</li> |
|
257 |
-<li> jakieś narzędzie z graficznym interfejsem do konfiguracji i raportowania, |
|
258 |
-dodatkowe punkty, jeśli ma ikonkę w zasobniku z opcjami menu po kliknięciu |
|
259 |
-prawym przyciskiem myszy. Podwójny bonus, jeśli działa na wielu platformach.</li> |
|
260 |
-<li> umożliwienie programowi używania rejestru Windowsa i obsługiwania |
|
261 |
-prawidłowych ścieżek w Windowsie, np. "C:\Program Files\Polipo".</li> |
|
262 |
-</ol> |
|
263 |
-</li> |
|
264 |
- |
|
265 | 212 |
<li> |
266 | 213 |
<b>Interfejs zdarzeń stanu kontrolera Tora dla programu Vidalia</b> <br /> |
267 | 214 |
Priorytet: <i>Średni</i> <br /> Poziom wysiłku: <i>Średni</i> <br /> Poziom |
... | ... |
@@ -376,44 +323,31 @@ adresu IP, ponownie łącząc obwody itd, przełączając się z 2G na 3G i Wifi |
376 | 323 |
tak dalej. |
377 | 324 |
</li> |
378 | 325 |
|
379 |
- |
|
380 |
- |
|
381 |
- |
|
382 |
- |
|
383 |
-<!--<li> |
|
384 |
- |
|
385 |
-<b>New Torbutton Features</b> |
|
386 |
-<br /> |
|
387 |
-Priority: <i>Medium</i> |
|
388 |
-<br /> |
|
389 |
-Effort Level: <i>High</i> |
|
390 |
-<br /> |
|
391 |
-Skill Level: <i>High</i> |
|
392 |
-<br /> |
|
393 |
-Likely Mentors: <i>Mike</i> |
|
394 |
-<br/> |
|
395 |
-There are several <a |
|
396 |
-href="https://trac.torproject.org/projects/tor/report/14">good |
|
397 |
-feature requests</a> on the Torbutton Trac section. In particular, <a |
|
398 |
-href="https://trac.torproject.org/projects/tor/ticket/523">Integrating |
|
399 |
-'New Identity' with Vidalia</a>, |
|
400 |
-<a href="https://trac.torproject.org/projects/tor/ticket/940">ways of |
|
401 |
-managing multiple cookie jars/identities</a>, |
|
402 |
-<a href="https://trac.torproject.org/projects/tor/ticket/637">preserving |
|
403 |
-specific cookies</a> when cookies are cleared, |
|
404 |
-<a |
|
405 |
-href="https://trac.torproject.org/projects/tor/ticket/524">better |
|
406 |
-referrer spoofing</a>, <a |
|
407 |
-href="https://trac.torproject.org/projects/tor/ticket/564">correct |
|
408 |
-Tor status reporting</a>, and <a |
|
409 |
-href="https://trac.torproject.org/projects/tor/ticket/462">"tor://" |
|
410 |
-and "tors://" urls</a> are all interesting |
|
411 |
-features that could be added. |
|
412 |
-<br /> |
|
326 |
+<li> |
|
327 |
+<b>New Torbutton Features</b> <br /> Priority: <i>Medium</i> <br /> Effort |
|
328 |
+Level: <i>High</i> <br /> Skill Level: <i>High</i> <br /> Likely Mentors: |
|
329 |
+<i>Mike</i> <br/> There are several <a |
|
330 |
+href="https://trac.torproject.org/projects/tor/report/14">good feature |
|
331 |
+requests</a> on the Torbutton Trac section. In particular, <a |
|
332 |
+href="https://trac.torproject.org/projects/tor/ticket/523">Integrating 'New |
|
333 |
+Identity' with Vidalia</a>, <a |
|
334 |
+href="https://trac.torproject.org/projects/tor/ticket/940">ways of managing |
|
335 |
+multiple cookie jars/identities</a>, <a |
|
336 |
+href="https://trac.torproject.org/projects/tor/ticket/637">preserving |
|
337 |
+specific cookies</a> when cookies are cleared, <a |
|
338 |
+href="https://trac.torproject.org/projects/tor/ticket/524">better referrer |
|
339 |
+spoofing</a>, <a |
|
340 |
+href="https://trac.torproject.org/projects/tor/ticket/564">correct Tor |
|
341 |
+status reporting</a>, and <a |
|
342 |
+href="https://trac.torproject.org/projects/tor/ticket/462">"tor://" and |
|
343 |
+"tors://" urls</a> are all interesting features that could be added. <br /> |
|
413 | 344 |
This work would be independent coding in Javascript and the fun world of <a |
414 | 345 |
href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>, |
415 | 346 |
with not too much involvement in the Tor internals. |
416 |
-</li>--> |
|
347 |
+</li> |
|
348 |
+ |
|
349 |
+ |
|
350 |
+ |
|
417 | 351 |
<!-- <li> |
418 | 352 |
|
419 | 353 |
<b>New Thandy Features</b> |
... | ... |
@@ -498,28 +432,6 @@ nowe działania mające na celu stworzenie rozszerzenia dla Thunderbirda, |
498 | 432 |
podobnego do Torbuttona. |
499 | 433 |
</li> |
500 | 434 |
|
501 |
- |
|
502 |
- |
|
503 |
-<!--<li> |
|
504 |
- |
|
505 |
-<b>Intermediate Level Network Device Driver</b> |
|
506 |
-<br /> |
|
507 |
-Priority: <i>Low</i> |
|
508 |
-<br /> |
|
509 |
-Effort Level: <i>High</i> |
|
510 |
-<br /> |
|
511 |
-Skill Level: <i>High</i> |
|
512 |
-<br /> |
|
513 |
-Likely Mentors: <i>Martin</i> |
|
514 |
-<br /> |
|
515 |
-The WinPCAP device driver used by Tor VM for bridged networking does |
|
516 |
-not support a number of wireless and non-Ethernet network adapters. |
|
517 |
-Implementation of a intermediate level network device driver for win32 |
|
518 |
-and 64bit would provide a way to intercept and route traffic over such |
|
519 |
-networks. This project will require knowledge of and experience with |
|
520 |
-Windows kernel device driver development and testing. Familiarity with |
|
521 |
-Winsock and Qemu would also be helpful. |
|
522 |
-</li>--> |
|
523 | 435 |
<li> |
524 | 436 |
<b>Ulepszenie Pogody Tora</b> <br /> Priorytet: <i>Średni</i> <br /> Poziom |
525 | 437 |
wysiłku: <i>Średni</i> <br /> Poziom umiejętności: <i>Średni</i> <br /> |
... | ... |
@@ -584,89 +496,15 @@ mechanizmach paczek, jak również trochę doświadczenia z pisaniu w |
584 | 496 |
C++. Uprzednie doświadczenie z Qt będzie przydatne, ale nie jest wymagane. |
585 | 497 |
</li> |
586 | 498 |
|
587 |
- |
|
588 |
- |
|
589 |
-<!--<li> |
|
590 |
- |
|
591 |
-<b>Tor/Polipo/Vidalia Auto-Update Framework</b> |
|
592 |
-<br /> |
|
593 |
-We're in need of a good authenticated-update framework. |
|
594 |
-Vidalia already has the ability to notice when the user is running an |
|
595 |
-outdated or unrecommended version of Tor, using signed statements inside |
|
596 |
-the Tor directory information. Currently, Vidalia simply pops |
|
597 |
-up a little message box that lets the user know they should manually |
|
598 |
-upgrade. The goal of this project would be to extend Vidalia with the |
|
599 |
-ability to also fetch and install the updated Tor software for the |
|
600 |
-user. We should do the fetches via Tor when possible, but also fall back |
|
601 |
-to direct fetches in a smart way. Time permitting, we would also like |
|
602 |
-to be able to update other |
|
603 |
-applications included in the bundled installers, such as Polipo and |
|
604 |
-Vidalia itself. |
|
605 |
-<br /> |
|
606 |
-To complete this project, the student will first need to first investigate |
|
607 |
-the existing auto-update frameworks (e.g., Sparkle on OS X) to evaluate |
|
608 |
-their strengths, weaknesses, security properties, and ability to be |
|
609 |
-integrated into Vidalia. If none are found to be suitable, the student |
|
610 |
-will design their own auto-update framework, document the design, and |
|
611 |
-then discuss the design with other developers to assess any security |
|
612 |
-issues. The student will then implement their framework (or integrate |
|
613 |
-an existing one) and test it. |
|
614 |
-<br /> |
|
615 |
-A person undertaking this project should have good C++ development |
|
616 |
-experience. Previous experience with Qt is helpful, but not required. One |
|
617 |
-should also have a good understanding of common security |
|
618 |
-practices, such as package signature verification. Good writing ability |
|
619 |
-is also important for this project, since a vital step of the project |
|
620 |
-will be producing a design document to review and discuss |
|
621 |
-with others prior to implementation. |
|
622 |
-</li>--> |
|
623 | 499 |
<li> |
624 |
-<b>Polepszenie procesu QA Tora: Ciągła integracja dla paczek</b> <br /> |
|
625 |
-Priorytet: <i>Średni</i> <br /> Poziom wysiłku: <i>Średni</i> <br /> Poziom |
|
626 |
-umiejętności: <i>Średni</i> <br /> Prawdopodobni opiekunowie: <i>Erinn</i> |
|
627 |
-<br /> Przydałby się automatyczny system tworzenia paczek dla Windows i być |
|
628 |
-może innych systemów. Celem posiadania środowiska ciągłej integracji jest |
|
629 |
-upewnienie się, że Windows nie zostanie w tyle z żadnym z projektów |
|
630 |
-używanych lub związanych z projektem Tor. Buildbot może być dobrym |
|
631 |
-rozwiązaniem, gdyż zdaje się obsługiwać te same platformy, co |
|
632 |
-Tor. Przeczytaj (po angielsku) <a |
|
633 |
-href="http://en.wikipedia.org/wiki/BuildBot">wpis na Wikipedii dotyczący |
|
634 |
-Buildbota</a>.<br /> Może jednak są lepsze rozwiązania, więc osoba |
|
635 |
-podejmująca się tego zadania powinna rozważyć inne opcje. Jakakolwiek osoba |
|
636 |
-pracująca nad tym systemem automatycznego budowania powinna mieć |
|
637 |
-doświadczenie lub chęć do nauczenia się tego, jak buduje się wszystkie |
|
638 |
-odpowiednie elementy Tora od zera. Ponadto, ta osoba powinna mieć jakieś |
|
639 |
-doświadczenie w kompilowaniu programów w Windows, jako że to jest ta część |
|
640 |
-użytkowników, których nie chcemy zostawiać w tyle. Zadanie będzie wymagała |
|
641 |
-bliskiej pracy z kodem Tora, ale prawdopodobnie tylko od strony kompilacji, |
|
642 |
-nie pisania.<br /> Ponadto, musimy zautomatyzować nasze testy wydajności dla |
|
643 |
-wszystkich systemów. Mamy już buildbota (za wyjątkiem Windows — jak |
|
644 |
-napisane powyżej) do automatyzacji naszej zwyczajnej integracji i kompilacji |
|
645 |
-testów, ale musimy zaktualizować nasze testy symulacji sieci (takie, jak w |
|
646 |
-torflow) do nowszych wersji Tora i zaprojektować je tak, by uruchamiać sieci |
|
647 |
-testowe albo na jednej maszynie, albo na kilku, abyśmy mogli automatycznie |
|
648 |
-badać zmiany wydajności na maszynach pełniących różne zadania.<br /> |
|
500 |
+<b>Usability testing of Tor</b> <br /> Priority: <i>Medium</i> <br /> Effort |
|
501 |
+Level: <i>Medium</i> <br /> Skill Level: <i>Low to Medium</i> <br /> Likely |
|
502 |
+Mentors: <i>Andrew</i> <br /> Especially the browser bundle, ideally amongst |
|
503 |
+our target demographic. That would help a lot in knowing what needs to be |
|
504 |
+done in terms of bug fixes or new features. We get this informally at the |
|
505 |
+moment, but a more structured process would be better. |
|
649 | 506 |
</li> |
650 | 507 |
|
651 |
- |
|
652 |
- |
|
653 |
-<!--<li> |
|
654 |
- |
|
655 |
-<b>Usability testing of Tor</b> |
|
656 |
-<br /> |
|
657 |
-Priority: <i>Medium</i> |
|
658 |
-<br /> |
|
659 |
-Effort Level: <i>Medium</i> |
|
660 |
-<br /> |
|
661 |
-Skill Level: <i>Low to Medium</i> |
|
662 |
-<br /> |
|
663 |
-Likely Mentors: <i>Andrew</i> |
|
664 |
-<br /> |
|
665 |
-Especially the browser bundle, ideally amongst our target demographic. |
|
666 |
-That would help a lot in knowing what needs to be done in terms of bug |
|
667 |
-fixes or new features. We get this informally at the moment, but a more |
|
668 |
-structured process would be better. |
|
669 |
-</li>--> |
|
670 | 508 |
<li> |
671 | 509 |
<b>Uwierzytelniające proxy dla IRC</b> <br /> Priorytet: <i>Niski</i> <br /> |
672 | 510 |
Poziom wysiłku: <i>Średni do Wysokiego</i> <br /> Poziom umiejętności: |
... | ... |
@@ -1,13 +7,12 @@ |
1 | 7 |
## translation metadata |
2 | 8 |
# Revision: $Revision$ |
3 | 9 |
# Translation-Priority: 3-low |
4 |
- |
|
5 | 10 |
#include "head.wmi" TITLE="Tor: News" CHARSET="UTF-8" |
6 |
- |
|
7 | 11 |
<div class="main-column"> |
8 | 12 |
|
9 |
-<!-- PUT CONTENT AFTER THIS TAG --> |
|
10 | 13 |
|
14 |
+ |
|
15 |
+<!-- PUT CONTENT AFTER THIS TAG --> |
|
11 | 16 |
<a id="News"></a> |
12 | 17 |
<h2><a class="anchor" href="#News">Tor: Новости</a></h2> |
13 | 18 |
<div class="underline"></div> |
... | ... |
@@ -18,7 +23,7 @@ |
18 | 23 |
соединений. Смотрите список изменений в<a |
19 | 24 |
href="https://blog.torproject.org/blog/tor-02126-stable-released">объявлении</a>.</li> |
20 | 25 |
<li>29 марта 2009: Tor и Printfection запускают Магазин Tor. Подробности - в <a |
21 |
-href="https://www.torproject.org/press/2010-03-25-tor-store-press-release.html.en">пресс-релизе</a>.</li> |
|
26 |
+href="<page press/2009-03-25-tor-store-press-release>">пресс-релизе</a>.</li> |
|
22 | 27 |
<li>16 марта 2010: выход стабильной версии Tor 0.2.1.25. Исправлена регрессия, |
23 | 28 |
появившаяся в версии 0.2.1.23, способная помешать ретрансляторам верно |
24 | 29 |
угадывать свой IP-адрес. Также исправлено несколько небольших потенциальных |
... | ... |
@@ -328,7 +328,7 @@ style="font-size: 90%;">sig</a>)</li> |
328 | 328 |
|
329 | 329 |
|
330 | 330 |
|
331 |
-<p>Почитайте наши инструкции <a href="<page verifying-signatures>">о проверке |
|
331 |
+<p>Почитайте наши инструкции <a href="<page verifying-signatures>о проверке |
|
332 | 332 |
пакетных подписей</a>, которые позволят вам убедиться, что вы скачали именно |
333 | 333 |
тот файл, который мы планировали вам передать. Также, обратите внимание, что |
334 | 334 |
Firefox в нашем пакете <a |
... | ... |
@@ -30,7 +30,7 @@ Tor Browser Bundle. В качестве альтернативы, следуйт |
30 | 30 |
<code>.exe</code> и все файлы с расширением <code>.rar</code>). Файлы в |
31 | 31 |
папке <code>signatures</code> позволяют убедиться, что вы скачали именно то, |
32 | 32 |
что мы намеревались вам предоставить. Ознакомьтесь с нашими инструкциями |
33 |
-по<a href="<page verifying-signatures>">проверке подписи пакетов</a></p> |
|
33 |
+по<a href="<page verifying-signatures>проверке подписи пакетов</a></p> |
|
34 | 34 |
|
35 | 35 |
<p id="Download-torbrowserbundle" style="font-size: 120%; margin: 5mm">Tor Browser Bundle для Операционной Системы Windows с браузером Firefox |
36 | 36 |
(версия <version-torbrowserbundle>, вариант "разбитых" файлов, общий объем |