September 2019 - tor-commits - lists.torproject.org

[translation/tpo-web] https://gitweb.torproject.org/translation.git/commit/?h=tpo-web
by translation＠torproject.org 19 Sep '19

19 Sep '19

commit 13ed720ab5d3ff4de6fa48671640e9df365c1d2b Author: Translation commit bot <translation(a)torproject.org> Date: Thu Sep 19 20:22:32 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tpo-web --- contents+pt-BR.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/contents+pt-BR.po b/contents+pt-BR.po index 7b32b9b20..f1e1f89d0 100644 --- a/contents+pt-BR.po +++ b/contents+pt-BR.po @@ -8,11 +8,11 @@ # Alexei Gonçalves de Oliveira <alexis(a)gessicahellmann.com>, 2019 # Danihells <dcdcampos75(a)gmail.com>, 2019 # Gus, 2019 -# Communia <ameaneantie(a)riseup.net>, 2019 # erinm, 2019 # Eduardo Addad de Oliveira <eduardoaddad(a)hotmail.com>, 2019 -# Emma Peel, 2019 # Chacal E., 2019 +# Emma Peel, 2019 +# Communia <ameaneantie(a)riseup.net>, 2019 # msgid "" msgstr "" @@ -20,7 +20,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-09-17 15:46+CET\n" "PO-Revision-Date: 2019-03-09 10:41+0000\n" -"Last-Translator: Chacal E., 2019\n" +"Last-Translator: Communia <ameaneantie(a)riseup.net>, 2019\n" "Language-Team: Portuguese (Brazil) (https://www.transifex.com/otf/teams/1519/pt_BR/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1415,15 +1415,15 @@ msgstr "Ler mais." #: templates/macros/question.html:12 msgid "Contributors to this page:" -msgstr "Contribuidores para esta página:" +msgstr "Contribuidores desta página:" #: templates/macros/question.html:14 msgid "Edit this page" -msgstr "Edite essa página" +msgstr "Editar esta página" #: templates/macros/question.html:15 msgid "Suggest Feedback" -msgstr "Sugerir Feedback" +msgstr "Sugerir Comentário" #: templates/macros/question.html:16 msgid "Permalink"

1 0

[community/master] Use Docker's 'latest' tag for up-to-date image.
by phw＠torproject.org 19 Sep '19

19 Sep '19

commit 2879ca75eb9411fe4060c2ed9503dcbba3b0d871 Author: Philipp Winter <phw(a)nymity.ch> Date: Thu Sep 19 12:28:45 2019 -0700 Use Docker's 'latest' tag for up-to-date image. --- content/relay-operations/technical-setup/bridge/docker/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index bf5f5b1..f82a65e 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -8,7 +8,7 @@ body: We are maintaining a docker container that allows you to quickly set up an obfs4 bridge. First, fetch the container: -`docker pull phwinter/obfs4-bridge:0.2` +`docker pull phwinter/obfs4-bridge:latest` Now, it's time to run the container. We maintain a script that automatically determines a free OR and obfs4 port for you. The script only requires your email address as argument: ```

1 0

[torspec/master] Update padding-spec.txt to cover hs circuit padding.
by nickm＠torproject.org 19 Sep '19

19 Sep '19

commit a7e52fc35d4dc83259f98f84563617dee3801e0a Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Wed Aug 14 19:07:59 2019 -0500 Update padding-spec.txt to cover hs circuit padding. Also update padding proposals that are deprecated by padding-spec.txt, to refer the reader to the new spec. --- padding-spec.txt | 266 ++++++++++++++++++++- proposals/251-netflow-padding.txt | 2 +- .../302-padding-machines-for-onion-clients.txt | 6 +- 3 files changed, 267 insertions(+), 7 deletions(-) diff --git a/padding-spec.txt b/padding-spec.txt index b85f0fd..455c5eb 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -1,6 +1,6 @@ Tor Padding Specification - Mike Perry + Mike Perry, George Kadianakis Note: This is an attempt to specify Tor as currently implemented. Future versions of Tor will implement improved algorithms. @@ -35,9 +35,15 @@ the anonymity and load-balancing implications of their choices. padding to be sent to any intermediate node in a circuit (as per Section 6.1 of tor-spec.txt). - Currently, only single-hop CELL_PADDING is used by Tor. It is described in - Section 2. At a later date, further sections will be added to this document - to describe various uses of multi-hop circuit-level padding. + Tor uses both connection level and circuit level padding. Connection + level padding is described in section 2. Circuit level padding is + described in section 3. + + The circuit-level padding system is completely orthogonal to the + connection-level padding. The connection-level padding system regards + circuit-level padding as normal data traffic, and hence the connection-level + padding system will not add any additional overhead while the circuit-level + padding system is actively padding. 2. Connection-level padding @@ -274,11 +280,257 @@ the anonymity and load-balancing implications of their choices. open. - Default: 3600 + +3. Circuit-level padding + + The circuit padding system in Tor is an extension of the WTF-PAD + event-driven state machine design[15]. At a high level, this design places + one or more padding state machines at the client, and one or more padding + state machines at a relay, on each circuit. + + State transition and histogram generation has been generalized to be fully + programmable, and probability distribution support was added to support more + compact representations like APE[16]. Additionally, packet count limits, + rate limiting, and circuit application conditions have been added. + + At present, Tor uses this system to deploy two pairs of circuit padding + machines, to obscure differences between the setup phase of client-side + onion service circuits, up to the first 10 cells. + + This specification covers only the resulting behavior of these padding + machines, and thus does not cover the state machine implementation details or + operation. For full details on using the circuit padding system to develop + future padding defenses, see the research developer documentation[17]. + +3.1. Circuit Padding Negotiation + + Circuit padding machines are advertised as "Padding" subprotocol versions + (see tor-spec.txt Section 9). The onion service circuit padding machines are + advertised as "Padding=2". + + Because circuit padding machines only become active at certain points in + circuit lifetime, and because more than one padding machine may be active at + any given point in circuit lifetime, there is also a padding negotiation cell, + with fields as follows: + + const CIRCPAD_COMMAND_STOP = 1; + const CIRCPAD_COMMAND_START = 2; + + const CIRCPAD_RESPONSE_OK = 1; + const CIRCPAD_RESPONSE_ERR = 2; + + const CIRCPAD_MACHINE_CIRC_SETUP = 1; + + struct circpad_negotiate { + u8 version IN [0]; + u8 command IN [CIRCPAD_COMMAND_START, CIRCPAD_COMMAND_STOP]; + + u8 machine_type IN [CIRCPAD_MACHINE_CIRC_SETUP]; + }; + + When a client wants to start a circuit padding machine, it first checks that + the desired destination hop advertises the appropriate subprotocol version for + that machine. It then sends a circpad_negotiate cell to that hop with + command=CIRCPAD_COMMAND_START, and machine_type=CIRCPAD_MACHINE_CIRC_SETUP (for + the circ setup machine, the destination hop is the second hop in the circuit). + + When a relay receives a circpad_negotiate cell, it checks that it supports + the requested machine, and sends a circpad_negotiated cell, which is formatted + as follows: + + struct circpad_negotiated { + u8 version IN [0]; + u8 command IN [CIRCPAD_COMMAND_START, CIRCPAD_COMMAND_STOP]; + u8 response IN [CIRCPAD_RESPONSE_OK, CIRCPAD_RESPONSE_ERR]; + + u8 machine_type IN [CIRCPAD_MACHINE_CIRC_SETUP]; + }; + + If the machine is supported, the response field will contain + CIRCPAD_RESPONSE_OK. If it is not, it will contain CIRCPAD_RESPONSE_ERR. + + Either side may send a CIRCPAD_COMMAND_STOP to shut down the padding machines + (clients MUST only send circpad_negotiate, and relays MUST only send + circpad_negotiated for this purpose). + +3.2. Circuit Padding Machine Message Management + + Clients MAY send padding cells towards the relay before receiving the + circpad_negotiated response, to allow for outbound cover traffic before + negotiation completes. + + Clients MAY send another circpad_negotiate cell before receiving the + circpad_negotiated response, to allow for rapid machine changes. + + Relays MUST NOT send padding cells or circpad_negotiated cells, unless a + padding machine is active. Any padding-related cells that arrive at the client + from unexpected relay sources are protocol violations, and clients MAY + immediately tear down such circuits to avoid side channel risk. + +3.3. Obfuscating client-side onion service circuit setup + + The circuit padding currently deployed in Tor attempts to hide client-side + onion service circuit setup. Service-side setup is not covered, because doing + so would involve significantly more overhead, and/or require interaction with + the application layer. + + The approach taken aims to make client-side introduction and rendezvous + circuits match the cell direction sequence and cell count of 3 hop general + circuits used for normal web traffic, for the first 10 cells only. The + lifespan of introduction circuits is also made to match the lifespan + of general circuits. + + Note that inter-arrival timing is not obfuscated by this defense. + +3.3.1. Common general circuit construction sequences + + Most general Tor circuits used to surf the web or download directory + information start with the following 6-cell relay cell sequence (cells + surrounded in [brackets] are outgoing, the others are incoming): + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [BEGIN] -> CONNECTED + + When this is done, the client has established a 3-hop circuit and also opened + a stream to the other end. Usually after this comes a series of DATA cell that + either fetches pages, establishes an SSL connection or fetches directory + information: + + [DATA] -> [DATA] -> DATA -> DATA...(inbound cells continue) + + The above stream of 10 relay cells defines the grand majority of general + circuits that come out of Tor browser during our testing, and it's what we use + to make introduction and rendezvous circuits blend in. + + Please note that in this section we only investigate relay cells and not + connection-level cells like CREATE/CREATED or AUTHENTICATE/etc. that are used + during the link-layer handshake. The rationale is that connection-level cells + depend on the type of guard used and are not an effective fingerprint for a + network/guard-level adversary. + +3.3.2 Client-side onion service introduction circuit obfuscation + + Two circuit padding machines work to hide client-side introduction circuits: + one machine at the origin, and one machine at the second hop of the circuit. + Each machine sends padding towards the other. The padding from the origin-side + machine terminates at the second hop and does not get forwarded to the actual + introduction point. + + From Section 3.3.1 above, most general circuits have the following initial + relay cell sequence (outgoing cells marked in [brackets]): + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [BEGIN] -> CONNECTED + -> [DATA] -> [DATA] -> DATA -> DATA...(inbound data cells continue) + + Whereas normal introduction circuits usually look like: + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 + -> [INTRO1] -> INTRODUCE_ACK + + This means that up to the sixth cell (first line of each sequence above), + both general and intro circuits have identical cell sequences. After that + we want to mimic the second line sequence of + -> [DATA] -> [DATA] -> DATA -> DATA...(inbound data cells continue) + + We achieve this by starting padding INTRODUCE1 has been sent. With padding + negotiation cells, in the common case of the second line looks like: + -> [INTRO1] -> [PADDING_NEGOTIATE] -> PADDING_NEGOTIATED -> INTRO_ACK + + Then, the middle node will send between INTRO_MACHINE_MINIMUM_PADDING (7) and + INTRO_MACHINE_MAXIMUM_PADDING (10) cells, to match the "...(inbound data cells + continue)" portion of the trace (aka the rest of an HTTPS response body). + + We also set a special flag which keeps the circuit open even after the + introduction is performed. With this feature the circuit will stay alive for + the same duration as normal web circuits before they expire (usually 10 + minutes). + +3.3.3. Client-side rendezvous circuit hiding + + Following a similar argument as for intro circuits, we are aiming for padded + rendezvous circuits to blend in with the initial cell sequence of general + circuits which usually look like this: + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [BEGIN] -> CONNECTED + -> [DATA] -> [DATA] -> DATA -> DATA...(incoming cells continue) + + Whereas normal rendezvous circuits usually look like: + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [EST_REND] -> REND_EST + -> REND2 -> [BEGIN] + + This means that up to the sixth cell (the first line), both general and + rend circuits have identical cell sequences. + + After that we want to mimic a [DATA] -> [DATA] -> DATA -> DATA sequence. + + With padding negotiation right after the REND_ESTABLISHED, the sequence + becomes: + + [EXTEND2] -> EXTENDED2 -> [EXTEND2] -> EXTENDED2 -> [EST_REND] -> REND_EST + -> [PADDING_NEGOTIATE] -> [DROP] -> PADDING_NEGOTIATED -> DROP... + + After which normal application DATA cells continue on the circuit. + + Hence this way we make rendezvous circuits look like general circuits up + till the end of the circuit setup. + + After that our machine gets deactivated, and we let the actual rendezvous + circuit shape the traffic flow. Since rendezvous circuits usually imitate + general circuits (their purpose is to surf the web), we can expect that they + will look alike. + +3.3.4. Circuit setup machine overhead + + For the intro circuit case, we see that the origin-side machine just sends a + single [PADDING_NEGOTIATE] cell, whereas the origin-side machine sends a + PADDING_NEGOTIATED cell and between 7 to 10 DROP cells. This means that the + average overhead of this machine is 11 padding cells per introduction circuit. + + For the rend circuit case, this machine is quite light. Both sides send 2 + padding cells, for a total of 4 padding cells. + +3.4. Circuit padding consensus parameters + + The circuit padding system has a handful of consensus parameters that can + either disable circuit padding entirely, or rate limit the total overhead + at relays and clients. + + * circpad_padding_disabled + - If set to 1, no circuit padding machines will negotiate, and all + current padding machines will cease padding immediately. + - Default: 0 + + * circpad_padding_reduced + - If set to 1, only circuit padding machines marked as "reduced"/"low + overhead" will be used. (Currently no such machines are marked + as "reduced overhead"). + - Default: 0 + + * circpad_global_allowed_cells + - This is the number of padding cells that must be sent before + the 'circpad_global_max_padding_percent' parameter is applied. + - Default: 0 + + * circpad_global_max_padding_percent + - This is the maximum ratio of padding cells to total cells, specified + as a percent. If the global ratio of padding cells to total cells + across all circuits exceeds this percent value, no more padding is sent + until the ratio becomes lower. 0 means no limit. + - Default: 0 + + * circpad_max_circ_queued_cells + - This is the maximum number of cells that can be in the circuitmux queue + before padding stops being sent on that circuit. + - Default: CIRCWINDOW_START_MAX (1000) + + A. Acknowledgments This research was supported in part by NSF grants CNS-1111539, CNS-1314637, CNS-1526306, CNS-1619454, and CNS-1640548. + XXX: There's more CNS numbers now.. + 1. https://en.wikipedia.org/wiki/NetFlow 2. http://infodoc.alcatel-lucent.com/html/0_add-h-f/93-0073-10-01/7750_SR_OS_R… 3. http://www.cisco.com/en/US/docs/ios/12_3t/netflow/command/reference/nfl_a1g… @@ -293,3 +545,9 @@ A. Acknowledgments 12. http://freehaven.net/anonbib/cache/murdoch-pet2007.pdf 13. https://gitweb.torproject.org/torspec.git/tree/proposals/188-bridge-guards.… 14. http://www.ntop.org/wp-content/uploads/2013/03/nProbe_UserGuide.pdf +15. http://arxiv.org/pdf/1512.00524 +16. https://www.cs.kau.se/pulls/hot/thebasketcase-ape/ +17. XXX-dev-doc +18. https://www.usenix.org/node/190967 + https://blog.torproject.org/technical-summary-usenix-fingerprinting-paper + diff --git a/proposals/251-netflow-padding.txt b/proposals/251-netflow-padding.txt index f1b9450..39cc795 100644 --- a/proposals/251-netflow-padding.txt +++ b/proposals/251-netflow-padding.txt @@ -5,7 +5,7 @@ Created: 20 August 2015 Status: Closed Implemented-In: 0.3.1.1-alpha -NOTE: Please look at padding-spec.txt now, not this document. +NOTE: Please look at section 2 of padding-spec.txt now, not this document. 0. Motivation diff --git a/proposals/302-padding-machines-for-onion-clients.txt b/proposals/302-padding-machines-for-onion-clients.txt index d7f583e..4123e85 100644 --- a/proposals/302-padding-machines-for-onion-clients.txt +++ b/proposals/302-padding-machines-for-onion-clients.txt @@ -2,8 +2,10 @@ Filename: 302-padding-machines-for-onion-clients.txt Title: Hiding onion service clients using padding Author: George Kadianakis, Mike Perry Created: Thursday 16 May 2019 -Status: Accepted -Ticket: #28634 +Status: Closed +Implemented-In: 0.4.1.1-alpha + +NOTE: Please look at section 3 of padding-spec.txt now, not this document. 0. Overview

1 0

[torspec/master] Remove "not done" and XXX about NSF numbers.
by nickm＠torproject.org 19 Sep '19

19 Sep '19

commit 2ebc16e26ceb2fd8fc6fe289f9adc1c14f79c8ce Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Thu Sep 19 14:05:13 2019 -0500 Remove "not done" and XXX about NSF numbers. NSF-TTP number for circpad is already in there. --- padding-spec.txt | 4 ---- 1 file changed, 4 deletions(-) diff --git a/padding-spec.txt b/padding-spec.txt index 455c5eb..26366ad 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -10,8 +10,6 @@ various traffic patterns from external and internal observers. Other implementations MAY take other approaches, but implementors should be aware of the anonymity and load-balancing implications of their choices. - THIS SPEC ISN'T DONE YET. - The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in @@ -529,8 +527,6 @@ A. Acknowledgments This research was supported in part by NSF grants CNS-1111539, CNS-1314637, CNS-1526306, CNS-1619454, and CNS-1640548. - XXX: There's more CNS numbers now.. - 1. https://en.wikipedia.org/wiki/NetFlow 2. http://infodoc.alcatel-lucent.com/html/0_add-h-f/93-0073-10-01/7750_SR_OS_R… 3. http://www.cisco.com/en/US/docs/ios/12_3t/netflow/command/reference/nfl_a1g…

1 0

[torspec/master] Merge remote-tracking branch 'mikeperry-github/hs-padding-spec'
by nickm＠torproject.org 19 Sep '19

19 Sep '19

commit 3b41712498d407923061dda2b16bf9ea5a6b5bc4 Merge: 317d09b 479f0dc Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 19 15:30:02 2019 -0400 Merge remote-tracking branch 'mikeperry-github/hs-padding-spec' padding-spec.txt | 266 ++++++++++++++++++++- proposals/251-netflow-padding.txt | 2 +- .../302-padding-machines-for-onion-clients.txt | 6 +- 3 files changed, 265 insertions(+), 9 deletions(-)

1 0

[torspec/master] Link to circuit padding dev doc location.
by nickm＠torproject.org 19 Sep '19

19 Sep '19

commit 479f0dc4bd2a873ab153ed0e7d7066e975069929 Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Thu Sep 19 14:10:51 2019 -0500 Link to circuit padding dev doc location. --- padding-spec.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/padding-spec.txt b/padding-spec.txt index 26366ad..4c3c152 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -543,7 +543,7 @@ A. Acknowledgments 14. http://www.ntop.org/wp-content/uploads/2013/03/nProbe_UserGuide.pdf 15. http://arxiv.org/pdf/1512.00524 16. https://www.cs.kau.se/pulls/hot/thebasketcase-ape/ -17. XXX-dev-doc +17. https://github.com/torproject/tor/tree/master/doc/HACKING/CircuitPaddingDev… 18. https://www.usenix.org/node/190967 https://blog.torproject.org/technical-summary-usenix-fingerprinting-paper

1 0

[community/master] trailing space
by emmapeel＠torproject.org 19 Sep '19

19 Sep '19

commit 6c4d1aba92d23a88ee60bca1490954bed1206203 Author: emma peel <emma.peel(a)riseup.net> Date: Thu Sep 19 18:49:39 2019 +0200 trailing space --- content/onion-services/overview/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/onion-services/overview/contents.lr b/content/onion-services/overview/contents.lr index 869db5e..c85306f 100644 --- a/content/onion-services/overview/contents.lr +++ b/content/onion-services/overview/contents.lr @@ -20,7 +20,7 @@ Onion services are services that can only be accessed over Tor. Running an onion ## Why onion services? -Onion services offer various privacy and security benefits to their users. +Onion services offer various privacy and security benefits to their users. ### Location hiding

1 0

[community/master] Editflowandgrammar.lr
by emmapeel＠torproject.org 19 Sep '19

19 Sep '19

commit f96b32d918d75b76c86723ae7b38e7bd49eae6ed Author: Stephanie A. Whited <steph(a)torproject.org> Date: Thu Sep 19 16:17:56 2019 +0000 Editflowandgrammar.lr --- content/localization/contents.lr | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/localization/contents.lr b/content/localization/contents.lr index ccdc74d..e356bc4 100644 --- a/content/localization/contents.lr +++ b/content/localization/contents.lr @@ -8,9 +8,9 @@ _template: layout.html --- title: Localization --- -subtitle: We want Tor to work for everyone in the world, which means a lot of languages. +subtitle: We want Tor to work for everyone in the world, which means our software must be translated into a lot of languages. --- -cta: Help us to translate +cta: Help us translate --- key: 2 --- @@ -22,4 +22,4 @@ body: In order for Tor to work for everyone, it needs to speak everyone's languages. Our volunteer translation team works hard to make this a reality, and we can always use more help. -Our current translation priorities are translating the [Tor Browser](https://torpat.ch/locales), its documentation and the [Tor Project website](https://torpat.ch/tpo-locales), and there are always other documents to translate. +Our current translation priorities are translating [Tor Browser](https://torpat.ch/locales), Tor Browser documentation, and the [Tor Project website](https://torpat.ch/tpo-locales), but there are many other documents that we could use help translating as well.

1 0

[community/master] FlowAndGrammarEdit.lr
by emmapeel＠torproject.org 19 Sep '19

19 Sep '19

commit 929778fb1e80405ebdf7e74c40d35d567e6d2d77 Author: Stephanie A. Whited <steph(a)torproject.org> Date: Thu Sep 19 15:51:08 2019 +0000 FlowAndGrammarEdit.lr --- content/localization/current-status/contents.lr | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/localization/current-status/contents.lr b/content/localization/current-status/contents.lr index 1f539df..e9131f6 100644 --- a/content/localization/current-status/contents.lr +++ b/content/localization/current-status/contents.lr @@ -16,14 +16,14 @@ html: two-columns-page.html --- body: -We have some languages in very good shape, with a number of active and committed contributors (as French, Spanish, Russian, Portuguese). Even when the translations are finished, we always welcome more contributors to this languages. +We have some languages in very good shape, with a number of active and committed contributors (as French, Spanish, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. -We also have a lot of languages with incomplete translations, maybe spoken by less numbers of people, but still important to improve access to the Tor network for people that does not speak English. +Our translations are incomplete for a lot of languages. They may be spoken by fewer people around the world, but it is still critical that we improve access to Tor for people who do not speak English. -We are committed to provide translations to more languagues, please consider [helping with translations](/localization/becoming-tor-translator/) to your native language. +Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language. -The most important languages we need help with at the moment are: Farsi (Persian), Arabic and Korean. But many other languages are being translated, as you can see here: +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: <img class="col-lg-6" src="../../static/images/localization/stats.png"> -You can also see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c…. +You can see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c….

1 0

[translation/https_everywhere_completed] https://gitweb.torproject.org/translation.git/commit/?h=https_everywhere_completed
by translation＠torproject.org 19 Sep '19

19 Sep '19

commit cf0eaa159ba4cba896c0d99b5690750b719de1c6 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Sep 19 14:46:09 2019 +0000 https://gitweb.torproject.org/translation.git/commit/?h=https_everywhere_co… --- es/https-everywhere.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/https-everywhere.dtd b/es/https-everywhere.dtd index 726568a31..1cd7f741c 100644 --- a/es/https-everywhere.dtd +++ b/es/https-everywhere.dtd @@ -14,7 +14,7 @@ <!ENTITY https-everywhere.menu.httpNoWhereExplainedBlocked "Las solicitudes sin cifrar están bloqueadas actualmente"> <!ENTITY https-everywhere.menu.httpNoWhereExplainedAllowed "La solicitudes sin cifrar están actualmente permitidas"> <!ENTITY https-everywhere.menu.seeMore "Ver más"> -<!ENTITY https-everywhere.menu.seeLess ""> +<!ENTITY https-everywhere.menu.seeLess "Ver menos"> <!ENTITY https-everywhere.menu.httpNoWhereMore "Este modo bloquea el contenido y las solicitudes sin cifrar."> <!ENTITY https-everywhere.menu.showCounter "Mostrar contador"> <!ENTITY https-everywhere.menu.viewAllRules "Ver todas las reglas"> @@ -48,7 +48,7 @@ <!ENTITY https-everywhere.chrome.settings_for_this_site_header "Configuraciones para este sitio"> <!ENTITY https-everywhere.chrome.settings_for_this_site_subheader "Cambia tus preferencias para conexiones cifradas"> -<!ENTITY https-everywhere.chrome.settings_for_this_site_explained ""> +<!ENTITY https-everywhere.chrome.settings_for_this_site_explained "Mientras navegas por diferentes sitios web, puedes cambiar tus preferencias para cada uno"> <!ENTITY https-everywhere.chrome.stable_rules "Reglas estables"> <!ENTITY https-everywhere.chrome.stable_rules_description "Forzar conexiones cifradas a estos sitios web:"> <!ENTITY https-everywhere.chrome.experimental_rules "Reglas estables">

1 0