tor-commits

Download

tor-commits@lists.torproject.org

December 2019

21 participants
1811 discussions

[tor/master] manpage: fix some quoting
by teor＠torproject.org 16 Dec '19

16 Dec '19

commit 645acaf1387a514cfefd5e5c50cb629c5ab3ded1 Author: Taylor Yu <catalyst(a)torproject.org> Date: Thu Dec 12 11:19:35 2019 -0600 manpage: fix some quoting Fix some quoting, especially of constructs like "[address:]port", that were proving tricky for Asciidoctor tooling to parse correctly. Also fix formatting of some configuration variable names that contained double underscores. Neither asciidoc nor asciidoctor was rendering some of those correctly. Part of ticket 32708. --- doc/tor.1.txt | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 2cc932cb1..5469c91b3 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -6,6 +6,8 @@ :man manual: Tor Manual // compat-mode tells Asciidoctor tools to process this as legacy AsciiDoc :compat-mode: +// attribute to make it easier to write names containing double underscores +:dbl_: __ = TOR(1) == NAME @@ -367,7 +369,7 @@ forward slash (/) in the configuration file and on the command line. all sockets will be set to this limit. Must be a value between 2048 and 262144, in 1024 byte increments. Default of 8192 is recommended. -[[ControlPort]] **ControlPort** \['address':]__port__|**unix:**__path__|**auto** [__flags__]:: +[[ControlPort]] **ControlPort** ['address'**:**]{empty}__port__|**unix:**__path__|**auto** [__flags__]:: If set, Tor will accept connections on this port and allow those connections to control the Tor process using the Tor Control Protocol (described in control-spec.txt in @@ -525,7 +527,7 @@ forward slash (/) in the configuration file and on the command line. circuits. If the option is set to "default", we obey a parameter in the consensus document. (Default: auto) -[[ExtORPort]] **ExtORPort** \['address':]__port__|**auto**:: +[[ExtORPort]] **ExtORPort** ['address'**:**]{empty}__port__|**auto**:: Open this port to listen for Extended ORPort connections from your pluggable transports. + (Default: **DataDirectory**/extended_orport_auth_cookie) @@ -1289,7 +1291,7 @@ The following options are useful only for clients (that is, if the same circuit. Currently, two addresses are "too close" if they lie in the same /16 range. (Default: 1) -[[SocksPort]] **SocksPort** \['address':]__port__|**unix:**__path__|**auto** [_flags_] [_isolation flags_]:: +[[SocksPort]] **SocksPort** ['address'**:**]{empty}__port__|**unix:**__path__|**auto** [_flags_] [_isolation flags_]:: Open this port to listen for connections from SOCKS-speaking applications. Set this to 0 if you don't want to allow application connections via SOCKS. Set it to "auto" to have Tor pick a port for @@ -1587,7 +1589,7 @@ The following options are useful only for clients (that is, if resolved. This helps trap accidental attempts to resolve URLs and so on. (Default: 0) -[[HTTPTunnelPort]] **HTTPTunnelPort** \['address':]__port__|**auto** [_isolation flags_]:: +[[HTTPTunnelPort]] **HTTPTunnelPort** ['address'**:**]{empty}__port__|**auto** [_isolation flags_]:: Open this port to listen for proxy connections using the "HTTP CONNECT" protocol instead of SOCKS. Set this to 0 if you don't want to allow "HTTP CONNECT" connections. Set the port @@ -1597,7 +1599,7 @@ The following options are useful only for clients (that is, if perform stream isolation between listeners by default. See SOCKSPort for an explanation of isolation flags. (Default: 0) -[[TransPort]] **TransPort** \['address':]__port__|**auto** [_isolation flags_]:: +[[TransPort]] **TransPort** ['address'**:**]{empty}__port__|**auto** [_isolation flags_]:: Open this port to listen for transparent proxy connections. Set this to 0 if you don't want to allow transparent proxy connections. Set the port to "auto" to have Tor pick a port for you. This directive can be @@ -1635,7 +1637,7 @@ The following options are useful only for clients (that is, if + (Default: "default") -[[NATDPort]] **NATDPort** \['address':]__port__|**auto** [_isolation flags_]:: +[[NATDPort]] **NATDPort** ['address'**:**]{empty}__port__|**auto** [_isolation flags_]:: Open this port to listen for connections from old versions of ipfw (as included in old versions of FreeBSD, etc) using the NATD protocol. Use 0 if you don't want to allow NATD connections. Set the port @@ -1658,7 +1660,7 @@ The following options are useful only for clients (that is, if A comma-separated list of suffixes to use with **AutomapHostsOnResolve**. The "." suffix is equivalent to "all addresses." (Default: .exit,.onion). -[[DNSPort]] **DNSPort** \['address':]__port__|**auto** [_isolation flags_]:: +[[DNSPort]] **DNSPort** ['address'**:**]{empty}__port__|**auto** [_isolation flags_]:: If non-zero, open this port to listen for UDP DNS requests, and resolve them anonymously. This port only handles A, AAAA, and PTR requests---it doesn't handle arbitrary DNS request types. Set the port to "auto" to @@ -2291,7 +2293,7 @@ is non-zero): parallelizable operations. If this is set to 0, Tor will try to detect how many CPUs you have, defaulting to 1 if it can't tell. (Default: 0) -[[ORPort]] **ORPort** \['address':]__PORT__|**auto** [_flags_]:: +[[ORPort]] **ORPort** ['address'**:**]{empty}__PORT__|**auto** [_flags_]:: Advertise this port to listen for connections from Tor clients and servers. This option is required to be a Tor server. Set it to "auto" to have Tor pick a port for you. Set it to 0 to not @@ -2614,7 +2616,7 @@ details.) to set up a separate webserver. There's a sample disclaimer in contrib/operator-tools/tor-exit-notice.html. -[[DirPort]] **DirPort** \['address':]__PORT__|**auto** [_flags_]:: +[[DirPort]] **DirPort** ['address'**:**]{empty}__PORT__|**auto** [_flags_]:: If this option is nonzero, advertise the directory service on this port. Set it to "auto" to have Tor pick a port for you. This option can occur more than once, but only one advertised DirPort is supported: all @@ -3419,7 +3421,7 @@ These options are not saved to the torrc file by the "SAVECONF" controller command. Other options of this type are documented in control-spec.txt, section 5.4. End-users should mostly ignore them. -[[UnderscorePorts]] **\_\_ControlPort**, **\_\_DirPort**, **\_\_DNSPort**, **\_\_ExtORPort**, **\_\_NATDPort**, **\_\_ORPort**, **\_\_SocksPort**, **\_\_TransPort**:: +[[UnderscorePorts]] **{dbl_}ControlPort**, **{dbl_}DirPort**, **{dbl_}DNSPort**, **{dbl_}ExtORPort**, **{dbl_}NATDPort**, **{dbl_}ORPort**, **{dbl_}SocksPort**, **{dbl_}TransPort**:: These underscore-prefixed options are variants of the regular Port options. They behave the same, except they are not saved to the torrc file by the controller's SAVECONF command.

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 16 Dec '19

16 Dec '19

commit e92533a3781f29a5d6121105de6d19af8b19d4f7 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Dec 16 23:25:39 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+es.po | 8 ++++---- contents+id.po | 27 ++++++++++++++------------- contents+ro.po | 10 +++++----- 3 files changed, 23 insertions(+), 22 deletions(-) diff --git a/contents+es.po b/contents+es.po index 0e383c9540..3b0f94bc2a 100644 --- a/contents+es.po +++ b/contents+es.po @@ -5,8 +5,8 @@ # erinm, 2019 # eulalio barbero espinosa <eulaliob(a)gmail.com>, 2019 # Nicolas Sera-Leyva <nseraleyva(a)internews.org>, 2019 -# Emma Peel, 2019 # Joaquín Serna <bubuanabelas(a)cryptolab.net>, 2019 +# Emma Peel, 2019 # msgid "" msgstr "" @@ -14,7 +14,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-11-14 16:04+CET\n" "PO-Revision-Date: 2018-10-02 22:41+0000\n" -"Last-Translator: Joaquín Serna <bubuanabelas(a)cryptolab.net>, 2019\n" +"Last-Translator: Emma Peel, 2019\n" "Language-Team: Spanish (https://www.transifex.com/otf/teams/1519/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -6706,8 +6706,8 @@ msgid "" "Compass is a web application to learn about currently running [Tor " "relays](#relay) in bulk." msgstr "" -"Compass es una aplicación web para aprender sobre la ejecución actual de " -"[relays de tor](#relay) a granel." +"Compass es una aplicación web para analizar en grupo los [repetidores de " +"tor](#relay) que hay en este momento." #: https//support.torproject.org/misc/glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) diff --git a/contents+id.po b/contents+id.po index 9abb74482a..b2306f70b7 100644 --- a/contents+id.po +++ b/contents+id.po @@ -4,9 +4,9 @@ # ical, 2019 # erinm, 2019 # Robert Dafis <robertdafis(a)gmail.com>, 2019 -# Emma Peel, 2019 # Joshua P, 2019 # cuna <cunaxc(a)gmail.com>, 2019 +# Emma Peel, 2019 # msgid "" msgstr "" @@ -14,7 +14,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-11-14 16:04+CET\n" "PO-Revision-Date: 2018-10-02 22:41+0000\n" -"Last-Translator: cuna <cunaxc(a)gmail.com>, 2019\n" +"Last-Translator: Emma Peel, 2019\n" "Language-Team: Indonesian (https://www.transifex.com/otf/teams/1519/id/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -372,7 +372,7 @@ msgid "" "and-challenges-ahead) on The Tor Blog all about it!" msgstr "" "Ingin mempelajari lebih lanjut tentang fingerprinting? Berikut ini adalah " -"[artikel] (https://blog.torproject.org/browser-fingerprinting-introduction-" +"[artikel](https://blog.torproject.org/browser-fingerprinting-introduction-" "and-challenges-ahead) didalam The Tor Blog all about it!" #: https//support.torproject.org/faq/faq-4/ @@ -393,10 +393,11 @@ msgid "" "easy.html.en#linux) and [macOS](https://www.torproject.org/download" "/download-easy.html.en#mac)." msgstr "" -"Tor Browser saat ini tersedia di [Windows] " -"(https://www.torproject.org/download/download-easy.html.en#windows) [Linux]" -" (https://www.torproject.org/download/download-easy.html.en#linux) dan " -"[macOS] (https://www.torproject.org/download/download-easy.html.en#mac)" +"Tor Browser saat ini tersedia di " +"[Windows](https://www.torproject.org/download/download-" +"easy.html.en#windows), [Linux] (https://www.torproject.org/download" +"/download-easy.html.en#linux) dan [macOS] " +"(https://www.torproject.org/download/download-easy.html.en#mac)" #: https//support.torproject.org/faq/faq-4/ #: (content/faq/faq-4/contents+en.lrquestion.description) @@ -409,9 +410,9 @@ msgid "" "[Orbot](https://play.google.com/store/apps/details?id=org.torproject.android)" " to route other apps on your Android device over the Tor network." msgstr "" -"Juga ada versi Tor Browser untuk [Android] " -"(https://www.torproject.org/download/#android) dan [The Guardian Project] " -"(https://guardianproject.info) juga menyediakan aplikasi [Orbot] ( " +"Juga ada versi Tor Browser untuk " +"[Android](https://www.torproject.org/download/#android) dan [The Guardian " +"Project](https://guardianproject.info) juga menyediakan aplikasi [Orbot]( " "https://play.google.com/store/apps/details?id=org.torproject.android) untuk " "merutekan aplikasi lain di perangkat Android Anda melalui jaringan Tor." @@ -424,7 +425,7 @@ msgid "" "Browser](https://onionbrowser.com)." msgstr "" "Belum ada versi resmi Tor untuk iOS sampai sekarang, namun kami " -"merekomendasikan [Onion Browser] (https://onionbrowser.com)" +"merekomendasikan [Onion Browser](https://onionbrowser.com)." #: https//support.torproject.org/faq/faq-5/ #: (content/faq/faq-5/contents+en.lrquestion.title) @@ -448,8 +449,8 @@ msgid "" "You can find more detailed information about Tor + VPN at [our " "wiki](https://trac.torproject.org/projects/tor/wiki/doc/TorPlusVPN)." msgstr "" -"Anda dapat menemukan informasi lebih rinci tentang Tor + VPN di [our wiki] " -"(https://trac.torproject.org/projects/tor/wiki/doc/TorPlusVPN)" +"Anda dapat menemukan informasi lebih rinci tentang Tor + VPN di [our " +"wiki](https://trac.torproject.org/projects/tor/wiki/doc/TorPlusVPN)." #: https//support.torproject.org/about/backdoor/ #: (content/about/backdoor/contents+en.lrquestion.title) diff --git a/contents+ro.po b/contents+ro.po index 094c3cdd24..6c3a205881 100644 --- a/contents+ro.po +++ b/contents+ro.po @@ -9538,8 +9538,8 @@ msgid "" "A list of all of our software projects can be found on our [projects " "page](https://www.torproject.org/projects/projects.html.en)." msgstr "" -"O listă cu toate proiectele noastre software poate fi găsită pe pagina " -"noastră de proiecte (https://www.torproject.org/projects/projects.html.en)" +"O listă cu toate proiectele noastre software poate fi găsită pe [pagina " +"noastră de proiecte](https://www.torproject.org/projects/projects.html.en)." #: https//support.torproject.org/misc/misc-8/ #: (content/misc/misc-8/contents+en.lrquestion.title) @@ -9710,8 +9710,8 @@ msgid "" "1. Log onto #tor. See [How can I chat with Tor Project teams?](/get-in-touch" "/irc-help/)" msgstr "" -"1. Conectați-vă pe #tor. Vedeți [Cum pot discuta cu echipele Proiectului Tor" -"?](/Get-in-touch/irc-help/)" +"1. Conectați-vă pe #tor. Vedeți [Cum pot discuta cu echipele Proiectului " +"Tor?](/ro/get-in-touch/irc-help/)" #: https//support.torproject.org/get-in-touch/why-i-cant-join-tor-channels/ #: (content/get-in-touch/why-i-cant-join-tor-channels/contents+en.lrquestion.description) @@ -10106,7 +10106,7 @@ msgstr "" #: https//support.torproject.org/apt/tor-ubuntu/ #: (content/apt/apt-2/contents+en.lrquestion.description) msgid "Please, use [Tor Debian repository](/apt/tor-deb-repo)." -msgstr "Vă rugăm să folosiți [Tor Debian repository](/apt/tor-deb-repo)." +msgstr "Vă rugăm să folosiți [Tor Debian repository](/ro/apt/tor-deb-repo)." #: https//support.torproject.org/apt/apt-over-tor/ #: (content/apt/apt-3/contents+en.lrquestion.title)

1 0

[translation/tails-misc_release] https://gitweb.torproject.org/translation.git/commit/?h=tails-misc_release
by translation＠torproject.org 16 Dec '19

16 Dec '19

commit d03cd70c74efb9314b47a72132e2bbb78518f20b Author: Translation commit bot <translation(a)torproject.org> Date: Mon Dec 16 23:19:44 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tails-misc_release --- pl.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl.po b/pl.po index badb350f3b..bca3b169ac 100644 --- a/pl.po +++ b/pl.po @@ -3,7 +3,7 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: -# Adam Stachowicz <saibamenppl(a)gmail.com>, 2015 +# Saibamen <saibamenppl(a)gmail.com>, 2015 # Aron <aron.plotnikowski(a)cryptolab.net>, 2014 # Dawid Job <hoek(a)tuta.io>, 2016-2017 # Dawid Job <hoek(a)tuta.io>, 2014

1 0

[translation/policies-code_of_conducttxtpot] https://gitweb.torproject.org/translation.git/commit/?h=policies-code_of_conducttxtpot
by translation＠torproject.org 16 Dec '19

16 Dec '19

commit f7480d67ae501a277a801421eaf1c87f7bf52bc0 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Dec 16 23:17:29 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=policies-code_of_co… --- code_of_conduct+de.po | 832 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 832 insertions(+) diff --git a/code_of_conduct+de.po b/code_of_conduct+de.po new file mode 100644 index 0000000000..5b095fd237 --- /dev/null +++ b/code_of_conduct+de.po @@ -0,0 +1,832 @@ +# Code of conduct of the tor project +# Copyright (C) 2019 tor project. +# This Code of Conduct is licensed under a Creative Commons CC-BY-SA 4.0 +# International license.e. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Martin Rey, 2019 +# Simon Kirchner <twistiosplayer(a)gmail.com>, 2019 +# Philipp Winter, 2019 +# Nicolas T <me(a)n-thumann.de>, 2019 +# Curtis Baltimore <curtisbaltimore(a)protonmail.com>, 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Code of conduct of the Tor Project\n" +"POT-Creation-Date: 2019-08-02 12:00+0000\n" +"PO-Revision-Date: 2019-08-27 18:54+0000\n" +"Last-Translator: Curtis Baltimore <curtisbaltimore(a)protonmail.com>, 2019\n" +"Language-Team: German (https://www.transifex.com/otf/teams/1519/de/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: de\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#. type: Plain text +#: ../code_of_conduct.txt:1 ../code_of_conduct.txt:24 +#: ../code_of_conduct.txt:51 ../code_of_conduct.txt:75 +#: ../code_of_conduct.txt:104 ../code_of_conduct.txt:180 +#: ../code_of_conduct.txt:193 ../code_of_conduct.txt:213 +#: ../code_of_conduct.txt:231 ../code_of_conduct.txt:243 +#: ../code_of_conduct.txt:253 ../code_of_conduct.txt:278 +#, no-wrap +msgid "============================================================\n" +msgstr "============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:3 +#, no-wrap +msgid "" +"Tor Project Code of Conduct\n" +"============================================================\n" +msgstr "" +"Tor Project Verhaltenscodex\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:6 +msgid "Statement of Intent:" +msgstr "Absichtserklärung" + +#. type: Plain text +#: ../code_of_conduct.txt:10 +msgid "" +"The Tor Project is committed to fostering an inclusive environment and " +"community. Tor is a place where people should feel safe to engage, share " +"their point of view, and participate." +msgstr "" +"Das Tor Project ist engagiert, eine einladende Umgebung und Gemeinschaft zu " +"pflegen. Tor ist ein Ort, wo alle sich sicher fühlen sollen sich zu " +"beteiligen, ihre Meinung zu äussern und mitzuwirken." + +#. type: Plain text +#: ../code_of_conduct.txt:15 +msgid "" +"This code of conduct applies to The Tor Project as a whole. It is intended " +"to provide guidelines for contributors. Employees and contractors of The Tor" +" Project, Inc. (TPI) are also subject to company policies and procedures. " +"Those people should feel free to contact HR with questions or concerns." +msgstr "" +"Dieser Verhaltenskodex gilt für das Tor-Projekt als Ganzes. Er bietet " +"Leitlinien für die Beitragenden. Mitarbeiter und Auftragnehmer von The Tor " +"Project, Inc. (TPI) unterliegen ebenfalls den Unternehmensrichtlinien und " +"-verfahren. Diese Personen dürfen sich gerne mit Fragen oder Anliegen an die" +" Personalabteilung wenden." + +#. type: Plain text +#: ../code_of_conduct.txt:23 +msgid "" +"This code of conduct is not exhaustive or complete. It is an ongoing effort " +"to summarize our shared understanding. We want to provide a welcoming, safe " +"environment, so we can work together to pursue powerful solutions. We " +"reserve the right to deviate from strictly enforcing this code. Any " +"deviations must produce an outcome which is fairer, and aligned with our " +"values. We understand that keeping a living document relevant and “patched” " +"involves sustained effort." +msgstr "" +"Dieser Verhaltenskodex ist nicht abschließend oder vollständig. Er ist ein " +"ständiges Bestreben, unser gemeinsames Verständnis zusammenzufassen. Wir " +"wollen eine einladende, sichere Umgebung schaffen, damit wir gemeinsam nach " +"leistungsstarken Lösungen suchen können. Wir behalten uns das Recht vor, von" +" der strikten Durchsetzung dieses Kodex abzuweichen. Abweichungen müssen zu " +"einem faireren und an unseren Werten orientierten Ergebnis führen. Wir " +"verstehen, dass es mit nachhaltigen Anstrengungen verbunden ist, ein " +"lebendes Dokument relevant und \"gepatcht\" zu halten." + +#. type: Plain text +#: ../code_of_conduct.txt:26 +#, no-wrap +msgid "" +"0. Summary: Don't be a jerk. Be awesome instead.\n" +"============================================================\n" +msgstr "" +"0. Zusammenfassung: Sei kein Dummkopf. Sei großartig stattdessen.\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:29 +msgid "The Tor community should be a good place where people are glad to be." +msgstr "" +"Die Tor-Community sollte ein guter Ort sein, an dem die Leute gerne sind." + +#. type: Plain text +#: ../code_of_conduct.txt:31 +#, no-wrap +msgid " DO: Be kind, thoughtful, and considerate.\n" +msgstr "" +" DO: Sei freundlich, aufmerksam und rücksichtsvoll.\n" +"\n" + +#. type: Plain text +#: ../code_of_conduct.txt:33 +#, no-wrap +msgid " DO: Make Tor a place where people are happy and comfortable.\n" +msgstr "" +" DO: Mache Tor zu einem Ort, an dem die Menschen glücklich und zufrieden " +"sind.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:36 +#, no-wrap +msgid "" +" DO: Remember: We are all contributing; we are all learning. Nobody was born\n" +" an expert.\n" +msgstr "" +" DO: Denke daran: Wir alle tragen dazu bei, wir alle lernen.\n" +"Niemand wurde als Experte geboren.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:38 +#, no-wrap +msgid " DO: Yield the floor. Listen. Make sure everyone gets heard.\n" +msgstr "" +" DO: Halte die Stellung. Hör zu. Sorg dafür, dass alle gehört werden.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:40 +#, no-wrap +msgid " DON'T: Insult, harass, intimidate, or be a jerk.\n" +msgstr "" +" DON'T: Beleidigen, belästigen, einschüchtern oder ein Dummkopf sein.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:43 +#, no-wrap +msgid "" +" DON'T: Treat honest mistakes as an excuse to hassle people. Mistakes are for\n" +" learning.\n" +msgstr "" +" DON'T: Behandle ehrliche Fehler als Vorwand, um Menschen zu belästigen.\n" +"Fehler sind zum Lernen da.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:46 +#, no-wrap +msgid "" +" DON'T: Hunt for ways to uphold the letter of this code while violating its\n" +" spirit.\n" +msgstr "" +" DON'T: Nach Möglichkeiten suchen, den Buchstaben dieses Codes " +"aufrechtzuerhalten und gleichzeitig gegen seinen Geist verstossen.\n" + +#. type: Plain text +#: ../code_of_conduct.txt:50 +#, no-wrap +msgid "" +" AND DO: Eagerly email: tor-community-council(a)lists.torproject.org with\n" +" questions or concerns. Public key:\n" +" https://trac.torproject.org/projects/tor/wiki/org/CommunityCouncil#Contact\n" +msgstr "" +" UND DO: Eifrig Fragen oder Sorgen an tor-community-council(a)lists.torproject.org e-mailen.\n" +"Öffentlicher Schlüssel:\n" +" https://trac.torproject.org/projects/tor/wiki/org/CommunityCouncil#Contact\n" + +#. type: Plain text +#: ../code_of_conduct.txt:53 +#, no-wrap +msgid "" +"1. Purpose\n" +"============================================================\n" +msgstr "" +"1. Zweck\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:63 +msgid "" +"A primary goal of the Tor community is to be inclusive of many different " +"contributors. We want to include contributors from the most varied and " +"diverse backgrounds possible. As such, we are committed to providing a " +"friendly, safe and welcoming environment for all, regardless of their " +"experience, gender identity or expression, sexual orientation, family, " +"relationships, ability (whether bodily or mental), personal appearance, " +"socioeconomic status, body size, race, ethnicity, age, religion, " +"nationality, or membership in a disadvantaged and/or underrepresented group." +msgstr "" +"Ein Hauptziel der Tor-Community ist es, viele verschiedene Mitwirkende " +"einzubeziehen. Wir wollen Mitwirkende aus den unterschiedlichsten und " +"vielfältigsten Bereichen einbeziehen. Daher sind wir bestrebt, ein " +"freundliches, sicheres und einladendes Umfeld für alle zu schaffen, " +"unabhängig von Erfahrung, geschlechtsspezifischer Identität oder Ausdruck, " +"sexueller Orientierung, Familie, Beziehungen, Fähigkeiten (ob körperlich " +"oder geistig), persönlichem Aussehen, sozioökonomischem Status, Körpergröße," +" Rasse, ethnischer Zugehörigkeit, Alter, Religion, Nationalität oder " +"Zugehörigkeit zu einer benachteiligten und/oder unterrepräsentierten Gruppe." + +#. type: Plain text +#: ../code_of_conduct.txt:68 +msgid "" +"A safe environment means one free from abuse, whether isolated or systemic. " +"We explicitly acknowledge that tolerating abuse is a security problem. " +"Allowing abusers and malicious people to disrupt our community puts our " +"software, developers, and users at risk." +msgstr "" +"Eine sichere Umgebung bedeutet, dass man frei von Missbrauch ist, sei es " +"isoliert oder systemisch. Wir erkennen ausdrücklich an, dass die Duldung von" +" Missbrauch ein Sicherheitsproblem ist. Zuzulassen dass Missbraucher und " +"böswillige Personen unsere Community stören, gefährdet unsere Software, " +"Entwickler und Benutzer." + +#. type: Plain text +#: ../code_of_conduct.txt:71 +msgid "" +"This code of conduct outlines our expectations for all those who participate" +" in our community, as well as the consequences for unacceptable behavior." +msgstr "" +"Dieser Verhaltenscodex beschreibt unsere Erwartungen an alle, die in unserer" +" Community mitwirken, sowie die Folgen für inakzeptables Verhalten." + +#. type: Plain text +#: ../code_of_conduct.txt:74 +msgid "" +"We invite all those who participate in The Tor Project to help us create " +"safe and positive experiences for everyone." +msgstr "" +"Wir laden alle, die am Tor-Projekt teilnehmen, ein uns zu helfen, sichere " +"und positive Erfahrungen für alle zu schaffen." + +#. type: Plain text +#: ../code_of_conduct.txt:77 +#, no-wrap +msgid "" +"2. Be your best self\n" +"============================================================\n" +msgstr "" +"2. Sei dein bestes Selbst\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:80 +msgid "" +"The following behaviors are expected and requested of all community members:" +msgstr "" +"Die folgenden Verhaltensweisen werden von allen Community-Mitgliedern " +"erwartet und gefordert:" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:83 +msgid "" +"Participate in an honest and active way. In doing so, you contribute to the " +"health and longevity of this community." +msgstr "" +"Nimm auf ehrliche und aktive Weise teil. Auf diese Weise trägst du zur " +"Gesundheit und Langlebigkeit dieser Community bei." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:85 +msgid "Exercise consideration and respect in your speech and actions." +msgstr "Übe Rücksicht und Respekt in deiner Rede und deinem Handeln." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:87 +msgid "Attempt collaboration and dialog before engaging in conflict." +msgstr "Versuchs mit Zusammenarbeit und Dialog, bevor es zu Konflikten kommt." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:89 +msgid "" +"Refrain from demeaning, discriminatory, or harassing behavior and speech." +msgstr "" +"Vermeide erniedrigende, diskriminierende oder belästigende Verhaltensweisen " +"und Reden." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:92 +msgid "" +"Be mindful of your surroundings and of your fellow participants. Alert " +"community leaders if you notice:" +msgstr "" +"Achte auf deine Umgebung und deine Mitstreiter. Warne die Community-Leiter, " +"wenn du Folgendes bemerkst:" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:94 +msgid "a dangerous situation" +msgstr "eine gefährliche Situation" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:96 +msgid "someone in distress" +msgstr "jemand in Not" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:98 +msgid "violations of this code of conduct, even if they seem minor" +msgstr "" +"Verstöße gegen diesen Verhaltenskodex, auch wenn sie geringfügig erscheinen" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:101 +msgid "" +"Remember that community event venues may be shared with members of the " +"public. Please be respectful to everyone using these locations." +msgstr "" +"Bedenke, dass die Veranstaltungsorte der Community mit der Öffentlichkeit " +"geteilt werden können. Bitte sei respektvoll gegenüber allen, die diese " +"Standorte nutzen." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:103 +msgid "Respect the privacy of your fellow community members." +msgstr "Respektiere die Privatsphäre deiner Community-Mitspieler." + +#. type: Plain text +#: ../code_of_conduct.txt:106 +#, no-wrap +msgid "" +"3. Unacceptable behaviors\n" +"============================================================\n" +msgstr "" +"3. Inakzeptables Verhalten\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:109 +msgid "The following behaviors are unacceptable within our community:" +msgstr "" +"Die folgenden Verhaltensweisen sind innerhalb unserer Community " +"inakzeptabel:" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:114 +msgid "" +"Violence, sexual assault, threats of violence, or violent language directed " +"against another person, especially violence against a person or group based " +"on a protected characteristic. (Display of weapons may constitute " +"intimidation or a threat of violence.)" +msgstr "" +"Gewalt, sexuelle Gewalt, Androhung von Gewalt oder gewalttätige Sprache " +"gegen eine andere Person, insbesondere Gewalt gegen eine Person oder Gruppe," +" die auf einem geschützten Merkmal beruht. (Das Zeigen von Waffen kann eine " +"Einschüchterung oder eine Androhung von Gewalt darstellen.)" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:117 +msgid "" +"Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory" +" jokes and language." +msgstr "" +"Sexistische, rassistische, homophobe, transphobe, ablehnende oder " +"anderweitig diskriminierende Witze und Formulierungen." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:122 +msgid "" +"Spontaneously posting or displaying sexually explicit or violent material. " +"(If it is necessary to share such material when working on Tor's mission, do" +" so with sensitivity. Be aware that many people don't want to see it.)" +msgstr "" +"Spontanes Posten oder Anzeigen von sexuell eindeutigem oder gewalttätigem " +"Material. (Wenn es notwendig ist, solches Material während der Arbeit an der" +" Mission von Tor zu teilen, tue dies mit Sorgfalt. Beachte dass viele Leute " +"es nicht sehen wollen.)" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:125 +msgid "" +"Posting or threatening to post other people’s personally identifying " +"information (\"doxing\") without their consent." +msgstr "" +"Veröffentlichen der personenbezogenen Daten anderer Personen ohne deren " +"Zustimmung oder die Drohung dazu (\"Doxing\")." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:127 +msgid "Personal insults or attacks, particularly those related to:" +msgstr "" +"Persönliche Beleidigungen oder Angriffe, insbesondere im Zusammenhang mit:" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:129 +msgid "experience" +msgstr "Erfahrung" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:131 +msgid "gender identity or expression" +msgstr "geschlechtsspezifische Identität oder Ausdrucksform" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:133 +msgid "sexual orientation" +msgstr "sexuelle Orientierung" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:135 +msgid "family" +msgstr "Familie" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:137 +msgid "relationships" +msgstr "Beziehungen" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:139 +msgid "ability (whether bodily or mental)" +msgstr "Fähigkeiten (ob körperlich oder geistig)" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:141 +msgid "personal appearance" +msgstr "persönliche Erscheinung" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:143 +msgid "socioeconomic status" +msgstr "sozioökonomischer Status" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:145 +msgid "body size" +msgstr "Körpergröße" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:147 +msgid "race" +msgstr "Rasse" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:149 +msgid "ethnicity" +msgstr "ethnische Zugehörigkeit" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:151 +msgid "age" +msgstr "Alter" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:153 +msgid "religion" +msgstr "Religion" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:155 +msgid "nationality" +msgstr "Nationalität" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:157 +msgid "membership in a disadvantaged and/or underrepresented group" +msgstr "" +"Zugehörigkeit zu einer benachteiligten und/oder unterrepräsentierten Gruppe" + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:161 +msgid "" +"Inappropriate photography, audio recording, or recording of personal " +"information. You should have someone's consent before recording these " +"things, and before posting them publicly." +msgstr "" +"Unzulässige Fotografie, Audioaufzeichnung oder Aufnahme von " +"personenbezogenen Daten. Du solltest die Zustimmung des Betreffenden " +"einholen, bevor du diese Dinge aufzeichnest und sie veröffentlichst." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:164 +msgid "" +"Inappropriate physical contact. You should have someone’s consent before " +"touching them." +msgstr "" +"Unangebrachter Körperkontakt. Du solltest die Zustimmung des Betreffenden " +"einholen, bevor du ihn berührst." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:167 +msgid "" +"Unwelcome sexual attention: this includes sexualized comments or jokes, " +"inappropriate touching, groping, and unwelcome sexual advances." +msgstr "" +"Unerwünschte sexuelle Aufmerksamkeit: Dazu gehören sexualisierte Kommentare " +"oder Witze, unangebrachtes Berühren, Tasten und unwillkommene sexuelle " +"Annäherungsversuche." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:169 +msgid "Deliberate intimidation, stalking or following (online or in person)." +msgstr "" +"Absichtliche Einschüchterung, Stalking oder Verfolgung (online oder " +"persönlich)." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:172 +msgid "" +"Deliberately undermining the spirit of this code while following the letter." +msgstr "" +"Den Geist dieses Kodex absichtlich zu untergraben, während man dem " +"Buchstaben folgt." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:175 +msgid "" +"Sustained disruption of any community events, including talks, " +"presentations, and online conversations." +msgstr "" +"Anhaltende Unterbrechung von Community-Veranstaltungen, einschließlich " +"Vorträgen, Präsentationen und Online-Gesprächen." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:177 +msgid "Deliberately pushing against someone's stated boundaries." +msgstr "Absichtliches Vorgehen gegen die angegebenen Grenzen von jemandem." + +#. type: Bullet: ' * ' +#: ../code_of_conduct.txt:179 +msgid "Advocating for, or encouraging, any of the above behavior." +msgstr "" +"Befürwortung oder Ermutigung eines der oben genannten Verhaltensweisen." + +#. type: Plain text +#: ../code_of_conduct.txt:182 +#, no-wrap +msgid "" +"4. Unacceptable behavior has consequences\n" +"============================================================\n" +msgstr "" +"4. Inakzeptables Verhalten hat Folgen\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:188 +msgid "" +"We will not tolerate unacceptable behavior from any community member. We " +"will not make exceptions for sponsors and those with decision-making " +"authority. People in formal or informal leadership roles must model the " +"highest standards of behavior." +msgstr "" +"Wir werden kein inakzeptables Verhalten von Community-Mitgliedern " +"tolerieren. Ausnahmen für Sponsoren und Entscheidungsträger werden nicht " +"gemacht. Menschen in formellen oder informellen Führungsrollen müssen " +"höchste Verhaltensstandards vorleben." + +#. type: Plain text +#: ../code_of_conduct.txt:192 +msgid "" +"Anyone asked by another community member to stop unacceptable behavior is " +"expected to comply immediately. Please don't step in on someone else's " +"behalf without their consent." +msgstr "" +"Von jedem, der von einem anderen Community-Mitglied aufgefordert wird, " +"inakzeptables Verhalten zu beenden, wird erwartet, dass er sich unverzüglich" +" daran hält. Bitte mische dich nicht in die Angelegenheiten einer anderen " +"Person ein ohne deren Zustimmung." + +#. type: Plain text +#: ../code_of_conduct.txt:195 +#, no-wrap +msgid "" +"5. Where to go for help\n" +"============================================================\n" +msgstr "" +"5. Wo kann man Hilfe bekommen?\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:201 +msgid "" +"The Community Council is an elected body of Tor Core Contributors who can " +"assist with intra-community conflict resolution. Community Council policies " +"and information can be found on the Community Council wiki [1]. You can " +"contact the whole Community council:" +msgstr "" +"Der Community-Rat ist ein gewähltes Gremium von Tor Core Contributors, das " +"bei der Lösung innergemeinschaftlicher Konflikte helfen kann. Die " +"Richtlinien und Informationen des Community-Rates findest du im Wiki des " +"Community-Rates[1]. Du kannst dich an den gesamten Community-Rat wenden:" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:203 +msgid "if you have questions or concerns about the code of conduct, or" +msgstr "wenn du Fragen oder Bedenken bezüglich des Verhaltenskodex hast, oder" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:205 +msgid "if you feel that you have witnessed a code of conduct violation" +msgstr "" +"wenn du das Gefühl hast, einen Verstoß gegen den Verhaltenskodex bemerkt zu " +"haben" + +#. type: Plain text +#: ../code_of_conduct.txt:212 +msgid "" +"However, if you feel that there is a conflict of interest with any council " +"member, you may contact members individually. Council members' GPG keys are " +"listed on the Community Council wiki. If there is a conflict of interest, " +"the affected council member will recuse themselves. They will not be " +"involved in any discussion or documentation of the incident. More about the " +"Community Council can be found in the guidelines [2]." +msgstr "" +"Wenn du jedoch der Meinung bist, dass es einen Interessenkonflikt mit einem " +"Ratsmitglied gibt, kannst du die Mitglieder einzeln kontaktieren. Die GPG-" +"Schlüssel der Ratsmitglieder sind im Community Rats-Wiki aufgelistet. Bei " +"einem Interessenkonflikt wird sich das betroffene Ratsmitglied selbst " +"zurückziehen. Es wird in keine Diskussion oder Dokumentation des Vorfalls " +"einbezogen. Mehr über den Community-Rat findest du in den Leitlinien[2]." + +#. type: Plain text +#: ../code_of_conduct.txt:215 +#, no-wrap +msgid "" +"6. What to do if you witness unacceptable behavior\n" +"============================================================\n" +msgstr "" +"6. Was tun, wenn du Zeuge eines inakzeptablen Verhaltens wirst?\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:230 +msgid "" +"If you are subject to or witness unacceptable behavior, or have any other " +"concerns, please notify the Community Council as soon as possible. You can " +"contact the community council in person, or at tor-community-" +"council(a)lists.torproject.org. Current councilmembers are listed on the wiki " +"[1]. The Community Council's incident response will vary on a case-by-case " +"basis. The council will make every effort to respond to the incident " +"immediately. The council will prioritize the safety of the person who has " +"been harmed, or is at risk of harm. Person(s) who have been harmed or are at" +" risk of harm can withdraw the incident report at any time. We will never do" +" anything without the consent of the person who has been harmed or is at " +"risk of harm, except in situations where there is a threat of imminent " +"danger or harm to anyone. More information about the Community Council's " +"incident reporting and response policies can be found on their wiki [1]." +msgstr "" +"Wenn du einem inakzeptablen Verhalten ausgesetzt bist, es miterlebt hast " +"oder andere Bedenken hast, benachrichtige bitte so schnell wie möglich den " +"Community-Rat. Du kannst den Community-Rat persönlich oder unter tor-" +"community-council(a)lists.torproject.org kontaktieren. Die aktuellen " +"Ratsmitglieder sind im Wiki[1] aufgeführt. Die Reaktion des Community-Rates " +"auf Vorfälle wird von Fall zu Fall unterschiedlich sein. Der Rat wird alle " +"Anstrengungen unternehmen, um auf den Vorfall unverzüglich zu reagieren. Der" +" Rat wird der Sicherheit der Person, die verletzt wurde oder von der Gefahr " +"eines Schadens bedroht ist, Priorität einräumen. Personen, die geschädigt " +"wurden oder von Schaden bedroht sind, können den Vorfallsbericht jederzeit " +"zurückziehen. Wir werden niemals etwas ohne die Zustimmung der Person tun, " +"die verletzt wurde oder von der Gefahr eines Schadens bedroht ist, außer in " +"Situationen, in denen eine unmittelbare Gefahr oder ein unmittelbarer " +"Schaden für irgendjemand sonst besteht. Weitere Informationen über die " +"Richtlinien des Community-Rates zur Meldung von Vorfällen und zur Reaktion " +"auf Vorfälle findest du in dessen Wiki[1]." + +#. type: Plain text +#: ../code_of_conduct.txt:233 +#, no-wrap +msgid "" +"7. What the person reporting a violation can expect\n" +"============================================================\n" +msgstr "" +"7. Was die Person, die einen Verstoß meldet, erwarten kann\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:242 +msgid "" +"The Community Council prioritizes the safety and well-being of any person " +"who feels that they have been harmed or may be in danger of being harmed. " +"Anyone reporting an issue to the Community Council can expect that their " +"report will be taken seriously. Initial reports can be taken in written or " +"verbal form. If the incident does not require an immediate resolution, then " +"a written report can be shared with the Community Council in an encrypted " +"format. The next steps in an incident response will vary on a case-by-case " +"basis." +msgstr "" +"Der Community-Rat legt den Schwerpunkt auf die Sicherheit und das " +"Wohlergehen jeder Person, die sich verletzt fühlt oder Gefahr läuft, " +"verletzt zu werden. Jeder, der dem Community-Rat über einen Sachverhalt " +"berichtet, kann erwarten, dass sein Bericht ernst genommen wird. Erste " +"Berichte können in schriftlicher oder mündlicher Form erstellt werden. " +"Erfordert der Vorfall keine sofortige Lösung, so kann dem Community-Rat ein " +"schriftlicher Bericht in verschlüsselter Form übermittelt werden. Die " +"nächsten Schritte bei der Reaktion auf einen Vorfall werden von Fall zu Fall" +" unterschiedlich sein." + +#. type: Plain text +#: ../code_of_conduct.txt:245 +#, no-wrap +msgid "" +"8. How the Community Council responds to incidents\n" +"============================================================\n" +msgstr "" +"8. Wie der Community-Rat auf Vorfälle reagiert\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:252 +msgid "" +"If a community member engages in unacceptable behavior, the Community " +"Council may take any action they deem appropriate, including but not limited" +" to a warning, informal mediation, temporary ban or permanent expulsion from" +" the community. Any actions and decisions by the Community Council may be " +"appealed by following the appeals process in the Community Council " +"Guidelines [1]." +msgstr "" +"Wenn ein Mitglied der Community ein inakzeptables Verhalten an den Tag legt," +" kann der Community-Rat alle Maßnahmen ergreifen, die er für angemessen " +"hält, einschließlich, aber nicht beschränkt auf eine Verwarnung, eine " +"informelle Vermittlung, ein vorübergehendes Verbot oder eine dauerhafte " +"Ausweisung aus der Community. Gegen Handlungen und Entscheidungen des " +"Community-Rates kann Beschwerde eingelegt werden, indem man dem " +"Beschwerdeverfahren in den Leitlinien des Community-Rates[1] folgt." + +#. type: Plain text +#: ../code_of_conduct.txt:255 +#, no-wrap +msgid "" +"9. Scope of this document\n" +"============================================================\n" +msgstr "" +"9. Umfang dieses Dokuments\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:258 +msgid "This code of conduct covers all community participants:" +msgstr "Dieser Verhaltenskodex gilt für alle Teilnehmer der Community:" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:260 +msgid "paid and unpaid contributors" +msgstr "bezahlte und unbezahlte Mitwirkende" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:262 +msgid "sponsors" +msgstr "Sponsoren" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:264 +msgid "other guests" +msgstr "andere Gäste" + +#. type: Plain text +#: ../code_of_conduct.txt:266 +msgid "when interacting:" +msgstr "bei der Kommunikation:" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:268 +msgid "in all online and in-person community venues" +msgstr "in allen Online- und persönlichen Community-Veranstaltungen" + +#. type: Bullet: ' - ' +#: ../code_of_conduct.txt:270 +msgid "in one-on-one communications that relate to community work" +msgstr "in der Einzelkommunikation, die sich auf die Community-Arbeit bezieht" + +#. type: Plain text +#: ../code_of_conduct.txt:277 +msgid "" +"This code of conduct and its related procedures also applies to unacceptable" +" behavior occurring outside the scope of community activities when such " +"behavior has the potential to adversely affect the safety and well-being of " +"community members. As members of the Tor community, we support and follow " +"this Code while we are working on Tor, and take care not to undermine it in " +"the rest of our time." +msgstr "" +"Dieser Verhaltenskodex und die damit verbundenen Verfahren gelten auch für " +"inakzeptables Verhalten außerhalb der Aktivitäten der Community, wenn dieses" +" Verhalten das Potenzial hat, die Sicherheit und das Wohlbefinden der " +"Community-Mitglieder zu beeinträchtigen. Als Mitglieder der Tor-Community " +"unterstützen und befolgen wir diesen Code, während wir an Tor arbeiten, und " +"achten darauf, ihn in der restlichen Zeit nicht zu untergraben." + +#. type: Plain text +#: ../code_of_conduct.txt:280 +#, no-wrap +msgid "" +"10. License and attribution\n" +"============================================================\n" +msgstr "" +"10. Lizenz und Zuschreibung\n" +"============================================================\n" + +#. type: Plain text +#: ../code_of_conduct.txt:284 +msgid "" +"This code of conduct is shared under a Creative Commons CC-BY-SA 4.0 " +"International license." +msgstr "" +"Dieser Verhaltenskodex wird unter einer Creative Commons CC-BY-SA 4.0 " +"International Lizenz geteilt." + +#. type: Plain text +#: ../code_of_conduct.txt:287 +msgid "" +"This code of conduct uses some language and framing from the Citizen Code of" +" Conduct, which is shared under a CC-BY-SA license: citizencodeofconduct.org" +msgstr "" +"Dieser Verhaltenskodex verwendet einige Formulierungen und Auszüge aus dem " +"Citizen Code of Conduct, der unter einer CC-BY-SA-Lizenz geteilt wird: " +"citizencodeofconduct.org" + +#. type: Plain text +#: ../code_of_conduct.txt:289 +msgid "" +"[1] https://trac.torproject.org/projects/tor/wiki/org/CommunityCouncil [2] " +"https://gitweb.torproject.org/community/policies.git/tree/community_council…" +msgstr "" +"[1] https://trac.torproject.org/projects/tor/wiki/org/CommunityCouncil [2] " +"https://gitweb.torproject.org/community/policies.git/tree/community_council…"

