tor-commits July 2018

tor-commits@lists.torproject.org

17 participants
1737 discussions

[translation/support-topics] Update translations for support-topics
by translation＠torproject.org 30 Jul '18

30 Jul '18

commit ceac5af0fb0d0e7174a9655e770f6b9da9245304 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jul 30 15:50:01 2018 +0000 Update translations for support-topics --- pt.json | 110 ++++++++++++++++++++++++++++++++-------------------------------- 1 file changed, 55 insertions(+), 55 deletions(-) diff --git a/pt.json b/pt.json index af01b261c..4aede4554 100644 --- a/pt.json +++ b/pt.json @@ -1,57 +1,57 @@ { - "faq": { - "path": "#faq", - "control": "faq", - "label": "As Perguntas Mais Frequentes" - }, - "tbb": { - "path": "#tbb", - "control": "tbb", - "label": "Tor Browser" - }, - "tormessenger": { - "path": "#tormessenger", - "control": "tormessenger", - "label": "Tor Messenger" - }, - "tormobile": { - "path": "#tormobile", - "control": "tormobile", - "label": "Tor Mobile" - }, - "gettor": { - "path": "#gettor", - "control": "gettor", - "label": "GetTor" - }, - "connecting": { - "path": "#connectingtotor", - "control": "connectingtotor", - "label": "Connecting To Tor" - }, - "censorship": { - "path": "#censorship", - "control": "censorship", - "label": "Censura" - }, - "https": { - "path": "#https", - "control": "https", - "label": "HTTPS" - }, - "operators": { - "path": "#operators", - "control": "operators", - "label": "Operators" - }, - "onionservices": { - "path": "#onionservices", - "control": "onionservices", - "label": "Serviços da Cebola" - }, - "misc": { - "path": "#misc", - "control": "misc", - "label": "Misc" - } + "faq": { + "path": "#faq", + "control": "faq", + "label": "As Perguntas Mais Frequentes" + }, + "tbb": { + "path": "#tbb", + "control": "tbb", + "label": "Tor Browser" + }, + "tormessenger": { + "path": "#tormessenger", + "control": "tormessenger", + "label": "Tor Messenger" + }, + "tormobile": { + "path": "#tormobile", + "control": "tormobile", + "label": "Tor Mobile" + }, + "gettor": { + "path": "#gettor", + "control": "gettor", + "label": "GetTor" + }, + "connecting": { + "path": "#connectingtotor", + "control": "connectingtotor", + "label": "Connecting To Tor" + }, + "censorship": { + "path": "#censorship", + "control": "censura", + "label": "Censura" + }, + "https": { + "path": "#https", + "control": "https", + "label": "HTTPS" + }, + "operators": { + "path": "#operators", + "control": "operadores", + "label": "Operadores" + }, + "onionservices": { + "path": "#onionservices", + "control": "onionservices", + "label": "Serviços da Cebola" + }, + "misc": { + "path": "#misc", + "control": "diversos", + "label": "Diversos" + } }

1 0

[translation/support-tbb] Update translations for support-tbb
by translation＠torproject.org 30 Jul '18

30 Jul '18

