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

[tor/release-0.3.4] Update Cargo.lock with new comment; suppress 29244.
by arma＠torproject.org 05 Feb '19

05 Feb '19

commit 4d7a0a1310886c6b27505aeea1ac54e811e7dbf0 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Feb 1 16:38:23 2019 +0100 Update Cargo.lock with new comment; suppress 29244. --- changes/bug29244 | 4 ++++ src/rust/Cargo.lock | 2 ++ 2 files changed, 6 insertions(+) diff --git a/changes/bug29244 b/changes/bug29244 new file mode 100644 index 000000000..6206a9546 --- /dev/null +++ b/changes/bug29244 @@ -0,0 +1,4 @@ + o Minor bugfixes (build, compatibility): + - … [View More]

1 0

[webwml/master] remove a confusing word
by arma＠torproject.org 05 Feb '19

05 Feb '19

commit 2f6fe19963ea3f9c1226be5ce94db0a15c92c4ac Author: Roger Dingledine <arma(a)torproject.org> Date: Tue Feb 5 07:17:48 2019 -0500 remove a confusing word --- docs/en/debian.wml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/debian.wml b/docs/en/debian.wml index 83e14365..1306d6ac 100644 --- a/docs/en/debian.wml +++ b/docs/en/debian.wml @@ -282,7 +282,7 @@ access it you might try to use the name of one of its part instead. Try <p… [View More]

1 0

[webwml/master] make that same change to another part of the file
by arma＠torproject.org 05 Feb '19

05 Feb '19

commit 07b9a1a6fc73a645dba1629d07de38485c8acd31 Author: Roger Dingledine <arma(a)torproject.org> Date: Tue Feb 5 07:17:01 2019 -0500 make that same change to another part of the file (i am still confused why this file has so many versions of itself. i assume it has to do with javascript. but still.) --- docs/en/debian.wml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/debian.wml b/docs/en/debian.wml index bd980cd1..83e14365 100644 --- … [View More]

1 0

[webwml/master] Who doesn't have gpg
by weasel＠torproject.org 05 Feb '19

05 Feb '19

commit 6ce2a20ac403f55f29258fa1988ecf86c66e5ea3 Author: Peter Palfrader <peter(a)palfrader.org> Date: Tue Feb 5 13:14:25 2019 +0100 Who doesn't have gpg --- docs/en/debian.wml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/en/debian.wml b/docs/en/debian.wml index 3a49d418..bd980cd1 100644 --- a/docs/en/debian.wml +++ b/docs/en/debian.wml @@ -71,14 +71,6 @@ the root password of your system. -GPG: -<a href="https://… [View More]

1 0

[webwml/master] Do not try to fetch the key from keyservers
by weasel＠torproject.org 05 Feb '19

05 Feb '19

commit bb9565587d53bae33ae3f3ea09bc3ba6bd9b16d8 Author: Peter Palfrader <peter(a)palfrader.org> Date: Tue Feb 5 13:12:15 2019 +0100 Do not try to fetch the key from keyservers --- docs/en/debian.wml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/debian.wml b/docs/en/debian.wml index 5b230b3a..3a49d418 100644 --- a/docs/en/debian.wml +++ b/docs/en/debian.wml @@ -134,8 +134,8 @@ deb https://deb.torproject.org/torproject.org jessie main Then … [View More]

1 0

[torspec/master] Set prop299 status to open
by nickm＠torproject.org 05 Feb '19

05 Feb '19

commit 6f3d59072b525e76282bec619c22c36744101760 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Feb 5 07:09:55 2019 -0500 Set prop299 status to open --- proposals/000-index.txt | 4 ++-- proposals/299-ip-failure-count.txt | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/000-index.txt b/proposals/000-index.txt index 8184b74..dac8d7b 100644 --- a/proposals/000-index.txt +++ b/proposals/000-index.txt @@ -219,7 +219,7 @@ Proposals … [View More]

1 0

[torspec/master] Convert prop299 to unix line-endings
by nickm＠torproject.org 05 Feb '19

05 Feb '19

commit 87bc2f172d87fff042dc493e16419687518c3866 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Feb 5 07:10:23 2019 -0500 Convert prop299 to unix line-endings --- proposals/299-ip-failure-count.txt | 234 ++++++++++++++++++------------------- 1 file changed, 117 insertions(+), 117 deletions(-) diff --git a/proposals/299-ip-failure-count.txt b/proposals/299-ip-failure-count.txt index 99d2534..60d35d4 100644 --- a/proposals/299-ip-failure-count.txt +++ b/proposals/299-ip-… [View More]failure-count.txt @@ -1,117 +1,117 @@ -Filename: 299-ip-failure-count.txt -Title: Preferring IPv4 or IPv6 based on IP Version Failure Count -Author: Neel Chauhan -Created: 25-Jan-2019 -Status: Open -Ticket: https://trac.torproject.org/projects/tor/ticket/27491 - -1. Introduction - - As IPv4 address space becomes scarce, ISPs and organizations will deploy - IPv6 in their networks. Right now, Tor clients connect to guards using - IPv4 connectivity by default. - - When networks first transition to IPv6, both IPv4 and IPv6 will be enabled - on most networks in a so-called "dual-stack" configuration. This is to not - break existing IPv4-only applications while enabling IPv6 connectivity. - However, IPv6 connectivity may be unreliable and clients should be able - to connect to the guard using the most reliable technology, whether IPv4 - or IPv6. - - In ticket #27490, we introduced the option ClientAutoIPv6ORPort which adds - preliminary "happy eyeballs" support. If set, this lets a client randomly - choose between IPv4 or IPv6. However, this random decision does not take - into account unreliable connectivity or network failures of an IP family. - A successful Tor implementation of the happy eyeballs algorithm requires - that unreliable connectivity on IPv4 and IPv6 are taken into consideration. - - This proposal describes an algorithm to take into account network failures - in the random decision used for choosing an IP family and the data fields - used by the algorithm. - -2. Failure Counter Design - - I propose that the failure counter uses the following fields: - - * IPv4 failure count - - * IPv4 failure count from no route (autofail) - - * IPv6 failure count - - * IPv6 failure count from no route (autofail) - - These entries will exist as internal counters for the current session, and - as a list of the previous counts of these counters from previous sessions in - the state file. - - These values will be stored as 32-bit unsigned integers for the current - session, and as comma seperated values in the statefile. - - The list capacity will be the 4 most recent sessions for each field above - stored in the state file with the least recent first. This is for the - following reasons: - - * We can forget about the oldest sessions without having to keep the - exact timestamp when a client failed. This prevents an attacker from - getting detailed failure information from the state file. - - * Some clients (mobile phones, laptops) may switch between networks of - which may be more or less reliable than the previous in terms of IPv4 - or IPv6. In this case, it makes less sense to remember old failures - caused on a different network from the current one. - - When Tor is being closed, and there are less than four entries for each - field, we will append the current session at the end. If there are four - entries, we will remove the oldest entry and then add the current session's - values at Tor's shutdown. - -3. Failure Probability Calculation - - The failure count of one IP version will increase the probability of the - other IP version. For instance, a failure of IPv4 will increase the IPv6 - probability, and vice versa. - - When the IP version is being chosen, I propose that these values will be - included in the guard selection code: - - * IPv4 failure points - - * IPv6 failure points - - * Total failure points - - These values will be stored as 32-bit unsigned integers. - - A generic failure of an IP version will add one point to the failure point - count values of the particular IP version which failed. - - A failure of an IP version from a "no route" error which happens when - connections automatically fail will be counted as two failure points - for the automatically failed version. - - The failure points for both IPv4 and IPv6 is sum of the values in the state - file plus the current session's failure values. The total failure points is - a sum of the IPv4 and IPv6 failure points. - - The probability of a particular IP version is the failure points of the - other version divided by the total number of failure points, multiplied - by 8 and stored as an integer. We will call this value the summarized - failure point value (SFPV). The reason for this summarization is to - emulate a probability in 1/8 intervals by the random number generator. - - In the random number generator, we will choose a random number between 0 - and 8. If the random number is less than the IPv6 SFPV, we will choose - IPv4. If it is equal or greater, we will choose IPv6. - - If the probability is 0/8 with a SFPV value of 0, it will be rounded to - 1/8 with a SFPV of 1. Also, if the probability is 8/8 with a SFPV of 8, - it will be rounded to 7/8 with a SFPV of 7. The reason for this is to - accomodate mobile clients which could change networks at any time (e.g. - WiFi to cellular) which may be more or less reliable in terms of a - particular IP family when compared to the previous network of the client. - -4. Acknowledgements - - Thank you teor for aiding me with the implementation of Happy Eyeballs in - Tor. This would not have been possible if it weren't for you. +Filename: 299-ip-failure-count.txt +Title: Preferring IPv4 or IPv6 based on IP Version Failure Count +Author: Neel Chauhan +Created: 25-Jan-2019 +Status: Open +Ticket: https://trac.torproject.org/projects/tor/ticket/27491 + +1. Introduction + + As IPv4 address space becomes scarce, ISPs and organizations will deploy + IPv6 in their networks. Right now, Tor clients connect to guards using + IPv4 connectivity by default. + + When networks first transition to IPv6, both IPv4 and IPv6 will be enabled + on most networks in a so-called "dual-stack" configuration. This is to not + break existing IPv4-only applications while enabling IPv6 connectivity. + However, IPv6 connectivity may be unreliable and clients should be able + to connect to the guard using the most reliable technology, whether IPv4 + or IPv6. + + In ticket #27490, we introduced the option ClientAutoIPv6ORPort which adds + preliminary "happy eyeballs" support. If set, this lets a client randomly + choose between IPv4 or IPv6. However, this random decision does not take + into account unreliable connectivity or network failures of an IP family. + A successful Tor implementation of the happy eyeballs algorithm requires + that unreliable connectivity on IPv4 and IPv6 are taken into consideration. + + This proposal describes an algorithm to take into account network failures + in the random decision used for choosing an IP family and the data fields + used by the algorithm. + +2. Failure Counter Design + + I propose that the failure counter uses the following fields: + + * IPv4 failure count + + * IPv4 failure count from no route (autofail) + + * IPv6 failure count + + * IPv6 failure count from no route (autofail) + + These entries will exist as internal counters for the current session, and + as a list of the previous counts of these counters from previous sessions in + the state file. + + These values will be stored as 32-bit unsigned integers for the current + session, and as comma seperated values in the statefile. + + The list capacity will be the 4 most recent sessions for each field above + stored in the state file with the least recent first. This is for the + following reasons: + + * We can forget about the oldest sessions without having to keep the + exact timestamp when a client failed. This prevents an attacker from + getting detailed failure information from the state file. + + * Some clients (mobile phones, laptops) may switch between networks of + which may be more or less reliable than the previous in terms of IPv4 + or IPv6. In this case, it makes less sense to remember old failures + caused on a different network from the current one. + + When Tor is being closed, and there are less than four entries for each + field, we will append the current session at the end. If there are four + entries, we will remove the oldest entry and then add the current session's + values at Tor's shutdown. + +3. Failure Probability Calculation + + The failure count of one IP version will increase the probability of the + other IP version. For instance, a failure of IPv4 will increase the IPv6 + probability, and vice versa. + + When the IP version is being chosen, I propose that these values will be + included in the guard selection code: + + * IPv4 failure points + + * IPv6 failure points + + * Total failure points + + These values will be stored as 32-bit unsigned integers. + + A generic failure of an IP version will add one point to the failure point + count values of the particular IP version which failed. + + A failure of an IP version from a "no route" error which happens when + connections automatically fail will be counted as two failure points + for the automatically failed version. + + The failure points for both IPv4 and IPv6 is sum of the values in the state + file plus the current session's failure values. The total failure points is + a sum of the IPv4 and IPv6 failure points. + + The probability of a particular IP version is the failure points of the + other version divided by the total number of failure points, multiplied + by 8 and stored as an integer. We will call this value the summarized + failure point value (SFPV). The reason for this summarization is to + emulate a probability in 1/8 intervals by the random number generator. + + In the random number generator, we will choose a random number between 0 + and 8. If the random number is less than the IPv6 SFPV, we will choose + IPv4. If it is equal or greater, we will choose IPv6. + + If the probability is 0/8 with a SFPV value of 0, it will be rounded to + 1/8 with a SFPV of 1. Also, if the probability is 8/8 with a SFPV of 8, + it will be rounded to 7/8 with a SFPV of 7. The reason for this is to + accomodate mobile clients which could change networks at any time (e.g. + WiFi to cellular) which may be more or less reliable in terms of a + particular IP family when compared to the previous network of the client. + +4. Acknowledgements + + Thank you teor for aiding me with the implementation of Happy Eyeballs in + Tor. This would not have been possible if it weren't for you. [View Less]

1 0

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 05 Feb '19

05 Feb '19

commit bd936257d30f296bbbf772d6a49cbb32551e5f00 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Feb 5 09:15:44 2019 +0000 Update translations for https_everywhere --- id/https-everywhere.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id/https-everywhere.dtd b/id/https-everywhere.dtd index b36312e21..3e5bab5a3 100644 --- a/id/https-everywhere.dtd +++ b/id/https-everywhere.dtd @@ -1,6 +1,6 @@ <!ENTITY https-everywhere.about.title "… [View More]

1 0

[obfs4/master] transports/meeklite: Enable the utls fork's vartime group feature
by yawning＠torproject.org 05 Feb '19

05 Feb '19

commit fd44ad42fd8afd44524614ecc716a4e98a645c80 Author: Yawning Angel <yawning(a)schwanenlied.me> Date: Tue Feb 5 07:39:20 2019 +0000 transports/meeklite: Enable the utls fork's vartime group feature --- transports/meeklite/transport.go | 1 + 1 file changed, 1 insertion(+) diff --git a/transports/meeklite/transport.go b/transports/meeklite/transport.go index 5817be0..85da3e2 100644 --- a/transports/meeklite/transport.go +++ b/transports/meeklite/transport.go @@ -234,4 +234,5 @@ … [View More]

1 0

[translation/support-portal] Update translations for support-portal
by translation＠torproject.org 04 Feb '19

04 Feb '19

commit 7c3ab316df90d9bea403239ae08b234392c3ab1c Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 4 21:50:02 2019 +0000 Update translations for support-portal --- contents+de.po | 22 ++++++++++++++++++---- contents+fr.po | 23 +++++++++++++++++++---- 2 files changed, 37 insertions(+), 8 deletions(-) diff --git a/contents+de.po b/contents+de.po index e5c61cf65..a00666cdd 100644 --- a/contents+de.po +++ b/contents+de.po @@ -939,13 +939,16 @@ msgid "" "In … [View More][Tor](#tor-/-tor-network/-core-tor) terms, a \"hop\" refers to " "[traffic](#traffic) moving between [relay](#relay) in a [circuit](#circuit)." msgstr "" +"In den [Tor](#tor-/-tor-network/-core-tor)-Begriffen bezieht sich ein " +"\"Hop\" auf [traffic](#traffic), der sich zwischen [relay](#relay) in einem " +"[circuit](#circuit) bewegt." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTP" -msgstr "" +msgstr "### HTTP" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -957,13 +960,17 @@ msgid "" "only web pages, it is now relied upon to deliver many forms of data and " "communication." msgstr "" +"Das [Hypertext Transfer Protocol (HTTP)](#http) ist ein Kanal zum Senden von" +" Dateien und Daten zwischen Geräten in einem Netzwerk. Ursprünglich nur für " +"die Übertragung von Webseiten verwendet, wird es heute für die " +"Bereitstellung vieler Formen von Daten und Kommunikation verwendet." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTPS" -msgstr "" +msgstr "### HTTPS" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -974,13 +981,16 @@ msgid "" "of the HTTP channel used to transfer files and data between devices on a " "network." msgstr "" +"Hypertext Transfer Protocol Secure ist die " +"[verschlüsselte](#Verschlüsselung) Version des HTTP-Kanals, mit der Dateien " +"und Daten zwischen Geräten in einem Netzwerk übertragen werden." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTPS-Everywhere" -msgstr "" +msgstr "### HTTPS-Everywhere" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -991,13 +1001,17 @@ msgid "" "](#add-on-extension-or-plugin) that makes [HTTPS](#https) the default on " "websites that have set up HTTPS but have not made it the default." msgstr "" +"HTTPS Everywhere ist eine [Firefox](#firefox), Chrome und Opera [extension" +"](#add-on-extension-or-plugin), die [HTTPS](#https) zum Standard auf " +"Websites macht, die HTTPS eingerichtet haben, es aber nicht zum Standard " +"geschafft haben." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "HTTPS Everywhere is installed in [Tor Browser](#tor-browser)." -msgstr "" +msgstr "HTTPS Everywhere ist in [Tor Browser](#tor-browser) installiert." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) diff --git a/contents+fr.po b/contents+fr.po index 2272fe7b1..215be9841 100644 --- a/contents+fr.po +++ b/contents+fr.po @@ -941,13 +941,16 @@ msgid "" "In [Tor](#tor-/-tor-network/-core-tor) terms, a \"hop\" refers to " "[traffic](#traffic) moving between [relay](#relay) in a [circuit](#circuit)." msgstr "" +"En termes de [Tor](#tor-/-tor-tor-network/-core-tor), un \"saut\" fait " +"référence au [trafic](#trafic) se déplaçant entre [relais](#relais) dans un " +"[circuit](#circuit)." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTP" -msgstr "" +msgstr "### HTTP" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -959,13 +962,18 @@ msgid "" "only web pages, it is now relied upon to deliver many forms of data and " "communication." msgstr "" +"Le [Protocole de transfert hypertexte (HTTP)](#http) est un canal utilisé " +"pour envoyer des fichiers et des données entre des périphériques sur un " +"réseau. Utilisé à l'origine uniquement pour transférer des pages Web, il est" +" maintenant utilisé pour fournir de nombreuses formes de données et de " +"communication." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTPS" -msgstr "" +msgstr "### HTTPS" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -976,13 +984,16 @@ msgid "" "of the HTTP channel used to transfer files and data between devices on a " "network." msgstr "" +"Hypertext Transfer Protocol Secure est la version [cryptée](#encryption) du " +"canal HTTP utilisée pour transférer des fichiers et des données entre les " +"périphériques d'un réseau." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "### HTTPS-Everywhere" -msgstr "" +msgstr "### HTTPS-Everywhere" #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -993,13 +1004,17 @@ msgid "" "](#add-on-extension-or-plugin) that makes [HTTPS](#https) the default on " "websites that have set up HTTPS but have not made it the default." msgstr "" +"HTTPS Everywhere est un [Firefox](#firefox), Chrome et Opera [extension" +"](#add-on-extension-or-plugin) qui fait de [HTTPS](#https) le site par " +"défaut sur les sites qui ont configuré HTTPS mais ne l'ont pas fait par " +"défaut." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) #: https//support.torproject.org/misc/tor-glossary/ #: (content/misc/glossary/contents+en.lrquestion.description) msgid "HTTPS Everywhere is installed in [Tor Browser](#tor-browser)." -msgstr "" +msgstr "HTTPS Everywhere est installé dans [Navigateur Tor](#tor-browser)." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) [View Less]

1 0