tor-commits January 2017

tor-commits@lists.torproject.org

22 participants
1796 discussions

[translation/whisperback] Update translations for whisperback
by translation＠torproject.org 03 Jan '17

03 Jan '17

commit 2c004de5003aae6b9791d8f4a7d1613adbded52c Author: Translation commit bot <translation(a)torproject.org> Date: Tue Jan 3 01:15:20 2017 +0000 Update translations for whisperback --- es_MX/es_MX.po | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/es_MX/es_MX.po b/es_MX/es_MX.po index bba58e5..818ba24 100644 --- a/es_MX/es_MX.po +++ b/es_MX/es_MX.po @@ -4,13 +4,14 @@ # # Translators: # Melvin Rohark <rohark20(a)gmail.com>, 2016 +# Sanxcher Motala <motala.sanxcher(a)yandex.com>, 2017 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2015-12-16 19:54+0100\n" -"PO-Revision-Date: 2016-09-23 16:00+0000\n" -"Last-Translator: Melvin Rohark <rohark20(a)gmail.com>\n" +"PO-Revision-Date: 2017-01-03 01:05+0000\n" +"Last-Translator: Sanxcher Motala <motala.sanxcher(a)yandex.com>\n" "Language-Team: Spanish (Mexico) (http://www.transifex.com/otf/torproject/language/es_MX/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -27,7 +28,7 @@ msgstr "Email de contacto incorrecto: %s" #: ../whisperBack/whisperback.py:73 #, python-format msgid "Invalid contact OpenPGP key: %s" -msgstr "" +msgstr "Clave invalida de contacto OpenPGP: %s" #: ../whisperBack/whisperback.py:75 msgid "Invalid contact OpenPGP public key block" @@ -123,7 +124,7 @@ msgstr "" #: ../whisperBack/gui.py:385 msgid "translator-credits" -msgstr "" +msgstr "Créditos al traductor" #: ../whisperBack/gui.py:412 msgid "This doesn't seem to be a valid URL or OpenPGP key."

1 0

[torspec/master] Reorder shared randomness and parameter fields
by atagar＠torproject.org 02 Jan '17

02 Jan '17