commit db40a97910d03e2a7188dbc90cd9265ae5aadbf4 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jul 30 15:49:43 2018 +0000 Update translations for support-tbb --- pt.json | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pt.json b/pt.json index 1020e63db..3fe356a44 100644 --- a/pt.json +++ b/pt.json @@ -74,7 +74,7 @@ "tbb-12": { "id": "#tbb-12", "control": "tbb-12", - "title": "Can I use Flash in Tor Browser?", + "title": "Eu posso utilizar o Flash no Tor Browser?", "description": "<p class=\"mb-3\">Flash is disabled in Tor Browser, and we recommend you do not enable it. We don’t think Flash is safe to use in any browser — it's a very insecure piece of software that can easily compromise your privacy or serve you malware. Fortunately, most websites, devices, and other browsers are moving away from the use of Flash.</p>" }, "tbb-13": { @@ -92,7 +92,7 @@ "tbb-15": { "id": "#tbb-15", "control": "tbb-15", - "title": "Can I download Tor Browser for ChromeOS?", + "title": "Eu posso transferir o Tor Browser para o ChromeOS?", "description": "<p class=\"mb-3\">Unfortunately, we don't yet have a version of Tor Browser for ChromeOS.</p>" }, "tbb-16": { @@ -164,13 +164,13 @@ "tbb-27": { "id": "#tbb-27", "control": "tbb-27", - "title": "How do I update Tor Browser?", + "title": "Como é que eu atualizo o Tor Browser?", "description": "<p class=\"mb-3\">You can update Tor Browser as soon as a new version is released.</p><div class=\"col-md-6\"><div class=\"card\"><img class=\"card-img-top\" src=\"/static/images/image4.png\" alt=\"New release alert\"><div class=\"card-body\"><h4 class=\"card-title\">Tor Browser will prompt you to update the software once a new version has been released.</h4><p class=\"card-text\">The Torbutton icon (the little green onion in the top left corner of the browser) will display a yellow triangle.</p></div></div></div><p class=\"mb-3\">You may see a written indication when Tor Browser opens telling you that an update is available.</p><div class=\"col-md-6\"><div class=\"card\"><img class=\"card-img-top\" src=\"/static/images/image5.png\" alt=\"New release alert\"><div class=\"card-body\"><h4 class=\"card-title\">Card title</h4><p class=\"card-text\">Card text</p></div></div></div><p class=\"mb-3\">Tor browser will install the updates.</p><div class=\"col-md-6\"><div clas s=\"card\"><img class=\"card-img-top\" src=\"/static/images/image3.png\" alt=\"New release alert\"><div class=\"card-body\"><h4 class=\"card-title\">Card title</h4><p class=\"card-text\">Card text</p></div></div></div>" }, "tbb-28": { "id": "#tbb-28", "control": "tbb-28", - "title": "How do I uninstall Tor Browser?", + "title": "Como é que eu desinstalo o Tor Browser?", "description": "<p class=\"mb-3\">Removing Tor Browser from your system is simple:</p><p class=\"mb-3\"><ol><li>Locate your Tor Browser folder or application. The default location on Windows is the Desktop; on macOS it is the Applications folder (on macOS, you have to move it into the Applications folder when you complete the installation process). On Linux, there is no default location, however the folder will be named \"tor-browser_en-US\" if you are running the English Tor Browser.</li><li>Delete the Tor Browser folder or application.</li><li>Empty your Trash.</li></ol></p><p class=\"mb-3\">Note that your operating system’s standard \"Uninstall\" utility is not used.</p>" }, "tbb-29": {

1 0

[translation/support-portal_completed] Update translations for support-portal_completed
by translation＠torproject.org 30 Jul '18

30 Jul '18

commit 384c9ff077464e4d6173704779f9d09b4646f873 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jul 30 14:49:57 2018 +0000 Update translations for support-portal_completed --- contents+es.po | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contents+es.po b/contents+es.po index a32415c27..9ff43e845 100644 --- a/contents+es.po +++ b/contents+es.po @@ -2292,7 +2292,7 @@ msgstr "" #: http//localhost/tormobile/tormobile-1/ #: (content/tormobile/tormobile-1/contents+en.lrquestion.seo_slug) msgid "run-tor-on-android" -msgstr "ejecutar-tor-para-androides" +msgstr "ejecutar-tor-en-android" #: http//localhost/tormobile/tormobile-2/ #: (content/tormobile/tormobile-2/contents+en.lrquestion.title) @@ -2329,7 +2329,7 @@ msgid "" "Project." msgstr "" "Recomendamos una aplicación para iOS llamada Onion Browser, de código " -"abierto, que usa enrutamiento Tor, y está desarrollada por alguien que " +"abierto, que usa enrutamiento Tor y está desarrollada por alguien que " "trabaja estrechamente con Tor Project." #: http//localhost/tormobile/tormobile-3/ @@ -2979,7 +2979,7 @@ msgstr "no-se-puede-alcanzar-x-onion" #: http//localhost/censorship/censorship-1/ #: (content/censorship/censorship-1/contents+en.lrquestion.seo_slug) msgid "our-website-is-blocked-by-a-censor" -msgstr "nuestr-web-está-bloqueada" +msgstr "nuestra-web-está-bloqueada" #: http//localhost/censorship/censorship-2/ #: (content/censorship/censorship-2/contents+en.lrquestion.description)

1 0

[translation/support-portal] Update translations for support-portal
by translation＠torproject.org 30 Jul '18

30 Jul '18

commit 22b77218ffc43199e001d2f69707645b76160ee7 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jul 30 14:49:51 2018 +0000 Update translations for support-portal --- contents+es.po | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contents+es.po b/contents+es.po index a32415c27..9ff43e845 100644 --- a/contents+es.po +++ b/contents+es.po @@ -2292,7 +2292,7 @@ msgstr "" #: http//localhost/tormobile/tormobile-1/ #: (content/tormobile/tormobile-1/contents+en.lrquestion.seo_slug) msgid "run-tor-on-android" -msgstr "ejecutar-tor-para-androides" +msgstr "ejecutar-tor-en-android" #: http//localhost/tormobile/tormobile-2/ #: (content/tormobile/tormobile-2/contents+en.lrquestion.title) @@ -2329,7 +2329,7 @@ msgid "" "Project." msgstr "" "Recomendamos una aplicación para iOS llamada Onion Browser, de código " -"abierto, que usa enrutamiento Tor, y está desarrollada por alguien que " +"abierto, que usa enrutamiento Tor y está desarrollada por alguien que " "trabaja estrechamente con Tor Project." #: http//localhost/tormobile/tormobile-3/ @@ -2979,7 +2979,7 @@ msgstr "no-se-puede-alcanzar-x-onion" #: http//localhost/censorship/censorship-1/ #: (content/censorship/censorship-1/contents+en.lrquestion.seo_slug) msgid "our-website-is-blocked-by-a-censor" -msgstr "nuestr-web-está-bloqueada" +msgstr "nuestra-web-está-bloqueada" #: http//localhost/censorship/censorship-2/ #: (content/censorship/censorship-2/contents+en.lrquestion.description)

1 0

[onionoo/master] Log less frequently requested parameter combinations.
by karsten＠torproject.org 30 Jul '18

30 Jul '18

commit 8ea8ab0fa06c566c66811a9970f5633cfd90d186 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Sun Jul 29 21:42:57 2018 +0200 Log less frequently requested parameter combinations. Implements the first part of #26919, which is to find out whether the "fingerprint" parameter is used at all. --- CHANGELOG.md | 4 ++++ .../java/org/torproject/onionoo/server/MostFrequentString.java | 9 ++++++--- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d024d83..f3428c1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,10 @@ - Support a comma-separated list of AS numbers in the "as" parameter. + * Minor changes + - Extend internal statistics to log less frequently requested + resources and parameter combinations without counts. + # Changes in version 6.1-1.15.0 - 2018-07-16 diff --git a/src/main/java/org/torproject/onionoo/server/MostFrequentString.java b/src/main/java/org/torproject/onionoo/server/MostFrequentString.java index 9fa51c7..c677bb5 100644 --- a/src/main/java/org/torproject/onionoo/server/MostFrequentString.java +++ b/src/main/java/org/torproject/onionoo/server/MostFrequentString.java @@ -43,17 +43,20 @@ class MostFrequentString { StringBuilder sb = new StringBuilder(); int stringsToAdd = 3; int written = 0; + SortedSet<String> remainingStrings = new TreeSet<>(); for (Map.Entry<Integer, SortedSet<String>> e : sortedFrequencies.entrySet()) { for (String string : e.getValue()) { if (stringsToAdd-- > 0) { sb.append((written++ > 0 ? ", " : "") + string + " (" + e.getKey() + ")"); + } else { + remainingStrings.add(string); } } - if (stringsToAdd == 0) { - break; - } + } + for (String string : remainingStrings) { + sb.append(", ").append(string); } return sb.toString(); }

1 0

[torspec/master] Update spec with SHOULD/MUST behavior for padding bytes
by nickm＠torproject.org 30 Jul '18

30 Jul '18

commit 7b1a76c734e186e50858de52675c50468bd8306a Author: Dave Rolek <dmr-x(a)riseup.net> Date: Wed Jul 18 21:00:38 2018 +0000 Update spec with SHOULD/MUST behavior for padding bytes In doing so, specify a general behavior for padding bytes in Section 3 and cross-reference other locations to this, to aid in future consistency. Also clarify a few vague parts of the prior wording. Fixes #26860. --- tor-spec.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index ea195ad..705b159 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -477,7 +477,9 @@ see tor-design.pdf. drop the cell. Since more cell types may be added in the future, ORs should generally not warn when encountering unrecognized commands. - The payload is padded with 0 bytes. + The cell is padded up to the cell length with padding bytes. Senders + SHOULD set padding bytes to NUL and receivers MUST ignore their + value. PADDING cells are currently used to implement connection keepalive. If there is no other traffic, ORs and OPs send one another a PADDING @@ -1479,7 +1481,9 @@ see tor-design.pdf. The 'Length' field of a relay cell contains the number of bytes in the relay payload which contain real payload data. The remainder of - the payload is padded with NUL bytes. + the unencrypted payload is padded with padding bytes. Implementations + handle padding bytes of unencrypted relay cells as they do padding + bytes for other cell types; see Section 3. If the RELAY cell is recognized but the relay command is not understood, the cell must be dropped and ignored. Its contents

1 0

[torspec/master] tor-spec: Prop#289: RELAY cell padding should be randomised
by nickm＠torproject.org 30 Jul '18

30 Jul '18

commit 46bc41bb1b0c00ec4b898d03f936d5c9d9c3fdef Author: teor <teor(a)torproject.org> Date: Fri Jul 20 11:44:29 2018 +1000 tor-spec: Prop#289: RELAY cell padding should be randomised Updates tor-spec for 26871 --- tor-spec.txt | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index 666bc93..114d13c 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -482,9 +482,24 @@ see tor-design.pdf. drop the cell. Since more cell types may be added in the future, ORs should generally not warn when encountering unrecognized commands. - The cell is padded up to the cell length with padding bytes. Senders - SHOULD set padding bytes to NUL and receivers MUST ignore their - value. + The cell is padded up to the cell length with padding bytes. + + Senders set padding bytes depending on the cell's command: + VERSIONS: Payload MUST NOT contain padding bytes. + AUTHORIZE: Payload is unspecified and reserved for future use. + Other variable-length cells: + Payload MAY contain padding bytes at the end of the cell. + Padding bytes SHOULD be set to NUL. + RELAY: Payload MUST be padded to PAYLOAD_LEN with padding bytes. + Padding bytes SHOULD be set to random values. + Other fixed-length cells: + Payload MUST be padded to PAYLOAD_LEN with padding bytes. + Padding bytes SHOULD be set to NUL. + We recommend random padding in RELAY cells, so that cell content is + unpredictable. See proposal 289 for details. For non-RELAY cells, TLS + authenticates cell content, so randomised padding bytes are redundant. + + Receivers MUST ignore padding bytes. PADDING cells are currently used to implement connection keepalive. If there is no other traffic, ORs and OPs send one another a PADDING

1 0

[torspec/master] tor-spec: Clarify padding bytes in VPADDING, PADDING, and DROP cells
by nickm＠torproject.org 30 Jul '18

30 Jul '18

commit 42d93671d424d4811fbebc8f283326634db51045 Author: teor <teor(a)torproject.org> Date: Thu Jul 19 13:05:22 2018 +1000 tor-spec: Clarify padding bytes in VPADDING, PADDING, and DROP cells Closes 26870. --- tor-spec.txt | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index 705b159..666bc93 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -420,7 +420,7 @@ see tor-design.pdf. CircID [CIRCID_LEN bytes] Command [1 byte] - Payload (padded with 0 bytes) [PAYLOAD_LEN bytes] + Payload (padded with padding bytes) [PAYLOAD_LEN bytes] On a version 2 or higher connection, all cells are as in version 1 connections, except for variable-length cells, whose format is: @@ -428,7 +428,11 @@ see tor-design.pdf. CircID [CIRCID_LEN octets] Command [1 octet] Length [2 octets; big-endian integer] - Payload [Length bytes] + Payload (some commands MAY pad) [Length bytes] + + Most variable-length cells MAY be padded with padding bytes, except + for VERSIONS cells, which MUST NOT contain any additional bytes. + (The payload of VPADDING cells consists of padding bytes.) On a version 2 connection, variable-length cells are indicated by a command byte equal to 7 ("VERSIONS"). On a version 3 or @@ -467,7 +471,8 @@ see tor-design.pdf. 132 -- AUTHORIZE (Client authorization) (Not yet used) The interpretation of 'Payload' depends on the type of the cell. - PADDING: Payload is unused. + VPADDING/PADDING: + Payload contains padding bytes. CREATE: Payload contains the handshake challenge. CREATED: Payload contains the handshake response. RELAY: Payload contains the relay header and relay body. @@ -838,6 +843,7 @@ see tor-design.pdf. The address format is a type/length/value sequence as given in section 6.4 below, without the final TTL. The timestamp is a big-endian unsigned integer number of seconds since the Unix epoch. + Implementations MUST ignore unexpected bytes at the end of the cell. Implementations MAY use the timestamp value to help decide if their clocks are skewed. Initiators MAY use "other OR's address" to help @@ -1725,8 +1731,8 @@ see tor-design.pdf. Link padding can be created by sending PADDING or VPADDING cells along the connection; relay cells of type "DROP" can be used for - long-range padding. The contents of a PADDING, VPADDING, or DROP - cell SHOULD be chosen randomly, and MUST be ignored. + long-range padding. The payloads of PADDING, VPADDING, or DROP + cells are filled with padding bytes. See Section 3. If the link protocol is version 5 or higher, link level padding is enabled as per padding-spec.txt. On these connections, clients may

1 0

[torspec/master] Merge branch '26228-padding-bytes_squashed'
by nickm＠torproject.org 30 Jul '18

30 Jul '18

commit 608c4a2b8be043a840c64b6f59f5cbfa48fae33b Merge: 54ef5f2 46bc41b Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Jul 30 10:10:53 2018 -0400 Merge branch '26228-padding-bytes_squashed' tor-spec.txt | 39 ++++++++++++++++++++++++++++++++------- 1 file changed, 32 insertions(+), 7 deletions(-) diff --cc tor-spec.txt index 02bb9ae,114d13c..4cc38b3 --- a/tor-spec.txt +++ b/tor-spec.txt @@@ -468,9 -471,10 +472,10 @@@ see tor-design.pdf 132 -- AUTHORIZE (Client authorization) (Not yet used) The interpretation of 'Payload' depends on the type of the cell. - PADDING: Payload is unused. + VPADDING/PADDING: + Payload contains padding bytes. - CREATE: Payload contains the handshake challenge. - CREATED: Payload contains the handshake response. + CREATE/CREATE2: Payload contains the handshake challenge. + CREATED/CREATED2: Payload contains the handshake response. RELAY: Payload contains the relay header and relay body. DESTROY: Payload contains a reason for closing the circuit. (see 5.4)

1 0

[torspec/master] Clarify some places where we meant RELAY to include RELAY_EARLY.
by nickm＠torproject.org 30 Jul '18

30 Jul '18

commit 684c46b8222f1ad96971729124cc06cb7fb3773a Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Jul 30 10:13:43 2018 -0400 Clarify some places where we meant RELAY to include RELAY_EARLY. --- tor-spec.txt | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index 4cc38b3..c54b63c 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -476,7 +476,7 @@ see tor-design.pdf. Payload contains padding bytes. CREATE/CREATE2: Payload contains the handshake challenge. CREATED/CREATED2: Payload contains the handshake response. - RELAY: Payload contains the relay header and relay body. + RELAY/RELAY_EARLY: Payload contains the relay header and relay body. DESTROY: Payload contains a reason for closing the circuit. (see 5.4) Upon receiving any other value for the command field, an OR must @@ -491,14 +491,15 @@ see tor-design.pdf. Other variable-length cells: Payload MAY contain padding bytes at the end of the cell. Padding bytes SHOULD be set to NUL. - RELAY: Payload MUST be padded to PAYLOAD_LEN with padding bytes. - Padding bytes SHOULD be set to random values. + RELAY/RELAY_EARLY: Payload MUST be padded to PAYLOAD_LEN with padding + bytes. Padding bytes SHOULD be set to random values. Other fixed-length cells: Payload MUST be padded to PAYLOAD_LEN with padding bytes. Padding bytes SHOULD be set to NUL. - We recommend random padding in RELAY cells, so that cell content is - unpredictable. See proposal 289 for details. For non-RELAY cells, TLS - authenticates cell content, so randomised padding bytes are redundant. + We recommend random padding in RELAY/RELAY_EARLY cells, so that the cell + content is unpredictable. See proposal 289 for details. For other + cells, TLS authenticates cell content, so randomised padding bytes are + redundant. Receivers MUST ignore padding bytes.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits July 2018