January 2018 - tor-commits - lists.torproject.org

[tor/maint-0.2.9] MAX_REND_FAILURES is 1, but we would try three times
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit a15eb9ff439623f800de813c1a78eeb5d61f7f5a Author: Roger Dingledine <arma(a)torproject.org> Date: Mon Jan 15 16:30:55 2018 -0500 MAX_REND_FAILURES is 1, but we would try three times Fix an "off by 2" error in counting rendezvous failures on the onion service side. While we thought we would stop the rendezvous attempt after one failed circuit, we were actually making three circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. --- changes/bug24895 | 6 ++++++ src/or/rendservice.c | 5 ++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/changes/bug24895 b/changes/bug24895 new file mode 100644 index 000000000..7b90f6d26 --- /dev/null +++ b/changes/bug24895 @@ -0,0 +1,6 @@ + o Major bugfixes (onion services): + - Fix an "off by 2" error in counting rendezvous failures on the + onion service side. While we thought we would stop the rendezvous + attempt after one failed circuit, we were actually making three + circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. + diff --git a/src/or/rendservice.c b/src/or/rendservice.c index a8c383444..acc431a57 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -2930,8 +2930,11 @@ rend_service_relaunch_rendezvous(origin_circuit_t *oldcirc) } oldcirc->hs_service_side_rend_circ_has_been_relaunched = 1; + /* We check failure_count >= MAX_REND_FAILURES-1 below rather than + * failure_count >= MAX_REND_FAILURES, because we increment the failure + * count for our current failure *after* this clause. */ if (!oldcirc->build_state || - oldcirc->build_state->failure_count > MAX_REND_FAILURES || + oldcirc->build_state->failure_count >= MAX_REND_FAILURES-1 || oldcirc->build_state->expiry_time < time(NULL)) { log_info(LD_REND, "Attempt to build circuit to %s for rendezvous has failed "

1 0

[tor/maint-0.2.9] turn MAX_REND_FAILURES into a function
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit cc5a9e96674f39677a65daa2f7a2f5af7ac3106e Author: Roger Dingledine <arma(a)torproject.org> Date: Fri Jan 19 02:38:07 2018 -0500 turn MAX_REND_FAILURES into a function no actual changes in behavior --- src/or/rendservice.c | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/src/or/rendservice.c b/src/or/rendservice.c index acc431a57..b503eda7f 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -108,13 +108,18 @@ struct rend_service_port_config_s { /** Don't try to build more than this many circuits before giving up * for a while.*/ #define MAX_INTRO_CIRCS_PER_PERIOD 10 -/** How many times will a hidden service operator attempt to connect to - * a requested rendezvous point before giving up? */ -#define MAX_REND_FAILURES 1 /** How many seconds should we spend trying to connect to a requested * rendezvous point before giving up? */ #define MAX_REND_TIMEOUT 30 +/** How many times will a hidden service operator attempt to connect to + * a requested rendezvous point before giving up? */ +static int +get_max_rend_failures(void) +{ + return 1; +} + /* Hidden service directory file names: * new file names should be added to rend_service_add_filenames_to_list() * for sandboxing purposes. */ @@ -2028,7 +2033,8 @@ rend_service_receive_introduction(origin_circuit_t *circuit, /* Launch a circuit to the client's chosen rendezvous point. */ - for (i=0;i<MAX_REND_FAILURES;i++) { + int max_rend_failures=get_max_rend_failures(); + for (i=0;i<max_rend_failures;i++) { int flags = CIRCLAUNCH_NEED_CAPACITY | CIRCLAUNCH_IS_INTERNAL; if (circ_needs_uptime) flags |= CIRCLAUNCH_NEED_UPTIME; /* A Single Onion Service only uses a direct connection if its @@ -2930,11 +2936,13 @@ rend_service_relaunch_rendezvous(origin_circuit_t *oldcirc) } oldcirc->hs_service_side_rend_circ_has_been_relaunched = 1; - /* We check failure_count >= MAX_REND_FAILURES-1 below rather than - * failure_count >= MAX_REND_FAILURES, because we increment the failure - * count for our current failure *after* this clause. */ + /* We check failure_count >= get_max_rend_failures()-1 below, and the -1 + * is because we increment the failure count for our current failure + * *after* this clause. */ + int max_rend_failures = get_max_rend_failures() - 1; + if (!oldcirc->build_state || - oldcirc->build_state->failure_count >= MAX_REND_FAILURES-1 || + oldcirc->build_state->failure_count >= max_rend_failures || oldcirc->build_state->expiry_time < time(NULL)) { log_info(LD_REND, "Attempt to build circuit to %s for rendezvous has failed "

1 0

[tor/maint-0.3.0] MAX_REND_FAILURES is 1, but we would try three times
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit a15eb9ff439623f800de813c1a78eeb5d61f7f5a Author: Roger Dingledine <arma(a)torproject.org> Date: Mon Jan 15 16:30:55 2018 -0500 MAX_REND_FAILURES is 1, but we would try three times Fix an "off by 2" error in counting rendezvous failures on the onion service side. While we thought we would stop the rendezvous attempt after one failed circuit, we were actually making three circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. --- changes/bug24895 | 6 ++++++ src/or/rendservice.c | 5 ++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/changes/bug24895 b/changes/bug24895 new file mode 100644 index 000000000..7b90f6d26 --- /dev/null +++ b/changes/bug24895 @@ -0,0 +1,6 @@ + o Major bugfixes (onion services): + - Fix an "off by 2" error in counting rendezvous failures on the + onion service side. While we thought we would stop the rendezvous + attempt after one failed circuit, we were actually making three + circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. + diff --git a/src/or/rendservice.c b/src/or/rendservice.c index a8c383444..acc431a57 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -2930,8 +2930,11 @@ rend_service_relaunch_rendezvous(origin_circuit_t *oldcirc) } oldcirc->hs_service_side_rend_circ_has_been_relaunched = 1; + /* We check failure_count >= MAX_REND_FAILURES-1 below rather than + * failure_count >= MAX_REND_FAILURES, because we increment the failure + * count for our current failure *after* this clause. */ if (!oldcirc->build_state || - oldcirc->build_state->failure_count > MAX_REND_FAILURES || + oldcirc->build_state->failure_count >= MAX_REND_FAILURES-1 || oldcirc->build_state->expiry_time < time(NULL)) { log_info(LD_REND, "Attempt to build circuit to %s for rendezvous has failed "

1 0

[tor/maint-0.3.0] hs: Use hs_service_max_rdv_failures consensus param, defaulting to 2
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit 490ae26b24a6b2b8843515425cedabf99801163a Author: Roger Dingledine <arma(a)torproject.org> Date: Fri Jan 19 03:00:43 2018 -0500 hs: Use hs_service_max_rdv_failures consensus param, defaulting to 2 --- changes/bug24895 | 10 ++++++---- src/or/rendservice.c | 10 +++++++++- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/changes/bug24895 b/changes/bug24895 index 7b90f6d26..7edde94a0 100644 --- a/changes/bug24895 +++ b/changes/bug24895 @@ -1,6 +1,8 @@ o Major bugfixes (onion services): - - Fix an "off by 2" error in counting rendezvous failures on the - onion service side. While we thought we would stop the rendezvous - attempt after one failed circuit, we were actually making three - circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. + - Fix an "off by 2" error in counting rendezvous failures on the onion + service side. While we thought we would stop the rendezvous attempt + after one failed circuit, we were actually making three circuit attempts + before giving up. Now switch to a default of 2, and allow the consensus + parameter "hs_service_max_rdv_failures" to override. Fixes bug 24895; + bugfix on 0.0.6. diff --git a/src/or/rendservice.c b/src/or/rendservice.c index b503eda7f..da200d138 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -111,13 +111,21 @@ struct rend_service_port_config_s { /** How many seconds should we spend trying to connect to a requested * rendezvous point before giving up? */ #define MAX_REND_TIMEOUT 30 +/* Default, minimum and maximum values for the maximum rendezvous failures + * consensus parameter. */ +#define MAX_REND_FAILURES_DEFAULT 2 +#define MAX_REND_FAILURES_MIN 1 +#define MAX_REND_FAILURES_MAX 10 /** How many times will a hidden service operator attempt to connect to * a requested rendezvous point before giving up? */ static int get_max_rend_failures(void) { - return 1; + return networkstatus_get_param(NULL, "hs_service_max_rdv_failures", + MAX_REND_FAILURES_DEFAULT, + MAX_REND_FAILURES_MIN, + MAX_REND_FAILURES_MAX); } /* Hidden service directory file names:

1 0

[tor/maint-0.2.9] hs: Use hs_service_max_rdv_failures consensus param, defaulting to 2
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit 490ae26b24a6b2b8843515425cedabf99801163a Author: Roger Dingledine <arma(a)torproject.org> Date: Fri Jan 19 03:00:43 2018 -0500 hs: Use hs_service_max_rdv_failures consensus param, defaulting to 2 --- changes/bug24895 | 10 ++++++---- src/or/rendservice.c | 10 +++++++++- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/changes/bug24895 b/changes/bug24895 index 7b90f6d26..7edde94a0 100644 --- a/changes/bug24895 +++ b/changes/bug24895 @@ -1,6 +1,8 @@ o Major bugfixes (onion services): - - Fix an "off by 2" error in counting rendezvous failures on the - onion service side. While we thought we would stop the rendezvous - attempt after one failed circuit, we were actually making three - circuit attempts before giving up. Fixes bug 24895; bugfix on 0.0.6. + - Fix an "off by 2" error in counting rendezvous failures on the onion + service side. While we thought we would stop the rendezvous attempt + after one failed circuit, we were actually making three circuit attempts + before giving up. Now switch to a default of 2, and allow the consensus + parameter "hs_service_max_rdv_failures" to override. Fixes bug 24895; + bugfix on 0.0.6. diff --git a/src/or/rendservice.c b/src/or/rendservice.c index b503eda7f..da200d138 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -111,13 +111,21 @@ struct rend_service_port_config_s { /** How many seconds should we spend trying to connect to a requested * rendezvous point before giving up? */ #define MAX_REND_TIMEOUT 30 +/* Default, minimum and maximum values for the maximum rendezvous failures + * consensus parameter. */ +#define MAX_REND_FAILURES_DEFAULT 2 +#define MAX_REND_FAILURES_MIN 1 +#define MAX_REND_FAILURES_MAX 10 /** How many times will a hidden service operator attempt to connect to * a requested rendezvous point before giving up? */ static int get_max_rend_failures(void) { - return 1; + return networkstatus_get_param(NULL, "hs_service_max_rdv_failures", + MAX_REND_FAILURES_DEFAULT, + MAX_REND_FAILURES_MIN, + MAX_REND_FAILURES_MAX); } /* Hidden service directory file names:

1 0

[tor/maint-0.2.9] Merge remote-tracking branch 'dgoulet/bug24895_029_02' into maint-0.2.9
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit a2aaf9509ba578f4e7705b506ee9a0f764d24ff2 Merge: 36567c5ca 490ae26b2 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Jan 19 16:29:15 2018 -0500 Merge remote-tracking branch 'dgoulet/bug24895_029_02' into maint-0.2.9 changes/bug24895 | 8 ++++++++ src/or/rendservice.c | 29 ++++++++++++++++++++++++----- 2 files changed, 32 insertions(+), 5 deletions(-)

1 0

[tor/maint-0.3.0] turn MAX_REND_FAILURES into a function
by nickm＠torproject.org 19 Jan '18

19 Jan '18

commit cc5a9e96674f39677a65daa2f7a2f5af7ac3106e Author: Roger Dingledine <arma(a)torproject.org> Date: Fri Jan 19 02:38:07 2018 -0500 turn MAX_REND_FAILURES into a function no actual changes in behavior --- src/or/rendservice.c | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/src/or/rendservice.c b/src/or/rendservice.c index acc431a57..b503eda7f 100644 --- a/src/or/rendservice.c +++ b/src/or/rendservice.c @@ -108,13 +108,18 @@ struct rend_service_port_config_s { /** Don't try to build more than this many circuits before giving up * for a while.*/ #define MAX_INTRO_CIRCS_PER_PERIOD 10 -/** How many times will a hidden service operator attempt to connect to - * a requested rendezvous point before giving up? */ -#define MAX_REND_FAILURES 1 /** How many seconds should we spend trying to connect to a requested * rendezvous point before giving up? */ #define MAX_REND_TIMEOUT 30 +/** How many times will a hidden service operator attempt to connect to + * a requested rendezvous point before giving up? */ +static int +get_max_rend_failures(void) +{ + return 1; +} + /* Hidden service directory file names: * new file names should be added to rend_service_add_filenames_to_list() * for sandboxing purposes. */ @@ -2028,7 +2033,8 @@ rend_service_receive_introduction(origin_circuit_t *circuit, /* Launch a circuit to the client's chosen rendezvous point. */ - for (i=0;i<MAX_REND_FAILURES;i++) { + int max_rend_failures=get_max_rend_failures(); + for (i=0;i<max_rend_failures;i++) { int flags = CIRCLAUNCH_NEED_CAPACITY | CIRCLAUNCH_IS_INTERNAL; if (circ_needs_uptime) flags |= CIRCLAUNCH_NEED_UPTIME; /* A Single Onion Service only uses a direct connection if its @@ -2930,11 +2936,13 @@ rend_service_relaunch_rendezvous(origin_circuit_t *oldcirc) } oldcirc->hs_service_side_rend_circ_has_been_relaunched = 1; - /* We check failure_count >= MAX_REND_FAILURES-1 below rather than - * failure_count >= MAX_REND_FAILURES, because we increment the failure - * count for our current failure *after* this clause. */ + /* We check failure_count >= get_max_rend_failures()-1 below, and the -1 + * is because we increment the failure count for our current failure + * *after* this clause. */ + int max_rend_failures = get_max_rend_failures() - 1; + if (!oldcirc->build_state || - oldcirc->build_state->failure_count >= MAX_REND_FAILURES-1 || + oldcirc->build_state->failure_count >= max_rend_failures || oldcirc->build_state->expiry_time < time(NULL)) { log_info(LD_REND, "Attempt to build circuit to %s for rendezvous has failed "

1 0

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

19 Jan '18

commit b049f6864d7dcf5ea59a4e5188d91732701f67cf Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 19 20:53:55 2018 +0000 Update translations for tor-browser-manual --- nn/nn.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nn/nn.po b/nn/nn.po index a7e1957c9..10e40c607 100644 --- a/nn/nn.po +++ b/nn/nn.po @@ -1,13 +1,13 @@ # Translators: # Bjørn I. <bjorn.svindseth(a)online.no>, 2016 # Tor Project <support-team-private(a)lists.torproject.org>, 2016 -# Øystein Alværvik <oystein.alver(a)gmail.com>, 2016 +# Øystein A <oystein.alver(a)gmail.com>, 2016 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: Øystein Alværvik <oystein.alver(a)gmail.com>, 2016\n" +"Last-Translator: Øystein A <oystein.alver(a)gmail.com>, 2016\n" "Language-Team: Norwegian Nynorsk (https://www.transifex.com/otf/teams/1519/nn/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/https_everywhere_completed] Update translations for https_everywhere_completed
by translation＠torproject.org 19 Jan '18

19 Jan '18

commit 945727216bc319a620216566f1aec81ea3a65660 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 19 20:15:48 2018 +0000 Update translations for https_everywhere_completed --- mk/ssl-observatory.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mk/ssl-observatory.dtd b/mk/ssl-observatory.dtd index d1d9ec723..8ebe517e8 100644 --- a/mk/ssl-observatory.dtd +++ b/mk/ssl-observatory.dtd @@ -3,7 +3,7 @@ <!ENTITY ssl-observatory.popup.later "Прашај ме подоцна"> <!ENTITY ssl-observatory.popup.no "Не"> -<!ENTITY ssl-observatory.popup.text "'HTTPS секаде' може да пронајде напади +<!ENTITY ssl-observatory.popup.text "'HTTPS Насекаде' може да пронајде напади против твојот пребарувач преку праќање на примените сертификати во опсерваторијата. Вклучи го ова?"> @@ -13,7 +13,7 @@ and auditing the certificates being presented to your browser. Would you like to turn it on?">--> <!ENTITY ssl-observatory.popup.title -"Треба ли 'HTTPS секаде' да користи SSL опсерваторија?"> +"Треба ли 'HTTPS Насекаде' да користи SSL опсерваторија?"> <!ENTITY ssl-observatory.popup.yes "Да">

1 0

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 19 Jan '18

19 Jan '18

commit 010cac980c14dc0181692361de61b3f5173da482 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 19 20:15:37 2018 +0000 Update translations for https_everywhere --- mk/ssl-observatory.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mk/ssl-observatory.dtd b/mk/ssl-observatory.dtd index d1d9ec723..8ebe517e8 100644 --- a/mk/ssl-observatory.dtd +++ b/mk/ssl-observatory.dtd @@ -3,7 +3,7 @@ <!ENTITY ssl-observatory.popup.later "Прашај ме подоцна"> <!ENTITY ssl-observatory.popup.no "Не"> -<!ENTITY ssl-observatory.popup.text "'HTTPS секаде' може да пронајде напади +<!ENTITY ssl-observatory.popup.text "'HTTPS Насекаде' може да пронајде напади против твојот пребарувач преку праќање на примените сертификати во опсерваторијата. Вклучи го ова?"> @@ -13,7 +13,7 @@ and auditing the certificates being presented to your browser. Would you like to turn it on?">--> <!ENTITY ssl-observatory.popup.title -"Треба ли 'HTTPS секаде' да користи SSL опсерваторија?"> +"Треба ли 'HTTPS Насекаде' да користи SSL опсерваторија?"> <!ENTITY ssl-observatory.popup.yes "Да">

1 0