commit 5700fdcfa7e0257b5adb92539f4e0c4e94d5e6b2 Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Jan 2 12:51:31 2017 -0800 Reorder shared randomness and parameter fields Oops! Thought I pushed this along with the other changes. Multiple new descriptor fields were added in the wrong order. Reordering them to match what actually appears in the consensus and votes... https://trac.torproject.org/projects/tor/ticket/21059 --- dir-spec.txt | 154 ++++++++++++++++++++++++++++++++--------------------------- 1 file changed, 83 insertions(+), 71 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index c25ccf7..32e6347 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1696,78 +1696,10 @@ that we'll ignore the advertised bandwidth claims of routers without measured bandwidth. - "shared-rand-participate" NL - - [At most once for votes; does not occur in consensuses.] - - Denotes that the directory authority supports and can participate in the - shared random protocol. - - "shared-rand-commit" SP Version SP AlgName SP Identity SP Commit [SP Reveal] NL - - [Any number for votes; does not occur in consensuses.] - - Version ::= An integer greater or equal to 0. - AlgName ::= 1*(ALPHA / DIGIT / "_" / "-") - Identity ::= 40 * HEXDIG - Commit ::= Base64-encoded-data - Reveal ::= Base64-encoded-data - - Denotes a directory authority commit for the shared randomness - protocol, containing the commitment value and potentially also the - reveal value. See sections [COMMITREVEAL] and [VALIDATEVALUES] of - proposal 250 on how to generate and validate these values. - - Version is the current shared randomness protocol version. AlgName is - the hash algorithm that is used (e.g. "sha3-256") and Identity is the - authority's SHA1 v3 identity fingerprint. Commit is the encoded - commitment value in base64. Reveal is optional and if it's set, it - contains the reveal value in base64. - - If a vote contains multiple commits from the same authority, the - receiver MUST only consider the first commit listed. - - "shared-rand-previous-value" SP NumReveals SP Value NL - - [At most once.] - - NumReveals ::= An integer greater or equal to 0. - Value ::= Base64-encoded-data - - The shared random value that was generated during the second-to-last - shared randomness protocol run. For example, if this document was - created on the 5th of November, this field carries the shared random - value generated during the protocol run of the 3rd of November. - - See section [SRCALC] of proposal 250 for instructions on how to compute - this value, and see section [CONS] for why we include old shared random - values in votes and consensus. - - Value is the actual shared random value encoded in base64. NumReveals - is the number of commits used to generate this SRV. - - "shared-rand-current-value" SP NumReveals SP Value NL - - [At most once.] - - NumReveals ::= An integer greater or equal to 0. - Value ::= Base64-encoded-data - - The shared random value that was generated during the latest shared - randomness protocol run. For example, if this document was created on - the 5th of November, this field carries the shared random value - generated during the protocol run of the 4th of November - - See section [SRCALC] of proposal 250 for instructions on how to compute - this value given the active commits. - - Value is the actual shared random value encoded in base64. NumReveals - is the number of commits used to generate this SRV. - - "recommended-relay-protocols" SP Entries NL - "required-relay-protocols" SP Entries NL "recommended-client-protocols" SP Entries NL + "recommended-relay-protocols" SP Entries NL "required-client-protocols" SP Entries NL + "required-relay-protocols" SP Entries NL [At most once for each.] @@ -1922,6 +1854,43 @@ the shared randomness protocol). Min: 1. Max: INT32_MAX. Default: 2/3 of the total number of dirauth. + "shared-rand-previous-value" SP NumReveals SP Value NL + + [At most once] + + NumReveals ::= An integer greater or equal to 0. + Value ::= Base64-encoded-data + + The shared random value that was generated during the second-to-last + shared randomness protocol run. For example, if this document was + created on the 5th of November, this field carries the shared random + value generated during the protocol run of the 3rd of November. + + See section [SRCALC] of proposal 250 for instructions on how to compute + this value, and see section [CONS] for why we include old shared random + values in votes and consensus. + + Value is the actual shared random value encoded in base64. NumReveals + is the number of commits used to generate this SRV. + + "shared-rand-current-value" SP NumReveals SP Value NL + + [At most once] + + NumReveals ::= An integer greater or equal to 0. + Value ::= Base64-encoded-data + + The shared random value that was generated during the latest shared + randomness protocol run. For example, if this document was created on + the 5th of November, this field carries the shared random value + generated during the protocol run of the 4th of November + + See section [SRCALC] of proposal 250 for instructions on how to compute + this value given the active commits. + + Value is the actual shared random value encoded in base64. NumReveals + is the number of commits used to generate this SRV. + The authority section of a vote contains the following items, followed in turn by the authority's current key certificate: @@ -1938,7 +1907,7 @@ "contact" SP string NL - [Exactly once.] + [Exactly once] An arbitrary string describing how to contact the directory server's administrator. Administrators should include at least an @@ -1956,6 +1925,49 @@ vulnerability that affected multiple authorities, like the Debian OpenSSL RNG bug of May 2008.) + "shared-rand-participate" NL + + [At most once] + + Denotes that the directory authority supports and can participate in the + shared random protocol. + + "shared-rand-commit" SP Version SP AlgName SP Identity SP Commit [SP Reveal] NL + + [Any number of times] + + Version ::= An integer greater or equal to 0. + AlgName ::= 1*(ALPHA / DIGIT / "_" / "-") + Identity ::= 40 * HEXDIG + Commit ::= Base64-encoded-data + Reveal ::= Base64-encoded-data + + Denotes a directory authority commit for the shared randomness + protocol, containing the commitment value and potentially also the + reveal value. See sections [COMMITREVEAL] and [VALIDATEVALUES] of + proposal 250 on how to generate and validate these values. + + Version is the current shared randomness protocol version. AlgName is + the hash algorithm that is used (e.g. "sha3-256") and Identity is the + authority's SHA1 v3 identity fingerprint. Commit is the encoded + commitment value in base64. Reveal is optional and if it's set, it + contains the reveal value in base64. + + If a vote contains multiple commits from the same authority, the + receiver MUST only consider the first commit listed. + + "shared-rand-previous-value" SP NumReveals SP Value NL + + [At most once] + + See shared-rand-previous-value description above. + + "shared-rand-current-value" SP NumReveals SP Value NL + + [At most once] + + See shared-rand-current-value decription above. + The authority section of a consensus contains groups the following items, in the order given, with one group for each authority that contributed to the consensus, with groups sorted by authority identity digest:

1 0

[torspec/master] Change header ordering from a MUST to SHOULD clause
by atagar＠torproject.org 02 Jan '17

02 Jan '17

commit 578477a6af99ec1e4a501e267a563730519ffc0f Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Jan 2 12:16:44 2017 -0800 Change header ordering from a MUST to SHOULD clause We had this as a 'MUST' because the directory authorities need to agree upon an ordering in their votes to derive at a signed consensus. However, this requirement is turning out to be very error prone... https://trac.torproject.org/projects/tor/ticket/21059 Got the ordering issues sorted out... I think. However, this has bitten us three times in a row and clearly will bite us more in the future so loosening these requirements a little. --- dir-spec.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dir-spec.txt b/dir-spec.txt index 26b0800..c25ccf7 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1526,7 +1526,7 @@ Some items appear only in votes, and some items appear only in consensuses. Unless specified, items occur in both. - The preamble contains the following items. They MUST occur in the + The preamble contains the following items. They SHOULD occur in the order given here: "network-status-version" SP version NL

1 0

[torspec/master] Fix ordering of flag-threshold parameter
by atagar＠torproject.org 02 Jan '17

02 Jan '17

commit 3c91ffac5f5c04b1f3295d961d95a8f00cf5c2fe Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Jan 2 12:15:26 2017 -0800 Fix ordering of flag-threshold parameter Spec doesn't match tor with regard to the ordering of this field either. It was added way back in 2013 but for Stem's checks I coded against tor's actual behavior rather than the spec. Hence why it went under the radar. --- dir-spec.txt | 88 ++++++++++++++++++++++++++++++------------------------------ 1 file changed, 44 insertions(+), 44 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index c701842..26b0800 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1575,50 +1575,6 @@ consensus document produced from this vote should not be used. See section 1.4 for voting timeline information. - "flag-thresholds" SP Thresholds NL - - [At most once for votes; does not occur in consensuses.] - - A space-separated list of the internal performance thresholds - that the directory authority had at the moment it was forming - a vote. - - The metaformat is: - Thresholds = Threshold | Threshold SP Thresholds - Threshold = ThresholdKey '=' ThresholdVal - ThresholdKey = (KeywordChar | "_") + - ThresholdVal = [0-9]+("."[0-9]+)? "%"? - - Commonly used Thresholds at this point include: - - "stable-uptime" -- Uptime (in seconds) required for a relay - to be marked as stable. - - "stable-mtbf" -- MTBF (in seconds) required for a relay to be - marked as stable. - - "enough-mtbf" -- Whether we have measured enough MTBF to look - at stable-mtbf instead of stable-uptime. - - "fast-speed" -- Bandwidth (in bytes per second) required for - a relay to be marked as fast. - - "guard-wfu" -- WFU (in seconds) required for a relay to be - marked as guard. - - "guard-tk" -- Weighted Time Known (in seconds) required for a - relay to be marked as guard. - - "guard-bw-inc-exits" -- If exits can be guards, then all guards - must have a bandwidth this high. - - "guard-bw-exc-exits" -- If exits can't be guards, then all guards - must have a bandwidth this high. - - "ignoring-advertised-bws" -- 1 if we have enough measured bandwidths - that we'll ignore the advertised bandwidth - claims of routers without measured bandwidth. - "fresh-until" SP YYYY-MM-DD SP HH:MM:SS NL [Exactly once.] @@ -1696,6 +1652,50 @@ enough votes were counted for the consensus for an authoritative opinion to have been formed about their status. + "flag-thresholds" SP Thresholds NL + + [At most once for votes; does not occur in consensuses.] + + A space-separated list of the internal performance thresholds + that the directory authority had at the moment it was forming + a vote. + + The metaformat is: + Thresholds = Threshold | Threshold SP Thresholds + Threshold = ThresholdKey '=' ThresholdVal + ThresholdKey = (KeywordChar | "_") + + ThresholdVal = [0-9]+("."[0-9]+)? "%"? + + Commonly used Thresholds at this point include: + + "stable-uptime" -- Uptime (in seconds) required for a relay + to be marked as stable. + + "stable-mtbf" -- MTBF (in seconds) required for a relay to be + marked as stable. + + "enough-mtbf" -- Whether we have measured enough MTBF to look + at stable-mtbf instead of stable-uptime. + + "fast-speed" -- Bandwidth (in bytes per second) required for + a relay to be marked as fast. + + "guard-wfu" -- WFU (in seconds) required for a relay to be + marked as guard. + + "guard-tk" -- Weighted Time Known (in seconds) required for a + relay to be marked as guard. + + "guard-bw-inc-exits" -- If exits can be guards, then all guards + must have a bandwidth this high. + + "guard-bw-exc-exits" -- If exits can't be guards, then all guards + must have a bandwidth this high. + + "ignoring-advertised-bws" -- 1 if we have enough measured bandwidths + that we'll ignore the advertised bandwidth + claims of routers without measured bandwidth. + "shared-rand-participate" NL [At most once for votes; does not occur in consensuses.]

1 0

[translation/tor-browser-manual] Update translations for tor-browser-manual
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit 24b2e657702752248459f701a2d327eaaca76ca6 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:48:24 2017 +0000 Update translations for tor-browser-manual --- es_MX/es_MX.po | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/es_MX/es_MX.po b/es_MX/es_MX.po index 0ae7776..0bb5c62 100644 --- a/es_MX/es_MX.po +++ b/es_MX/es_MX.po @@ -2,12 +2,13 @@ # Héctor Limón López <hill900013(a)gmail.com>, 2016 # luanducho <luis.anducho(a)hotmail.com>, 2016 # Christian Reyes <christian-crg(a)hotmail.com>, 2016 +# Sanxcher Motala <motala.sanxcher(a)yandex.com>, 2017 msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2016-12-06 16:36-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Christian Reyes <christian-crg(a)hotmail.com>, 2016\n" +"Last-Translator: Sanxcher Motala <motala.sanxcher(a)yandex.com>, 2017\n" "Language-Team: Spanish (Mexico) (https://www.transifex.com/otf/teams/1519/es_MX/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -766,10 +767,14 @@ msgid "" " that it is connecting to the right location and that the connection is not " "being tampered with." msgstr "" +"La dirección de un servicio de cebolla es generada automáticamente, asi que " +"los operadores no tienen que comprar un nombre de dominio. La URL de .onion " +"también ayuda a que Tor se asegure de estar conectado al lugar correcto y " +"que la conexión no sea alterada. " #: onionsites.page:46 msgid "How to access an onion service" -msgstr "" +msgstr "Como acceder un servicio de cebolla" #. This is a reference to an external file such as an image or video. When #. the file changes, the md5 hash will change to let you know you need to @@ -788,6 +793,9 @@ msgid "" "service in order to connect to it. An onion address is a string of sixteen " "mostly random letters and numbers, followed by “.onion”." msgstr "" +"Como cualquier otro sitio, tienes que saber la dirección de un servicio de " +"cebolla para conectarte a el. Una dirección de cebolla es una linea de " +"dieciséis letras y numeros al azar, seguidos por \".onion\" (cebolla)." #: onionsites.page:58 troubleshooting.page:10 msgid "Troubleshooting"

1 0

[translation/tails-openpgp-applet] Update translations for tails-openpgp-applet
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit 016fbbc5593a39fc2da1adc81ada0d898a478be6 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:47:15 2017 +0000 Update translations for tails-openpgp-applet --- es_MX/openpgp-applet.pot | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/es_MX/openpgp-applet.pot b/es_MX/openpgp-applet.pot index d9e517a..4594e27 100644 --- a/es_MX/openpgp-applet.pot +++ b/es_MX/openpgp-applet.pot @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: tails(a)boum.org\n" "POT-Creation-Date: 2015-08-10 15:55+0200\n" -"PO-Revision-Date: 2017-01-02 18:10+0000\n" +"PO-Revision-Date: 2017-01-02 18:19+0000\n" "Last-Translator: Sanxcher Motala <motala.sanxcher(a)yandex.com>\n" "Language-Team: Spanish (Mexico) (http://www.transifex.com/otf/torproject/language/es_MX/)\n" "MIME-Version: 1.0\n" @@ -84,7 +84,7 @@ msgstr "" #: bin/openpgp-applet:412 msgid "Status" -msgstr "" +msgstr "Estatus" #: bin/openpgp-applet:444 msgid "Fingerprint:" @@ -112,7 +112,7 @@ msgstr "" msgid "" "Hide the user IDs of all recipients of an encrypted message. Otherwise " "anyone that sees the encrypted message can see who the recipients are." -msgstr "" +msgstr "Esconde la identificación de usuario de todos los receptores de un mensaje codificado. De otra manera cualquiera que vea el mensaje codificado puede ver quienes son los receptores. " #: bin/openpgp-applet:556 msgid "Sign message as:"

1 0

[translation/tor_animation] Update translations for tor_animation
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit ebdff4529f21be32d6c43fddca42fc2ad4c40f0c Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:46:57 2017 +0000 Update translations for tor_animation --- es_MX.srt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es_MX.srt b/es_MX.srt index 887bf35..327fb46 100644 --- a/es_MX.srt +++ b/es_MX.srt @@ -111,8 +111,8 @@ the stronger it gets 24 00:01:23,140 --> 00:01:27,800 -as it's easier to hide in a crowd -of people who look exactly the same. +Es mas fácil esconderse entre +gente que parezca exactamente igual 25 00:01:28,700 --> 00:01:31,240

1 0

[translation/tails-greeter-2] Update translations for tails-greeter-2
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit 0ce8e8947f22e0972e8e29698ec69f9d4ae3be2b Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:18:23 2017 +0000 Update translations for tails-greeter-2 --- es_MX/es_MX.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es_MX/es_MX.po b/es_MX/es_MX.po index d4e244e..2753f46 100644 --- a/es_MX/es_MX.po +++ b/es_MX/es_MX.po @@ -10,7 +10,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-12-03 13:14+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Arturo J. Gueta Lozano <arturo(a)gueta.net>, 2016\n" +"Last-Translator: Sanxcher Motala <motala.sanxcher(a)yandex.com>, 2017\n" "Language-Team: Spanish (Mexico) (https://www.transifex.com/otf/teams/1519/es_MX/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -95,7 +95,7 @@ msgstr "" #: ../data/greeter.ui.h:20 msgid "Language & Region" -msgstr "" +msgstr "Lenguaje y Región" #: ../data/greeter.ui.h:21 msgid "Default Settings"

1 0

[translation/tor-messenger-uiproperties] Update translations for tor-messenger-uiproperties
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit 2995016289a22aab887fd25fe2c3518cdb283808 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:18:16 2017 +0000 Update translations for tor-messenger-uiproperties --- es_MX/ui.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es_MX/ui.properties b/es_MX/ui.properties index de5c232..db5598e 100644 --- a/es_MX/ui.properties +++ b/es_MX/ui.properties @@ -10,7 +10,7 @@ auth.successThem=Your contact has successfully verified your identity. You may w auth.fail=Failed to verify your contact's identity. auth.waiting=Waiting for contact ... reauth.label=Reverify your contact's identity -prefs.label=OTR Preferences +prefs.label=Preferencias de OTR alert.start=Attempting to start a private conversation with %S. alert.refresh=Attempting to refresh the private conversation with %S. alert.gone_insecure=Private conversation with %S ended.

1 0

[translation/tor-messenger-privdtd_completed] Update translations for tor-messenger-privdtd_completed
by translation＠torproject.org 02 Jan '17

02 Jan '17

commit 62b92b7d71b588c2f942682d3e7b0b983038b01c Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jan 2 18:18:08 2017 +0000 Update translations for tor-messenger-privdtd_completed --- es_MX/priv.dtd | 2 ++ 1 file changed, 2 insertions(+) diff --git a/es_MX/priv.dtd b/es_MX/priv.dtd new file mode 100644 index 0000000..145e808 --- /dev/null +++ b/es_MX/priv.dtd @@ -0,0 +1,2 @@ +<!ENTITY privDialog.title "Generando llave privada"> +<!ENTITY privDialog.done "Hecho"> \ No newline at end of file

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits January 2017