1 0

[translation/communitytpo-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot
by translation＠torproject.org 16 Dec '19

16 Dec '19

commit 749587c11c458ecb1de2209a0476921793001d31 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Dec 16 23:15:44 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-conten… --- contents+it.po | 94 ++++- contents+ka.po | 70 +++- contents+pt-PT.po | 14 +- contents+ro.po | 1166 ++++++++++++++++++++++++++++++++++++++++++++--------- 4 files changed, 1125 insertions(+), 219 deletions(-) diff --git a/contents+it.po b/contents+it.po index bcef0cdc23..74a5c37211 100644 --- a/contents+it.po +++ b/contents+it.po @@ -12,6 +12,7 @@ # Luke <94lukecatellani(a)gmail.com>, 2019 # Davide Sant <spuuu(a)outlook.it>, 2019 # Emma Peel, 2019 +# giulio marino <iulio.marino(a)gmail.com>, 2019 # msgid "" msgstr "" @@ -19,7 +20,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-12-11 12:15+CET\n" "PO-Revision-Date: 2019-12-11 10:50+0000\n" -"Last-Translator: Emma Peel, 2019\n" +"Last-Translator: giulio marino <iulio.marino(a)gmail.com>, 2019\n" "Language-Team: Italian (https://www.transifex.com/otf/teams/1519/it/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -34,28 +35,37 @@ msgstr "Unisciti alla Community di Tor" #: https//community.torproject.org/ (content/contents+en.lrpage.subtitle) msgid "Our community is made up of human rights defenders around the world." msgstr "" +"La nostra Community è costituita da difensori di diritti civili da tutte le " +"parti del mondo." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "The Tor community is made up of all kinds of contributors." -msgstr "" +msgstr "La Community di Tor è costituita da collaboratori di ogni genere." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" "Some people write documentation and bug reports, while others hold Tor " "events and conduct outreach." msgstr "" +"Alcuni scrivono la documentazione e riportano i bug, altri si concentrano " +"sugli eventi di Tor e sulla sensibilizzazione" #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" "Whether you have a lot of time to volunteer or a little, and whether you " "consider yourself technical or not, we want you to join our community, too." msgstr "" +"Hai molto tempo da dedicare al volontariato? Ne hai poco? Hai competenze " +"tecniche o non ne hai? In ogni caso, desideriamo che ti unisca alla nostra " +"Community." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" "Below you'll find some different ways to volunteer with the Tor community as" " well as resources to help you help Tor." msgstr "" +"Qui sotto troverai vari modi per collaborare con la Community di Tor e " +"risorse che ti aiuteranno ad aiutare Tor." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.title) @@ -68,21 +78,23 @@ msgid "" "Relays are the backbone of the Tor network. Help make Tor stronger and " "faster by running a relay today." msgstr "" +"I relè sono la spina dorsale della rete Tor. Aiuta Tor ad essere più potente" +" e veloce facendo funzionare un Relay oggi stesso." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.cta) msgid "Grow the Tor network" -msgstr "" +msgstr "Fai crescere la rete Tor" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "The Tor network relies on volunteers to donate bandwidth." -msgstr "" +msgstr "La rete Tor si fonda sulla larghezza di banda donata da volontari." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "The more people who run relays, the better the Tor network will be." -msgstr "" +msgstr "Più persone fanno girare relè, meglio funzionerà la rete Tor." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -91,31 +103,36 @@ msgid "" "need to use Tor, which means we need more dedicated volunteers like you to " "run relays." msgstr "" +"La rete Tor di oggi è piuttosto piccola rispetto al numero di persone che ne" +" hanno bisogno: questo significa che abbiamo di più volontari come te che si" +" dedichino a far girare relè." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "By running a Tor relay you can help make the Tor network:" -msgstr "" +msgstr "Facendo girare un relè di Tor puoi aiutare a rendere la rete Tor:" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* faster (and therefore more usable)" -msgstr "" +msgstr "* più veloce (e quindi più funzionale)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more robust against attacks" -msgstr "" +msgstr "* più resistente agli attacchi" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more stable in case of outages" -msgstr "" +msgstr "* più stabile in caso di interruzioni" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* safer for its users (spying on more relays is harder than on a few)" msgstr "" +"* più sicura per i suoi utenti (spiare su più relè è più difficile che su un" +" numero inferiore)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -123,6 +140,9 @@ msgid "" "Running a relay requires technical skill and commitment, which is why we've " "created a wealth of resources to help our relay operators." msgstr "" +"Far girare un relè richiede competenze tecniche e impegno: questo è il " +"motivo per cui abbiamo creato molte risorse per aiutare i nostri gestori di " +"relè" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.title) @@ -135,17 +155,17 @@ msgstr "" #: (content/training/resources/contents+en.lrpage.subtitle) msgid "" "Do you teach your community about using Tor? These resources are for you." -msgstr "" +msgstr "Insegni alla Community come usare Tor? Queste risorse sono per te" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.cta) msgid "Check our resources" -msgstr "" +msgstr "Consulta le nostre risorse" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) msgid "## We want to teach the world about Tor. Can you help?" -msgstr "" +msgstr "## Vogliamo insegnare al mondo riguardo Tor. Puoi aiutare?" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -153,6 +173,9 @@ msgid "" "Are you a Tor trainer or interested in becoming one? Looking for resources " "to help your community learn the most about Tor? We've got you covered." msgstr "" +"Sei un istruttore di Tor o interessato a diventarlo? Stai cercando risorse " +"per aiutare la tua Community a saperne di più su Tor? Abbiamo quel che ti " +"serve." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -160,6 +183,8 @@ msgid "" "For some users with serious threat models, teaching Tor and other privacy " "tools can be risky if not done with care." msgstr "" +"Per alcuni utenti con seri modelli di minaccia, insegnare Tor e altri " +"strumenti di privacy può essere rischioso se si è attenti." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -168,6 +193,10 @@ msgid "" " Community Team](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-" "community-team) for more help." msgstr "" +"Se questo è un problema connesso alla tua community, o se non ne sei sicuro," +" per favore [contatta il nostro Community Team] " +"(https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team) " +"per avere un aiuto." #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.title) @@ -180,16 +209,18 @@ msgid "" "Onion services help you and your users defeat surveillance and censorship. " "Learn how you can deploy onion services." msgstr "" +"I servizi Onion aiutano te e i tuoi utenti a sconfiggere il controllo e la " +"censura. Impara come puoi impiegare i servizi Onion." #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.cta) msgid "Grow your .onion" -msgstr "" +msgstr "Sviluppa i tuoi .onion" #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.body) msgid "##What are Onion Services?" -msgstr "" +msgstr "##Che cosa sono i servizi Onion?" #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.body) @@ -198,11 +229,14 @@ msgid "" "onion service gives your users all the security of HTTPS with the added " "privacy benefits of Tor Browser." msgstr "" +"I servizi Onion sono servizi accessibili solo attraverso Tor. Avere un " +"servizio onion offre ai tuoi utenti tutta la sicurezza dell'HTTPS con in più" +" i benefici di privacy della rete Tor." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.title) msgid "Localization" -msgstr "" +msgstr "Localizzazione" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.subtitle) @@ -210,16 +244,19 @@ msgid "" "We want Tor to work for everyone in the world, which means our software must" " be translated into a lot of languages." msgstr "" +"Vogliamo che Tor funzioni per chiunque nel mondo, per cui il nostro software" +" deve essere tradotto in molte lingue" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.cta) msgid "Help us translate" -msgstr "" +msgstr "Aiutaci a tradurre" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) msgid "##Localization is how we reach a global community." msgstr "" +"##La localizzazione è il modo in cui raggiungiamo un Community globale" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -227,6 +264,8 @@ msgid "" "In order for Tor to work for everyone, it needs to speak everyone's " "languages." msgstr "" +"Per far sì che Tor funzioni per tutti, deve poter parlare le lingue di " +"tutti." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -234,6 +273,8 @@ msgid "" "Our volunteer translation team works hard to make this a reality, and we can" " always use more help." msgstr "" +"Il nostro team di traduttori lavora duramente per realizzare questo " +"risultato, e ogni ulteriore aiuto è sempre benvenuto." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -243,26 +284,30 @@ msgid "" " Project website](https://torpat.ch/tpo-locales), but there are many other " "documents that we could use help translating as well." msgstr "" +"Le nostra priorità sono tradurre [il Browser Tor], " +"(https://torpat.ch/locales) la documentazione del Browser Tor, e il [sito " +"del Progetto Tor](https://torpat.ch/tpo-locales), ma ci sono molti altri " +"documenti da tradurre." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.title) msgid "Outreach" -msgstr "" +msgstr "Presenza" #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.subtitle) msgid "Bring Tor materials to your next community event." -msgstr "" +msgstr "Porta materiali di Tor ai prossimi eventi della tua community." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.cta) msgid "Tell the world about Tor" -msgstr "" +msgstr "Parla al mondo di Tor." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) msgid "##Tell the world about Tor" -msgstr "" +msgstr "##Diffondi il verbo di Tor nel mondo" #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) @@ -270,6 +315,8 @@ msgid "" "We love it when people bring information about Tor to their community " "events, conferences, and meetups." msgstr "" +"Siamo entusiasti quando le persone diffondono le informazioni su Tor agli " +"eventi, conferenze e incontri delle proprie community." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) @@ -277,6 +324,8 @@ msgid "" "We've curated some beautiful materials for sharing in-person and on social " "media we welcome you to use." msgstr "" +"Abbiamo curato del buon materiale da condividere di persona e sui social " +"media: è a vostra disposizione" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.title) @@ -289,6 +338,8 @@ msgid "" "How to install and configure each type of relay: bridge, guard, middle, and " "exit." msgstr "" +"Come installare e configurare ogni tipo di relè: bridge, guard, middle ed " +"exit." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -296,6 +347,9 @@ msgid "" "This section covers the installation and configuration of the program " "required to run a Tor relay for various operating systems." msgstr "" +"Questa sezione tratta dell'installazione e della configurazione del " +"programma richiesto per far funzionare un relè Tor sui vari sistemi " +"operativi." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) diff --git a/contents+ka.po b/contents+ka.po index 65a3d61397..d0933aac43 100644 --- a/contents+ka.po +++ b/contents+ka.po @@ -79,11 +79,15 @@ msgstr "გააფართოვეთ Tor-ქსელი" #: (content/relay-operations/contents+en.lrpage.body) msgid "The Tor network relies on volunteers to donate bandwidth." msgstr "" +"Tor-ქსელი დამოკიდებულია მოხალისეებზე, რომლებიც სწირავენ თავიანთ " +"გამტარუნარიანობას." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "The more people who run relays, the better the Tor network will be." msgstr "" +"რაც უფრო მეტი ადამიანი გაუშვებს გადამცემს, მით უფრო უკეთ იმუშავებს Tor-" +"ქსელი." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -92,31 +96,36 @@ msgid "" "need to use Tor, which means we need more dedicated volunteers like you to " "run relays." msgstr "" +"ამჟამინდელი Tor-ქსელი იმაზე გაცილებით მცირეა, ვიდრე Tor-ით სარგებლობის " +"მსურველებს ესაჭიროებათ, ეს კი ნიშნავს რომ თქვენნაირი ცალკეული მოხალისეების " +"დახმარება გადამცემების გასაშვებად, ჩვენთვის მეტად მნიშვნელოვანია." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "By running a Tor relay you can help make the Tor network:" -msgstr "" +msgstr "Tor-ის გადამცემის გაშვებით, დაგვეხმარებით რომ გავხადოთ Tor-ქსელი:" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* faster (and therefore more usable)" -msgstr "" +msgstr "* სწრაფი (შესაბამისად მეტად გამოსადეგი)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more robust against attacks" -msgstr "" +msgstr "* მეტად მტკიცე, შეტევების წინააღმდეგ" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more stable in case of outages" -msgstr "" +msgstr "* მეტად მდგრადი შეფერხებებისგან" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* safer for its users (spying on more relays is harder than on a few)" msgstr "" +"* მეტად უსაფრთხო, მომხმარებლებისთვის (თვალთვალი ბევრ გადამცემზე გაცილებით " +"რთულია)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -124,6 +133,9 @@ msgid "" "Running a relay requires technical skill and commitment, which is why we've " "created a wealth of resources to help our relay operators." msgstr "" +"გადამცემის გაშვება საჭიროებს ტექნიკურ უნარებსა და პასუხისმგებლობას, სწორედ " +"ამიტომ შევქმენით მდიდარი მასალა, ჩვენი გადამცემების მუშაობის " +"უზრუნველმყოფთათვის." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.title) @@ -371,13 +383,15 @@ msgstr "" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "# Questions you should clarify before configuring Tor" -msgstr "" +msgstr "# საკითხები, რომლებზეც უნდა შეჯერდეთ, სანამ გამართავთ Tor-ს" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* Do you want to run a Tor exit or non-exit (bridge/guard/middle) relay?" msgstr "" +"* Tor-ის გამავალი თუ არაგამავალი (ხიდი/მცველი/შუალედური) გადამცემის გაშვება " +"გსურთ?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -385,17 +399,20 @@ msgid "" "* If you want to run an exit relay: Which ports do you want to allow in your" " exit policy?" msgstr "" +"* თუ გსურთ გაუშვათ გამავალი გადამცემი: რომელი პორტები იქნება დაშვებული " +"გამსვლელი დებულებით?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "(More ports usually means potentially more abuse complaints.)" -msgstr "" +msgstr "(მეტი პორტი ჩვეულებრივ გულისხმობს მეტ საჩივარს დარღვევებზე)" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* What external TCP port do you want to use for incoming Tor connections?" msgstr "" +"* რომელი გარეშე TCP-პორტის გამოყენება გსურთ შემომავალი Tor-კავშირებისთვის?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -403,6 +420,8 @@ msgid "" "(\"ORPort\" configuration: We recommend port 443 if that is not used by " "another daemon on your server already." msgstr "" +"(„ORPort“ გამართვა: ჩვენ გირჩევთ 443 პორტს, თუ მას სხვა პროცესი არ იყენებს " +"თქვენს სერვერზე." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -410,33 +429,39 @@ msgid "" "ORPort 443 is recommended because it is often one of the few open ports on " "public WIFI networks." msgstr "" +"ORPort 443 სასურველია იმიტომ, რომ იგი ჩვეულებრივ ერთ-ერთია, მცირე რაოდენობის" +" ღია პორტებს შორის საჯარო WIFI-ქსელებზე." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "Port 9001 is another commonly used ORPort.)" -msgstr "" +msgstr "9001 პორტი კიდევ ერთი გავრცელებული ORPort არის.)" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* What email address will you use in the ContactInfo field of your relay(s)?" msgstr "" +"* ელფოსტის რომელ მისამართს მიუთითებთ საკონტაქტო ველში თქვენი " +"გადამცემ(ებ)ისთვის?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "This information will be made public." -msgstr "" +msgstr "ეს მონაცემი საჯაროდ ხილული იქნება." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* How much bandwidth/monthly traffic do you want to allow for Tor traffic?" msgstr "" +"* რა სიდიდის გამტარუნარიანობა/თვეში მიმოცვლილი მონაცემები გსურთ დაუთმოთ Tor-" +"ის კავშირებს?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "* Does the server have an IPv6 address?" -msgstr "" +msgstr "* გააჩნია აღნიშნულ სერვერს IPv6-მისამართი?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -444,6 +469,8 @@ msgid "" "The installation commands are shown in code blocks and must be executed with" " root privileges." msgstr "" +"დასაყენებელი ბრძანებები მოცემულია კოდის ნაწილებად და უნდა გაეშვას ძირეული " +"უფლებებით." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -451,6 +478,9 @@ msgid "" "Click below in which type of relay do you want to host and don't forget to " "read [Relay post-install and good practices](/relay/setup/post-install/)." msgstr "" +"დაწკაპეთ ქვემოთ, თუ რომელი სახის გადამცემი გსურთ ამუშაოთ და არ დაგავიწყდეთ " +"გადაიკითხოთ [გადამცემის დაყენების შემდგომი და სხვა სასარგებლო " +"რჩევები](/relay/setup/post-install/)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.title) @@ -463,6 +493,9 @@ msgid "" "Requirements for Tor relays depend on the type of relay and the bandwidth " "they provide. Learn more about specific relay requirements." msgstr "" +"Tor-გადამცემების მოთხოვნები დამოკიდებულია გადამცემის სახეობასა და " +"გამტარუნარიანობაზე, რომელსაც უნდა იძლეოდეს. ვრცლად, გადამცემის შესაბამისი " +"საჭიროებების შესახებ." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -470,6 +503,8 @@ msgid "" "Requirements for Tor relays depend on the type of relay and the bandwidth " "they provide." msgstr "" +"Tor-გადამცემების მოთხოვნები დამოკიდებულია გადამცემის სახეობასა და " +"გამტარუნარიანობაზე, რომელსაც უნდა იძლეოდეს." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -482,6 +517,8 @@ msgid "" "A non-exit relay should be able to handle at least 7000 concurrent " "connections." msgstr "" +"არაგამავალ გადამცემს, უნდა შეეძლოს ერთბაშად სულ მცირე 7000 კავშირის " +"უზრუნველყოფა." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -489,6 +526,9 @@ msgid "" "This can overwhelm consumer-level routers. If you run the Tor relay from a " "server (virtual or dedicated) in a data center you will be fine." msgstr "" +"ამან შესაძლოა ზედმეტად დატვირთოს სამომხმარებლო დონის როუტერები. თუ Tor-" +"გადამცემს სერვერიდან უშვებთ (ვირტუალური თუ გამოყოფილი) რომელიც მონაცემთა " +"ცენტრშია, მაშინ ყველაფერი რიგზე იქნება." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -496,6 +536,9 @@ msgid "" "If you run it behind a consumer-level router at home you will have to try " "and see if your home router can handle it or if it starts failing." msgstr "" +"თუ მას უშვებთ სამომხმარებლო დონის როუტერის გავლით სახლიდან, მაშინ ჯერ უნდა " +"სცადოთ და დააკვირდეთ, შეუძლია სახლის როუტერს ამ დატვირთვის დაძლევა თუ ეწყება" +" ჩავარდნები." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -503,6 +546,8 @@ msgid "" "Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent" " connections (>100k)." msgstr "" +"სწრაფი გამსვლელი გადამცემები (>=100 მბიტ/წმ) ჩვეულებრივ საჭიროებს გაცილებით " +"მეტი კავშირის ერთბაშად უზრუნველყოფას (>100k)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -511,6 +556,9 @@ msgid "" "bandwidth and 16 Mbit/s (Mbps) download bandwidth available for Tor. More is" " better." msgstr "" +"სასურველია, რომ გადამცემს გააჩნდეს სულ მცირე 16 მბიტ/წმ (მეგაბიტ-წამი) " +"ატვირთვის გამტარუნარიანობა და 16 მბიტ/წმ (მეგაბიტ-წამი) ჩამოტვირთვის " +"გამტარუნარიანობა ხელმისაწვდომი Tor-ისთვის. მეტი უკეთესია." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -523,6 +571,8 @@ msgid "" "If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a" " [bridge with obfs4 support](relay/setup/bridge)." msgstr "" +"თუ თქვენი გამტარუნარიანობა 10 მბიტ/წმ-ზე ნაკლებია, მაგრამ 1 მბიტ/წმ-ზე " +"მეტია, გირჩევთ გაუშვათ [ხიდი obfs4-ის მხარდაჭერით](relay/setup/bridge)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -530,6 +580,8 @@ msgid "" "If you do not know your bandwidth you can use http://beta.speedtest.net to " "measure it." msgstr "" +"თუ არ იცით თქვენი გამტარუნარიანობა, შეგიძლიათ გამოიყენოთ " +"http://beta.speedtest.net მის გასაზომად." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) diff --git a/contents+pt-PT.po b/contents+pt-PT.po index 454aa9858c..b033c57ac3 100644 --- a/contents+pt-PT.po +++ b/contents+pt-PT.po @@ -3,9 +3,9 @@ # erinm, 2019 # Hugo9191 <hugoncosta(a)gmail.com>, 2019 # Rui <xymarior(a)yandex.com>, 2019 -# A Russo <quisquiliarum2001-habitica(a)yahoo.co.uk>, 2019 # Manuela Silva <inactive+h_manuela_rodsilva(a)transifex.com>, 2019 # Manuela Silva <manuelarodsilva(a)gmail.com>, 2019 +# A Russo <quisquiliarum2001-habitica(a)yahoo.co.uk>, 2019 # msgid "" msgstr "" @@ -13,7 +13,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-12-11 12:15+CET\n" "PO-Revision-Date: 2019-12-11 10:50+0000\n" -"Last-Translator: Manuela Silva <manuelarodsilva(a)gmail.com>, 2019\n" +"Last-Translator: A Russo <quisquiliarum2001-habitica(a)yahoo.co.uk>, 2019\n" "Language-Team: Portuguese (Portugal) (https://www.transifex.com/otf/teams/1519/pt_PT/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -23,27 +23,33 @@ msgstr "" #: https//community.torproject.org/ (content/contents+en.lrpage.title) msgid "Join the Tor Community" -msgstr "" +msgstr "Junte-se à Comunidade Tor" #: https//community.torproject.org/ (content/contents+en.lrpage.subtitle) msgid "Our community is made up of human rights defenders around the world." msgstr "" +"A nossa comunidade é composta de defensores de direitos humanos por todo o " +"mundo." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "The Tor community is made up of all kinds of contributors." -msgstr "" +msgstr "A comunidade Tor possui todo o tipo de contribuidores." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" "Some people write documentation and bug reports, while others hold Tor " "events and conduct outreach." msgstr "" +"Algumas pessoas escrevem documentação, enquanto outros organizam eventos Tor" +" e trabalham em divulgação." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" "Whether you have a lot of time to volunteer or a little, and whether you " "consider yourself technical or not, we want you to join our community, too." msgstr "" +"Quer tenha muito ou pouco tempo para realizar voluntariado, e quer pense que" +" é muito ou pouco técnico, queremos que também se junte à nossa comunidade." #: https//community.torproject.org/ (content/contents+en.lrpage.body) msgid "" diff --git a/contents+ro.po b/contents+ro.po index 173fa3ca59..14920e06d9 100644 --- a/contents+ro.po +++ b/contents+ro.po @@ -81,12 +81,14 @@ msgstr "Creșteți rețeaua Tor" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "The Tor network relies on volunteers to donate bandwidth." -msgstr "" +msgstr "Rețeaua Tor se bazează pe voluntari care donează lățime de bandă." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "The more people who run relays, the better the Tor network will be." msgstr "" +"Cu cât sunt mai mulți oameni care rulează relee, cu atât rețeaua Tor va " +"funcționa mai bine." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -95,31 +97,36 @@ msgid "" "need to use Tor, which means we need more dedicated volunteers like you to " "run relays." msgstr "" +"Rețeaua Tor actuală este destul de mică în comparație cu numărul de oameni " +"care trebuie să utilizeze Tor, ceea ce înseamnă că avem nevoie de mai mulți " +"voluntari dedicați ca tine pentru a rula relee." #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "By running a Tor relay you can help make the Tor network:" -msgstr "" +msgstr "Prin rularea unui releu Tor, puteți ajuta la crearea rețelei Tor:" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* faster (and therefore more usable)" -msgstr "" +msgstr "* mai rapidă (și, prin urmare, mai utilizabilă)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more robust against attacks" -msgstr "" +msgstr "* mai robustă împotriva atacurilor" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* more stable in case of outages" -msgstr "" +msgstr "* mai stabilă în cazul întreruperilor" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) msgid "* safer for its users (spying on more relays is harder than on a few)" msgstr "" +"* mai sigură pentru utilizatorii săi (spionarea este mai dificilă atunci " +"când sunt mai multe relee)" #: https//community.torproject.org/relay/ #: (content/relay-operations/contents+en.lrpage.body) @@ -127,11 +134,14 @@ msgid "" "Running a relay requires technical skill and commitment, which is why we've " "created a wealth of resources to help our relay operators." msgstr "" +"Rularea unui releu necesită abilitate tehnică și angajament, motiv pentru " +"care am creat o multitudine de resurse pentru a ajuta operatorii noștri de " +"relee." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.title) msgid "Training" -msgstr "" +msgstr "Instruire" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.subtitle) @@ -140,16 +150,18 @@ msgstr "" msgid "" "Do you teach your community about using Tor? These resources are for you." msgstr "" +"Ați informat comunitatea dvs. despre utilizarea Tor? Aceste resurse sunt " +"pentru dumneavoastră." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.cta) msgid "Check our resources" -msgstr "" +msgstr "Verificați resursele noastre" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) msgid "## We want to teach the world about Tor. Can you help?" -msgstr "" +msgstr "## Vrem să informăm lumea despre Tor. Puteți să ne ajutați?" #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -157,6 +169,9 @@ msgid "" "Are you a Tor trainer or interested in becoming one? Looking for resources " "to help your community learn the most about Tor? We've got you covered." msgstr "" +"Sunteți un antrenor Tor sau sunteți interesat să deveniți unul? Căutați " +"resurse care să ajute comunitatea dvs. să învețe mai multe despre Tor? Aici " +"găsiți informațiile necesare." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -164,6 +179,9 @@ msgid "" "For some users with serious threat models, teaching Tor and other privacy " "tools can be risky if not done with care." msgstr "" +"Pentru unii utilizatori cu modele grave de amenințare, informațiile despre " +"Tor și alte instrumente de confidențialitate pot fi riscante, dacă nu sunt " +"făcute cu grijă." #: https//community.torproject.org/training/ #: (content/training/contents+en.lrpage.body) @@ -172,6 +190,10 @@ msgid "" " Community Team](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-" "community-team) for more help." msgstr "" +"Dacă acest lucru descrie comunitatea dvs. sau dacă nu sunteți sigur, vă " +"rugăm [contactați echipa noastră - Community Team] " +"(https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team) " +"pentru mai multe informații." #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.title) @@ -184,16 +206,18 @@ msgid "" "Onion services help you and your users defeat surveillance and censorship. " "Learn how you can deploy onion services." msgstr "" +"Serviciile Onion vă ajută pe dvs. și pe utilizatori să eliminați " +"supravegherea și cenzura. Aflați cum puteți implementa serviciile Onion." #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.cta) msgid "Grow your .onion" -msgstr "" +msgstr "Îmbunătățiți .onion" #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.body) msgid "##What are Onion Services?" -msgstr "" +msgstr "##Ce sunt serviciile Onion?" #: https//community.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrpage.body) @@ -202,11 +226,14 @@ msgid "" "onion service gives your users all the security of HTTPS with the added " "privacy benefits of Tor Browser." msgstr "" +"Serviciile Onion sunt servicii care pot fi accesate doar prin Tor. Rularea " +"unui serviciu Onion oferă utilizatorilor toată securitatea HTTPS cu " +"beneficiile adăugate de confidențialitate ale Tor Browser." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.title) msgid "Localization" -msgstr "" +msgstr "Localizare" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.subtitle) @@ -214,16 +241,18 @@ msgid "" "We want Tor to work for everyone in the world, which means our software must" " be translated into a lot of languages." msgstr "" +"Dorim ca Tor să lucreze pentru toată lumea, ceea ce înseamnă că software-ul " +"nostru trebuie tradus într-o multitudine de limbi." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.cta) msgid "Help us translate" -msgstr "" +msgstr "Ajutați-ne la traducere" #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) msgid "##Localization is how we reach a global community." -msgstr "" +msgstr "##Localizarea este modul în care ajungem la o comunitate globală." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -231,6 +260,8 @@ msgid "" "In order for Tor to work for everyone, it needs to speak everyone's " "languages." msgstr "" +"Pentru ca Tor să funcționeze pentru toți, trebuie să fie tradus în limbile " +"tuturor." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -238,6 +269,8 @@ msgid "" "Our volunteer translation team works hard to make this a reality, and we can" " always use more help." msgstr "" +"Echipa noastră de traducători voluntari lucrează din greu pentru a aduce " +"acest lucru la realitate și întotdeauna putem folosi mai mult ajutor." #: https//community.torproject.org/localization/ #: (content/localization/contents+en.lrpage.body) @@ -247,26 +280,30 @@ msgid "" " Project website](https://torpat.ch/tpo-locales), but there are many other " "documents that we could use help translating as well." msgstr "" +"Prioritățile noastre de traducere curente sunt traducerea [Tor Browser] " +"(https://torpat.ch/locales) documentația Tor Browser și [site-ul Tor " +"Project] (https://torpat.ch/tpo-locales) dar există multe alte documente la" +" care ne-ar putea folosi traducerea." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.title) msgid "Outreach" -msgstr "" +msgstr "Mobilizare" #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.subtitle) msgid "Bring Tor materials to your next community event." -msgstr "" +msgstr "Aduceți materiale Tor la următorul dvs. eveniment comunitar." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.cta) msgid "Tell the world about Tor" -msgstr "" +msgstr "Informați lumea despre Tor" #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) msgid "##Tell the world about Tor" -msgstr "" +msgstr "##Informați lumea despre Tor" #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) @@ -274,6 +311,8 @@ msgid "" "We love it when people bring information about Tor to their community " "events, conferences, and meetups." msgstr "" +"Ne place când oamenii aduc informații despre Tor la evenimentele, " +"conferințele și întâlnirile comunității lor." #: https//community.torproject.org/outreach/ #: (content/outreach/contents+en.lrpage.body) @@ -281,11 +320,13 @@ msgid "" "We've curated some beautiful materials for sharing in-person and on social " "media we welcome you to use." msgstr "" +"Am realizat câteva materiale frumoase pentru partajarea personală și pe " +"social media pe care vă rugăm să le utilizați." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.title) msgid "Technical Setup" -msgstr "" +msgstr "Configurare tehnică" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.subtitle) @@ -293,6 +334,8 @@ msgid "" "How to install and configure each type of relay: bridge, guard, middle, and " "exit." msgstr "" +"Cum se instalează și se configurează fiecare tip de releu: punte, pază, " +"mijloc și ieșire." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -300,6 +343,8 @@ msgid "" "This section covers the installation and configuration of the program " "required to run a Tor relay for various operating systems." msgstr "" +"Această secțiune descrie instalarea și configurarea programului necesar " +"pentru a rula un releu Tor pe diferite sisteme de operare." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -307,6 +352,8 @@ msgid "" "These steps are intended for the latest stable version of the given OS, on " "Ubuntu for the latest LTS release." msgstr "" +"Acești pași sunt valabili pentru cea mai recentă versiune stabilă a " +"sistemului de operare dat, în Ubuntu pentru cea mai recentă versiune LTS." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -314,6 +361,9 @@ msgid "" "Note: For some operating systems, there are alpha version packages available" " (Tor versions with new features not deemed to be stable yet)." msgstr "" +"Notă: Pentru unele sisteme de operare, există pachete de versiuni alfa " +"disponibile (versiunile Tor cu funcții noi care nu sunt considerate încă " +"stabile)." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -321,6 +371,8 @@ msgid "" "These are only recommended for people eager to test and report bugs in " "bleeding edge releases/features." msgstr "" +"Acestea sunt recomandate numai persoanelor dornice să testeze și să " +"raporteze erori în versiunile / caracteristicile instabile." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -328,17 +380,22 @@ msgid "" "If you are looking to run a relay with minimal effort, we recommend you " "stick to stable releases." msgstr "" +"Dacă doriți să rulați un releu cu efort minim, vă recomandăm să rămâneți la " +"versiunile stabile." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "# Questions you should clarify before configuring Tor" msgstr "" +"# Întrebări pe care ar trebui să le clarificați înainte de a configura Tor" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* Do you want to run a Tor exit or non-exit (bridge/guard/middle) relay?" msgstr "" +"* Doriți să rulați un releu de ieșire Tor sau de non-ieșire (punte / pază / " +"mijloc)?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -346,17 +403,22 @@ msgid "" "* If you want to run an exit relay: Which ports do you want to allow in your" " exit policy?" msgstr "" +"* Dacă doriți să rulați un releu de ieșire: Ce porturi doriți să folosiți în" +" politica de ieșire?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "(More ports usually means potentially more abuse complaints.)" msgstr "" +"(De obicei, mai multe porturi înseamnă mai multe posibile reclamații de " +"abuz.)" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* What external TCP port do you want to use for incoming Tor connections?" msgstr "" +"* Ce port TCP extern doriți să utilizați pentru conexiunile Tor primite?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -364,6 +426,8 @@ msgid "" "(\"ORPort\" configuration: We recommend port 443 if that is not used by " "another daemon on your server already." msgstr "" +"(Configurație \"ORPort\": Recomandăm portul 443 dacă acesta nu este deja " +"folosit de un alt demon de pe serverul dvs." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -371,33 +435,38 @@ msgid "" "ORPort 443 is recommended because it is often one of the few open ports on " "public WIFI networks." msgstr "" +"Este recomandat ORPort 443, deoarece acesta este deseori unul dintre " +"puținele porturi deschise din rețelele publice WIFI." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "Port 9001 is another commonly used ORPort.)" -msgstr "" +msgstr "Portul 9001 este un alt ORPort utilizat frecvent.)" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* What email address will you use in the ContactInfo field of your relay(s)?" msgstr "" +"* Ce adresă de e-mail veți utiliza în câmpul ContactInfo al releului " +"(releurilor) dvs.?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "This information will be made public." -msgstr "" +msgstr "Aceste informații vor fi făcute publice." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "" "* How much bandwidth/monthly traffic do you want to allow for Tor traffic?" msgstr "" +"* Câtă lățime de bandă / trafic lunar doriți să permiteți traficul Tor?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) msgid "* Does the server have an IPv6 address?" -msgstr "" +msgstr "* Serverul are o adresă IPv6?" #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -405,6 +474,8 @@ msgid "" "The installation commands are shown in code blocks and must be executed with" " root privileges." msgstr "" +"Comenzile de instalare sunt afișate în blocuri de cod și trebuie executate " +"cu privilegii de administrator." #: https//community.torproject.org/relay/setup/ #: (content/relay-operations/technical-setup/contents+en.lrpage.body) @@ -412,11 +483,14 @@ msgid "" "Click below in which type of relay do you want to host and don't forget to " "read [Relay post-install and good practices](/relay/setup/post-install/)." msgstr "" +"Faceți clic mai jos pentru a alege ce tip de releu doriți să găzduiți și nu " +"uitați să citiți [Post-instalare relee și bune practici] (/relay/setup/post-" +"install/)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.title) msgid "Relay requirements" -msgstr "" +msgstr "Cerințe pentru releu" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.subtitle) @@ -424,6 +498,9 @@ msgid "" "Requirements for Tor relays depend on the type of relay and the bandwidth " "they provide. Learn more about specific relay requirements." msgstr "" +"Cerințele pentru releele Tor depind de tipul releului și de lățimea de bandă" +" pe care le furnizează. Aflați mai multe despre cerințele specifice ale " +"releelor." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -431,11 +508,13 @@ msgid "" "Requirements for Tor relays depend on the type of relay and the bandwidth " "they provide." msgstr "" +"Cerințele pentru releele Tor depind de tipul releului și de lățimea de bandă" +" pe care le furnizează." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Bandwidth and Connections" -msgstr "" +msgstr "# Lățime de bandă și conexiuni" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -443,6 +522,8 @@ msgid "" "A non-exit relay should be able to handle at least 7000 concurrent " "connections." msgstr "" +"Un releu fără ieșire ar trebui să poată gestiona cel puțin 7000 de conexiuni" +" concomitente." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -450,6 +531,9 @@ msgid "" "This can overwhelm consumer-level routers. If you run the Tor relay from a " "server (virtual or dedicated) in a data center you will be fine." msgstr "" +"Acest lucru poate copleși routerele la nivel de consumator. Dacă rulați " +"releul Tor de pe un server (virtual sau dedicat) într-un centru de date va " +"fi bine." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -457,6 +541,9 @@ msgid "" "If you run it behind a consumer-level router at home you will have to try " "and see if your home router can handle it or if it starts failing." msgstr "" +"Dacă îl rulați în spatele unui router la nivel de consumator acasă, va " +"trebui să încercați să vedeți dacă routerul dvs. de acasă îl poate gestiona " +"sau dacă eșuează." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -464,6 +551,8 @@ msgid "" "Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent" " connections (>100k)." msgstr "" +"Releele de ieșire rapidă (>=100Mbit/s) trebuie să gestioneze conexiuni mult " +"mai concurente (>100k)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -472,11 +561,14 @@ msgid "" "bandwidth and 16 Mbit/s (Mbps) download bandwidth available for Tor. More is" " better." msgstr "" +"Se recomandă ca un releu să aibă cel puțin 16 Mbit/s (Mbps) lățime de bandă " +"și 16 Mbit/s (Mbps) lățime de bandă disponibile pentru Tor. Mai mult e mai " +"bine." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "The minimum requirements for a relay are 10 Mbit/s (Mbps)." -msgstr "" +msgstr "Cerințele minime pentru un releu sunt 10 Mbit / s (Mbps)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -484,6 +576,8 @@ msgid "" "If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a" " [bridge with obfs4 support](relay/setup/bridge)." msgstr "" +"Dacă aveți mai puțin de 10 Mbit/s, dar cel puțin 1 Mbit/s, vă recomandăm să " +"rulați o [punte cu suport obfs4] (relay/setup/bridge)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -491,11 +585,13 @@ msgid "" "If you do not know your bandwidth you can use http://beta.speedtest.net to " "measure it." msgstr "" +"Dacă nu cunoașteți lățimea de bandă, puteți utiliza " +"http://beta.speedtest.net pentru a o măsura." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Monthly Outbound Traffic" -msgstr "" +msgstr "# Trafic lunar de ieșire" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -503,6 +599,9 @@ msgid "" "It is required that a Tor relay be allowed to use a minimum of 100 GByte of " "outbound traffic (and the same amount of incoming traffic) per month." msgstr "" +"Este necesar ca unui releu Tor să i se permită să utilizeze minimum 100 " +"GByte de trafic de ieșire (și aceeași cantitate de trafic de intrare) pe " +"lună." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -510,11 +609,13 @@ msgid "" "Note: That is only about 1 day worth of traffic on a 10 Mbit/s (Mbps) " "connection." msgstr "" +"Notă: Aceasta înseamnă aproximativ doar 1 zi de trafic pe o conexiune de 10 " +"Mbit/s (Mbps)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "More (>2 TB/month) is better and recommended." -msgstr "" +msgstr "Mai mult (>2 TB/lună) este mai bun și recomandat." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -522,6 +623,8 @@ msgid "" "**Ideally a relay runs on an unmetered plan** or includes 2 TB/month or " "more." msgstr "" +"** În mod ideal, un releu funcționează pe un plan neschimbat ** sau include " +"2 TB/lună sau mai mult." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -529,11 +632,14 @@ msgid "" "If you have a metered plan you might want to configure tor to only use a " "given amount of [bandwidth or monthly traffic](/relay/setup/post-install/)." msgstr "" +"Dacă aveți un plan contorizat, poate doriți să configurați Tor pentru a " +"utiliza doar o anumită cantitate de [lățime de bandă sau trafic lunar] " +"(/relay/setup/post-install/)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Public IPv4 Address" -msgstr "" +msgstr "# Adresa publică IPv4" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -541,6 +647,8 @@ msgid "" "Every relay needs a public IPv4 address - either directly on the host " "(preferred) or via NAT and port forwarding." msgstr "" +"Fiecare releu are nevoie de o adresă publică IPv4 - fie direct pe gazdă (de " +"preferat), fie prin NAT și prin redirecționarea porturilor." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -548,6 +656,8 @@ msgid "" "The IPv4 address is not required to be static but static IP addresses are " "preferred." msgstr "" +"Adresa IPv4 nu trebuie neapărat să fie statică, dar se preferă adresele IP " +"statice." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -557,6 +667,11 @@ msgid "" " relay or bridge there since it takes time to distribute the new list of " "relay IPs to clients - which happens only once every hour)." msgstr "" +"Adresa dvs. IPv4 ar trebui să rămână neschimbată timp de cel puțin 3 ore " +"(dacă se schimbă în mod regulat mai des decât atât, nu are prea mult sens să" +" rulați un releu sau o punte acolo, deoarece necesită timp pentru a " +"distribui noua listă de IP-uri releu către clienți - care se întâmplă o dată" +" la fiecare oră)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -564,6 +679,8 @@ msgid "" "Additional IPv6 connectivity is great and recommended/encouraged but not a " "requirement." msgstr "" +"Conectivitatea suplimentară IPv6 este excelentă și recomandată / încurajată," +" dar nu este obligatorie." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -571,50 +688,61 @@ msgid "" "There should be no problem at all with this requirement (all commercially " "available servers come with at least one IPv4 address)." msgstr "" +"Nu ar trebui să existe nicio problemă despre această cerință (toate " +"serverele disponibile în comerț au cel puțin o adresă IPv4)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "Note: You can only run two Tor relays per public IPv4 address." msgstr "" +"Notă: Puteți rula doar două relee Tor pentru fiecare adresă IPv4 publică." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "" "If you want to run more than two relays you will need more IPv4 addresses." msgstr "" +"Dacă doriți să rulați mai mult de două relee, veți avea nevoie de mai multe " +"adrese IPv4." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Memory Requirements" -msgstr "" +msgstr "# Cerințe pentru memorie" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "" "* A <40 Mbit/s non-exit relay should have at least 512 MB of RAM available." msgstr "" +"* Un releu de ieșire <40 Mbit/s ar trebui să aibă cel puțin 512 MB RAM " +"disponibil." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "" "* A non-exit relay faster than 40 Mbit/s should have at least 1 GB of RAM." msgstr "" +"* Un releu fără ieșire mai rapid de 40 Mbit/s ar trebui să aibă cel puțin 1 " +"GB RAM." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "" "* On an exit relay we recommend at least 1.5 GB of RAM per tor instance." msgstr "" +"* La un releu de ieșire, vă recomandăm cel puțin 1,5 GB RAM pentru fiecare " +"instanță Tor." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Disk Storage" -msgstr "" +msgstr "# Depozitare pe disc" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "Tor does not need much disk storage." -msgstr "" +msgstr "Tor nu are nevoie de multă stocare pe disc." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -622,16 +750,18 @@ msgid "" "A typical Tor relay needs less than 200 MB for Tor related data (in addition" " to the operating system itself)." msgstr "" +"Un releu Tor obișnuit are nevoie de mai puțin de 200 MB pentru datele " +"referitoare la Tor (în plus față de sistemul de operare în sine)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# CPU" -msgstr "" +msgstr "# CPU" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "* Any modern CPU should be fine." -msgstr "" +msgstr "* Orice procesor modern ar trebui să fie bun." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -640,6 +770,9 @@ msgid "" "performance and allow for up to about ~400-450 Mbps in each direction on a " "single tor instance on modern CPUs)." msgstr "" +"* Se recomandă utilizarea procesoarelor cu suport AESNI (care va îmbunătăți " +"performanța și va permite până la aproximativ ~ 400-450 Mbps în fiecare " +"direcție pentru o singură instanță Tor pe procesoare moderne)." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -647,11 +780,13 @@ msgid "" "If the file /proc/cpuinfo contains the word aes your CPU has support for " "AES-NI." msgstr "" +"Dacă fișierul /proc/cpuinfo conține cuvântul aes, procesorul dvs. are suport" +" pentru AES-NI." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Uptime" -msgstr "" +msgstr "# Timpul de funcționare" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -659,21 +794,25 @@ msgid "" "Tor has no hard uptime requirement but if your relay is not running for more" " than 2 hours a day its usefulness is limited." msgstr "" +"Tor nu are cerințe de utilizare dificilă, dar dacă releul dvs. nu " +"funcționează mai mult de 2 ore pe zi, utilitatea sa este limitată." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "Ideally the relay runs on a server which runs 24/7." -msgstr "" +msgstr "În mod ideal, releul rulează pe un server care rulează 24/7." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "Reboots and tor daemon restarts are fine." msgstr "" +"Pot fi realizate reporniri ale sistemului de operare și reporniri ale daemon" +" Tor." #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) msgid "# Tor Version" -msgstr "" +msgstr "# Versiunea Tor" #: https//community.torproject.org/relay/relays-requirements/ #: (content/relay-operations/relays-requirements/contents+en.lrpage.body) @@ -683,11 +822,15 @@ msgid "" " insecure. Relays that attempt to downgrade to an insecure version will be " "rejected from the network automatically." msgstr "" +"Din motive de securitate, releele Tor nu ar trebui să-și downgradeze " +"versiunea tor de la o versiune compatibilă la una neacceptată. Unele " +"versiuni neacceptate sunt nesigure. Releurile care încearcă să treacă la o " +"versiune nesigură vor fi respinse automat din rețea." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.title) msgid "Types of relays on the Tor network" -msgstr "" +msgstr "Tipuri de relee din rețeaua Tor" #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.subtitle) @@ -695,6 +838,9 @@ msgid "" "Bridges, guards, middle relays, and exits all serve important functions in " "the Tor network. Learn about the different relays you can run." msgstr "" +"Toate punțile, paza, releele de mijloc și de ieșire servesc funcții " +"importante în rețeaua Tor. Aflați mai multe despre diferitele relee pe care " +"le puteți rula." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -702,6 +848,8 @@ msgid "" "All nodes are important, but they have different technical requirements and " "legal implications." msgstr "" +"Toate nodurile sunt importante, dar au cerințe tehnice și implicații legale " +"diferite." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -709,16 +857,18 @@ msgid "" "Understanding the different kinds of nodes is the first step to learning " "which one is right for you." msgstr "" +"Înțelegerea diferitelor tipuri de noduri este primul pas pentru a afla care " +"vă este potrivită." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "# Guard and middle relay" -msgstr "" +msgstr "# Releu de pază și mijloc" #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "(also known as non-exit relays)" -msgstr "" +msgstr "(cunoscut și sub numele de releu fără ieșire)" #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -726,6 +876,8 @@ msgid "" "A guard relay is the first relay in the chain of 3 relays building a Tor " "circuit." msgstr "" +"Un releu de pază este primul releu din lanțul de 3 relee care construiește " +"un circuit Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -733,6 +885,8 @@ msgid "" "A middle relay is neither a guard nor an exit, but acts as the second hop " "between the two." msgstr "" +"Un releu de mijloc nu este nici releu paznic, nici releu de ieșire, dar " +"acționează ca al doilea salt între cele două." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -740,11 +894,14 @@ msgid "" "To become a guard, a relay has to be stable and fast (at least 2MByte/s) " "otherwise it will remain a middle relay." msgstr "" +"Pentru a deveni releu paznic, un releu trebuie să fie stabil și rapid (cel " +"puțin 2MByte/s), altfel va rămâne un releu de mijloc." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "Guard and middle relays usually do not receive abuse complaints." msgstr "" +"De obicei, releele de pază și de mijloc nu primesc reclamații de abuz." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -753,6 +910,9 @@ msgid "" "blocked by certain services that don't understand how Tor works or " "deliberately want to censor Tor users." msgstr "" +"Toate releele vor fi listate în lista publică de relee Tor, deci pot fi " +"blocate de anumite servicii care nu înțeleg cum funcționează Tor sau doresc " +"intenționat să cenzureze utilizatorii Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -761,6 +921,9 @@ msgid "" " consider running a bridge instead so that your non-Tor traffic doesn't get " "blocked as though it's coming from Tor." msgstr "" +"Dacă rulați un releu de acasă și aveți un singur IP static, poate doriți să " +"luați în considerare rularea unei punți, astfel încât traficul dvs. non-Tor " +"să nu fie blocat ca și cum ar veni din Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -768,6 +931,8 @@ msgid "" "If you have a dynamic IP address or multiple static IPs, this isn't as much " "of an issue." msgstr "" +"Dacă aveți o adresă IP dinamică sau mai multe IP statice, aceasta nu este o " +"problemă." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -776,6 +941,9 @@ msgid "" "usage can be highly customized in the tor configuration (will be covered in " "more detail later in this guide)." msgstr "" +"Un releu Tor fără ieșire necesită eforturi minime de întreținere, iar " +"utilizarea lățimii de bandă poate fi foarte personalizată în configurația " +"Tor (va fi descrisă detaliat mai târziu în acest ghid)." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -783,16 +951,18 @@ msgid "" "The so called \"exit policy\" of the relay decides if it is a relay allowing" " clients to exit or not." msgstr "" +"Așa-numita „politică de ieșire” a releului decide dacă este un releu care " +"permite clienților să iasă sau nu." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "A non-exit relay does not allow exiting in its exit policy." -msgstr "" +msgstr "Un releu fără ieșire nu permite ieșirea prin politica sa de ieșire." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "# Exit relay" -msgstr "" +msgstr "# Releu de ieșire" #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -800,6 +970,8 @@ msgid "" "The exit relay is the final relay in a Tor circuit, the one that sends " "traffic out its destination." msgstr "" +"Releul de ieșire este releul final dintr-un circuit Tor, cel care trimite " +"traficul la destinație." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -808,6 +980,9 @@ msgid "" "provider, etc) will see the IP address of the exit relay instead of their " "real IP address of the Tor user." msgstr "" +"Serviciile pe care le conectează clienții Tor (site-ul web, serviciul de " +"chat, furnizorul de email etc.) vor vedea adresa IP a releului de ieșire în " +"loc de adresa reală a utilizatorului Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -815,6 +990,8 @@ msgid "" "Exit relays have the greatest legal exposure and liability of all the " "relays." msgstr "" +"Dintre toate releele, releele de ieșire au cea mai mare expunere și " +"răspundere legală." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -824,6 +1001,11 @@ msgid "" "notice](https://www.dmca.com/Solutions/view.aspx?ID=712f28a5-93f2-467b-" "ba92-3d58c8345a32&?ref=sol08a2)." msgstr "" +"De exemplu, dacă un utilizator descarcă materiale protejate prin drepturi de" +" autor în timpul utilizării releului dvs. de ieșire, operatorul poate primi " +"o [notificare " +"DMCA](https://www.dmca.com/Solutions/view.aspx?ID=712f28a5-93f2-467b-" +"ba92-3d58c8345a32&?ref=sol08a2)." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -831,6 +1013,8 @@ msgid "" "Any abuse complaints about the exit will go directly to you (via your " "hoster, depending on the WHOIS records)." msgstr "" +"Orice reclamații despre abuz în legătură cu ieșirea se vor adresa direct " +"dvs. (prin intermediul gazdei dvs., în funcție de înregistrările WHOIS)." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -838,6 +1022,9 @@ msgid "" "Generally, most complaints can be handled pretty easily through template " "letters, which we'll discuss more in legal considerations section." msgstr "" +"În general, cele mai multe reclamații pot fi tratate destul de ușor prin " +"șabloane de scrisori, despre care vom discuta mai mult în secțiunea de " +"considerente legale." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -845,6 +1032,8 @@ msgid "" "Because of the legal exposure that comes with running an exit relay, you " "should not run a Tor exit relay from your home." msgstr "" +"Din cauza expunerii legale care vine cu rularea unui releu de ieșire, nu ar " +"trebui să rulați un releu de ieșire Tor de acasă." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -852,6 +1041,9 @@ msgid "" "Ideal exit relay operators are affiliated with some institution, like a " "university, a library, a hackerspace or a privacy related organization." msgstr "" +"Operatorii de relee de ieșire ideale sunt afiliați cu o instituție, cum ar " +"fi o universitate, o bibliotecă, un spațiu hacker sau o organizație legată " +"de confidențialitate." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -860,6 +1052,9 @@ msgid "" "better positioned to handle abuse complaints or the rare law enforcement " "inquiry." msgstr "" +"O instituție nu numai că oferă o lățime de bandă mai mare pentru ieșire, dar" +" este mai bine poziționată pentru a gestiona plângerile de abuzuri sau " +"posibilele anchete de aplicare a legii." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -867,11 +1062,14 @@ msgid "" "If you are considering running an exit relay, please read the [section on " "legal considerations](/relay/community-resources) for exit relay operators." msgstr "" +"Dacă vă gândiți să rulați un releu de ieșire, citiți [secțiunea cu " +"considerente legale] (/relay/community-resources) pentru operatorii de relee" +" de ieșire." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) msgid "# Bridge" -msgstr "" +msgstr "# Punte" #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -879,6 +1077,7 @@ msgid "" "The design of the Tor network means that the IP address of Tor relays is " "public." msgstr "" +"Proiectarea rețelei Tor înseamnă că adresa IP a releelor Tor este publică." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -886,6 +1085,9 @@ msgid "" "However, one of the ways Tor can be blocked by governments or ISPs is by " "blacklisting the IP addresses of these public Tor nodes." msgstr "" +"Cu toate acestea, unul dintre modurile în care Tor poate fi blocat de " +"guverne sau ISP-uri este prin lista neagră a adreselor IP ale acestor noduri" +" publice Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -893,6 +1095,8 @@ msgid "" "Tor bridges are nodes in the network that are not listed in the public Tor " "directory, which make it harder for ISPs and governments to block them." msgstr "" +"Punțile Tor sunt noduri din rețea care nu sunt listate în directorul public " +"Tor, fapt care îngreunează blocarea lor de către ISP-uri și guverne." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -901,6 +1105,10 @@ msgid "" "want an extra layer of security because they're worried somebody will " "recognize that they are contacting a public Tor relay IP address." msgstr "" +"Punțile sunt utile pentru utilizatorii Tor în regimuri opresive sau pentru " +"persoanele care doresc un nivel suplimentar de securitate, deoarece își fac " +"griji că cineva va recunoaște că ei contactează o adresă publică a releului " +"Tor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -918,6 +1126,9 @@ msgid "" "transports.html.en), a special kind of bridge, address this by adding an " "additional layer of obfuscation." msgstr "" +"[Transporturile conectabile](https://2019.www.torproject.org/docs/pluggable-" +"transports.html.en),un tip special de punte, abordează acest lucru adăugând " +"un strat suplimentar de confuzie." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -925,6 +1136,8 @@ msgid "" "Bridges are relatively easy, low-risk and low bandwidth Tor nodes to " "operate, but they have a big impact on users." msgstr "" +"Punțile sunt relativ ușor de utilizat, cu risc redus în utilizarea nodurilor" +" Tor cu lățime mică de bandă, dar au un impact mare asupra utilizatorilor." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -933,6 +1146,9 @@ msgid "" " not listed in the public consensus, they are unlikely to be blocked by " "popular services." msgstr "" +"O punte nu poate primi nicio reclamație de abuz și, deoarece podurile nu " +"sunt enumerate în consensul public, este puțin probabil să fie blocate de " +"serviciile populare." #: https//community.torproject.org/relay/types-of-relays/ #: (content/relay-operations/types-of-relays/contents+en.lrpage.body) @@ -941,11 +1157,15 @@ msgid "" "network, have only one static IP, and don't have a huge amount of bandwidth " "to donate -- we recommend giving your bridge at least 1 Mbit/sec." msgstr "" +"Punțile sunt o opțiune excelentă dacă puteți rula un nod Tor din rețeaua de " +"domiciliu, aveți un singur IP static și nu aveți o cantitate imensă de " +"lățime de bandă de donat - vă recomandăm să oferiți punții dvs. cel puțin 1 " +"Mbit/sec." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.title) msgid "Community and legal resources" -msgstr "" +msgstr "Resurse comunitare și legale" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.subtitle) @@ -954,11 +1174,14 @@ msgid "" "responding to abuse complaints, and how to start an organization dedicated " "to relay operation." msgstr "" +"Cum să vă implicați în comunitatea operatorilor de relee Tor, sfaturi despre" +" răspunsul la reclamațiile de abuz și cum să porniți o organizație dedicată " +"funcționării releului." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "# Legal resources" -msgstr "" +msgstr "# Resurse legale" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -966,6 +1189,8 @@ msgid "" "Exit relay operators should understand the potential risks associated with " "running an exit relay." msgstr "" +"Operatorii releelor de ieșire ar trebui să înțeleagă riscurile potențiale " +"asociate cu rularea unui releu de ieșire." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -973,6 +1198,8 @@ msgid "" "For the majority of operators in most countries, bridges and guard/middle " "relays are very low risk." msgstr "" +"Pentru majoritatea operatorilor din majoritatea țărilor, podurile și releele" +" de pază / mijloc sunt cu risc foarte scăzut." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -983,6 +1210,11 @@ msgid "" " reading through some of the legal resources that Tor-supportive lawyers " "have put together." msgstr "" +"Ieșirile sunt cele care prezintă anumite probleme legale, dar, în cele mai " +"multe circumstanțe, operatorii vor putea să se ocupe de problemele legale, " +"având o scrisoare de răspuns la abuz, efectuând ieșirea dintr-o locație care" +" nu este casa lor și citând unele dintre resursele legale, oferite de " +"avocații care susțin Tor." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -993,6 +1225,11 @@ msgid "" "wiki](https://www.noisebridge.net/wiki/Noisebridge_Tor/FBI) for additional " "legal resources." msgstr "" +"[Întrebările frecvente EFF Tor Legal] (/relay/community-resources/eff-tor-" +"legal-faq) răspund la multe întrebări comune despre funcționarea releului și" +" legalitate. De asemenea, ne place [wiki-ul lui Noisebridge] " +"(https://www.noisebridge.net/wiki/Noisebridge_Tor/FBI) pentru resurse legale" +" suplimentare." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1002,6 +1239,10 @@ msgid "" "operators have been harassed, or if you're the only exit relay operator in " "your region." msgstr "" +"În general, este bine să vă consultați cu un avocat înainte de a decide să " +"opereze un releu de ieșire, mai ales dacă locuiți într-un loc în care " +"operatorii de relee de ieșire au fost hărțuiți sau dacă sunteți singurul " +"operator de relee de ieșire din regiunea dvs." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1012,16 +1253,22 @@ msgid "" "EFF](https://www.eff.org/about/contact) and see if they can help connect " "you." msgstr "" +"Luați legătura cu organizația dvs. locală pentru drepturi digitale pentru a " +"afla dacă au recomandări cu privire la asistența juridică și dacă nu sunteți" +" sigur ce organizații lucrează în regiunea dvs., [scrieți la FEP] " +"(https://www.eff.org/about/contact) și vedeți dacă vă pot ajuta să vă " +"conectați." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "Also see the [Tor Exit Guidelines](tor-exit-guidelines)." msgstr "" +"A se vedea, de asemenea, [Ghid de ieșire din Tor] (tor-exit-guidelines)." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "# Responding to abuse complaints" -msgstr "" +msgstr "# Răspuns la reclamațiile de abuz" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1030,6 +1277,9 @@ msgid "" " one of many templates that Tor has created: [Tor Abuse Templates](tor-" "abuse-templates)." msgstr "" +"Operatorii pot pune la dispoziție propriile șabloande de răspunsuri la " +"reclamații din unul dintre numeroasele șabloane create de Tor : [Șabloane de" +" abuz Tor] (tor-abuse-templates)." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1038,6 +1288,9 @@ msgid "" "within 24 hours). If the hoster gets annoyed by the amount of abuse you can" " reduce the amount of ports allowed in your exit policy." msgstr "" +"Este important să răspundeți la reclamațiile de abuz în timp util (de obicei" +" în 24 de ore). Dacă gazda se plânge de un abuz, puteți reduce cantitatea de" +" porturi permise în politica de ieșire." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1045,11 +1298,13 @@ msgid "" "Please document your experience with new hosters on the following page: " "[GoodBadISPs](good-bad-isps)" msgstr "" +"Vă rugăm să vă descrieți experiența cu noua gazdă pe pagina următoare: " +"[GoodBadISPs] (good-bad-isps)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "Other docs we like:" -msgstr "" +msgstr "Alte documente care ne plac:" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1058,6 +1313,10 @@ msgid "" "exit relay: [What happened when we got subpoenaed over our Tor exit " "node](https://boingboing.net/2015/08/04/what-happened-when-the-fbi-sub.html)" msgstr "" +"* o scrisoare Boing Boing folosită pentru a răspunde unei citări federale " +"din SUA despre releul de ieșire al acestora: [Ce s-a întâmplat când am " +"primit o citație peste nodul nostru de ieșire Tor] " +"(https://boingboing.net/2015/08/04/what-happened-when-the-fbi-sub.html)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1068,11 +1327,15 @@ msgid "" "Template](https://github.com/coldhakca/abuse-" "templates/blob/master/generic.template)." msgstr "" +"* șabloane de răspuns la abuz de la Coldhak, o organizație din Canada care " +"rulează mai multe relee: [Template DMCA] (https://github.com/coldhakca" +"/abuse-templates/blob/master/dmca.template), [Șablon generic de abuz] " +"(https://github.com/coldhakca/abuse-templates/blob/master/generic.template)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "# Running a relay with other people" -msgstr "" +msgstr "# Rularea unui releu cu alți oameni" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1081,11 +1344,14 @@ msgid "" "university department, your employer or institution, or an organization like" " [Torservers.net](https://torservers.net) to run a relay." msgstr "" +"Rularea de relee este mai distractivă cu alți oameni! Puteți lucra cu " +"departamentul universitar, angajatorul sau instituția dvs. sau o organizație" +" precum [Torservers.net] (https://torservers.net) pentru a rula un releu." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "## Torservers.net" -msgstr "" +msgstr "## Torservers.net" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1093,6 +1359,8 @@ msgid "" "Torservers is an independent, global network of organizations that help the " "Tor network by running high bandwidth Tor relays." msgstr "" +"Torservers este o rețea independentă de organizații globale care ajută " +"rețeaua Tor se ruleze relee Tor cu lățime mare de bandă." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1101,6 +1369,10 @@ msgid "" "Tor relay community, and can help you connect with dedicated relay operators" " around the world for solidarity and support." msgstr "" +"O modalitate bună de a vă implica mai mult în comunitatea releelor Tor este " +"să deveniți partener Torservers și acest lucru vă poate ajuta să vă " +"conectați cu operatorii de relee dedicate din întreaga lume pentru " +"solidaritate și sprijin." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1109,6 +1381,9 @@ msgid "" "of people (3-5 suggested to start) interested in helping with the various " "activities required for running relays." msgstr "" +"Pentru a începe un parteneriat Torservers, cel mai important este să aveți " +"un grup de persoane (la început se recomandă 3-5 persoane) interesate să " +"ajute cu diversele activități necesare pentru rularea releelor." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1116,6 +1391,8 @@ msgid "" "There should be mutual trust between the people in the group, and members " "should commit to running relays for the long term." msgstr "" +"Ar trebui să existe încredere reciprocă între oamenii din grup, iar membrii " +"ar trebui să se angajeze să ruleze relee pe termen lung." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1124,6 +1401,9 @@ msgid "" "relays, one place to meet people is [your local " "hackerspace](https://wiki.hackerspaces.org/Hackerspaces)." msgstr "" +"Dacă nu cunoașteți pe nimeni din rețeaua dvs. socială interesat să ruleze " +"relee, un loc unde să vă întâlniți este [spațiul dvs. local de hackeri] " +"(https://wiki.hackerspaces.org/Hackerspaces)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1131,6 +1411,8 @@ msgid "" "Once you have a trusted group of people, depending on your region, it is " "often advised to create some type of non-profit corporation." msgstr "" +"După ce aveți un grup de oameni de încredere, în funcție de regiunea dvs., " +"este de multe ori recomandat să creați un tip de societate non-profit." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1138,6 +1420,8 @@ msgid "" "This is useful for having a bank account, shared ownership, grant " "applications, etc." msgstr "" +"Acest lucru este util pentru a avea un cont bancar, proprietate comună, " +"cereri de grant etc." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1145,11 +1429,15 @@ msgid "" "In many countries operating as a corporation instead of as an individual can" " also get you certain legal protections." msgstr "" +"În multe țări care operează ca o corporație, în loc de persoană fizică, " +"puteți obține și anumite protecții legale." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "The next steps are figuring out hardware, transit, and server hosting." msgstr "" +"Următorii pași sunt utilizarea de hardware, tranzitul și găzduirea pe " +"server." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1157,6 +1445,8 @@ msgid "" "Depending on your location and connections within the technical community of" " the area, the last one may be the hardest step." msgstr "" +"În funcție de locația dvs. și de conexiunile din cadrul comunității tehnice " +"din zonă, ultima poate fi cea mai grea etapă." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1164,17 +1454,22 @@ msgid "" "Small local ISPs often have extra bandwidth, and may be interested in " "supporting your group with some bandwidth or rackspace." msgstr "" +"ISP-urile locale mici au adesea o lățime de bandă suplimentară și pot fi " +"interesate să vă sprijine grupul cu o lățime de bandă sau un spațiu de tip " +"rackspace." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "" "It is extremely important to maintain good relationships with these ISPs." msgstr "" +"Este extrem de important să menținem relații bune cu acești furnizori de " +"servicii Internet." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "## At your university" -msgstr "" +msgstr "## La universitatea dvs." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1182,6 +1477,8 @@ msgid "" "Many computer science departments, university libraries, and individual " "students and faculty run relays from university networks." msgstr "" +"Multe departamente de informatică, biblioteci universitare și studenți " +"individuali rulează relee din rețelele universitare." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1191,6 +1488,10 @@ msgid "" "Washington, Northeastern University, Karlstad University, Universitaet " "Stuttgart, and Friedrich-Alexander University Erlangen-Nuremberg." msgstr "" +"Aceste universități includ Institutul Tehnologic din Massachusetts (MIT " +"CSAIL), Universitatea Boston, Universitatea din Waterloo, Universitatea din " +"Washington, Universitatea Northeastern, Universitatea Karlstad, Universitaet" +" Stuttgart și Universitatea Friedrich-Alexander Erlangen-Nuremberg." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1199,11 +1500,14 @@ msgid "" "network, check out EFF's resources: [Tor on " "campus](https://www.eff.org/torchallenge/tor-on-campus.html)." msgstr "" +"Pentru a afla mai multe despre cum puteți obține suport pentru un releu în " +"rețeaua universității dvs., consultați resursele EFF: [Tor în campus] " +"(https://www.eff.org/torchallenge/tor-on-campus.html)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "## At your company or organization" -msgstr "" +msgstr "## În compania sau organizația dvs." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1211,6 +1515,8 @@ msgid "" "If you work at a Tor-friendly company or organization, that's another ideal " "place to run a relay." msgstr "" +"Dacă lucrați într-o companie sau organizație Tor-friendly, acesta este un " +"alt loc ideal pentru a rula un releu." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1221,6 +1527,11 @@ msgid "" "Access](https://www.privateinternetaccess.com/), [Boing " "Boing](https://boingboing.net/) and OmuraVPN." msgstr "" +"Unele companii care rulează relee includ [Brass Horn Communications] " +"(https://brasshorncommunications.uk/) [Quintex Alliance Consulting] " +"(https://www.quintex.com/) [Acces la internet privat] " +"(https://www.privateinternetaccess.com/) [Boing Boing] " +"(https://boingboing.net/) și OmuraVPN." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1230,11 +1541,15 @@ msgid "" "Digitales](https://tor.derechosdigitales.org), [Enjambre " "Digital](https://tor.enjambre.net/) and Lebanon Libraries in New Hampshire." msgstr "" +"Unele organizații care rulează relee Tor includ Digital Courage, [Access " +"Now] (https://www.accessnow.org/) [Derechos Digitales] " +"(https://tor.derechosdigitales.org) [Enjambre Digital] " +"(https://tor.enjambre.net/) și Bibliotecile Libanului din New Hampshire." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "# Bad relays" -msgstr "" +msgstr "# Relee necorespunzătoare" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1243,6 +1558,9 @@ msgid "" "users' connections. This can be either through maliciousness or " "misconfiguration." msgstr "" +"Un releu necorespunzător este unul care nu funcționează corect sau nu " +"modifică conexiunile utilizatorilor noștri. Acest lucru se poate datora fie " +"răutății, fie configurării greșite." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1251,16 +1569,20 @@ msgid "" " all your help and vigilance! Learn how you can report [bad relays](bad-" "relays)." msgstr "" +"Multe relee necorespunzătoare sunt găsite datorită comunității noastre " +"largi, căreia le aducem mulțumiri pentru tot ajutorul și vigilența lor! " +"Aflați cum puteți raporta [releele necorespunzătoare] (bad-relays)." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "# Other resources" -msgstr "" +msgstr "# Alte resurse" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) msgid "Congratulations, you're officially a Tor relay operator! What now?" msgstr "" +"Felicitări, sunteți oficial un operator de relee Tor! Ce puteți face acum?" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1269,6 +1591,9 @@ msgid "" "[Relay Search](https://metrics.torproject.org/rs.html) (your relay will " "appear on \"Relay Search\" about 3 hours after you started it)." msgstr "" +"* Puteți consulta traficul și alte statistici pentru releul dvs. la [Căutare" +" releu] (https://metrics.torproject.org/rs.html) (releul dvs. va apărea în " +"„Căutare releu” la aproximativ 3 ore de la începerea activității lui)." #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1276,6 +1601,9 @@ msgid "" "* There is also more info about running a relay at the [Tor " "FAQ](https://2019.www.torproject.org/docs/faq.html.en#HowDoIDecide)." msgstr "" +"* Există, de asemenea, mai multe informații despre rularea unui releu la " +"[Întrebări frecvente despre Tor] " +"(https://2019.www.torproject.org/docs/faq.html.en#HowDoIDecide)" #: https//community.torproject.org/relay/community-resources/ #: (content/relay-operations/community-resources/contents+en.lrpage.body) @@ -1284,11 +1612,15 @@ msgid "" " your swag](swag). It's our way of saying thanks for defending privacy and " "free speech online." msgstr "" +"* Și, cel mai important, asigurați-vă că trimiteți un e-mail la " +"tshirt(a)torproject.org și [revendicați-vă recompensa] (recompensa). Este " +"modul nostru de a vă mulțumi pentru apărarea vieții private și a comunicării" +" gratuite online." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.title) msgid "Technical considerations" -msgstr "" +msgstr "Considerații tehnice" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.subtitle) @@ -1296,11 +1628,13 @@ msgid "" "How to choose a good hosting provider, what's an AS and Operating System " "diversity." msgstr "" +"Cum să alegeți un furnizor bun de găzduire, ce este AS și diversitatea " +"sistemelor de operare." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "# Choosing a hosting provider" -msgstr "" +msgstr "# Alegerea unui furnizor de găzduire" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1309,6 +1643,9 @@ msgid "" "directions) and a physical piece of computer hardware is the best way to run" " a relay." msgstr "" +"Cea mai bună modalitate de a rula un releu este să aveți acces la o " +"conexiune la internet de mare viteză (>= 100 Mbit/s în ambele direcții) și " +"la o componentă fizică hardware." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1316,6 +1653,8 @@ msgid "" "Having full control over the hardware and connection gives you a more " "controllable and (if done correctly) secure environment." msgstr "" +"Deținerea controlului complet asupra hardware-ului și a conexiunii vă oferă " +"un mediu mai controlabil și (dacă este făcută corect) mai sigur." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1323,11 +1662,13 @@ msgid "" "You can host your own physical hardware at home (do NOT run a Tor exit relay" " from your home) or in a data center." msgstr "" +"Vă puteți găzdui propriul hardware fizic de acasă (NU rulați un releu de " +"ieșire Tor de acasă) sau dintr-un centru de date." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "Sometimes this is referred to as installing the relay on \"bare metal.\"" -msgstr "" +msgstr "Uneori, aceasta se referă la instalarea releului pe \"bare metal.\"" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1335,6 +1676,8 @@ msgid "" "If you do not own physical hardware, you could run a relay on a rented " "dedicated server or virtual private server (VPS)." msgstr "" +"Dacă nu dețineți hardware fizic, puteți rula un releu pe un server dedicat " +"închiriat sau pe un server privat virtual (VPS)." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1342,11 +1685,14 @@ msgid "" "This can cost anywhere between $3.00/month and thousands per month, " "depending on your provider, hardware configuration, and bandwidth usage." msgstr "" +"Acest lucru poate costa de la 3.00 $/lună până la mii de dolari pe lună, în " +"funcție de furnizorul dvs., configurația hardware și utilizarea lățimii de " +"bandă." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "Many VPS providers will not allow you to run exit relays." -msgstr "" +msgstr "Mulți furnizori VPS nu vă vor permite să rulați relee de ieșire." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1354,6 +1700,8 @@ msgid "" "You must follow the VPS provider's terms of service, or risk having your " "account disabled." msgstr "" +"Trebuie să urmați condițiile de furnizare ale furnizorului VPS, altfel " +"riscați să vă dezactivați contul." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1362,16 +1710,21 @@ msgid "" " relays, please see this list maintained by the Tor community: " "[GoodBadISPs](/relay/community-resources/good-bad-isps)." msgstr "" +"Pentru mai multe informații despre furnizorii de găzduire și politicile lor " +"privind permiterea releelor Tor, consultați această listă menținută de " +"comunitatea Tor: [GoodBadISPs] (/relay/community-resources/good-bad-isps)." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "## Questions to consider when choosing a host" -msgstr "" +msgstr "## Întrebări de luat în considerare atunci când alegeți o gazdă" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* How much monthly traffic is included? Is bandwidth \"unmetered\"?" msgstr "" +"* Cât de mult trafic lunar este inclus? Lățimea de bandă este " +"„nemodificată”?" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1379,6 +1732,7 @@ msgid "" "* Does the hoster provide IPv6 connectivity? It is recommended, but not " "required." msgstr "" +"* Gazda oferă conectivitate IPv6? Este recomandat, dar nu este necesar." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1386,6 +1740,8 @@ msgid "" "* What virtualization / hypervisor (if any) does the provider use? Anything " "but OpenVZ should be fine." msgstr "" +"* Ce virtualizare / hipervizor (dacă există) utilizează furnizorul? Orice în" +" afară de OpenVZ ar trebui să fie în regulă." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1393,6 +1749,8 @@ msgid "" "* Does the hoster start to throttle bandwidth after a certain amount of " "traffic?" msgstr "" +"* Gazda începe să micșoreze lățimea de bandă după o anumită cantitate de " +"trafic?" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1401,11 +1759,14 @@ msgid "" "question you can use the AS rank of the autonomous systems if you want to " "compare: (a lower value is better) http://as-rank.caida.org/" msgstr "" +"* Cât de bine conectat este sistemul autonom al gazdei? Pentru a răspunde la" +" această întrebare, puteți utiliza rangul AS al sistemelor autonome pentru " +"comparație: (o valoare mai mică este mai bună) http://as-rank.caida.org/" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "## If you plan to run exit relays" -msgstr "" +msgstr "## Dacă intenționați să rulați relee de ieșire" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1413,6 +1774,8 @@ msgid "" "* Does the hoster allow Tor exit relays? We recommend you explicitly ask " "them before getting started." msgstr "" +"* Gazda permite releele de ieșire Tor? Vă recomandăm să o întrebați în mod " +"explicit înainte de a începe." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1420,6 +1783,8 @@ msgid "" "* Does the hoster allow custom WHOIS records for your IP addresses? This " "helps reduce the amount of abuse sent to the hoster instead of you." msgstr "" +"* Gazda permite înregistrări WHOIS personalizate pentru adresele dvs. IP? " +"Acest lucru ajută la reducerea abuzului trimis către gazdă în locul dvs." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1427,16 +1792,18 @@ msgid "" "* Does the hoster allow you to set a custom DNS reverse entry? (DNS PTR " "record)" msgstr "" +"* Gazda vă permite să setați o intrare inversă DNS personalizată? " +"(înregistrare DNS PTR)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "You can usually ask these questions in a Pre-Sales ticket." -msgstr "" +msgstr "De obicei, puteți pune aceste întrebări într-un tichet pre-vânzare." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "# AS/location diversity" -msgstr "" +msgstr "# Diversitatea AS/locație" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1444,22 +1811,27 @@ msgid "" "When selecting your hosting provider, consider network diversity on an " "autonomous system (AS) and country level." msgstr "" +"Când selectați furnizorul dvs. de găzduire, luați în considerare " +"diversitatea rețelei pe un sistem autonom (AS) și la nivel de țară." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "A more diverse network is more resilient to attacks and outages." -msgstr "" +msgstr "O rețea mai diversă este mai rezistentă la atacuri și întreruperi." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "" "Sometimes it is not clear which AS you are buying from in case of resellers." msgstr "" +"Uneori nu este clar de la ce sistem cumpărați în cazul revânzătorilor." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "To be sure, ask the host about the AS number before ordering a server." msgstr "" +"Pentru a fi siguri, întrebați gazda despre numărul AS înainte de a comanda " +"un server." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1467,31 +1839,34 @@ msgid "" "It is best to avoid hosts where many Tor relays are already hosted, but it " "is still better to add one there than to run no relay at all." msgstr "" +"Cel mai bine este să evitați gazdele în care sunt deja găzduite multe relee " +"Tor, dar este totuși mai bine să adăugați acolo un releu, decât să nu rulați" +" niciun releu." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "**Try to avoid** the following hosters:" -msgstr "" +msgstr "**Încercați să evitați** următoarele gazde:" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* OVH SAS (AS16276)" -msgstr "" +msgstr "* OVH SAS (AS16276)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* Online S.a.s. (AS12876)" -msgstr "" +msgstr "* Online S.a.s. (AS12876)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* Hetzner Online GmbH (AS24940)" -msgstr "" +msgstr "* Hetzner Online GmbH (AS24940)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* DigitalOcean, LLC (AS14061)" -msgstr "" +msgstr "* DigitalOcean, LLC (AS14061)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1499,6 +1874,8 @@ msgid "" "To find out which host and countries are already used by many other " "operators (that should be avoided) you can use Relay Search:" msgstr "" +"Pentru a afla ce gazde și țări sunt deja folosite de mulți alți operatori " +"(care ar trebui evitate), puteți utiliza căutarea de releu:" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1506,6 +1883,8 @@ msgid "" "* [Autonomous System Level " "Overview](https://metrics.torproject.org/rs.html#aggregate/as)" msgstr "" +"*[Prezentare generală la nivel de sistem " +"autonom](https://metrics.torproject.org/rs.html#aggregate/as)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1513,11 +1892,13 @@ msgid "" "* [Country Level " "Overview](https://metrics.torproject.org/rs.html#aggregate/cc)" msgstr "" +"* [Prezentare generală la nivel de " +"țară](https://metrics.torproject.org/rs.html#aggregate/cc)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "# Choosing an Operating System" -msgstr "" +msgstr "# Alegerea unui sistem de operare" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1526,11 +1907,14 @@ msgid "" "you're able, the network would most benefit from BSD and other non-Linux " "based relays." msgstr "" +"Vă recomandăm să utilizați sistemul de operare cu care sunteți familiarizat," +" dar dacă se poate, rețeaua ar beneficia cel mai mult de BSD și alte relee " +"bazate pe Linux." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "Most relays currently run on Debian." -msgstr "" +msgstr "Majoritatea releelor rulează în prezent pe Debian." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1538,16 +1922,19 @@ msgid "" "The following table shows the current OS distribution on the Tor network to " "give you an idea of how much more non-Linux relays we should have:" msgstr "" +"Următorul tabel arată distribuția curentă a sistemului de operare în rețeaua" +" Tor pentru a vă oferi o idee despre cât de multe relee non-Linux ar trebui " +"să avem:" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "* https://nusenu.github.io/OrNetStats/#os-distribution-relays" -msgstr "" +msgstr "* https://nusenu.github.io/OrNetStats/#os-distribution-relays" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "# OS Level Configuration" -msgstr "" +msgstr "# Configurarea la nivel de sistem de operare" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1556,11 +1943,14 @@ msgid "" "points are crucial for a Tor relay, so we want to mention them here " "nonetheless." msgstr "" +"Configurarea sistemului de operare nu se află în sfera de aplicare a acestui" +" ghid, dar următoarele puncte sunt cruciale pentru un releu Tor, așadar " +"dorim să le menționăm aici." #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) msgid "## Time Synchronization (NTP)" -msgstr "" +msgstr "## Sincronizarea timpului (NTP)" #: https//community.torproject.org/relay/technical-considerations/ #: (content/relay-operations/technical-considerations/contents+en.lrpage.body) @@ -1569,16 +1959,19 @@ msgid "" "you use the network time protocol (NTP) for time synchronization and ensure " "your timezone is set correctly." msgstr "" +"Setările corecte de timp sunt esențiale pentru releele Tor. Este recomandat " +"să utilizați protocolul de timp de rețea (NTP) pentru sincronizarea timpului" +" și să vă asigurați că fusul dvs. orar este setat corect." #: https//community.torproject.org/relay/getting-help/ #: (content/relay-operations/getting-help/contents+en.lrpage.title) msgid "Getting help" -msgstr "" +msgstr "Obținerea de ajutor" #: https//community.torproject.org/relay/getting-help/ #: (content/relay-operations/getting-help/contents+en.lrpage.subtitle) msgid "How to get help if you run into issues" -msgstr "" +msgstr "Cum să obțineți ajutor dacă aveți probleme" #: https//community.torproject.org/relay/getting-help/ #: (content/relay-operations/getting-help/contents+en.lrpage.body) @@ -1589,6 +1982,12 @@ msgid "" "The list is a great resource for asking (and answering) questions, and for " "getting to know other relay operators. Make sure to check out the archives!" msgstr "" +"Dacă întâmpinați probleme în timpul configurarii releului, puteți pune " +"întrebări pe [lista de corespondență relee Tor] " +"(https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays) publică. " +"Lista este o resursă excelentă pentru a pune (și a răspunde) la întrebări și" +" pentru a cunoaște alți operatori de relee. Asigurați-vă că verificați și " +"arhivele!" #: https//community.torproject.org/relay/getting-help/ #: (content/relay-operations/getting-help/contents+en.lrpage.body) @@ -1596,17 +1995,22 @@ msgid "" "You can also get help by joining the IRC channel #tor-relays in the network " "[irc.oftc.net](https://support.torproject.org/get-in-touch/#irc-help)." msgstr "" +"De asemenea, puteți obține ajutor prin accesarea canalului IRC #tor-relays " +"din rețea [irc.oftc.net] (https://support.torproject.org/get-in-touch/#irc-" +"help)." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.title) msgid "Risks" -msgstr "" +msgstr "Riscuri" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.subtitle) msgid "" "Things you should be aware of before running a digital security training." msgstr "" +"Lucruri de care ar trebui să fiți conștienți înainte de a efectua o " +"instruire digitală pentru securitate." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1614,6 +2018,8 @@ msgid "" "To our knowledge, no Tor trainer has ever faced consequences as a result of " "training others or speaking about Tor." msgstr "" +"Din câte știm, niciun instructor Tor nu s-a confruntat vreodată cu " +"consecințe ca urmare a instruirii altora sau a discuțiilor despre Tor." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1624,6 +2030,11 @@ msgid "" "threats, placement on government watch lists, and targeting for " "surveillance." msgstr "" +"Cu toate acestea, în unele țări și în anumite circumstanțe, este posibil ca " +"o simplă adunare a apărătorilor drepturilor omului să poată fi riscantă, " +"ilegală sau chiar să trimită pe cineva la închisoare, să îl supună la " +"agresiuni fizice, amenzi mari, amenințări, plasarea pe listele de pază ale " +"guvernului și vizarea pentru supraveghere." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1633,6 +2044,10 @@ msgid "" "read this document and, in case of doubt, to reach out to the Tor Community " "Team privately." msgstr "" +"Dacă doriți să efectuați pentru prima dată o instruire Tor și nu știți cum " +"să evaluați mediul politic și social, vă încurajăm cu încredere să citiți " +"acest document și, în caz de îndoială, să vă adresați în privat echipei " +"comunității Tor." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1640,11 +2055,14 @@ msgid "" "Some potential risks of running a digital security training are only valid " "in specific contexts." msgstr "" +"Unele potențiale riscuri ale unei instruiri de securitate digitală sunt " +"valabile doar în anumite contexte." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "The potential risks associated with running a Tor training depend on:" msgstr "" +"Riscurile potențiale asociate cu efectuarea unei instruiri Tor depind de:" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1653,6 +2071,10 @@ msgid "" "surveillance, for example, might attract more attention when reaching out " "other activists to run a digital security training." msgstr "" +"1. **Modelul dvs. de amenințare.** Un activist cu profil înalt care se află " +"deja sub supraveghere, de exemplu, poate atrage mai multă atenție atunci " +"când ajunge la alți activiști pentru a efectua o instruire de securitate " +"digitală." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1662,6 +2084,10 @@ msgid "" " has a record in prosecuting individuals engaging in similar types of " "activities." msgstr "" +"2. **Legile și reglementările din țară.** Întrebați avocații locali și " +"organizațiile locale despre libertatea de exprimare și aflați dacă țara dvs." +" are o evidență de urmărire a persoanelor care desfășoară activități " +"similare." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1669,6 +2095,8 @@ msgid "" "3. **The types of training.** Not all trainings carry the same weight in " "terms of potential risk." msgstr "" +"3. **Tipurile de instruire.** Nu toate instruirile au aceeași însemnătate " +"din punct de vedere al riscului potențial." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1677,6 +2105,9 @@ msgid "" "but teaching how to circumvent government censorship could be a serious " "felony." msgstr "" +"De exemplu, a vorbi despre confidențialitate în era digitală ar putea fi " +"apreciată, dar a învăța cum să ocolim cenzura guvernamentală ar putea fi o " +"infracțiune gravă." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1686,6 +2117,10 @@ msgid "" "leaked documents about government corruption, you might need to be extra " "careful on how to reach out them in a private way." msgstr "" +"4. **Publicul.** Adunarea studenților universitari s-ar putea să nu atragă " +"atenția, dar dacă adunați un grup de jurnaliști care lucrează cu documente " +"despre corupția guvernamentală, ar trebui să fiți atenți la modul în care " +"să-i contactați în mod privat." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1693,6 +2128,8 @@ msgid "" "5. **The training venue.** Running a Tor training in some spaces could " "expose your participants' identities." msgstr "" +"5. **Locul de instruire.** Desfășurarea unei instruiri Tor în unele spații " +"ar putea expune identitatea participanților." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1700,6 +2137,8 @@ msgid "" "Ideally, you should use a private space where you control the participants' " "entrance." msgstr "" +"În mod ideal, ar trebui să utilizați un spațiu privat unde se poate controla" +" intrarea participanților." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1707,11 +2146,14 @@ msgid "" "If the space isn't private, check before the training to find out if " "participants are comfortable revealing their identity to a third party." msgstr "" +"Dacă spațiul nu este privat, verificați-l înainte de instruire, pentru a " +"afla dacă participanții doresc să își dezvăluie identitatea fără probleme " +"față de o terță parte." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "## Evaluating risks" -msgstr "" +msgstr "## Evaluarea riscurilor" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1719,6 +2161,8 @@ msgid "" "Some questions you may want to answer before running a digital security " "training include:" msgstr "" +"Unele întrebări la care doriți să răspundeți înainte de a efectua o " +"instruire de securitate digitală includ:" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1727,6 +2171,9 @@ msgid "" "activity? (This does not necessarily need to be specific to digital security" " training or use of Tor.)" msgstr "" +"* A fost cineva incriminat vreodată în țara mea din cauza activității pe " +"internet? (Acest lucru nu trebuie neapărat să fie specific pentru instruirea" +" în domeniul securității digitale sau utilizarea Tor.)" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1734,31 +2181,33 @@ msgid "" "* Are there laws in my country that require Internet Service Providers " "(ISPs) to track my online activity?" msgstr "" +"* Există legi în țara mea care solicită ca furnizorii de servicii Internet " +"(ISP) să-mi urmărească activitatea online?" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* Is it illegal for me to access certain websites?" -msgstr "" +msgstr "* Este ilegal pentru mine să accesez anumite site-uri web?" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* Does my country prohibit me from using:" -msgstr "" +msgstr "* Țara mea îmi interzice utilizarea:" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* Cryptography?" -msgstr "" +msgstr "* Criptografiei?" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* Anonymity software?" -msgstr "" +msgstr "* Software-ului de anonimat?" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "Note, this is not an exhaustive list of questions." -msgstr "" +msgstr "Notă, aceasta nu este o listă exhaustivă de întrebări." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1768,6 +2217,10 @@ msgid "" "security tools may still be criminalized in certain countries under other, " "broader laws." msgstr "" +"În plus, în timp ce multe țări nu au legi care interzic în mod special " +"activitatea de instruire în domeniul securității digitale, utilizarea " +"instrumentelor de securitate digitală poate fi încă incriminată în anumite " +"țări, în conformitate cu alte legi mai largi." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1775,6 +2228,8 @@ msgid "" "For example, using Tor Browser may be viewed as illegal or anti-government " "activity." msgstr "" +"De exemplu, utilizarea Tor Browser poate fi privită ca activitate ilegală " +"sau anti-guvernamentală." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1782,6 +2237,8 @@ msgid "" "Please note that we are not lawyers, and any information we give you does " "not constitute legal advice." msgstr "" +"Vă rugăm să rețineți că nu suntem avocați, iar informațiile pe care vi le " +"oferim nu constituie consultanță juridică." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1790,6 +2247,9 @@ msgid "" "privilege, so law enforcement may subpoena and obtain any information you " "give us." msgstr "" +"În plus, comunicarea dvs. cu noi nu este protejată de niciun privilegiu " +"legal, astfel încât forțele de ordine pot cita și obține orice informație pe" +" care ne-o oferiți." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1797,16 +2257,20 @@ msgid "" "However, we may be able to put you in touch with lawyers who are capable of " "addressing your questions and/or concerns." msgstr "" +"Cu toate acestea, este posibil să vă putem pune în legătură cu avocații care" +" sunt capabili să vă răspundă la întrebări și/sau probleme." #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "Some relevant resources include:" -msgstr "" +msgstr "Unele resurse relevante includ:" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* [EFF Know your rights](https://www.eff.org/issues/know-your-rights)" msgstr "" +"* [EFF Cunoașteți-vă drepturile](https://www.eff.org/issues/know-your-" +"rights)" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) @@ -1814,31 +2278,34 @@ msgid "" "* [EFF Tor legal FAQ](https://community.torproject.org/relay/community-" "resources/eff-tor-legal-faq/)" msgstr "" +"* [EFF Întrebări frecvente legale despre " +"Tor](https://community.torproject.org/relay/community-resources/eff-tor-" +"legal-faq/)" #: https//community.torproject.org/training/risks/ #: (content/training/risks/contents+en.lrpage.body) msgid "* [OONI disclaimer](https://ooni.io/about/risks/)" -msgstr "" +msgstr "* [Act de renunțate OONI](https://ooni.io/about/risks/)" #: https//community.torproject.org/training/code-of-conduct/ #: (content/training/code-of-conduct/contents+en.lrpage.title) msgid "Code of Conduct for Trainers" -msgstr "" +msgstr "Codul de conduită pentru formatori" #: https//community.torproject.org/training/code-of-conduct/ #: (content/training/code-of-conduct/contents+en.lrpage.subtitle) msgid "Foster a safe, engaging environment." -msgstr "" +msgstr "Încurajarea unui mediu sigur și antrenant." #: https//community.torproject.org/training/code-of-conduct/ #: (content/training/code-of-conduct/contents+en.lrpage.cta) msgid "Code of Conduct" -msgstr "" +msgstr "Cod de conduită" #: https//community.torproject.org/training/code-of-conduct/ #: (content/training/code-of-conduct/contents+en.lrpage.body) msgid "## Code of Conduct for Trainers" -msgstr "" +msgstr "## Codul de conduită pentru formatori" #: https//community.torproject.org/training/code-of-conduct/ #: (content/training/code-of-conduct/contents+en.lrpage.body) @@ -1854,7 +2321,7 @@ msgstr "" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.title) msgid "Training Checklist" -msgstr "" +msgstr "Lista de verificare a instruirii" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.subtitle) @@ -1862,16 +2329,19 @@ msgid "" "Based on our best practices, we have a checklist to help you prepare to " "conduct your training." msgstr "" +"Pe baza celor mai bune practici, avem o listă de verificare pentru a vă " +"ajuta să vă pregătiți în vederea realizării instruirii." #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "Complete this checklist before running a Tor training." msgstr "" +"Completați această listă de verificare înainte de a efectua o instruire Tor." #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## Prepare" -msgstr "" +msgstr "## Pregătirea" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) @@ -1879,26 +2349,29 @@ msgid "" "[ ] I read and agree with the Tor Project [Code of " "Coduct](https://community.torproject.org/training/code-of-conduct/)" msgstr "" +"[ ] Am citit și sunt de acord cu [Codul de " +"Conduită](https://community.torproject.org/training/code-of-conduct/) al " +"Proiectului Tor" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I read the Trainers Guide" -msgstr "" +msgstr "[ ] Am citit Ghidul formatorilor" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I have an agenda for the training" -msgstr "" +msgstr "[ ] Am o agendă pentru instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I reviewed the training slides" -msgstr "" +msgstr "[ ] Am analizat diapozitivele pentru instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## Security Protocol" -msgstr "" +msgstr "## Protocol de Securitate" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) @@ -1906,6 +2379,8 @@ msgid "" "[ ] I already contacted my organization and told them that I'm organizing " "this training" msgstr "" +"[ ] Am contactat deja organizația mea și le-am spus că organizez această " +"instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) @@ -1913,106 +2388,108 @@ msgid "" "[ ] I shared a contact to whom my organization should call if something " "happens" msgstr "" +"[ ] Am distribuit un contact la care organizația mea ar trebui să apeleze " +"dacă se întâmplă ceva" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## About the Venue" -msgstr "" +msgstr "## Despre locul de desfășurare" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] The venue has enough tables and chairs to everyone" -msgstr "" +msgstr "[ ] Locul are suficiente mese și scaune pentru toată lumea" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] The venue has internet connection and I know the wifi password" -msgstr "" +msgstr "[ ] Locul are conexiune la internet și știu parola wifi" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] It has a projector available and works on my computer" -msgstr "" +msgstr "[ ] Are un proiector disponibil și funcționează pe computerul meu" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## Audience & Communication" -msgstr "" +msgstr "## Audiență și comunicare" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I sent an e-mail with the address and time to all participants" -msgstr "" +msgstr "[ ] Am trimis un e-mail cu adresa și ora tuturor participanților" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I asked them to bring the necessary equipment to the training" -msgstr "" +msgstr "[ ] I-am rugat să aducă echipamentul necesar la instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] I have confirmed participants for the training" -msgstr "" +msgstr "[ ] Am confirmare de la participanții pentru instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## During the Training" -msgstr "" +msgstr "## În timpul instruirii" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "Before starting the training, make sure you:" -msgstr "" +msgstr "Înainte de a începe instruirea, asigurați-vă că:" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Make an agreement about taking or not taking photos" -msgstr "" +msgstr "[ ] Faceți un acord cu privire la realizarea sau nu de fotografii" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Present the agenda" -msgstr "" +msgstr "[ ] Prezentați ordinea de zi" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Introduce yourself and ask people to introduce themselves" -msgstr "" +msgstr "[ ] Prezentați-vă și cereți oamenilor să se prezinte" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] \"All questions are welcome\"" -msgstr "" +msgstr "[ ] \"Toate întrebările sunt binevenite\"" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "## After the Training" -msgstr "" +msgstr "## După instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Collect participants feedback" -msgstr "" +msgstr "[ ] Colectați feedback-ul participanților" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Leave an e-mail for further contact and support" -msgstr "" +msgstr "[ ] Lăsați un e-mail pentru mai multe contacte și asistență" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Make an evaluation about the training" -msgstr "" +msgstr "[ ] Faceți o evaluare cu privire la instruire" #: https//community.torproject.org/training/checklist/ #: (content/training/checklist/contents+en.lrpage.body) msgid "[ ] Report privately to Community Team" -msgstr "" +msgstr "[ ] Raportați în mod privat echipei Community Team" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.title) msgid "Training Best Practices" -msgstr "" +msgstr "Cele mai bune practici de instruire" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.subtitle) @@ -2021,11 +2498,14 @@ msgid "" "Good preparation is essential to an effective and safe training, so we've " "curated some resources to help you make the most of your training event." msgstr "" +"O pregătire bună este esențială pentru o instruire eficientă și sigură, așa " +"că vă oferim câteva resurse care să vă ajute să profitați la maxim de " +"evenimentul dvs. de instruire." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.cta) msgid "Best Practices for Trainers" -msgstr "" +msgstr "Cele mai bune practici pentru instructori" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2033,16 +2513,19 @@ msgid "" "Running security training is a fun and rewarding way to help your community " "conduct human rights work safely." msgstr "" +"Desfășurarea instruirii în domeniul securității este o modalitate " +"distractivă și plină de satisfacții de a ajuta comunitatea dvs. să " +"folosească drepturile omului pentru a lucra în siguranță." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "## Before the training" -msgstr "" +msgstr "## Înainte de instruire" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "_Am I the right person to give this training?_" -msgstr "" +msgstr "_Sunt persoana potrivită pentru a oferi această instruire?_" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2051,6 +2534,9 @@ msgid "" "but there are additional considerations to be made before training some at-" "risk groups." msgstr "" +"Instruirile de securitate pot ajuta oamenii să comunice și să folosească " +"internetul în condiții de siguranță, dar există considerente suplimentare " +"care trebuie făcute înainte de instruirea unor grupuri cu risc." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2059,6 +2545,9 @@ msgid "" "Companion, [\"Am I the right person to give this " "training?\"](https://sec.eff.org/articles/right-person-to-train)." msgstr "" +"De aceea, recomandăm această resursă de la EFF's Security Education " +"Companion, [\"Sunt persoana potrivită pentru a oferi această instruire?\"] " +"(https://sec.eff.org/articles/right-person-to-train)" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2066,17 +2555,21 @@ msgid "" "This resource can help you be sure that you're doing the best by the " "community of people you wish to train." msgstr "" +"Această resursă vă poate ajuta să vă asigurați că faceți tot ce este mai bun" +" pentru comunitatea de oameni pe care doriți să o instruiți." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "Other questions to ask yourself before deciding to do a training:" msgstr "" +"Alte întrebări care vi le puteți pune înainte de a decide să faceți o " +"instruire:" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "" "- How will you assess the needs of your group? What needs can you meet?" -msgstr "" +msgstr "- Cum veți evalua nevoile grupului dvs.? Ce nevoi puteți satisface?" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2084,12 +2577,16 @@ msgid "" "- How will you assess the skill level of your group? What skill levels can " "you teach to?" msgstr "" +"- Cum veți evalua nivelul de îndemânare al grupului dvs.? Ce niveluri de " +"abilități puteți învăța?" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "" "Once you've answered those questions, you're ready to plan your training!" msgstr "" +"După ce ați răspuns la aceste întrebări, sunteți gata să vă planificați " +"instruirea!" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2097,11 +2594,13 @@ msgid "" "1. Find a location that is accessible, affordable, has an internet " "connection and other materials like a white board, projector, and screen." msgstr "" +"1. Găsiți o locație accesibilă, ușor de reperat, care are o conexiune la " +"internet și alte materiale precum o tablă albă, un proiector și un ecran." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "Make sure that the location is safe for your attendees to visit." -msgstr "" +msgstr "Asigurați-vă că locația este în siguranță pentru vizitatorii dvs." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2109,6 +2608,8 @@ msgid "" "2. Promote your event in your community's spaces, taking safety into " "consideration." msgstr "" +"2. Promovați evenimentul în spațiile comunității dvs., luând în considerare " +"siguranța." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2118,6 +2619,10 @@ msgid "" "require community members to share information individually to other trusted" " people." msgstr "" +"În multe circumstanțe, social media este excelentă pentru promovare, dar " +"pentru grupurile cu risc mai mare, poate doriți să utilizați o rețea vocală " +"mai mică sau să solicitați membrilor comunității să partajeze personal " +"informații altor persoane de încredere." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2125,37 +2630,45 @@ msgid "" "3. Create localized handouts for some of the more difficult concepts that " "you'll be teaching." msgstr "" +"3. Creați-vă notițe pentru unele dintre conceptele mai dificile pe care le " +"veți preda." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "4. Make sure you have plenty of stickers to hand out to participants!" msgstr "" +"4. Asigurați-vă că aveți destule autocolante pe care să le oferiți " +"participanților!" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "5. Create a link list of all the resources you'll be talking about." -msgstr "" +msgstr "5. Creați o listă de legături cu toate resursele despre care vorbiți." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "This includes downloads and PDFs of handouts." -msgstr "" +msgstr "Aici sunt incluse și descărcări de pe Internet și fișiere PDF." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "" "You'll share this link list on a whiteboard or project it at the training." msgstr "" +"Veți oferi această listă de linkuri pe o tablă albă sau o veți proiecta la " +"instruire." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "6. Determine how you'll do hands-on assistance at your training." msgstr "" +"6. Determinați modul în care veți face asistență practică la instruire." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "Will you be able to handle this alone? Or will you require partners?" msgstr "" +"Veți putea să vă descurcați singur? Sau veți avea nevoie de parteneri?" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2165,6 +2678,10 @@ msgid "" "the community to make sure they're okay with you bringing in additional " "trainers." msgstr "" +"Dacă aveți nevoie de mai mult ajutor, asigurați-vă că partenerii pe care îi " +"aduceți sunt conștienți de nevoile de siguranță ale comunității și " +"comunicați cu persoanele din comunitatea dvs. pentru a vă asigura că sunt de" +" acord ca să aduceți instructori suplimentari." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2174,6 +2691,10 @@ msgid "" "odp and pdf -- and on at least one additional device -- for example, on your" " computer and on a USB stick." msgstr "" +"7. Asigurați-vă că prezentarea dvs. este actualizată (atât informații, cât " +"și capturi de ecran) și salvați prezentarea în două formate de fișiere - de " +"exemplu, odp și pdf - și pe cel puțin un dispozitiv suplimentar - de " +"exemplu, pe computer și pe un stick USB." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2181,6 +2702,8 @@ msgid "" "8. Decide how you will facilitate a safer space. We recommend using the [Tor" " Code of Conduct](/training/code-of-conduct/)." msgstr "" +"8. Decideți cum veți facilita un spațiu mai sigur. Vă recomandăm să folosiți" +" [Codul de conduită Tor] (/training/code-of-conduct/)." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2188,11 +2711,13 @@ msgid "" "You can also start the training by asking participants to come up with their" " own community agreements for the space." msgstr "" +"De asemenea, puteți începe antrenamentul solicitând participanților să vină " +"cu propriile acorduri comunitare pentru acest spațiu." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "## At the training" -msgstr "" +msgstr "## La instruire" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2200,6 +2725,9 @@ msgid "" "1. Create an agenda and share it on a projection or on a whiteboard so that " "your participants can be prepared for the day." msgstr "" +"1. Creați o agendă și afișați-o cu ajutorul proiectorului sau pe o tablă " +"albă, astfel încât participanții dvs. să poată fi pregătiți pentru ziua " +"respectivă." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2207,6 +2735,8 @@ msgid "" "2. Communicate about how much time the training will take, and when breaks " "will happen. Make sure you take breaks!" msgstr "" +"2. Comunicați participanților despre cât timp va dura instruirea și când se " +"vor face pauze. Asigurați-vă că vor fi făcute pauze!" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2214,11 +2744,15 @@ msgid "" "3. Communicate about when you'll take questions, either during the training," " at the end, or both." msgstr "" +"3. Comunicați când veți primi întrebări, fie în timpul instruirii, fie la " +"sfârșit, fie în ambele situații." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "4. Communicate about how you'll offer hands-on help (if at all)." msgstr "" +"4. Comunicați participanților modul în care veți oferi ajutor (dacă este " +"necesar)." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2226,6 +2760,8 @@ msgid "" "5. Communicate about how participants can contact you securely after the " "training." msgstr "" +"5. Comunicați modul în care participanții vă pot contacta în siguranță după " +"instruire." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2234,6 +2770,9 @@ msgid "" "[community.torproject.org](https://community.torproject.org) and " "[support.torproject.org](https://support.torproject.org)." msgstr "" +"6. Arătați participantilor resursele de la " +"[community.torproject.org](https://community.torproject.org) și " +"[support.torproject.org](https://support.torproject.org)." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2241,16 +2780,18 @@ msgid "" "7. Show the participants other resources like " "[sec.eff.org](https://sec.eff.org)." msgstr "" +"7. Arătați participanților alte resurse, cum ar fi " +"[sec.eff.org](https://sec.eff.org)." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "## After the training" -msgstr "" +msgstr "## După instruire" #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) msgid "1. Think about how you will evaluate your success at the training." -msgstr "" +msgstr "1. Gândiți-vă cum vă veți evalua succesul la instruire." #: https//community.torproject.org/training/best-practices/ #: (content/training/best-practices/contents+en.lrpage.body) @@ -2258,11 +2799,13 @@ msgid "" "You may want to create a follow up survey, or at least contact participants " "and ask them to share their feedback with you." msgstr "" +"Poate doriți să creați un sondaj de monitorizare sau, cel puțin, să " +"contactați participanții și să le cereți să vă transmită un feedback." #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.title) msgid "Tor Training FAQ" -msgstr "" +msgstr "Întrebări frecvente pentru instruirea Tor" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.subtitle) @@ -2270,6 +2813,8 @@ msgid "" "People new to Tor often ask similar questions, and we can help you prepare " "for answering them." msgstr "" +"Oamenii nou veniți la Tor își pun deseori întrebări similare și vă putem " +"ajuta să vă pregătiți pentru a le răspunde." #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2277,6 +2822,8 @@ msgid "" "After running a couple of Tor trainings, you will find that first time users" " have some similar questions about Tor." msgstr "" +"După ce ați efectuat câteva instruiri Tor, veți vedea că utilizatorii " +"începători au întrebări similare despre Tor." #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2284,6 +2831,9 @@ msgid "" "These are the most frequent questions we hear during our training sessions. " "Be prepared for them before running your training." msgstr "" +"Acestea sunt cele mai frecvente întrebări pe care le auzim în timpul " +"sesiunilor noastre de instruire. Fiți pregătit pentru ele înainte de a " +"începe instruirea." #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2291,6 +2841,8 @@ msgid "" "For an extensive resource, check [Support " "portal](https://support.torproject.org)." msgstr "" +"Pentru o resursă extinsă, verificați [Portalul de asistență] " +"(https://support.torproject.org)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2298,6 +2850,8 @@ msgid "" "* [Why is it called Tor?](https://support.torproject.org/about/why-is-it-" "called-tor/)" msgstr "" +"* [De ce se numește Tor?](https://support.torproject.org/about/why-is-it-" +"called-tor/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2305,6 +2859,8 @@ msgid "" "* [Does using Tor Browser protect other applications on my " "computer?](https://support.torproject.org/tbb/tbb-13/)" msgstr "" +"* [Utilizarea Tor Browser protejează alte aplicații de pe computerul " +"meu?](https://support.torproject.org/tbb/tbb-13/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2312,6 +2868,8 @@ msgid "" "* [Is using Tor with a VPN more " "secure?](https://support.torproject.org/faq/faq-5/)" msgstr "" +"* [Utilizează Tor un VPN mai " +"sigur?](https://support.torproject.org/faq/faq-5/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2319,6 +2877,8 @@ msgid "" "* [Can I browse HTTPS sites with " "Tor?](https://support.torproject.org/https/https-2/)" msgstr "" +"* [Pot naviga pe site-uri HTTPS cu " +"Tor?](https://support.torproject.org/https/https-2/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2326,6 +2886,8 @@ msgid "" "* [Is it possible to find out the path that a client is taking on the Tor " "Network?](https://support.torproject.org/misc/misc-1/)" msgstr "" +"* [Este posibil să se afle calea pe care o alege un client din rețeaua " +"Tor?](https://support.torproject.org/misc/misc-1/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2333,6 +2895,8 @@ msgid "" "* [Why don't you prevent bad people from doing bad things when using " "Tor?](https://support.torproject.org/misc/misc-2/)" msgstr "" +"* [De ce nu sunt împiedicați oamenii răi să facă lucruri rele când se " +"folosește Tor?](https://support.torproject.org/misc/misc-2/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2340,6 +2904,8 @@ msgid "" "* [When I use Tor Browser, will anyone be able to tell which websites I " "visit?](https://support.torproject.org/tbb/tbb-3/)" msgstr "" +"* [Când folosesc Tor Browser, oricine va putea spune ce site-uri web " +"vizitez?](https://support.torproject.org/tbb/tbb-3/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2347,6 +2913,8 @@ msgid "" "* [Why did my search engine switch to DuckDuckGo? Or what is " "DuckDuckGo?](https://support.torproject.org/tbb/tbb-41/)" msgstr "" +"* [De ce motorul meu de căutare a trecut la DuckDuckGo? Sau ce este " +"DuckDuckGo?](https://support.torproject.org/tbb/tbb-41/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2354,6 +2922,8 @@ msgid "" "* [What is a " "bridge?](https://support.torproject.org/censorship/censorship-7/)" msgstr "" +"* [Ce este o " +"punte?](https://support.torproject.org/censorship/censorship-7/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2361,6 +2931,8 @@ msgid "" "* [Tor Browser won't connect, but it doesn’t seem to be an issue with " "censorship.](https://support.torproject.org/tbb/tbb-20/)" msgstr "" +"* [Tor Browser nu se conectează, dar pare să nu fie o problemă cu " +"cenzura.](https://support.torproject.org/tbb/tbb-20/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2368,6 +2940,9 @@ msgid "" "* [What is the difference between using Tor Browser and 'incognito mode' or " "private tabs? ](https://support.torproject.org/tbb/tbb-and-incognito-mode/)" msgstr "" +"* [Care este diferența dintre utilizarea Tor Browser și 'modul incognito' " +"sau filele private? ](https://support.torproject.org/tbb/tbb-and-incognito-" +"mode/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2375,11 +2950,13 @@ msgid "" "* [Does running Tor Browser make me a " "relay?](https://support.torproject.org/tbb/tbb-33/)" msgstr "" +"* [Rularea Tor Browser mă face " +"releu?](https://support.torproject.org/tbb/tbb-33/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) msgid "* [Who funds Tor?](https://support.torproject.org/misc/misc-3/)" -msgstr "" +msgstr "* [Cine finanțează Tor?](https://support.torproject.org/misc/misc-3/)" #: https//community.torproject.org/training/faq/ #: (content/training/faq/contents+en.lrpage.body) @@ -2387,21 +2964,23 @@ msgid "" "* [Is there a backdoor in " "Tor?](https://support.torproject.org/about/backdoor/)" msgstr "" +"* [Există un backdoor în " +"Tor?](https://support.torproject.org/about/backdoor/)" #: https//community.torproject.org/training/resources/ #: (content/training/resources/contents+en.lrpage.title) msgid "Training Resources" -msgstr "" +msgstr "Resurse de instruire" #: https//community.torproject.org/training/resources/ #: (content/training/resources/contents+en.lrpage.cta) msgid "Check out our resources" -msgstr "" +msgstr "Vedeți resursele noastre" #: https//community.torproject.org/training/resources/ #: (content/training/resources/contents+en.lrpage.body) msgid "##Resources" -msgstr "" +msgstr "##Resurse" #: https//community.torproject.org/training/resources/ #: (content/training/resources/contents+en.lrpage.body) @@ -2409,21 +2988,23 @@ msgid "" "Do you teach your community about using Tor? These training resources are " "for you." msgstr "" +"Intenționați să învățati comunitatea dvs. despre utilizarea Tor? Aceste " +"resurse de instruire sunt pentru dvs." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.title) msgid "How do onion services work?" -msgstr "" +msgstr "Cum funcționează serviciile Onion?" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.subtitle) msgid "Learn how onion services work." -msgstr "" +msgstr "Aflați cum funcționează serviciile Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "Onion services are services that can only be accessed over Tor." -msgstr "" +msgstr "Serviciile Onion sunt servicii care pot fi accesate doar prin Tor." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2431,27 +3012,31 @@ msgid "" "Running an onion service gives your users all the security of HTTPS with the" " added privacy benefits of Tor Browser." msgstr "" +"Rularea unui serviciu Onion oferă utilizatorilor dvs. toată securitatea " +"HTTPS, cu beneficiile adăugate de confidențialitate ale Tor Browser." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "## Why onion services?" -msgstr "" +msgstr "## De ce serviciile Onion?" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "" "Onion services offer various privacy and security benefits to their users." msgstr "" +"Serviciile Onion oferă utilizatorilor lor diverse avantaje de " +"confidențialitate și securitate." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Location hiding" -msgstr "" +msgstr "### Ascunderea locației" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "An onion service's IP address is protected." -msgstr "" +msgstr "Adresa IP a unui serviciu Onion este protejată." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2460,11 +3045,14 @@ msgid "" "addresses are not even meaningful to onion services: they are not even used " "in the protocol." msgstr "" +"Serviciile de tip Onion sunt o rețea de suprapunere deasupra TCP/IP, astfel " +"încât, într-un anumit sens, adresele IP nu sunt chiar importante pentru " +"serviciile Onion: nici măcar nu sunt utilizate în protocol." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### End-to-end authentication" -msgstr "" +msgstr "### Autentificare end-to-end" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2472,11 +3060,13 @@ msgid "" "When a user visits a particular onion, they know that the content they are " "seeing can only come from that particular onion." msgstr "" +"Când un utilizator vizitează un sait printr-un serviciu Onion, furnizorii " +"știu că cererea provine doar de la acel serviciu Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "No impersonation is possible, which is generally not the case." -msgstr "" +msgstr "Nu este posibilă nici o răspundere, și, în general, nu este cazul." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2484,31 +3074,33 @@ msgid "" "Usually, reaching a website does not mean that a man-in-the-middle did not " "reroute to some other location (e.g. DNS attacks)." msgstr "" +"De obicei, accesarea unui site web nu înseamnă că un mijlocitor nu s-a " +"reorientat către o altă locație (de exemplu, atacurile DNS)." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### End-to-end encryption" -msgstr "" +msgstr "### Criptare end-to-end" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "Onion service traffic is encrypted from the client to the onion host." -msgstr "" +msgstr "Traficul serviciului Onion este criptat de la client la gazda Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "This is like getting strong SSL/HTTPS for free." -msgstr "" +msgstr "Aceasta este ca și cum ați folosi un SSL/HTTPS puternic și gratuit." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### NAT punching" -msgstr "" +msgstr "### punctarea NAT" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "Is your network filtered and you can't open ports on your firewall?" -msgstr "" +msgstr "Rețeaua dvs. este filtrată și nu puteți deschide porturi pe firewall?" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2516,6 +3108,8 @@ msgid "" "This could happen if you are in a university campus, an office, an airport, " "or pretty much anywhere." msgstr "" +"Acest lucru s-ar putea întâmpla dacă vă aflați într-un campus universitar, " +"un birou, un aeroport sau aproape oriunde." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2523,11 +3117,13 @@ msgid "" "Onion services don't need open ports because they punch through NAT. They " "only establish outgoing connections." msgstr "" +"Serviciile Onion nu au nevoie de porturi deschise, deoarece sunt punctate " +"prin NAT. Ele stabilesc doar conexiunile de ieșire." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "## The Onion Service Protocol: Overview" -msgstr "" +msgstr "## Protocolul Serviciului Onion: Prezentare generală" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2535,6 +3131,8 @@ msgid "" "Now the question becomes **what kind of protocol is needed to achieve all " "these properties?**" msgstr "" +"Acum, apare întrebarea **ce fel de protocol este necesar pentru a atinge " +"toate aceste proprietăți?**" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2542,6 +3140,8 @@ msgid "" "Usually, people connect to an IP address and are done, but how can you " "connect to something that does not have an IP address?" msgstr "" +"De obicei, oamenii se conectează la o adresă IP, dar cum vă puteți conecta " +"la ceva care nu are o adresă IP?" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2549,6 +3149,8 @@ msgid "" "In particular, an onion service's address looks like this: " "`vww6ybal4bd7szmgncyruucpgfkqahzddi37ktceo3ah7ngmcopnpyyd.onion`" msgstr "" +"În special, adresa unui serviciu Onion arată așa: " +"`vww6ybal4bd7szmgncyruucpgfkqahzddi37ktceo3ah7ngmcopnpyyd.onion`" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2556,12 +3158,16 @@ msgid "" "This looks weird and random because it's the _identity public key_ of the " "onion service." msgstr "" +"Acest lucru pare ciudat și aleatoriu, deoarece este _identity public key_ a" +" serviciului Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "" "That's one of the reasons we can achieve the security properties above." msgstr "" +"Acesta este unul dintre motivele pentru care putem realiza proprietățile de " +"securitate de mai sus." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2570,16 +3176,20 @@ msgid "" "can introduce itself to the service (Bob), and then set up a rendezvous " "point with the service over the Tor network." msgstr "" +"Protocolul serviciului Onion folosește rețeaua Tor, astfel încât clientul " +"(Alice) să se poată adăuga la serviciu (Bob), apoi să configureze un punct " +"de întâlnire cu serviciul prin rețeaua Tor." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "Here is a detailed breakdown of how this happens:" -msgstr "" +msgstr "Iată o detaliere a modului în care se întâmplă acest lucru:" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 1: Where the onion service sets up its introduction points" msgstr "" +"### Actul 1: În care serviciul Onion își stabilește punctele de introducere" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2587,6 +3197,8 @@ msgid "" "![Onion Services: Step 1](/static/images/onion-services/overview/tor-onion-" "services-1.png)" msgstr "" +"![Servicii Onion: Pasul 1](/static/images/onion-services/overview/tor-onion-" +"services-1.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2595,6 +3207,9 @@ msgid "" "of Tor relays and asks them to act as his _introduction points_, by " "establishing long-term circuits to them." msgstr "" +"Ca prim pas în protocol, Bob (serviciul Onion) ia legătura cu o mulțime de " +"relee Tor și le cere să acționeze ca puncte ale sale de introducere, prin " +"stabilirea circuitelor lor pe termen lung." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2602,6 +3217,8 @@ msgid "" "These circuits are anonymized circuits, so Bob does not reveal his locations" " to his introduction points." msgstr "" +"Aceste circuite sunt circuite anonimizate, astfel încât Bob nu își dezvăluie" +" locațiile din punctele sale de introducere." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2610,11 +3227,15 @@ msgid "" "\"authentication key\", so that if any clients come for introductions later " "the introduction point can use that key to match them to Bob." msgstr "" +"Ca parte a acestei etape, Bob oferă punctului său de introducere o „cheie de" +" autentificare” specială, astfel încât, dacă unii clienți vin pentru o " +"introducere ulterioară, punctul de introducere poate utiliza această cheie " +"pentru a le potrivi cu Bob." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 2: Where the onion service publishes its descriptors" -msgstr "" +msgstr "### Actul 2: În care serviciul Onion își publică descriptorii" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2622,6 +3243,8 @@ msgid "" "![Onion Services: Step 2](/static/images/onion-services/overview/tor-onion-" "services-2.png)" msgstr "" +"![Servicii Onion: Pasul 2](/static/images/onion-services/overview/tor-onion-" +"services-2.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2629,6 +3252,8 @@ msgid "" "Now that the introduction points are setup, we need to create a way for " "clients to be able to find them." msgstr "" +"Acum că punctele de introducere sunt configurate, trebuie să creăm o " +"modalitate pentru ca clienții să le poată găsi." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2637,6 +3262,10 @@ msgid "" "list of his introduction points (and their \"authentication keys\"), and " "signs this descriptor with his _identity private key_." msgstr "" +"Din acest motiv, Bob asamblează un descriptor al serviciului, _onion service" +" descriptor_, care conține o listă a punctelor sale de introducere (și " +"„cheile de autentificare” ale acestora) și semnează acest descriptor cu " +"cheia sa privată _identity private key_." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2644,6 +3273,8 @@ msgid "" "The _identity private key_ used here is the private part of the **public key" " that is encoded in the onion service address**." msgstr "" +"Cheia de identitate privată _identity private key_ folosită aici este partea" +" privată a **cheii publice care este codată pe adresa serviciului Onion**." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2651,6 +3282,9 @@ msgid "" "Now, Bob uploads that signed descriptor to a _distributed hash table_ which " "is part of the Tor network, so that clients can also get it." msgstr "" +"Acum, Bob încarcă acel descriptor semnat într-o tabelă de hash distribuită " +"_distributed hash table_ care face parte din rețeaua Tor, astfel încât " +"clienții să o poată obține." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2658,11 +3292,13 @@ msgid "" "Bob uses an anonymized Tor circuit to do this upload, so that he does not " "reveal his location." msgstr "" +"Pentru a face această încărcare, Bob folosește un circuit Tor anonimizat, ca" +" să nu-și dezvăluie locația." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 3: Where a client wants to visit the onion service" -msgstr "" +msgstr "### Actul 3: În care un client dorește să viziteze serviciul Onion" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2670,6 +3306,8 @@ msgid "" "All the previous steps were just setup for the onion service so that it's " "reachable by clients." msgstr "" +"Toate etapele anterioare au fost doar configurarea pentru serviciul Onion, " +"astfel încât acesta să poată fi accesat de clienți." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2677,6 +3315,8 @@ msgid "" "Now let's fast-forward to the point where an actual client wants to visit " "the service:" msgstr "" +"Acum să trecem rapid la punctul în care un client real dorește să viziteze " +"serviciul:" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2684,6 +3324,8 @@ msgid "" "![Onion Services: Step 3](/static/images/onion-services/overview/tor-onion-" "services-3.png)" msgstr "" +"![Servicii Onion: Pasul 3](/static/images/onion-services/overview/tor-onion-" +"services-3.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2691,6 +3333,8 @@ msgid "" "In this case, Alice (the client) has the onion address of Bob and she wants " "to visit it, so she connects to it with her Tor Browser." msgstr "" +"În acest caz, Alice (clientul) are adresa Onion a lui Bob și vrea să o " +"viziteze, așa că se conectează la ea cu Tor Browser." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2699,6 +3343,9 @@ msgid "" "_distributed hash table_ from the step above, and ask for the signed " "descriptor of Bob." msgstr "" +"Acum, următorul lucru care se petrece este că Alice merge la tabelul " +"_distributed hash table_ de la pasul de mai sus și cere descriptorul semnat " +"de Bob." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2706,6 +3353,8 @@ msgid "" "When Alice receives the signed descriptor, she verifies the signature of the" " descriptor using the public key that is encoded in the onion address." msgstr "" +"Când Alice primește descriptorul semnat, verifică semnătura descriptorului " +"folosind cheia publică care este codată pe adresa Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2714,6 +3363,9 @@ msgid "" "are now sure that this descriptor could only be produced by Bob and no one " "else." msgstr "" +"Aceasta oferă proprietatea de siguranță _end-to-end authentication_, " +"deoarece suntem siguri că acest descriptor ar putea fi produs doar de Bob și" +" de nimeni altcineva." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2721,11 +3373,13 @@ msgid "" "And inside the descriptor there are the introduction points which allow " "Alice to introduce herself to Bob." msgstr "" +"În interiorul descriptorului există puncte de introducere care îi permit lui" +" Alice să se prezinte lui Bob." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 4: Where the client establishes a rendezvous point" -msgstr "" +msgstr "### Actul 4: În care clientul stabilește un punct de întâlnire" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2733,6 +3387,8 @@ msgid "" "Now before the introduction takes place, Alice picks a Tor relay and " "establishes a circuit to it." msgstr "" +"Acum, înainte de a avea loc introducerea, Alice alege un releu Tor și îi " +"stabilește un circuit." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2740,11 +3396,14 @@ msgid "" "Alice asks the relay to become her _rendezvous point_ and gives it an \"one-" "time secret\" that will be used as part of the rendezvous procedure." msgstr "" +"Alice solicită releului să devină punctul său de întâlnire _rendezvous " +"point_ și îi oferă un „secret unic” care va fi folosit ca parte a procedurii" +" de întâlnire." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 5: Where the client introduces itself to the onion service" -msgstr "" +msgstr "### Actul 5: În care clientul se prezintă la serviciul Onion" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2752,6 +3411,8 @@ msgid "" "![Onion Services: Step 4](/static/images/onion-services/overview/tor-onion-" "services-4.png)" msgstr "" +"![Servicii Onion: Pasul 4](/static/images/onion-services/overview/tor-onion-" +"services-4.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2759,6 +3420,8 @@ msgid "" "Now, Alice goes ahead and connects to one of Bob's introduction points and " "introduces herself to Bob." msgstr "" +"Acum, Alice merge și se conectează la unul dintre punctele de introducere " +"ale lui Bob și se prezintă la Bob." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2766,11 +3429,13 @@ msgid "" "Through this introduction Bob learns Alice's choice of rendezvous point and " "the \"one-time secret\"." msgstr "" +"Prin această introducere, Bob învață alegerea lui Alice despre punctul de " +"întâlnire și „secretul unic”." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 6: Where the onion service rendezvous with the client" -msgstr "" +msgstr "### Actul 6: În care serviciul Onion se întâlnește cu clientul" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2778,6 +3443,8 @@ msgid "" "![Onion Services: Step 5](/static/images/onion-services/overview/tor-onion-" "services-5.png)" msgstr "" +"![Servicii Onion: Pasul 5](/static/images/onion-services/overview/tor-onion-" +"services-5.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2785,6 +3452,8 @@ msgid "" "In this last act, the onion service is now aware of Alice's rendezvous " "point." msgstr "" +"În acest ultim act, serviciul Onion este acum conștient de punctul de " +"întâlnire al lui Alice." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2792,6 +3461,8 @@ msgid "" "The onion service connects to the rendezvous point (through an anonymized " "circuit) and sends the \"one-time secret\" to it." msgstr "" +"Serviciul Onion se conectează la punctul de întâlnire (printr-un circuit " +"anonimizat) și îi trimite „secretul unic”." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2800,6 +3471,9 @@ msgid "" "informs Alice that the connection has been **successfuly completed**, and " "now Alice and Bob can use this circuit to communicate with each other." msgstr "" +"La punctul de întâlnire care primește „secretul unic” de la Bob, acesta o " +"informează pe Alice că conexiunea a fost **finalizată cu succes**, iar acum " +"Alice și Bob pot folosi acest circuit pentru a comunica între ei." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2807,6 +3481,8 @@ msgid "" "The rendezvous point simply relays (end-to-end encrypted) messages from " "client to service and vice versa." msgstr "" +"Punctul de întâlnire transmite pur și simplu mesaje (criptate de la un capăt" +" la celălalt) de la client la serviciu și invers." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2815,11 +3491,15 @@ msgid "" "consists of 6 relays: 3 of them were picked by the client with the third " "being the rendezvous point and the other 3 were picked by the onion service." msgstr "" +"În general, conexiunea completă între client și serviciul Onion constă din 6" +" relee: 3 dintre ele au fost alese de client, al treilea fiind punctul de " +"întâlnire, iar celelalte 3 au fost selectate de serviciul Onion." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "This provides _location hiding_ to this connection:" msgstr "" +"Aceasta oferă ascunderea locației _location hiding_ la această conexiune:" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2827,11 +3507,13 @@ msgid "" "![Onion Services: Step 6](/static/images/onion-services/overview/tor-onion-" "services-6.png)" msgstr "" +"![Servicii Onion: Pasul 6](/static/images/onion-services/overview/tor-onion-" +"services-6.png)" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "## Further resources" -msgstr "" +msgstr "## Resurse suplimentare" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) @@ -2839,51 +3521,54 @@ msgid "" "This was just a high-level overview of the Tor onion services protocol. Here" " are some more resources if you want to learn more:" msgstr "" +"Aceasta a fost doar o imagine de ansamblu la nivel înalt a protocolului " +"serviciilor Onion Tor. Iată câteva resurse suplimentare dacă doriți să " +"aflați mai multe:" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "- The original Tor design paper describing the original design:" -msgstr "" +msgstr "- Lucrarea originală de design Tor care descrie designul original:" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf" -msgstr "" +msgstr "https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "- The Tor v3 onion services protocol specification." -msgstr "" +msgstr "- Specificația protocolului serviciilor Onion Tor v3." #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt" -msgstr "" +msgstr "https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "- Presentations about onion services" -msgstr "" +msgstr "- Prezentări ale serviciilor Onion" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "https://www.youtube.com/watch?v=VmsFxBEN3fc" -msgstr "" +msgstr "https://www.youtube.com/watch?v=VmsFxBEN3fc" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "https://www.youtube.com/watch?v=Di7qAVidy1Y" -msgstr "" +msgstr "https://www.youtube.com/watch?v=Di7qAVidy1Y" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.title) msgid "Set up Your Onion Service" -msgstr "" +msgstr "Configurarea serviciului Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.subtitle) msgid "Learn how to set up a .onion site of your very own." -msgstr "" +msgstr "Aflați cum puteți configura un site .onion." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.cta) @@ -2894,11 +3579,13 @@ msgstr "Începeți" #: (content/onion-services/setup/contents+en.lrpage.body) msgid "This guide shows you how to set up an onion service for your website." msgstr "" +"Acest ghid vă arată cum puteți configura un serviciu Onion pentru site-ul " +"dvs. web." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 0: Get a working Tor" -msgstr "" +msgstr "## Pasul 0: Luați un Tor pentru lucru" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2907,6 +3594,10 @@ msgid "" "machine. Tor should be up and running correctly for this guide to work. You " "should also know where Tor's configuration files are." msgstr "" +"Ca parte a acestui ghid, vom presupune că aveți un Tor funcțional pe " +"computer. Tor ar trebui să funcționeze corect pentru ca să funcționeze și " +"acest ghid. De asemenea, ar trebui să știți unde sunt fișierele de " +"configurare ale lui Tor." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2917,11 +3608,17 @@ msgid "" "/tor-doc-osx.html.en), and Linux/BSD/Unix users should follow the [Unix " "howto](https://2019.www.torproject.org/docs/tor-doc-unix.html.en)." msgstr "" +"Pentru a configura Tor, utilizatorii Windows pot urmări [modul de lucrul în " +"Windows] (https://2019.www.torproject.org/docs/tor-doc-windows.html.en) " +"utilizatorii OS X ar trebui să urmeze etapele descrise în [mod de lucru în " +"OS X] (https://2019.www.torproject.org/docs/tor-doc-osx.html.en) iar " +"utilizatorii Linux / BSD / Unix ar trebui să urmeze pașii din [mod de lucru" +" în Unix] (https://2019.www.torproject.org/docs/tor-doc-unix.html.en)" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 1: Get a web server working" -msgstr "" +msgstr "## Pasul 1: Folosiți un server web funcțional" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2929,6 +3626,8 @@ msgid "" "As a first step you should setup a web server locally, like nginx or " "lighttpd. Setting up a web server can be complex." msgstr "" +"Ca prim pas, ar trebui să configurați un server web local, cum ar fi nginx " +"sau lighttpd. Configurarea unui server web poate fi complexă." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2936,12 +3635,16 @@ msgid "" "We're not going to cover how to set up a web server here. If you get stuck " "or want to do more, find a friend who can help you." msgstr "" +"Aici nu vom descrie modul de configurare a unui server web. Dacă vă blocați " +"sau doriți să faceți mai multe, găsiți un prieten care vă poate ajuta." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "" "We recommend you install a new separate web server for your onion service." msgstr "" +"Vă recomandăm să instalați un nou server web separat pentru serviciul dvs. " +"Onion." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2949,6 +3652,8 @@ msgid "" "You need to configure your web server so it doesn't give away any " "information about you, your computer, or your location." msgstr "" +"Trebuie să configurați serverul dvs. web, astfel încât să nu ofere " +"informații despre dvs., despre computer sau despre locația dvs." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2956,6 +3661,9 @@ msgid "" "This is not an easy task and in the end of this document we will offer more " "resources on how to make this possible." msgstr "" +"Aceasta nu este o sarcină ușoară și în finalul acestui document vom oferi " +"mai multe resurse cu privire la modul în care se poate face posibil acest " +"lucru." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2964,6 +3672,10 @@ msgid "" " to http://localhost:8080/, where 8080 is the webserver port you chose " "during setup (you can choose any port, 8080 is just an example)." msgstr "" +"După ce serverul dvs. web este configurat, asigurați-vă că funcționează: " +"deschideți browserul dvs. și accesați la http://localhost:8080/, unde 8080 " +"este portul webserver pe care l-ați ales în timpul configurării (puteți " +"alege orice port, 8080 este doar un exemplu )." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2971,11 +3683,13 @@ msgid "" "Then try putting a file in the main html directory, and make sure it shows " "up when you access the site." msgstr "" +"Apoi încercați să introduceți un fișier în directorul html principal și " +"asigurați-vă că acesta apare atunci când accesați site-ul." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 2: Configure your Tor onion service" -msgstr "" +msgstr "## Pasul 2: Configurați serviciul Tor Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2983,6 +3697,9 @@ msgid "" "The next step is opening the config file of Tor (torrc) and doing the " "appropriate configurations to setup an onion service." msgstr "" +"Următorul pas este deschiderea fișierului de configurare al Tor (torrc) și " +"efectuarea configurațiilor corespunzătoare pentru a configura un serviciu " +"Onion." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -2990,21 +3707,23 @@ msgid "" "Depending on your operating system and setup, your Tor configuration file " "can be at a different location or look different." msgstr "" +"În funcție de sistemul de operare și configurare, fișierul dvs. de " +"configurare Tor poate fi într-o locație diferită sau să arate diferit." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "You will need to put the following two lines in your torrc:" -msgstr "" +msgstr "Va trebui să introduceți următoarele două linii în torrc:" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "HiddenServiceDir /var/lib/tor/hidden_service/" -msgstr "" +msgstr "HiddenServiceDir /var/lib/tor/hidden_service/" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "HiddenServicePort 80 127.0.0.1:8080" -msgstr "" +msgstr "HiddenServicePort 80 127.0.0.1:8080" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3012,6 +3731,8 @@ msgid "" "The `HiddenServiceDir` line specifies the directory which should contain " "information and cryptographic keys for your onion service." msgstr "" +"Linia `HiddenServiceDir` specifică directorul care ar trebui să conțină " +"informații și chei criptografice pentru serviciul dvs. Onion." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3020,6 +3741,8 @@ msgid "" " actual directory that is readable/writeable by the user that will be " "running Tor." msgstr "" +"Aici schimbați linia `HiddenServiceDir`, astfel încât să indice un director " +"real care poate fi citit/scris de către utilizatorul care va rula Tor." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3030,16 +3753,21 @@ msgid "" "should be redirected to `127.0.0.1:8080` (which is where the web server from" " step 1 is listening)." msgstr "" +"Linia „HiddenServicePort” specifică un _virtual port_ (adică portul pe care" +" îl vor folosi persoanele care vizitează serviciul dvs. Onion), iar în cazul" +" de mai sus, spune că orice trafic care intră în portul 80 al serviciului " +"dvs. Onion trebuie redirecționat către `127.0.0.1: 8080` (care este locul în" +" care ascultă serverul web de la pasul 1)." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 3: Restart Tor and check that it worked" -msgstr "" +msgstr "## Pasul 3: Reporniți Tor și verificați dacă funcționează" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "Now save your `torrc` and restart Tor." -msgstr "" +msgstr "Acum salvați „torrc” și reporniți Tor." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3047,6 +3775,8 @@ msgid "" "If Tor starts up again, great. Otherwise, something is wrong. First look at " "your logfiles for hints." msgstr "" +"Dacă Tor pornește din nou, este grozav. În caz contrar, ceva nu este în " +"regulă. Mai întâi, consultați fișierele dvs. de jurnal pentru indicii." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3054,6 +3784,8 @@ msgid "" "It will print some warnings or error messages. That should give you an idea " "what went wrong." msgstr "" +"Va imprima unele avertismente sau mesaje de eroare. Asta ar trebui să vă dea" +" o idee despre ce a mers prost." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3061,11 +3793,13 @@ msgid "" "When Tor starts, it will automatically create the `HiddenServiceDir` that " "you specified (if necessary). Make sure this is the case." msgstr "" +"Când Tor se deschide, va crea automat `HiddenServiceDir` pe care l-ați " +"specificat (dacă este necesar). Asigurați-vă că este creat." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 4: Test that your onion service works" -msgstr "" +msgstr "## Pasul 4: Testați dacă funcționează serviciul dvs. Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3073,6 +3807,8 @@ msgid "" "Now to get your onion service address, go to your `HiddenServiceDir` " "directory, and find a file named `hostname`." msgstr "" +"Acum pentru a obține adresa serviciului Onion, accesați directorul dvs. " +"„HiddenServiceDir` și găsiți un fișier numit` hostname`." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3080,6 +3816,8 @@ msgid "" "The `hostname` file in your hidden service configuration directory contains " "the hostname for your new onion v3 hidden service." msgstr "" +"Fișierul `hostname` din directorul dvs. de configurare a serviciului ascuns " +"conține numele gazdei pentru noul dvs. serviciu ascuns onion v3." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3087,6 +3825,8 @@ msgid "" "The other files are your hidden service keys, so it is imperative that these" " are kept private." msgstr "" +"Celelalte fișiere sunt cheile dvs. de serviciu ascunse, așa că este " +"obligatoriu ca acestea să fie păstrate private." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3094,6 +3834,8 @@ msgid "" "If your keys leak, other people can impersonate your onion service, deeming " "it compromised, useless, and dangerous to visit." msgstr "" +"Dacă cheile sunt aflate, alte persoane vă pot folosi serviciul Onion, iar " +"acesta devine compromis, inutil și periculos de vizitat." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3101,6 +3843,8 @@ msgid "" "Now you can connect to your onion service using Tor Browser, and you should " "get the html page you setup back in step 1." msgstr "" +"Acum vă puteți conecta la serviciul Onion folosind Tor Browser și ar trebui " +"să obțineți pagina html pe care ați configurat-o la pasul 1." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3108,16 +3852,18 @@ msgid "" "If it doesn't work, look in your logs for some hints, and keep playing with " "it until it works." msgstr "" +"Dacă nu funcționează, căutați în jurnalele dvs. câteva indicii și continuați" +" să le examinați până când Tor funcționează." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "## Step 5: More advanced tips" -msgstr "" +msgstr "## Pasul 5: Sfaturi mai avansate" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "The above guide is just a baseline to setup an onion service." -msgstr "" +msgstr "Ghidul de mai sus descrie pe scurt configurarea unui serviciu Onion." #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3125,11 +3871,13 @@ msgid "" "In this section we will offer more resources to better configure and protect" " your onion service:" msgstr "" +"În această secțiune, vom oferi mai multe resurse pentru a vă configura și " +"proteja mai bine serviciul Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "- Best practices for onion services" -msgstr "" +msgstr "- Cele mai bune practici pentru serviciile Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) @@ -3137,31 +3885,33 @@ msgid "" "https://riseup.net/el/security/network-security/tor/onionservices-best-" "practices" msgstr "" +"https://riseup.net/el/security/network-security/tor/onionservices-best-" +"practices" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "- More advanced tips for onion services" -msgstr "" +msgstr "- Sfaturi mai avansate pentru serviciile Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "https://2019.www.torproject.org/docs/tor-onion-service.html.en#three" -msgstr "" +msgstr "https://2019.www.torproject.org/docs/tor-onion-service.html.en#three" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "- Advanced onion service security" -msgstr "" +msgstr "- Securitate avansată a serviciului Onion" #: https//community.torproject.org/onion-services/setup/ #: (content/onion-services/setup/contents+en.lrpage.body) msgid "https://blog.torproject.org/announcing-vanguards-add-onion-services" -msgstr "" +msgstr "https://blog.torproject.org/announcing-vanguards-add-onion-services" #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.title) msgid "Current Status of Translations" -msgstr "" +msgstr "Starea actuală a traducerilor" #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.subtitle) @@ -3169,6 +3919,8 @@ msgid "" "Not sure where to start? Here you can find an overview of the current " "localization status for all of the different Tor Project projects." msgstr "" +"Nu sunteți sigur de unde să începeți? Aici puteți găsi o imagine de ansamblu" +" asupra stării de localizare actuale pentru toate proiecte Tor Project." #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) @@ -3178,6 +3930,10 @@ msgid "" "the translations are finished, you are still welcome to help us with these " "languages." msgstr "" +"Avem câteva traduceri foarte bune, cu o serie de participanți activi și " +"dedicați (ca franceză, spaniolă, rusă, portugheză). Chiar și după terminarea" +" traducerilor, sunteți încă binevenit să ne ajutați cu revizuirea acestori " +"traduceri." #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) @@ -3186,6 +3942,9 @@ msgid "" "by fewer people around the world, but it is still critical that we improve " "access to Tor for people who do not speak English." msgstr "" +"Traducerile noastre sunt incomplete pentru multe limbi. S-ar putea să fie " +"vorbite de mai puține persoane din întreaga lume, dar este totuși esențial " +"să îmbunătățim accesul la Tor pentru persoanele care nu vorbesc engleză." #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) @@ -3193,6 +3952,8 @@ msgid "" "Please consider [helping with translations](/localization/becoming-tor-" "translator/) in your native language." msgstr "" +"Vă rugăm să luați în considerare acest aspect, [ajutând cu traduceri] " +"(/localization/becoming-tor-translator/) în limba dvs. maternă." #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) @@ -3200,13 +3961,15 @@ msgid "" "Right now, we need the most help with Farsi (Persian), Arabic, and Korean. " "But many other languages are being translated, as you can see here:" msgstr "" +"Momentan, avem nevoie de cel mai mare ajutor cu Farsi (persană), arabă și " +"coreeană. Dar multe alte limbi sunt traduse, după cum puteți vedea aici:" #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) #: https//community.torproject.org/localization/pick-a-project/ #: (content/localization/pick-a-project/contents+en.lrpage.body) msgid "<img class=\"col-lg-6\" src=\"../../static/images/localization/stats.png\">" -msgstr "" +msgstr "<img class=\"col-lg-6\" src=\"../../static/images/localization/stats.png\">" #: https//community.torproject.org/localization/current-status/ #: (content/localization/current-status/contents+en.lrpage.body) @@ -3214,6 +3977,9 @@ msgid "" "You can see the open tickets about translation problems on our " "[bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c…." msgstr "" +"Puteți vedea tichetele deschise despre problemele noastre de traducere pe " +"[bugtracker] " +"(https://trac.torproject.org/projects/tor/query?status=!closed&component=Com…)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.title) @@ -3227,11 +3993,14 @@ msgid "" "third-party translation platform. Learn how to sign up and begin " "contributing." msgstr "" +"Eforturile noastre de localizare se petrec în Localization Lab Hub pe " +"Transifex, o platformă de traduceri terță parte. Aflați cum să vă înscrieți " +"și să începeți să contribuiți." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "Thank you for your interest in helping us with translations." -msgstr "" +msgstr "Vă mulțumim pentru interesul dvs. de a ne ajuta cu traduceri." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3240,6 +4009,9 @@ msgid "" "Hub](https://www.localizationlab.org/) on Transifex, a third-party " "translation platform." msgstr "" +"Eforturile noastre de localizare sunt găzduite în [Localization Lab Hub] " +"(https://www.localizationlab.org/) pe Transifex, o platformă de traducere " +"terță parte." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3249,11 +4021,15 @@ msgid "" " page includes guidelines, resources, and priorities that will help you make" " the most out of your contribution." msgstr "" +"Înainte de a traduce, citiți pagina Proiectului Tor din [Localizare Lab " +"Wiki] (https://wiki.localizationlab.org/index.php/Tor) Pagina include " +"ghiduri, resurse și priorități care vă vor ajuta să profitați la maximum de " +"contribuția dvs." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "### Localization mailing list" -msgstr "" +msgstr "### Lista de e-mail pentru localizare" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3263,6 +4039,10 @@ msgid "" "organize translations, participate in our decisions, report errors in source" " strings, etc." msgstr "" +"Sunteți invitat cordial să vă alăturați [listei de distribuție de localizare" +" Tor] (https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n) să " +"organizați traduceri, să participați la deciziile noastre, să raportați " +"erori ale șirurilor din sursă etc." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3270,17 +4050,21 @@ msgid "" "In order to begin contributing you will have to sign up with Transifex. " "Here's an outline of what to expect during that process." msgstr "" +"Pentru a începe să contribuiți, va trebui să vă înscrieți la Transifex. Iată" +" o prezentare la ceea puteți să vă așteptați în timpul acelui proces." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "# Signing Up On Transifex" -msgstr "" +msgstr "# Înregistrare pe Transifex" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "" "1. Head over to the [Transifex signup page](https://transifex.com/signup/)." msgstr "" +"1. Accesați [pagina de înregistrare în " +"Transifex](https://transifex.com/signup/)." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3292,7 +4076,7 @@ msgstr "" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "![Sign up to Transifex](/static/images/localization/tr1.png)" -msgstr "" +msgstr "![Înregistrare în Transifex](/static/images/localization/tr1.png)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3300,16 +4084,20 @@ msgid "" "1. Fill out the next page with your name and select \"Localization\" and " "\"Translator\" from the drop-down menus:" msgstr "" +"1. Completați pagina următoare cu numele dvs. și selectați „Localizare” și " +"„Traducător” din meniurile derulante:" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "![Fill out details](/static/images/localization/tr2.png)" -msgstr "" +msgstr "![Completare detalii](/static/images/localization/tr2.png)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "1. On the next page, select 'Join an existing project' and continue." msgstr "" +"1. În pagina următoare, selectați „Alăturați-vă unui proiect existent” și " +"continuați." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3317,6 +4105,8 @@ msgid "" "1. On the next page, select the languages you speak from the drop-down menu " "and continue." msgstr "" +"1. În pagina următoare, selectați limbile pe care le vorbiți din meniul " +"derulant și continuați." #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) @@ -3324,47 +4114,51 @@ msgid "" "1. You are now signed up! Go to the [Tor Transifex " "page](https://www.transifex.com/otf/torproject/)." msgstr "" +"1. Acum sunteți înscris! Accesați [pagina Tor Transifex] " +"(https://www.transifex.com/otf/torproject/)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "1. Click the blue 'Join Team' button on the far right:" msgstr "" +"1. Faceți clic pe butonul albastru „Alăturați-vă echipei” din partea " +"dreaptă:" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "![Join Team](/static/images/localization/tr3.png)" -msgstr "" +msgstr "![Alăturați-vă echipei](/static/images/localization/tr3.png)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "" "1. Select the language you would like to translate from the dropdown menu:" -msgstr "" +msgstr "1. Selectați limba pe care doriți să o traduceți din meniul derulant:" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "![Choose Language](/static/images/localization/tr4.png)" -msgstr "" +msgstr "![Selectați limba](/static/images/localization/tr4.png)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "1. A notification will now show up on the top of the page like so:" -msgstr "" +msgstr "1. În partea de sus a paginii va apărea o notificare, astfel:" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "![Request Submitted](/static/images/localization/tr5.png)" -msgstr "" +msgstr "![Cerere trimisă](/static/images/localization/tr5.png)" #: https//community.torproject.org/localization/becoming-tor-translator/ #: (content/localization/becoming-tor-translator/contents+en.lrpage.body) msgid "After your membership is approved, you're ready to begin." -msgstr "" +msgstr "După aprobarea înscrierii dvs., sunteți gata să începeți." #: https//community.torproject.org/localization/pick-a-project/ #: (content/localization/pick-a-project/contents+en.lrpage.title) msgid "Pick a project" -msgstr "" +msgstr "Alegeți un proiect" #: https//community.torproject.org/localization/pick-a-project/ #: (content/localization/pick-a-project/contents+en.lrpage.subtitle)

1 0

[tor/master] Add changes file
by asn＠torproject.org 16 Dec '19

16 Dec '19

commit e01e199005f5d1157f9a91a9d7e4591ada0869e7 Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Wed Dec 11 13:38:00 2019 -0800 Add changes file --- changes/ticket28804 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/changes/ticket28804 b/changes/ticket28804 new file mode 100644 index 000000000..9c4eb4776 --- /dev/null +++ b/changes/ticket28804 @@ -0,0 +1,5 @@ + o Major features (documentation): + - Provide a Circuit Padding Framework quickstart guide and developer + documentation for researchers to implement and study Circuit Padding + machines. Closes ticket 28804. +

1 0

[tor/master] Add circuit padding developer and quickstart docs.
by asn＠torproject.org 16 Dec '19

16 Dec '19

commit 981350815dfd3f7f7a91eb6cf3f2cbcc9e93a729 Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Thu Aug 15 15:35:06 2019 -0500 Add circuit padding developer and quickstart docs. --- doc/HACKING/CircuitPaddingDevelopment.md | 1230 ++++++++++++++++++++++++++++++ doc/HACKING/CircuitPaddingQuickStart.md | 263 +++++++ 2 files changed, 1493 insertions(+) diff --git a/doc/HACKING/CircuitPaddingDevelopment.md b/doc/HACKING/CircuitPaddingDevelopment.md new file mode 100644 index 000000000..a0dee68e9 --- /dev/null +++ b/doc/HACKING/CircuitPaddingDevelopment.md @@ -0,0 +1,1230 @@ +# Circuit Padding Developer Documentation + +This document is written for researchers who wish to prototype and evaluate circuit-level padding defenses in Tor. + +Written by Mike Perry and George Kadianakis. + +# Table of Contents + +- [0. Background](#0-background) +- [1. Introduction](#1-introduction) + - [1.1. System Overview](#11-system-overview) + - [1.2. Layering Model](#12-layering-model) + - [1.3. Computation Model](#13-computation-model) + - [1.4. Deployment Constraints](#14-other-deployment-constraints) +- [2. Creating New Padding Machines](#2-creating-new-padding-machines) + - [2.1. Registering a New Padding Machine](#21-registering-a-new-padding-machine) + - [2.2. Machine Activation and Shutdown](#22-machine-activation-and-shutdown) +- [3. Specifying Padding Machines](#3-specifying-padding-machines) + - [3.1. Padding Machine States](#31-padding-machine-states) + - [3.2. Padding Machine State Transitions](#32-padding-machine-state-transitions) + - [3.3. Specifying Per-State Padding](#33-specifying-per-state-padding) + - [3.4. Specifying Precise Cell Counts](#34-specifying-precise-cell-counts) + - [3.5. Specifying Overhead Limits](#35-specifying-overhead-limits) +- [4. Evaluating Padding Machines](#4-evaluating-padding-machines) + - [4.1. Pure Simulation](#41-pure-simulation) + - [4.2. Testing in Chutney](#42-testing-in-chutney) + - [4.3. Testing in Shadow](#43-testing-in-shadow) + - [4.4. Testing on the Live Network](#44-testing-on-the-live-network) +- [5. Example Padding Machines](#5-example-padding-machines) + - [5.1. Deployed Circuit Setup Machines](#51-deployed-circuit-setup-machines) + - [5.2. Adaptive Padding Early](#52-adaptive-padding-early) + - [5.3. Sketch of Tamaraw](#53-sketch-of-tamaraw) + - [5.4. Other Padding Machines](#54-other-padding-machines) +- [6. Framework Implementation Details](#6-framework-implementation-details) + - [6.1. Memory Allocation Conventions](#61-memory-allocation-conventions) + - [6.2. Machine Application Events](#62-machine-application-events) + - [6.3. Internal Machine Events](#63-internal-machine-events) +- [7. Future Features and Optimizations](#7-future-features-and-optimizations) + - [7.1. Load Balancing and Flow Control](#71-load-balancing-and-flow-control) + - [7.2. Timing and Queuing Optimizations](#72-timing-and-queuing-optimizations) + - [7.3. Better Machine Negotiation](#73-better-machine-negotiation) + - [7.4. Probabilistic State Transitions](#74-probabilistic-state-transitions) + - [7.5. More Complex Pattern Recognition](#75-more-complex-pattern-recognition) +- [8. Open Research Problems](#8-open-research-problems) + - [8.1. Onion Service Circuit Setup](#81-onion-service-circuit-setup) + - [8.2. Onion Service Fingerprinting](#82-onion-service-fingerprinting) + - [8.3. Open World Fingerprinting](#83-open-world-fingerprinting) + - [8.4. Protocol Usage Fingerprinting](#84-protocol-usage-fingerprinting) + - [8.5. Datagram Transport Side Channels](#85-datagram-transport-side-channels) +- [9. Must Read Papers](#9-must-read-papers) + + +## 0. Background + +Tor supports both connection-level and circuit-level padding, and both +systems are live on the network today. The connection-level padding behavior +is described in [section 2 of +padding-spec.txt](https://github.com/torproject/torspec/blob/master/padding-spec.txt#L47). The +circuit-level padding behavior is described in [section 3 of +padding-spec.txt](https://github.com/torproject/torspec/blob/master/padding-spec.txt#L282). + +These two systems are orthogonal and should not be confused. The +connection-level padding system is only active while the TLS connection is +otherwise idle. Moreover, it regards circuit-level padding as normal data +traffic, and hence while the circuit-level padding system is actively padding, +the connection-level padding system will not add any additional overhead. + +While the currently deployed circuit-level padding behavior is quite simple, +it is built on a flexible framework. This framework supports the description +of event-driven finite state machine by filling in fields of a simple C +structure, and is designed to support any delay-free statistically shaped +cover traffic on individual circuits, with cover traffic flowing to and from a +node of the implementor's choice (Guard, Middle, Exit, Rendezvous, etc). + +This class of system was first proposed in +[Timing analysis in low-latency mix networks: attacks and defenses](https://www.freehaven.net/anonbib/cache/ShWa-Timing06.pdf) +by Shmatikov and Wang, and extended for the website traffic fingerprinting +domain by Juarez et al. in +[Toward an Efficient Website Fingerprinting Defense](http://arxiv.org/pdf/1512.00524). The +framework also supports fixed parameterized probability distributions, as +used in [APE](https://www.cs.kau.se/pulls/hot/thebasketcase-ape/) by Tobias +Pulls, and many other features. + +This document describes how to use Tor's circuit padding framework to +implement and deploy novel delay-free cover traffic defenses. + +## 1. Introduction + +The circuit padding framework is the official way to implement padding +defenses in Tor. It may be used in combination with application-layer +defenses, and/or obfuscation defenses, or on its own. + +Its current design should be enough to deploy most defenses without +modification, but you can extend it to [provide new +features](#7-future-features-and-optimizations) as well. + +### 1.1. System Overview + +Circuit-level padding can occur between Tor clients and relays at any hop of +one of the client's circuits. Both parties need to support the same padding +mechanisms for the system to work, and the client must enable it. + +We added a padding negotiation relay cell to the Tor protocol that clients use +to ask a relay to start padding, as well as a torrc directive for researchers +to pin their clients' relay selection to the subset of Tor nodes that +implement their custom defenses, to support ethical live network testing and +evaluation. + +Circuit-level padding is performed by 'padding machines'. A padding machine is +a finite state machine. Every state specifies a different form of +padding style, or stage of padding, in terms of inter-packet timings and total +packet counts. + +Padding state machines are specified by filling in fields of a C structure, +which specifies the transitions between padding states based on various events, +probability distributions of inter-packet delays, and the conditions under +which padding machines should be applied to circuits. + +This compact C structure representation is designed to function as a +microlanguage, which can be compiled down into a +bitstring that [can be tuned](#13-computation-model) using various +optimization methods (such as gradient descent, GAs, or GANs), either in +bitstring form or C struct form. + +The event driven, self-contained nature of this framework is also designed to +make [evaluation](#4-evaluating-padding-machines) both expedient and rigorously +reproducible. + +This document covers the engineering steps to write, test, and deploy a +padding machine, as well as how to extend the framework to support new machine +features. + +If you prefer to learn by example, you may want to skip to either the +[QuickStart Guide](CircuitPaddingQuickStart.md), and/or [Section +5](#5-example-padding-machines) for example machines to get you up and running +quickly. + +### 1.2. Layering Model + +The circuit padding framework is designed to provide one layer in a layered +system of interchangeable components. + +The circuit padding framework operates at the Tor circuit layer. It only deals +with the inter-cell timings and quantity of cells sent on a circuit. It can +insert cells on a circuit in arbitrary patterns, and in response to arbitrary +conditions, but it cannot delay cells. It also does not deal with packet +sizes, how cells are packed into TLS records, or ways that the Tor protocol +might be recognized on the wire. + +The problem of differentiating Tor traffic from non-Tor traffic based on +TCP/TLS packet sizes, initial handshake patterns, and DPI characteristics is the +domain of [pluggable +transports](https://trac.torproject.org/projects/tor/wiki/doc/AChildsGardenOfPluggableTransports), +which may optionally be used in conjunction with this framework (or without +it). + +This document focuses primarily on the circuit padding framework's cover +traffic features, and will only briefly touch on the potential obfuscation and +application layer coupling points of the framework. Explicit layer coupling +points can be created by adding either new [machine application +events](#62-machine-application-events) or new [internal machine +events](#63-internal-machine-events) to the circuit padding framework, so that +your padding machines can react to events from other layers. + +### 1.3. Computation Model + +The circuit padding framework is designed to support succinctly specified +defenses that can be tuned through [computer-assisted +optimization](#4-evaluating-padding-machines). + +We chose to generalize the original [Adaptive Padding 2-state +design](https://www.freehaven.net/anonbib/cache/ShWa-Timing06.pdf) into an +event-driven state machine because state machines are the simplest form of +sequence recognition devices from [automata +theory](https://en.wikipedia.org/wiki/Finite-state_machine). + +Most importantly: this framing allows cover traffic defenses to be modeled as +an optimization problem search space, expressed as fields of a C structure +(which is simultaneously a compact opaque bitstring as well as a symbolic +vector in an abstract feature space). This kind of space is particularly well +suited to search by gradient descent, GAs, and GANs. + +When performing this optimization search, each padding machine should have a +fitness function, which will allow two padding machines to be compared for +relative effectiveness. Optimization searches work best if this fitness can be +represented as a single number, for example the total amount by which it +reduces the [Balanced +Accuracy](https://en.wikipedia.org/wiki/Precision_and_recall#Imbalanced_Data) +of an adversary's classifier, divided by an amount of traffic overhead. + +Before you begin the optimization phase for your defense, you should +also carefully consider the [features and +optimizations](#7-future-features-and-optimizations) that we suspect will be +useful, and also see if you can come up with any more. You should similarly be +sure to restrict your search space to avoid areas of the bitstring/feature +vector that you are sure you will not need. For example, some +[applications](#8-open-research-problems) may not need the histogram +accounting used by Adaptive Padding, but might need to add other forms of +[pattern recognition](#75-more-complex-pattern-recognition) to react to +sequences that resemble HTTP GET and HTTP POST. + +### 1.4. Other Deployment Constraints + +The framework has some limitations that are the result of deliberate +choices. We are unlikely to deploy defenses that ignore these limitations. + +In particular, we have deliberately not provided any mechanism to delay actual +user traffic, even though we are keenly aware that if we were to support +additional delay, defenses would be able to have [more success with less +bandwidth +overhead](https://freedom.cs.purdue.edu/anonymity/trilemma/index.html). + +In the website traffic fingerprinting domain, [provably optimal +defenses](https://www.cypherpunks.ca/~iang/pubs/webfingerprint-ccs14.pdf) +achieve their bandwidth overhead bounds by ensuring that a non-empty queue is +maintained, by rate limiting traffic below the actual throughput of a circuit. +For optimal results, this queue must avoid draining to empty, and yet it +must also be drained fast enough to avoid tremendous queue overhead in fast +Tor relays, which carry hundreds of thousands of circuits simultaneously. + +Unfortunately, Tor's end-to-end flow control is not congestion control. Its +window sizes are currently fixed. This means there is no signal when queuing +occurs, and thus no ability to limit queue size through pushback. This means +there is currently no way to do the fine-grained queue management necessary to +create such a queue and rate limit traffic effectively enough to keep this +queue from draining to empty, without also risking that aggregate queuing +would cause out-of-memory conditions on fast relays. + +It may be possible to create a congestion control algorithm that can support +such fine grained queue management, but this is a [deeply unsolved area of +research](https://lists.torproject.org/pipermail/tor-dev/2018-November/013562.html). + +Even beyond these major technical hurdles, additional latency is also +unappealing to the wider Internet community, for the simple reason that +bandwidth [continues to increase +exponentially](https://ipcarrier.blogspot.com/2014/02/bandwidth-growth-nearly-what-one-would.html) +where as the speed of light is fixed. Significant engineering effort has been +devoted to optimizations that reduce the effect of latency on Internet +protocols. To go against this trend would ensure our irrelevance to the wider +conversation about traffic analysis defenses for low latency Internet protocols. + +On the other hand, through [load +balancing](https://gitweb.torproject.org/torspec.git/tree/proposals/265-load-balancing-with-overhead.txt) +and [circuit multiplexing strategies](https://bugs.torproject.org/29494), we +believe it is possible to add significant bandwidth overhead in the form of +cover traffic, without significantly impacting end-user performance. + +For these reasons, we believe the trade-off should be in favor of adding more +cover traffic, rather than imposing queuing memory overhead and queuing delay. + +As a last resort for narrowly scoped application domains (such as +shaping Tor service-side onion service traffic to look like other websites or +different application-layer protocols), delay *may* be added at the +[application layer](https://petsymposium.org/2017/papers/issue2/paper54-2017-2-source.pd…. +Any additional cover traffic required by such defenses should still be +added at the circuit padding layer using this framework, to provide +engineering efficiency through loose layer coupling and component re-use, as +well as to provide additional gains against [low +resolution](https://github.com/torproject/torspec/blob/master/padding-spec.txt#L47) +end-to-end traffic correlation. + +Because such delay-based defenses will impact performance significantly more +than simply adding cover traffic, they must be optional, and negotiated by +only specific application layer endpoints that want them. This will have +consequences for anonymity sets and base rates, if such traffic shaping and +additional cover traffic is not very carefully constructed. + +In terms of acceptable overhead, because Tor onion services +[currently use](https://metrics.torproject.org/hidserv-rend-relayed-cells.html) +less than 1% of the +[total consumed bandwidth](https://metrics.torproject.org/bandwidth-flags.html) +of the Tor network, and because onion services exist to provide higher +security as compared to Tor Exit traffic, they are an attractive target for +higher-overhead defenses. We encourage researchers to target this use case +for defenses that require more overhead, and/or for the deployment of +optional negotiated application-layer delays on either the server or the +client side. + +## 2. Creating New Padding Machines + +This section explains how to use the existing mechanisms in Tor to define a +new circuit padding machine. We assume here that you know C, and are at +least somewhat familiar with Tor development. For more information on Tor +development in general, see the other files in doc/HACKING/ in a recent Tor +distribution. + +Again, if you prefer to learn by example, you may want to skip to either the +[QuickStart Guide](CircuitPaddingQuickStart.md), and/or [Section +5](#5-example-padding-machines) for example machines to get up and running +quickly. + +To create a new padding machine, you must: + + 1. Define your machine using the fields of a heap-allocated + `circpad_machine_spec_t` C structure. + + 2. Register this object in the global list of available padding machines, + using `circpad_register_padding_machine()`. + + 3. Ensure that your machine is properly negotiated under your desired + circuit conditions. + +### 2.1. Registering a New Padding Machine + +Again, a circuit padding machine is designed to be specified entirely as a [single +C structure](#13-computation-model). + +Your machine definitions should go into their own functions in +[circuitpadding_machines.c](https://github.com/torproject/tor/blob/master/src/core/or/circuitpadding_machines.c). For +details on all of the fields involved in specifying a padding machine, see +[Section 3](#3-specifying-padding-machines). + +You must register your machine in `circpad_machines_init()` in +[circuitpadding.c](https://github.com/torproject/tor/blob/master/src/core/or/circuitpadding.c). To +add a new padding machine specification, you must allocate a +`circpad_machine_spec_t` on the heap with `tor_malloc_zero()`, give it a +human readable name string, and a machine number equivalent to the number of +machines in the list, and register the structure using +`circpad_register_padding_machine()`. + +Each machine must have a client instance and a relay instance. Register your +client-side machine instance in the `origin_padding_machines` list, and your +relay side machine instance in the `relay_padding_machines` list. Once you +have registered your instance, you do not need to worry about deallocation; +this is handled for you automatically. + +Both machine lists use registration order to signal machine precedence for a +given `machine_idx` slot on a circuit. This means that machines that are +registered last are checked for activation *before* machines that are +registered first. (This reverse precedence ordering allows us to +deprecate older machines simply by adding new ones after them.) + +### 2.2. Machine Activation and Shutdown + +After a machine has been successfully registered with the framework, it will +be instantiated on any client-side circuits that support it. Only client-side +circuits may initiate padding machines, but either clients or relays may shut +down padding machines. + +#### 2.2.1. Machine Application Conditions + +The +[circpad_machine_conditions_t conditions field](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff… +of your `circpad_machine_spec_t` machine definition instance controls the +conditions under which your machine will be attached and enabled on a Tor +circuit, and when it gets shut down. + +*All* of your explicitly specified conditions in +`circpad_machine_spec_t.conditions` *must* be met for the machine to be +applied to a circuit. If *any* condition ceases to be met, then the machine +is shut down. (This is checked on every event that arrives, even if the +condition is unrelated to the event.) +Another way to look at this is that +all specified conditions must evaluate to true for the entire duration that +your machine is running. If any are false, your machine does not run (or +stops running and shuts down). + +In particular, as part of the +[circpad_machine_conditions_t structure](https://github.com/torproject/tor/blob/master/src/core/or/circui…, +the circuit padding subsystem gives the developer the option to enable a +machine based on: + - The + [length](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399df… + on the circuit (via the `min_hops` field). + - The + [current state](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff… + of the circuit, such as streams, relay_early, etc. (via the + `circpad_circuit_state_t state_mask` field). + - The + [purpose](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399d… + (i.e. type) of the circuit (via the `circpad_purpose_mask_t purpose_mask` + field). + +This condition mechanism is the preferred way to determine if a machine should +apply to a circuit. For information about potentially useful conditions that +we have considered but have not yet implemented, see [Section +7.3](#73-better-machine-negotiation). We will happily accept patches for those +conditions, or any for other additional conditions that are needed for your +use case. + +#### 2.2.2. Detecting and Negotiating Machine Support + +When a new machine specification is added to Tor (or removed from Tor), you +should bump the Padding subprotocol version in `src/core/or/protover.c` and +`src/rust/protover/protover.rs`, add a field to `protover_summary_flags_t` in +`or.h`, and set this field in `memoize_protover_summary()` in versions.c. This +new field must then be checked in `circpad_node_supports_padding()` in +`circuitpadding.c`. + +Note that this protocol version update and associated support check is not +necessary if your experiments will *only* be using your own relays that +support your own padding machines. This can be accomplished by using the +`MiddleNodes` directive; see [Section 4](#4-evaluating-padding-machines) for more information. + +If the protocol support check passes for the circuit, then the client sends a +`RELAY_COMMAND_PADDING_NEGOTIATE` cell towards the +`circpad_machine_spec_t.target_hop` relay, and immediately enables the +padding machine, and may begin sending padding. (The framework does not wait +for the `RELAY_COMMAND_PADDING_NEGOTIATED` response to begin padding, +so that we can +switch between machines rapidly.) + +#### 2.2.3. Machine Shutdown Mechanisms + +Padding machines can be shut down on a circuit in three main ways: + 1. During a `circpad_machine_event` callback, when + `circpad_machine_spec_t.conditions` no longer applies (client side) + 2. After a transition to the CIRCPAD_STATE_END, if + `circpad_machine_spec_t.should_negotiate_end` is set (client or relay + side) + 3. If there is a `RELAY_COMMAND_PADDING_NEGOTIATED` error response from the + relay during negotiation. + +Each of these cases causes the originating node to send a relay cell towards +the other side, indicating that shutdown has occurred. The client side sends +`RELAY_COMMAND_PADDING_NEGOTIATE`, and the relay side sends +`RELAY_COMMAND_PADDING_NEGOTIATED`. + +Because padding from malicious exit nodes can be used to construct active +timing-based side channels to malicious guard nodes, the client checks that +padding-related cells only come from relays with active padding machines. +For this reason, when a client decides to shut down a padding machine, +the framework frees the mutable `circuit_t.padding_info`, but leaves the +`circuit_t.padding_machine` pointer set until the +`RELAY_COMMAND_PADDING_NEGOTIATED` response comes back, to ensure that any +remaining in-flight padding packets are recognized a valid. Tor does +not yet close circuits due to violation of this property, but the +[vanguards addon component "bandguard"](https://github.com/mikeperry-tor/vanguards/blob/master/README_TECHNICAL.md#the-bandguards-subsystem) +does. + +As an optimization, a client may replace a machine with another, by +sending a `RELAY_COMMAND_PADDING_NEGOTIATE` cell to shut down a machine, and +immediately sending a `RELAY_COMMAND_PADDING_NEGOTIATE` to start a new machine +in the same index, without waiting for the response from the first negotiate +cell. + +Unfortunately, there is a known bug as a consequence of this optimization. If +your machine depends on repeated shutdown and restart of the same machine +number on the same circuit, please see [Bug +30922](https://bugs.torproject.org/30992). Depending on your use case, we may +need to fix that bug or help you find a workaround. See also [Section +6.1.3](#613-deallocation-and-shutdown) for some more technical details on this +mechanism. + + +## 3. Specifying Padding Machines + +By now, you should understand how to register, negotiate, and control the +lifetime of your padding machine, but you still don't know how to make it do +anything yet. This section should help you understand how to specify how your +machine reacts to events and adds padding to the wire. + +If you prefer to learn by example first instead, you may wish to skip to +[Section 5](#5-example-padding-machines). + + +A padding machine is specified by filling in an instance of +[circpad_machine_spec_t](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff863bc6fb20a/src/core/or/circuitpadding.h#L605). Instances +of this structure specify the precise functionality of a machine: it's +what the circuit padding developer is called to write. These instances +are created only at startup, and are referenced via `const` pointers during +normal operation. + +In this section we will go through the most important elements of this +structure. + +### 3.1. Padding Machine States + +A padding machine is a finite state machine where each state +specifies a different style of padding. + +As an example of a simple padding machine, you could have a state machine +with the following states: `[START] -> [SETUP] -> [HTTP] -> [END]` where the +`[SETUP]` state pads in a way that obfuscates the ''circuit setup'' of Tor, +and the `[HTTP]` state pads in a way that emulates a simple HTTP session. Of +course, padding machines can be more complicated than that, with dozens of +states and non-trivial transitions. + +Padding developers encode the machine states in the +[circpad_machine_spec_t structure](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab239…. Each +machine state is described by a +[circpad_state_t structure](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab239… +and each such structure specifies the style and amount of padding to be sent, +as well as the possible state transitions. + +The function `circpad_machine_states_init()` must be used for allocating and +initializing the `circpad_machine_spec_t.states` array before states and +state transitions can be defined, as some of the state object has non-zero +default values. + +### 3.2. Padding Machine State Transitions + +As described above, padding machines can have multiple states, to +support different forms of padding. Machines can transition between +states based on events that occur either on the circuit level or on +the machine level. + +State transitions are specified using the +[next_state field](https://github.com/torproject/tor/blob/master/src/core/or/circuitpad… +of the `circpad_state_t` structure. As a simple example, to transition +from state `A` to state `B` when event `E` occurs, you would use the +following code: `A.next_state[E] = B`. + +#### 3.2.1. State Transition Events + +Here we will go through +[the various events](https://github.com/torproject/tor/blob/master/src/core/or/circuitpa… +that can be used to transition between states: + +* Circuit-level events + * `CIRCPAD_EVENT_NONPADDING_RECV`: A non-padding cell is received + * `CIRCPAD_EVENT_NONPADDING_SENT`: A non-adding cell is sent + * `CIRCPAD_EVENT_PADDING_SENT`: A padding cell is sent + * `CIRCPAD_EVENT_PADDING_RECV`: A padding cell is received +* Machine-level events + * `CIRCPAD_EVENT_INFINITY`: Tried to schedule padding using the ''infinity bin''. + * `CIRCPAD_EVENT_BINS_EMPTY`: All histogram bins are empty (out of tokens) + * `CIRCPAD_EVENT_LENGTH_COUNT`: State has used all its padding capacity (see `length_dist` below) + +### 3.3. Specifying Per-State Padding + +Each state of a padding machine specifies either: + * A padding histogram describing inter-transmission delays between cells; +d OR + * A parameterized delay probability distribution for inter-transmission + delays between cells. + +Either mechanism specifies essentially the *minimum inter-transmission time* +distribution. If non-padding traffic does not get transmitted from this +endpoint before the delay value sampled from this distribution expires, a +padding packet is sent. + +The choice between histograms and probability distributions can be subtle. A +rule of thumb is that probability distributions are easy to specify and +consume very little memory, but might not be able to describe certain types +of complex padding logic. Histograms, in contrast, can support precise +packet-count oriented or multimodal delay schemes, and can use token removal +logic to reduce overhead and shape the total padding+non-padding inter-packet +delay distribution towards an overall target distribution. + +We suggest that you start with a probability distribution if possible, and +you move to a histogram-based approach only if a probability distribution +does not suit your needs. + +#### 3.3.1. Padding Probability Distributions + +The easiest, most compact way to schedule padding using a machine state is to +use a probability distribution that specifies the possible delays. That can +be done +[using the circpad_state_t fields](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399df… +`iat_dist`, `dist_max_sample_usec` and `dist_added_shift_usec`. + +The Tor circuit padding framework +[supports multiple types](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff… +of probability distributions, and the developer should use the +[circpad_distribution_t structure](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab239… +to specify them as well as the required parameters. + +#### 3.3.2. Padding Histograms + +A more advanced way to schedule padding is to use a ''padding +histogram''. The main advantages of a histogram are that it allows you to +specify distributions that are not easily parameterized in closed form, or +require specific packet counts at particular time intervals. Histograms also +allow you to make use of an optional traffic minimization and shaping +optimization called *token removal*, which is central to the original +[Adaptive Padding](https://www.freehaven.net/anonbib/cache/ShWa-Timing06.pdf) +concept. + +If a histogram is used by a state (as opposed to a fixed parameterized +distribution), then the developer must use the +[histogram-related fields](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399df… +of the `circpad_state_t` structure. + +The width of a histogram bin specifies the range of inter-packet delay times, +whereas its height specifies the amount of tokens in each bin. To sample a +padding delay from a histogram, we first randomly pick a bin (weighted by the +amount of tokens in each bin) and then sample a delay from within that bin by +picking a uniformly random delay using the width of the bin as the range. + +Each histogram also has an ''infinity bin'' as its final bin. If the +''infinity bin'' is chosen, +we don't schedule any padding (i.e., we schedule padding with +infinite delay). If the developer does not want infinite delay, they +should not give any tokens to the ''infinity bin''. + +If a token removal strategy is specified (via the +`circpad_state_t.token_removal` field), each time padding is sent using a +histogram, the padding machine will remove a token from the appropriate +histogram bin whenever this endpoint sends *either a padding packet or a +non-padding packet*. The different removal strategies govern what to do when +the bin corresponding to the current inter-packet delay is empty. + +Token removal is optional. It is useful if you want to do things like specify +a burst should be at least N packets long, and you only want to add padding +packets if there are not enough non-padding packets. The cost of doing token +removal is additional memory allocations for making per-circuit copies of +your histogram that can be modified. + +### 3.4. Specifying Precise Cell Counts + +Padding machines should be able to specify the exact amount of padding they +send. For histogram-based machines this can be done using a specific amount +of tokens, but another (and perhaps easier) way to do this, is to use the +[length_dist field](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff… +of the `circpad_state_t` structure. + +The `length_dist` field is basically a probability distribution similar to the +padding probability distributions, which applies to a specific machine state +and specifies the amount of padding we are willing to send during that state. +This value gets sampled when we transition to that state (TODO document this +in the code). + +### 3.5. Specifying Overhead Limits + +Separately from the length counts, it is possible to rate limit the overhead +percentage of padding at both the global level across all machines, and on a +per-machine basis. + +At the global level, the overhead percentage of all circuit padding machines +as compared to total traffic can be limited through the Tor consensus +parameter `circpad_global_max_padding_pct`. This overhead is defined as the +percentage of padding cells *sent* out of the sum of non padding and padding +cells *sent*, and is applied *only after* at least +`circpad_global_allowed_cells` padding cells are sent by that relay or client +(to allow for small bursts of pure padding on otherwise idle or freshly +restarted relays). When both of these limits are hit by a relay or client, no +further padding cells will be sent, until sufficient non-padding traffic is +sent to cause the percentage of padding traffic to fall back below the +threshold. + +Additionally, each individual padding machine can rate limit itself by +filling in the fields `circpad_machine_spec_t.max_padding_percent` and +`circpad_machine_spec_t.allowed_padding_count`, which behave identically to +the consensus parameters, but only apply to that specific machine. + +## 4. Evaluating Padding Machines + +One of the goals of the circuit padding framework is to provide improved +evaluation and scientific reproducibility for lower cost. This includes both +the [choice](#13-computation-model) of the compact C structure representation +(which has an easy-to-produce bitstring representation for optimization by +gradient descent, GAs, or GANs), as well as rapid prototyping and evaluation. + +So far, whenever evaluation cost has been a barrier, each research group has +developed their own ad-hoc packet-level simulators of various padding +mechanisms for evaluating website fingerprinting attacks and defenses. The +process typically involves doing a crawl of Alexa top sites over Tor, and +recording the Tor cell count and timing information for each page in the +trace. These traces are then fed to simulations of defenses, which output +modified trace files. + +Because no standardized simulation and evaluation mechanism exists, it is +often hard to tell if independent implementations of various attacks and +defenses are in fact true-to-form or even properly calibrated for direct +comparison, and discrepancies in results across the literature suggests +this is not always so. + +Our preferred outcome with this framework is that machines are tuned +and optimized on a tracing simulator, but that the final results come from +an actual live network test of the defense. The traces from this final crawl +should be preserved as artifacts to be run on the simulator and reproduced +on the live network by future papers, ideally in journal venues that have an +artifact preservation policy. + +### 4.1. Pure Simulation + +When doing initial tuning of padding machines, especially in adversarial +settings, variations of a padding machine defense may need to be applied to +network activity hundreds or even millions of times. The wall-clock time +required to do this kind of tuning using live testing or even Shadow network +emulation may often be prohibitive. + +To help address this, and to better standardize results, Tobias Pulls has +implemented a [circpad machine trace simulator](https://github.com/pylls/circpad-sim), +which uses Tor's unit test framework to simulate applying padding machines to +circuit packet traces via a combination of Tor patches and python scripts. This +simulator can be used to record traces from clients, Guards, Middles, Exits, +and any other hop in the path, only for circuits that are run by the +researcher. This makes it possible to safely record baseline traces and +ultimately even mount passive attacks on the live network, without impacting +or recording any normal user traffic. + +In this way, a live crawl of the Alexa top sites could be performed once, to +produce a standard "undefended" corpus. Padding machines can be then quickly +evaluated and tuned on these simulated traces in a standardized way, and then +the results can then be [reproduced on the live Tor +network](#44-Testing-on-the-Live-Network) with the machines running on your own relays. + +Please be mindful of the Limitations section of the simulator documentation, +however, to ensure that you are aware of the edge cases and timing +approximations that are introduced by this approach. + +### 4.2. Testing in Chutney + +The Tor Project provides a tool called +[Chutney](https://github.com/torproject/chutney/) which makes it very easy to +setup private Tor networks. While getting it work for the first time might +take you some time of doc reading, the final result is well worth it for the +following reasons: + +- You control all the relays and hence you have greater control and debugging + capabilities. +- You control all the relays and hence you can toggle padding support on/off + at will. +- You don't need to be cautious about overhead or damaging the real Tor + network during testing. +- You don't even need to be online; you can do all your testing offline over + localhost. + +A final word of warning here is that since Chutney runs over localhost, the +packet latencies and delays are completely different from the real Tor +network, so if your padding machines rely on real network timings you will +get different results on Chutney. You can work around this by using a +different set of delays if Chutney is used, or by moving your padding +machines to the real network when you want to do latency-related testing. + +### 4.3. Testing in Shadow + +[Shadow](https://shadow.github.io/) is an environment for running entire Tor +network simulations, similar to Chutney, but designed to be both more memory +efficient, as well as provide an accurate Tor network topology and latency +model. + +While Shadow is significantly more memory efficient than Chutney, and can make +use of extremely accurate Tor network capacity and latency models, it will not +be as fast or efficient as the [circpad trace simulator](https://github.com/pylls/circpad-sim), +if you need to do many many iterations of an experiment to tune your defense. + +### 4.4. Testing on the Live Network + +Live network testing is the gold standard for verifying that any attack or +defense is behaving as expected, to minimize the influence of simplifying +assumptions. + +However, it is not ethical, or necessarily possible, to run high-resolution +traffic analysis attacks on the entire Tor network. But it is both ethical +and possible to run small scale experiments that target only your own +clients, who will only use your own Tor relays that support your new padding +machines. + +We provide the `MiddleNodes` torrc directive to enable this, which will allow +you to specify the fingerprints and/or IP netmasks of relays to be used in +the second hop position. Options to restrict other hops also exist, if your +padding system is padding to a different hop. The `HSLayer2Nodes` option +overrides the `MiddleNodes` option for onion service circuits, if both are +set. (The +[vanguards addon](https://github.com/mikeperry-tor/vanguards/README_TECHNICAL.md) +will set `HSLayer2Nodes`.) + +When you run your own clients, and use MiddleNodes to restrict your clients +to use your relays, you can perform live network evaluations of a defense +applied to whatever traffic crawl or activity your clients do. + +## 5. Example Padding Machines + +### 5.1. Deployed Circuit Setup Machines + +Tor currently has two padding machines enabled by default, which aim to hide +certain features of the client-side onion service circuit setup protocol. For +more details on their precise goal and function, please see +[proposal 302](https://github.com/torproject/torspec/blob/master/proposals/302-paddin… +. In this section we will go over the code of those machines to clarify some +of the engineering parts: + +#### 5.1.1. Overview + +The codebase of proposal 302 can be found in +[circuitpadding_machines.c](https://github.com/torproject/tor/blob/master/src/core/or/circuitpadding_machines.c) +and specifies four padding machines: + +- The [client-side introduction](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab… circuit machine. +- The [relay-side introduction](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab… circuit machine. +- The [client-side rendezvous](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab23… circuit machine +- The [relay-side rendezvous](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab23… circuit machine. + +Each of those machines has its own setup function, and +[they are all initialized](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2… +by the circuit padding framework. To understand more about them, please +carefully read the individual setup function for each machine which are +fairly well documented. Each function goes through the following steps: +- Machine initialization + - Give it a [name](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff8… + - Specify [which hop](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399dff86… the padding should go to + - Specify whether it should be [client-side](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2… or relay-side. +- Specify for [which types of circuits](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399… the machine should apply +- Specify whether the circuits should be [kept alive](https://github.com/torproject/tor/blob/master/src/core/or/circuitpad… until the machine finishes padding. +- Sets [padding limits](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399df… to avoid too much overhead in case of bugs or errors. +- Setup [machine states](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399df… + - Specify [state transitions](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2…. +- Finally [register the machine](https://github.com/torproject/tor/blob/35e978da61efa04af9a5ab2399d… to the global machine list + +### 5.2. Adaptive Padding Early + +[Adaptive Padding Early](https://www.cs.kau.se/pulls/hot/thebasketcase-ape/) +is a variant of Adaptive Padding/WTF-PAD that does not use histograms or token +removal to shift padding distributions, but instead uses fixed parameterized +distributions to specify inter-packet timing thresholds for burst and gap +inter-packet delays. + +Tobias Pulls's [QuickStart Guide](CircuitPaddingQuickStart.md) describes how +to get this machine up and running, and has links to branches with a working +implementation. + +### 5.3. Sketch of Tamaraw + +The [Tamaraw defense +paper](https://www.cypherpunks.ca/~iang/pubs/webfingerprint-ccs14.pdf) is the +only defense to date that provides a proof of optimality for the finite-length +website traffic fingerprinting domain. These bounds assume that a defense is +able to perform a full, arbitrary transform of a trace that is under a fixed +number of packets in length. + +The key insight to understand Tamaraw's optimality is that it achieves one +such optimal transform by delaying traffic below a circuit's throughput. By +doing this, it creates a queue that is rarely empty, allowing it to produce +a provably optimal transform with minimal overhead. As [Section +1.4](#14-other-deployment-constraints) explains, this queue +cannot be maintained on the live Tor network without risk of out-of-memory +conditions at relays. + +However, if the queue is not maintained in the Tor network, but instead by the +application layer, it could be deployed by websites that opt in to using it. + +In this case, the application layer component would do *optional* constant +rate shaping, negotiated between a web browser and a website. The Circuit +Padding Framework can then easily fill in any missing gaps of cover traffic +packets, and also ensure that only a fixed length number of packets are sent +in total. + +However, for such a defense to be safe, additional care must be taken to +ensure that the resulting traffic pattern still has a large +anonymity/confusion set with other traces on the live network. + +Accomplishing this is an unsolved problem. + +### 5.4. Other Padding Machines + +Our partners in this project at RIT have produced a couple prototypes, based +on their published research designs +[REB and RBB](https://www.researchgate.net/publication/329743510_UNDERSTANDING_FEATU…. + +As [their writeup +explains](https://github.com/notem/tor-rbp-padding-machine-doc), because RBB +uses delay, the circuit padding machine that they made is a no-delay version. + +They also ran into an issue with the 0-delay timing workaround for [bug +31653](https://bugs.torproject.org/31653). Keep an eye on that bug for updates +with improved workarounds/fixes. + +Their code is [available on github](https://github.com/notem/tor/tree/circuit_padding_rbp_machine). + + +## 6. Framework Implementation Details + +If you need to add additional events, conditions, or other features to the +circuit padding framework, then this section is for you. + +### 6.1. Memory Allocation Conventions + +If the existing circuit padding features are sufficient for your needs, then +you do not need to worry about memory management or pointer lifespans. The +circuit padding framework should take care of this for you automatically. + +However, if you need to add new padding machine features to support your +padding machines, then it will be helpful to understand how circuits +correspond to the global machine definitions, and how mutable padding machine +memory is managed. + +#### 6.1.1. Circuits and Padding Machines + +In Tor, the +[circuit_t structure](https://github.com/torproject/tor/blob/master/src/core/or/circui… +is the superclass structure for circuit-related state that is used on both +clients and relays. On clients, the actual datatype of the object pointed to +by `circuit_t *` is the subclass structure +[origin_circuit_t](https://github.com/torproject/tor/blob/master/src/core/or/origin_circuit_st.h). The +macros `CIRCUIT_IS_ORIGIN()` and `TO_ORIGIN_CIRCUIT()` are used to determine +if a circuit is a client-side (origin) circuit and to cast the pointer safely +to `origin_circuit_t *`. + +Because circuit padding machines can be present at both clients and relays, +the circuit padding fields are stored in the `circuit_t *` superclass +structure. Notice that there are actually two sets of circuit padding fields: +a `const circpad_machine_spec_t *` array, and a `circpad_machine_runtime_t *` +array. Each of these arrays holds at most two elements, as there can be at +most two padding machines on each circuit. + +The `const circpad_machine_spec_t *` points to a globally allocated machine +specification. These machine specifications are +allocated and set up during Tor program startup, in `circpad_machines_init()` +in +[circuitpadding.c](https://github.com/torproject/tor/blob/master/src/core/or/circuitpadding.c). Because +the machine specification object is shared by all circuits, it must not be +modified or freed until program exit (by `circpad_machines_free()`). The +`const` qualifier should enforce this at compile time. + +The `circpad_machine_runtime_t *` array member points to the mutable runtime +information for machine specification at that same array index. This runtime +structure keeps track of the current machine state, packet counts, and other +information that must be updated as the machine operates. When a padding +machine is successfully negotiated `circpad_setup_machine_on_circ()` allocates +the associated runtime information. + +#### 6.1.2. Histogram Management + +If a `circpad_state_t` of a machine specifies a `token_removal` strategy +other than `CIRCPAD_TOKEN_REMOVAL_NONE`, then every time +there is a state transition into this state, `circpad_machine_setup_tokens()` +will copy the read-only `circpad_state_t.histogram` array into a mutable +version at `circpad_machine_runtime_t.histogram`. This mutable copy is used +to decrement the histogram bin accounts as packets are sent, as per the +specified token removal strategy. + +When the state machine transitions out of this state, the mutable histogram copy is freed +by this same `circpad_machine_setup_tokens()` function. + +#### 6.1.3. Deallocation and Shutdown + +As an optimization, padding machines can be swapped in and out by the client +without waiting a full round trip for the relay machine to shut down. + +Internally, this is accomplished by immediately freeing the heap-allocated +`circuit_t.padding_info` field corresponding to that machine, but still preserving the +`circuit_t.padding_machine` pointer to the global padding machine +specification until the response comes back from the relay. Once the response +comes back, that `circuit_t.padding_machine` pointer is set to NULL, if the +response machine number matches the current machine present. + +Because of this partial shutdown condition, we have two macros for iterating +over machines. `FOR_EACH_ACTIVE_CIRCUIT_MACHINE_BEGIN()` is used to iterate +over machines that have both a `circuit_t.padding_info` slot and a +`circuit_t.padding_machine` slot occupied. `FOR_EACH_CIRCUIT_MACHINE_BEGIN()` +is used when we need to iterate over all machines that are either active or +are simply waiting for a response to a shutdown request. + +If the machine is replaced instead of just shut down, then the client frees +the `circuit_t.padding_info`, and then sets the `circuit_t.padding_machine` +and `circuit_t.padding_info` fields for this next machine immediately. This is +done in `circpad_add_matching_machines()`. In this case, since the new machine +should have a different machine number, the shut down response from the relay +is silently discarded, since it will not match the new machine number. + +If this sequence of machine teardown and spin-up happens rapidly enough for +the same machine number (as opposed to different machines), then a race +condition can happen. This is +[known bug #30992](https://bugs.torproject.org/30992). + +When the relay side decides to shut down a machine, it sends a +`RELAY_COMMAND_PADDING_NEGOTIATED` towards the client. If this cell matches the +current machine number on the client, that machine is torn down, by freeing +the `circuit_t.padding_info` slot and immediately setting +`circuit_t.padding_machine` slot to NULL. + +Additionally, if Tor decides to close a circuit forcibly due to error before +the padding machine is shut down, then `circuit_t.padding_info` is still +properly freed by the call to `circpad_circuit_free_all_machineinfos()` +in `circuit_free_()`. + +### 6.2. Machine Application Events + +The framework checks client-side origin circuits to see if padding machines +should be activated or terminated during specific event callbacks in +`circuitpadding.c`. We list these event callbacks here only for reference. You +should not modify any of these callbacks to get your machine to run; instead, +you should use the `circpad_machine_spec_t.conditions` field. + +However, you may add new event callbacks if you need other activation events, +for example to provide obfuscation-layer or application-layer signaling. Any +new event callbacks should behave exactly like the existing callbacks. + +During each of these event callbacks, the framework checks to see if any +current running padding machines have conditions that no longer apply as a +result of the event, and shuts those machines down. Then, it checks to see if +any new padding machines should be activated as a result of the event, based +on their circuit application conditions. **Remember: Machines are checked in +reverse order in the machine list. This means that later, more recently added +machines take precedence over older, earlier entries in each list.** + +Both of these checks are performed using the machine application conditions +that you specify in your machine's `circpad_machine_spec_t.conditions` field. + +The machine application event callbacks are prefixed by `circpad_machine_event_` by convention in circuitpadding.c. As of this writing, these callbacks are: + + - `circpad_machine_event_circ_added_hop()`: Called whenever a new hop is + added to a circuit. + - `circpad_machine_event_circ_built()`: Called when a circuit has completed + construction and is + opened.  + - `circpad_machine_event_circ_purpose_changed()`: Called when a circuit + changes purpose. + - `circpad_machine_event_circ_has_no_relay_early()`: Called when a circuit + runs out of `RELAY_EARLY` cells. + - `circpad_machine_event_circ_has_streams()`: Called when a circuit gets a + stream attached. + - `circpad_machine_event_circ_has_no_streams()`: Called when the last + stream is detached from a circuit. + +### 6.3. Internal Machine Events + +To provide for some additional capabilities beyond simple finite state machine +behavior, the circuit padding machines also have internal events that they +emit to themselves when packet count length limits are hit, when the Infinity +bin is sampled, and when the histogram bins are emptied of all tokens. + +These events are implemented as `circpad_internal_event_*` functions in +`circuitpadding.c`, which are called from various areas that determine when +the events should occur. + +While the conditions that trigger these internal events to be called may be +complex, they are processed by the state machine definitions in a nearly +identical manner as the cell processing events, with the exception that they +are sent to the current machine only, rather than all machines on the circuit. + + +## 7. Future Features and Optimizations + +While implementing the circuit padding framework, our goal was to deploy a +system that obscured client-side onion service circuit setup and supported +deployment of WTF-PAD and/or APE. Along the way, we noticed several features +that might prove useful to others, but were not essential to implement +immediately. We do not have immediate plans to implement these ideas, but we +would gladly accept patches that do so. + +The following list gives an overview of these improvements, but as this +document ages, it may become stale. The canonical list of improvements that +researchers may find useful is tagged in our bugtracker with +[circpad-researchers](https://trac.torproject.org/projects/tor/query?keywords=~circpad-researchers), +and the list of improvements that are known to be necessary for some research +areas are tagged with +[circpad-researchers-want](https://trac.torproject.org/projects/tor/query?keywords=~circpad-researchers-want). + +Please consult those lists for the latest status of these issues. Note that +not all fixes will be backported to all Tor versions, so be mindful of which +Tor releases receive which fixes as you conduct your experiments. + +### 7.1. Load Balancing and Flow Control + +Fortunately, non-Exit bandwidth is already plentiful and exceeds the Exit +capacity, and we anticipate that if we inform our relay operator community of +the need for non-Exit bandwidth to satisfy padding overhead requirements, +they will be able to provide that with relative ease. + +Unfortunately, padding machines that have large quantities of overhead will +require changes to our load balancing system to account for this +overhead. The necessary changes are documented in +[Proposal 265](https://gitweb.torproject.org/torspec.git/tree/proposals/265-load-bala…. + +Additionally, padding cells are not currently subjected to flow control. For +high amounts of padding, we may want to change this. See [ticket +31782](https://bugs.torproject.org/31782) for details. + +### 7.2. Timing and Queuing Optimizations + +The circuitpadding framework has some timing related issues that may impact +results. If high-resolution timestamps are fed to opaque deep learning +trainers, those training models may end up able to differentiate padding +traffic from non-padding traffic due to these timing bugs. + +The circuit padding cell event callbacks come from post-decryption points in +the cell processing codepath, and from the pre-queue points in the cell send +codepath. This means that our cell events will not reflect the actual time +when packets are read or sent on the wire. This is much worse in the send +direction, as the circuitmux queue, channel outbuf, and kernel TCP buffer will +impose significant additional delay between when we currently report that a +packet was sent, and when it actually hits the wire. + +[Ticket 29494](https://bugs.torproject.org/29494) has a more detailed +description of this problem, and an experimental branch that changes the cell +event callback locations to be from circuitmux post-queue, which with KIST, +should be an accurate reflection of when they are actually sent on the wire. + +If your padding machine and problem space depends on very accurate notions of +relay-side packet timing, please try that branch and let us know on the +ticket if you need any further assistance fixing it up. + +Additionally, with these changes, it will be possible to provide further +overhead reducing optimizations by letting machines specify flags to indicate +that padding should not be sent if there are any cells pending in the cell +queue, for doing things like extending cell bursts more accurately and with +less overhead. + +However, even if we solve the queuing issues, Tor's current timers are not as +precise as some padding designs may require. We will still have issues of +timing precision to solve. [Ticket 31653](https://bugs.torproject.org/31653) +describes an issue the circuit padding system has with sending 0-delay padding +cells, and [ticket 32670](https://bugs.torproject.org/32670) describes a +libevent timer accuracy issue, which causes callbacks to vary up to 10ms from +their scheduled time, even in absence of load. + +All of these issues strongly suggest that you either truncate the resolution +of any timers you feed to your classifier, or that you omit timestamps +entirely from the classification problem until these issues are addressed. + +### 7.3. Better Machine Negotiation + +Circuit padding is applied to circuits through machine conditions. + +The following machine conditions may be useful for some use cases, but have +not been implemented yet: + * [Exit Policy-based Stream Conditions](https://bugs.torproject.org/29083) + * [Probability to apply machine/Cointoss condition](https://bugs.torproject.org/30092) + * [Probability distributions for launching new padding circuit(s)](https://bugs.torproject.org/31783) + * [More flexible purpose handling](https://bugs.torproject.org/32040) + +Additionally, the following features may help to obscure that padding is being +negotiated, and/or streamline that negotiation process: + * [Always send negotiation cell on all circuits](https://bugs.torproject.org/30172) + * [Better shutdown handling](https://bugs.torproject.org/30992) + * [Preference-ordered negotiation menu](https://bugs.torproject.org/30348) + +### 7.4. Probabilistic State Transitions + +Right now, the state machine transitions are fully deterministic. However, +one could imagine a state machine that uses probabilistic transitions between +states to simulate a random walk or Hidden Markov Model traversal across +several pages. + +The simplest way to implement this is to make the `circpad_state_t.next_state` array +into an array of structs that have a next state field, and a probability to +transition to that state. + +If you need this feature, please see [ticket +31787](https://bugs.torproject.org/31787) for more details. + +### 7.5. More Complex Pattern Recognition + +State machines are extremely efficient sequence recognition devices. But they +are not great pattern recognition devices. This is one of the reasons why +[Adaptive Padding](https://www.freehaven.net/anonbib/cache/ShWa-Timing06.pdf) +used state machines in combination with histograms, to model the target +distribution of interpacket delays for transmitted packets. + +However, there currently is no such optimization for reaction to patterns of +*received* traffic. There may also be cases where defenses must react to more +complex patterns of sent traffic than can be expressed by our current +histogram and length count events. + +For example: if you wish your machine to react to a certain count of incoming +cells in a row, right now you have to have a state for each cell, and use the +infinity bin to timeout of the sequence in each state. We could make this more +compact if each state had an arrival cell counter and inter-cell timeout. Or +we could make more complex mechanisms to recognize certain patterns of arrival +traffic in a state. + +The best way to build recognition primitives like this into the framework is +to add additional [Internal Machine Events](#63-internal-machine-events) for +the pattern in question. + +As another simple example, a useful additional event might be to transition +whenever any of your histogram bins are empty, rather than all of them. To do +this, you would add `CIRCPAD_EVENT_ANY_BIN_EMPTY` to the enum +`circpad_event_t` in `circuitpadding.h`. You would then create a function +`circuitpadding_internal_event_any_bin_empty()`, which would work just like +`circuitpadding_internal_event_bin_empty()`, and also be called from +`check_machine_token_supply()` in `circuitpadding.c` but with the check for +each bin being zero instead of the total. With this change, new machines could +react to this new event in the same way as any other. + +If you have any other ideas that may be useful, please comment on [ticket +32680](https://bugs.torproject.org/32680). + + +## 8. Open Research Problems + +### 8.1. Onion Service Circuit Setup + +Our circuit setup padding does not address timing-based features, only +packet counts. Deep learning can probably see this. + +However, before going too deep down the timing rabithole, we may need to make +[some improvements to Tor](#72-timing-and-queuing-optimizations). Please +comment on those tickets if you need this. + +### 8.2. Onion Service Fingerprinting + +We have done nothing to obscure the service side of onion service circuit +setup. Because service-side onion services will have the reverse traffic byte +counts as normal clients, they will likely need some kind of [hybrid +application layer traffic shaping](#53-sketch-of-tamaraw), in addition to +simple circuit setup obfuscation. + +Fingerprinting in +[combination](https://github.com/mikeperry-tor/vanguards/blob/master/README_SECURITY.md) +with +[vanguards](https://github.com/mikeperry-tor/vanguards/blob/master/README_TECHNICAL.md) +ia also an open issue. + +### 8.3. Open World Fingerprinting + +Similarly, Open World/clearweb website fingerprinting defenses remain +an unsolved problem from the practicality point of view. The original WTF-PAD +defense was never tuned, and it is showing accuracy issues against deep +learning attacks. + +### 8.4. Protocol Usage Fingerprinting + +Traffic Fingerprinting to determine the protocol in use by a client has not +been studied, either from the attack or defense point of view. + +### 8.5. Datagram Transport Side Channels + +Padding can reduce the accuracy of dropped-cell side channels in such +transports, but we don't know [how to measure +this](https://lists.torproject.org/pipermail/tor-dev/2018-November/013562.html). + +## 9. Must Read Papers + +These are by far the most important papers in the space, to date: + + - [Tamaraw](https://www.cypherpunks.ca/~iang/pubs/webfingerprint-ccs14.pdf) + - [Bayes, Not Naive](https://www.petsymposium.org/2017/papers/issue4/paper50-2017-4-sourc… + - [Anonymity Trilemma](https://eprint.iacr.org/2017/954.pdf) + - [WTF-PAD](http://arxiv.org/pdf/1512.00524) + +Except for WTF-PAD, these papers were selected because they point towards +optimality bounds that can be benchmarked against. + +We cite them even though we are skeptical that provably optimal defenses can +be constructed, at least not without trivial or impractical transforms (such as +those that can be created with unbounded queue capacity, or stored knowledge +of traces for every possible HTTP trace on the Internet). + +We also are not demanding an optimality or security proof for every defense. + +Instead, we cite the above as benchmarks. We believe the space, especially the +open-world case, to be more akin to an optimization problem, where a +WTF-PAD-like defense must be tuned through an optimizer to produce results +comparable to provably optimal but practically unrealizable defenses, through +rigorous adversarial evaluation. diff --git a/doc/HACKING/CircuitPaddingQuickStart.md b/doc/HACKING/CircuitPaddingQuickStart.md new file mode 100644 index 000000000..167ff9f29 --- /dev/null +++ b/doc/HACKING/CircuitPaddingQuickStart.md @@ -0,0 +1,263 @@ +# A Padding Machine from Scratch + +A quickstart guide by Tobias Pulls. + +This document describes the process of building a "padding machine" in tor's new +circuit padding framework from scratch. Notes were taken as part of porting +[Adaptive Padding Early +(APE)](https://www.cs.kau.se/pulls/hot/thebasketcase-ape/) from basket2 to the +circuit padding framework. The goal is just to document the process and provide +useful pointers along the way, not create a useful machine. + +The quick and dirty plan is to: +1. clone and compile tor +2. use newly built tor in TB and at small (non-exit) relay we run +3. add a bare-bones APE padding machine +4. run the machine, inspect logs for activity +5. port APE's state machine without thinking much about parameters + +## Clone and compile tor + +```bash +git clone https://git.torproject.org/tor.git +cd tor +git checkout tor-0.4.1.5 +``` +Above we use the tag for tor-0.4.1.5 where the circuit padding framework was +released. Note that this version of the framework is missing many features and +fixes that have since been merged to origin/master. If you need the newest +framework features, you should use that master instead. + +```bash +sh autogen.sh +./configure +make +``` +When you run `./configure` you'll be told of missing dependencies and packages +to install on debian-based distributions. Important: if you plan to run `tor` on +a relay as part of the real Tor network and your server runs a distribution that +uses systemd, then I'd recommend that you `apt install dpkg dpkg-dev +libevent-dev libssl-dev asciidoc quilt dh-apparmor libseccomp-dev dh-systemd +libsystemd-dev pkg-config dh-autoreconf libfakeroot zlib1g zlib1g-dev automake +liblzma-dev libzstd-dev` and ensure that tor has systemd support enabled: +`./configure --enable-systemd`. Without this, on a recent Ubuntu, my tor service +was forcefully restarted (SIGINT interrupt) by systemd every five minutes. + +If you want to install on your localsystem, run `make install`. For our case we +just want the tor binary at `src/app/tor`. + +## Use tor in TB and at a relay +Download and install a fresh Tor Browser (TB) from torproject.org. Make sure it +works. From the command line, relative to the folder created when you extracted +TB, run `./Browser/start-tor-browser --verbose` to get some basic log output. +Note the version of tor, in my case, `Tor 0.4.0.5 (git-bf071e34aa26e096)` as +part of TB 8.5.4. Shut down TB, copy the `tor` binary that you compiled earlier +and replace `Browser/TorBrowser/Tor/tor`. Start TB from the command line again, +you should see a different version, in my case `Tor 0.4.1.5 +(git-439ca48989ece545)`. + +The relay we run is also on linux, and `tor` is located at `/usr/bin/tor`. To +view relevant logs since last boot `sudo journalctl -b /usr/bin/tor`, where we +find `Tor 0.4.0.5 running on Linux`. Copy the locally compiled `tor` to the +relay at a temporary location and then make sure it's ownership and access +rights are identical to `/usr/bin/tor`. Next, shut down the running tor service +with `sudo service tor stop`, wait for it to stop (typically 30s), copy our +locally compiled tor to replace `/usr/bin/tor` then start the service again. +Checking the logs we see `or 0.4.1.5 (git-439ca48989ece545)`. + +Repeatedly shutting down a relay is detrimental to the network and should be +avoided. Sorry about that. + +We have one more step left before we move on the machine: configure TB to always +use our middle relay. Edit `Browser/TorBrowser/Data/Tor/torrc` and set +`MiddleNodes <fingerprint>`, where `<fingerprint>` is the fingerprint of the +relay. Start TB, visit a website, and manually confirm that the middle is used +by looking at the circuit display. + +## Add a bare-bones APE padding machine +Now the fun part. We have several resources at our disposal (mind that links +might be broken in the future, just search for the headings): +- The official [Circuit Padding Developer + Documentation](https://storm.torproject.org/shared/ChieH_sLU93313A2gopZYT3x…. +- Notes we made on the [implementation of the circuit padding + framework](https://github.com/pylls/padding-machines-for-tor/blob/master/no…. +- The implementation of the current circuit padding machines in tor: + [circuitpadding.c](https://gitweb.torproject.org/tor.git/tree/src/core/or/ci… + and + [circuitpadding_machines.h](https://gitweb.torproject.org/tor.git/tree/src/c…. + +Please consult the above links for details. Moving forward, the focus is to +describe what was done, not necessarily explaining all the details why. + +Since we plan to make changes to tor, create a new branch `git checkout -b +circuit-padding-ape-machine tor-0.4.1.5`. + +We start with declaring two functions, one for the machine at the client and one +at the relay, in `circuitpadding_machines.h`: + +```c +void circpad_machine_relay_wf_ape(smartlist_t *machines_sl); +void circpad_machine_client_wf_ape(smartlist_t *machines_sl); +``` + +The definitions go into `circuitpadding_machines.c`: + +```c +/**************** Adaptive Padding Early (APE) machine ****************/ + +/** + * Create a relay-side padding machine based on the APE design. + */ +void +circpad_machine_relay_wf_ape(smartlist_t *machines_sl) +{ + circpad_machine_spec_t *relay_machine + = tor_malloc_zero(sizeof(circpad_machine_spec_t)); + + relay_machine->name = "relay_wf_ape"; + relay_machine->is_origin_side = 0; // relay-side + + // Pad to/from the middle relay, only when the circuit has streams + relay_machine->target_hopnum = 2; + relay_machine->conditions.min_hops = 2; + relay_machine->conditions.state_mask = CIRCPAD_CIRC_STREAMS; + + // limits to help guard against excessive padding + relay_machine->allowed_padding_count = 1; + relay_machine->max_padding_percent = 1; + + // one state to start with: START (-> END, never takes a slot in states) + circpad_machine_states_init(relay_machine, 1); + relay_machine->states[CIRCPAD_STATE_START]. + next_state[CIRCPAD_EVENT_NONPADDING_SENT] = + CIRCPAD_STATE_END; + + // register the machine + relay_machine->machine_num = smartlist_len(machines_sl); + circpad_register_padding_machine(relay_machine, machines_sl); + + log_info(LD_CIRC, + "Registered relay WF APE padding machine (%u)", + relay_machine->machine_num); +} + +/** + * Create a client-side padding machine based on the APE design. + */ +void +circpad_machine_client_wf_ape(smartlist_t *machines_sl) +{ + circpad_machine_spec_t *client_machine + = tor_malloc_zero(sizeof(circpad_machine_spec_t)); + + client_machine->name = "client_wf_ape"; + client_machine->is_origin_side = 1; // client-side + + /** Pad to/from the middle relay, only when the circuit has streams, and only + * for general purpose circuits (typical for web browsing) + */ + client_machine->target_hopnum = 2; + client_machine->conditions.min_hops = 2; + client_machine->conditions.state_mask = CIRCPAD_CIRC_STREAMS; + client_machine->conditions.purpose_mask = + circpad_circ_purpose_to_mask(CIRCUIT_PURPOSE_C_GENERAL); + + // limits to help guard against excessive padding + client_machine->allowed_padding_count = 1; + client_machine->max_padding_percent = 1; + + // one state to start with: START (-> END, never takes a slot in states) + circpad_machine_states_init(client_machine, 1); + client_machine->states[CIRCPAD_STATE_START]. + next_state[CIRCPAD_EVENT_NONPADDING_SENT] = + CIRCPAD_STATE_END; + + client_machine->machine_num = smartlist_len(machines_sl); + circpad_register_padding_machine(client_machine, machines_sl); + log_info(LD_CIRC, + "Registered client WF APE padding machine (%u)", + client_machine->machine_num); +} +``` + +We also have to modify `circpad_machines_init()` in `circuitpadding.c` to +register our machines: + +```c + /* Register machines for the APE WF defense */ + circpad_machine_client_wf_ape(origin_padding_machines); + circpad_machine_relay_wf_ape(relay_padding_machines); +``` + +We run `make` to get a new `tor` binary and copy it to our local TB. + +## Run the machine +To be able +to view circuit info events in the console as we launch TB, we add `Log +[circ]info notice stdout` to `torrc` of TB. + +Running TB to visit example.com we first find in the log: + +``` +Aug 30 18:36:43.000 [info] circpad_machine_client_hide_intro_circuits(): Registered client intro point hiding padding machine (0) +Aug 30 18:36:43.000 [info] circpad_machine_relay_hide_intro_circuits(): Registered relay intro circuit hiding padding machine (0) +Aug 30 18:36:43.000 [info] circpad_machine_client_hide_rend_circuits(): Registered client rendezvous circuit hiding padding machine (1) +Aug 30 18:36:43.000 [info] circpad_machine_relay_hide_rend_circuits(): Registered relay rendezvous circuit hiding padding machine (1) +Aug 30 18:36:43.000 [info] circpad_machine_client_wf_ape(): Registered client WF APE padding machine (2) +Aug 30 18:36:43.000 [info] circpad_machine_relay_wf_ape(): Registered relay WF APE padding machine (2) +``` + +All good, our machine is running. Looking further we find: + +``` +Aug 30 18:36:55.000 [info] circpad_setup_machine_on_circ(): Registering machine client_wf_ape to origin circ 2 (5) +Aug 30 18:36:55.000 [info] circpad_node_supports_padding(): Checking padding: supported +Aug 30 18:36:55.000 [info] circpad_negotiate_padding(): Negotiating padding on circuit 2 (5), command 2 +Aug 30 18:36:55.000 [info] circpad_machine_spec_transition(): Circuit 2 circpad machine 0 transitioning from 0 to 65535 +Aug 30 18:36:55.000 [info] circpad_machine_spec_transitioned_to_end(): Padding machine in end state on circuit 2 (5) +Aug 30 18:36:55.000 [info] circpad_circuit_machineinfo_free_idx(): Freeing padding info idx 0 on circuit 2 (5) +Aug 30 18:36:55.000 [info] circpad_handle_padding_negotiated(): Middle node did not accept our padding request on circuit 2 (5) +``` +We see that our middle support padding (since we upgraded to tor-0.4.1.5), that +we attempt to negotiate, our machine starts on the client, transitions to the +end state, and is freed. The last line shows that the middle doesn't have a +padding machine that can run. + +Next, we follow the same steps as earlier and replace the modified `tor` at our +middle relay. We don't update the logging there to avoid logging on the info +level on the live network. Looking at the client log again we see that +negotiation works as before except for the last line: it's missing, so the +machine is running at the middle as well. + +## Implementing the APE state machine + +Porting is fairly straightforward: define the states for all machines, add two +more machines (for the receive portion of WTFP-PAD, beyond AP), and pick +reasonable parameters for the distributions (I completely winged it now, as when +implementing APE). The [circuit-padding-ape-machine +branch](https://github.com/pylls/tor/tree/circuit-padding-ape-machine) contains +the commits for the full machines with plenty of comments. + +Some comments on the process: + +- `tor-0.4.1.5` does not support two machines on the same circuit, the following + fix has to be made: https://trac.torproject.org/projects/tor/ticket/31111 . + The good news is that everything else seems to work after the small change in + the fix. +- APE randomizes its distributions. Currently, this can only be done during + start of `tor`. This makes sense in the censorship circumvention setting + (`obfs4`), less so for WF defenses: further randomizing each circuit is likely + a PITA for attackers with few downsides. +- it was annoying to figure out that the lack of systemd support in my compiled + tor caused systemd to interrupt (SIGINT) my tor process at the middle relay + every five minutes. Updated build steps above to hopefully save others the + pain. +- there's for sure some bug on relays when sending padding cells too early (?). + It can happen with some probability with the APE implementation due to + `circpad_machine_relay_wf_ape_send()`. Will investigate next. +- Moving the registration of machines from the definition of the machines to + `circpad_machines_init()` makes sense, as suggested in the circuit padding doc + draft. + +Remember that APE is just a proof-of-concept and we make zero claims about its +ability to withstand WF attacks, in particular those based on deep learning.

1 0

[tor/master] Merge branch 'tor-github/pr/1591'
by asn＠torproject.org 16 Dec '19

16 Dec '19

commit e6bffeca64b9961207488e627848ce26e7f8101c Merge: 5082eeba3 e01e19900 Author: George Kadianakis <desnacked(a)riseup.net> Date: Mon Dec 16 22:01:10 2019 +0200 Merge branch 'tor-github/pr/1591' changes/ticket28804 | 5 + doc/HACKING/CircuitPaddingDevelopment.md | 1230 ++++++++++++++++++++++++++++++ doc/HACKING/CircuitPaddingQuickStart.md | 263 +++++++ 3 files changed, 1498 insertions(+)

1 0

[tor-browser-build/master] Revert "Bug 31130: Use Debian 10 for our Android container images"
by boklm＠torproject.org 16 Dec '19

16 Dec '19

commit 2d7921cd17c52fe2a16d0a3dc19235d0d48fa575 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Mon Dec 16 14:47:58 2019 +0100 Revert "Bug 31130: Use Debian 10 for our Android container images" This reverts commit 26be3f16054b7d9b1c4c6cf0332d90f92511fc3e. This commit causes the android builds to fail. See #32761. --- projects/debootstrap-image/config | 17 ++++++++--------- projects/firefox/build | 1 - projects/firefox/config | 5 +++++ projects/https-everywhere/config | 1 - projects/tor-android-service/config | 6 ++++++ projects/tor-browser/build.android | 2 +- projects/tor-browser/config | 1 + projects/tor-onion-proxy-library/config | 6 ++++++ rbm.conf | 13 ++----------- 9 files changed, 29 insertions(+), 23 deletions(-) diff --git a/projects/debootstrap-image/config b/projects/debootstrap-image/config index f7b9e57..a50cbf1 100644 --- a/projects/debootstrap-image/config +++ b/projects/debootstrap-image/config @@ -4,7 +4,7 @@ version: 2 pkg_type: build var: - ubuntu_version: 19.10 + ubuntu_version: 18.04.1 container: use_container: 1 @@ -15,6 +15,8 @@ pre: | #!/bin/sh set -e export DEBIAN_FRONTEND=noninteractive + # Bug 29158: install fixed packages for apt vulnerability (CVE-2019-3462) + dpkg -i ./apt_1.6.6ubuntu0.1_amd64.deb ./libapt-pkg5.0_1.6.6ubuntu0.1_amd64.deb apt-get update -y -q apt-get install -y -q debian-archive-keyring ubuntu-keyring debootstrap debootstrap --arch=[% c("var/container/arch") %] [% c("var/container/debootstrap_opt") %] [% c("var/container/suite") %] base-image [% c("var/container/debootstrap_mirror") %] @@ -63,17 +65,14 @@ targets: suite: stretch arch: amd64 - buster-amd64: - var: - minimal_apt_version: 1.8.2 - container: - suite: buster - arch: amd64 - input_files: - URL: 'http://cdimage.ubuntu.com/ubuntu-base/releases/[% c("var/ubuntu_version") %]/release/ubuntu-base-[% c("var/ubuntu_version") %]-base-amd64.tar.gz' filename: 'container-image_ubuntu-base-[% c("var/ubuntu_version") %]-base-amd64.tar.gz' - sha256sum: eedcb1dc0ccc86b59eb1f89960c322a2ba3ed3e0323a20a1da8bcc0e6f100f4f + sha256sum: ed76e649f65548a80b361b68011085ec4dde7bb762d667657acbef87765e1a12 + - URL: http://security.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6ubuntu0.1_amd64.… + sha256sum: df210f9e30cf9deba5fbe815203af854e5e77bdbbe0b96d0d1c0da46a6a8dd0a + - URL: http://security.ubuntu.com/ubuntu/pool/main/a/apt/libapt-pkg5.0_1.6.6ubuntu… + sha256sum: 0a05a97b1e9b8d52ee8df040a14c5fabdebbb2c2235ac495db29df34f4c8cec3 - URL: '[% c("var/apt_packages_baseurl") %]/[% c("var/apt_package_filename") %]' sha256sum: '[% c("var/apt_package_sha256sum") %]' enable: '[% c("var/apt_package_filename") %]' diff --git a/projects/firefox/build b/projects/firefox/build index 067453d..5179634 100644 --- a/projects/firefox/build +++ b/projects/firefox/build @@ -57,7 +57,6 @@ mv -f $rootdir/[% c('input_files_by_name/mozconfig') %] .mozconfig [% END -%] [% IF c("var/android") %] - export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64 gradle_repo=/var/tmp/dist/gradle-dependencies export GRADLE_MAVEN_REPOSITORIES="file://$gradle_repo" export GRADLE_FLAGS="--no-daemon --offline" diff --git a/projects/firefox/config b/projects/firefox/config index 2c7c037..c6f840b 100644 --- a/projects/firefox/config +++ b/projects/firefox/config @@ -54,6 +54,11 @@ targets: var: branding_directory: '[% IF c("var/android") %]mobile/android[% ELSE %]browser[% END %]/branding/nightly' + android: + var: + arch_deps: + - openjdk-8-jdk + linux: var: post_pkginst: | diff --git a/projects/https-everywhere/config b/projects/https-everywhere/config index c66d7fe..1bc6f98 100644 --- a/projects/https-everywhere/config +++ b/projects/https-everywhere/config @@ -27,7 +27,6 @@ var: - rsync - zip - unzip - pre_pkginst: '' input_files: - project: container-image diff --git a/projects/tor-android-service/config b/projects/tor-android-service/config index 4a07c87..9d7bc84 100644 --- a/projects/tor-android-service/config +++ b/projects/tor-android-service/config @@ -13,6 +13,12 @@ var: # this should be updated when the list of gradle dependencies is changed gradle_dependencies_version: 3 +targets: + android: + var: + arch_deps: + - openjdk-8-jdk + input_files: - project: container-image - name: '[% c("var/compiler") %]' diff --git a/projects/tor-browser/build.android b/projects/tor-browser/build.android index 751db11..f8f3a8d 100644 --- a/projects/tor-browser/build.android +++ b/projects/tor-browser/build.android @@ -55,4 +55,4 @@ cd tmp }) %] # Sign a QA build. This apk is not a debug version and doesn't contain a debug flag in the manifest -java -jar /usr/lib/android-sdk/build-tools/debian/apksigner.jar sign --verbose --min-sdk-version [% c("var/android_min_api") %] --ks $rootdir/android-qa.keystore --out $qa_apk --in $apk --ks-key-alias androidqakey --key-pass pass:android --ks-pass pass:android +java -jar /usr/share/apksigner/apksigner.jar sign --verbose --min-sdk-version [% c("var/android_min_api") %] --ks $rootdir/android-qa.keystore --out $qa_apk --in $apk --ks-key-alias androidqakey --key-pass pass:android --ks-pass pass:android diff --git a/projects/tor-browser/config b/projects/tor-browser/config index 4a26049..819ebad 100644 --- a/projects/tor-browser/config +++ b/projects/tor-browser/config @@ -45,6 +45,7 @@ targets: build: '[% INCLUDE build.android %]' var: arch_deps: + - openjdk-8-jdk - apksigner input_files: diff --git a/projects/tor-onion-proxy-library/config b/projects/tor-onion-proxy-library/config index 0849623..ff3432c 100644 --- a/projects/tor-onion-proxy-library/config +++ b/projects/tor-onion-proxy-library/config @@ -15,6 +15,12 @@ var: # this should be updated when the list of gradle dependencies is changed gradle_dependencies_version: 3 +targets: + android: + var: + arch_deps: + - openjdk-8-jdk + input_files: - project: container-image - name: '[% c("var/compiler") %]' diff --git a/rbm.conf b/rbm.conf index f94cf4a..0fe7acb 100644 --- a/rbm.conf +++ b/rbm.conf @@ -236,7 +236,7 @@ targets: CC: '$ANDROID_NDK_HOME/[% c("var/toolchain_arch") %]/bin/clang' CXX: '$ANDROID_NDK_HOME/[% c("var/toolchain_arch") %]/bin/clang++' container: - suite: buster + suite: stretch arch: amd64 deps: - build-essential @@ -245,16 +245,7 @@ targets: - libtool - zip - unzip - pre_pkginst: | - SNAPSHOT_VERSION=20191201T212855Z - OPENJDK_URL=https://snapshot.debian.org/archive/debian/$SNAPSHOT_VERSION/po… - JDK_VERSION=8u232-b09-1~deb9u1_amd64 - apt-get install -y -q wget ca-certificates-java - wget $OPENJDK_URL/openjdk-8-jdk-headless_$JDK_VERSION.deb - wget $OPENJDK_URL/openjdk-8-jre-headless_$JDK_VERSION.deb - echo 92b4f8fb77d793a86e0b03b3b0750592b40a26a5d75956d10dd984a7b3aad4c9 openjdk-8-jdk-headless_$JDK_VERSION.deb | sha256sum -c - echo 84bf52b6cce20ead08b0d5b9fd9b81b4aa3da385ca951b313fe11d5cb1aa4d17 openjdk-8-jre-headless_$JDK_VERSION.deb | sha256sum -c - dpkg -i ./openjdk-8-jre-headless_$JDK_VERSION.deb ./openjdk-8-jdk-headless_$JDK_VERSION.deb + torbrowser-linux-x86_64: - linux-x86_64 - linux

1 0

[community/master] add redirects for languages still not published.
by emmapeel＠torproject.org 16 Dec '19

16 Dec '19

commit f1d585122351616a09acddc86d37d6a35d3328d0 Author: emma peel <emma.peel(a)riseup.net> Date: Mon Dec 16 11:22:31 2019 +0100 add redirects for languages still not published. will-fix: https://trac.torproject.org/projects/tor/ticket/32760 --- .htaccess | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/.htaccess b/.htaccess index 6e2c53a..ba7c37a 100644 --- a/.htaccess +++ b/.htaccess @@ -1,4 +1,22 @@ +RewriteEngine On + # forward requests in /en to the root folder RewriteRule ^(en-US|en)$ / [R=302,L] RewriteRule ^(en-US|en)/(.*) /$2 [R=302,L] +# forward requests in /en and /en-US to the root folder +RewriteRule ^(en|en-US)$ / [R=302,L] +RewriteRule ^(en|en-US)/(.*) /$2 [R=302,L] + +# Rewrites for languages that have a different mapping in the page than in TBB +RewriteRule ^(es-ES|es-MX|es-CO|es-AR)(.*) /es$2 [R=302,L] + +# we have only one translation for this locales +RewriteRule ^(bn-BD|bn-IN)(.*) /bn$2 [R=302,L] +RewriteRule ^ga-IE/(.*) /ga$1 [R=302,L] + +# Rewrites for languages that have a Tor Browser release +# but don't have a community page +# You can see them at https://dist.torproject.org/torbrowser/, pick the last alpha for the most languages +# this languages are the translation priority for the community portal! +RewriteRule ^(ar|ca|cs|da|de|el|es|fa|fr|ga|he|hu|id|is|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-BR|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)/(.*) /$2 [R=302,L]

1 0

Jump to page: