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

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

24 Aug '18

commit 29c99439098883d481740296f3d267681b725207 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Aug 24 18:47:19 2018 +0000 Update translations for tor-browser-manual --- ru/ru.po | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/ru/ru.po b/ru/ru.po index 54d01ec1c..d387b079d 100644 --- a/ru/ru.po +++ b/ru/ru.po @@ -17,12 +17,13 @@ # Roberto Brigante, 2017 # Антон Толмачев <a.tolmachev(a)richart-consalt.ru>, 2017 # Boris Shminke, 2017 +# Sergey Lapshov <sfinx641(a)gmail.com>, 2018 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: Boris Shminke, 2017\n" +"Last-Translator: Sergey Lapshov <sfinx641(a)gmail.com>, 2018\n" "Language-Team: Russian (https://www.transifex.com/otf/teams/1519/ru/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -232,6 +233,11 @@ msgid "" " may be down. Please use one of the above methods to obtain more bridge " "addresses, and try again." msgstr "" +"Нажмите «Подключиться». Использование мостов может замедлить соединение по " +"сравнению с обычными ретрансляторами Tor. Если соединение не удалось, мосты," +" которые вы получили, могут быть недоступны. Для получения большего " +"количества адресов моста используйте один из приведенных выше методов и " +"повторите попытку." #: circumvention.page:6 msgid "What to do if the Tor network is blocked" @@ -250,6 +256,12 @@ msgid "" "page for more information on the types of transport that are currently " "available." msgstr "" +"Прямой доступ к сети Tor иногда может блокироваться вашим интернет-" +"провайдером или правительством. Tor Browser включает некоторые инструменты " +"обхода, чтобы обойти эти блокировки. Эти инструменты называются " +"подключаемыми транспортами - «Pluggable Transports». Дополнительную " +"информацию о типах транспорта, доступных в настоящее время, смотрите на " +"странице Pluggable Transports." #: circumvention.page:22 msgid "Using pluggable transports"

1 0

[tor/master] Fix revision counter bugs caused by bad SRV start time computation.
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 5febea0d54ea986ab66dc62905a686cc23abbcb6 Author: George Kadianakis <desnacked(a)riseup.net> Date: Fri Aug 17 15:10:20 2018 +0300 Fix revision counter bugs caused by bad SRV start time computation. Bug description: For each descriptor, its revision counter is the OPE ciphertext of the number of seconds since the start time of its SRV value. This bug caused us to confuse the SRV start time in the middle of the lifetime of a descriptor in some edge-cases, which caused descriptor rejects. Bug cause: The bug occurs when we fetch a 23:00 consensus after midnight (e.g. at 00:08 when not all dirauths have fetched the latest 00:00 consensus). In that case, the voting schedule (which was used for SRV start time calculation) would return a valid-after past-midnight, whereas our consensus would be pre-midnight, and that would confuse the SRV start time computation which is used by HS revision counters (because we would reset the start time of SRV, without rotating descriptors). Bug fix: We now use our local consensus time to calculate the SRV start time, instead of the voting schedule. The voting schedule does not work as originally envisioned in this case, because it was created for voting by dirauths and not for scheduling stuff on clients. --- src/feature/hs_common/shared_random_client.c | 21 +++++++++++++---- src/test/test_shared_random.c | 34 ++++++++++++++++++++++++++++ 2 files changed, 51 insertions(+), 4 deletions(-) diff --git a/src/feature/hs_common/shared_random_client.c b/src/feature/hs_common/shared_random_client.c index ff98a719d..a13404a32 100644 --- a/src/feature/hs_common/shared_random_client.c +++ b/src/feature/hs_common/shared_random_client.c @@ -51,9 +51,13 @@ get_voting_interval(void) return interval; } -/* Given the time <b>now</b>, return the start time of the current round of +/* Given the current consensus, return the start time of the current round of * the SR protocol. For example, if it's 23:47:08, the current round thus - * started at 23:47:00 for a voting interval of 10 seconds. */ + * started at 23:47:00 for a voting interval of 10 seconds. + * + * This function uses the consensus voting schedule to derive its results, + * instead of the actual consensus we are currently using, so it should be used + * for voting purposes. */ time_t get_start_time_of_current_round(void) { @@ -231,8 +235,17 @@ sr_state_get_start_time_of_current_protocol_run(void) { int total_rounds = SHARED_RANDOM_N_ROUNDS * SHARED_RANDOM_N_PHASES; int voting_interval = get_voting_interval(); - /* Find the time the current round started. */ - time_t beginning_of_curr_round = get_start_time_of_current_round(); + time_t beginning_of_curr_round; + + /* This function is not used for voting purposes, so if we have a live + consensus, use its valid-after as the beginning of the current round, + otherwise resort to the voting schedule which should always exist. */ + networkstatus_t *ns = networkstatus_get_live_consensus(approx_time()); + if (ns) { + beginning_of_curr_round = ns->valid_after; + } else { + beginning_of_curr_round = get_start_time_of_current_round(); + } /* Get current SR protocol round */ int curr_round_slot; diff --git a/src/test/test_shared_random.c b/src/test/test_shared_random.c index d2defdf68..72e4522da 100644 --- a/src/test/test_shared_random.c +++ b/src/test/test_shared_random.c @@ -290,6 +290,40 @@ test_get_start_time_of_current_run(void *arg) tt_str_op("2015-04-20 00:00:00", OP_EQ, tbuf); } + { + /* We want the local time to be past midnight, but the current consensus to + * have valid-after 23:00 (e.g. this can happen if we fetch a new consensus + * at 00:08 before dircaches have a chance to get the midnight consensus). + * + * Basically, we want to cause a desynch between ns->valid_after (23:00) + * and the voting_schedule.interval_starts (01:00), to make sure that + * sr_state_get_start_time_of_current_protocol_run() handles it gracefully: + * It should actually follow the local consensus time and not the voting + * schedule (which is designed for authority voting purposes). */ + retval = parse_rfc1123_time("Mon, 20 Apr 2015 00:00:00 UTC", + &mock_consensus.fresh_until); + tt_int_op(retval, OP_EQ, 0); + + retval = parse_rfc1123_time("Mon, 19 Apr 2015 23:00:00 UTC", + &mock_consensus.valid_after); + + retval = parse_rfc1123_time("Mon, 20 Apr 2015 00:08:00 UTC", + &current_time); + tt_int_op(retval, OP_EQ, 0); + update_approx_time(current_time); + voting_schedule_recalculate_timing(get_options(), current_time); + + run_start_time = sr_state_get_start_time_of_current_protocol_run(); + + /* Compare it with the correct result */ + format_iso_time(tbuf, run_start_time); + tt_str_op("2015-04-19 00:00:00", OP_EQ, tbuf); + /* Check that voting_schedule.interval_starts is at 01:00 (see above) */ + time_t interval_starts = voting_schedule_get_next_valid_after_time(); + format_iso_time(tbuf, interval_starts); + tt_str_op("2015-04-20 01:00:00", OP_EQ, tbuf); + } + /* Next test is testing it without a consensus to use the testing voting * interval . */ UNMOCK(networkstatus_get_live_consensus);

1 0

[tor/master] Merge remote-tracking branch 'tor-github/pr/289'
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 7217bdacb50e6934abdf9bb43b4c9b1073155647 Merge: 4c3b43604 5febea0d5 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Aug 24 12:57:18 2018 -0400 Merge remote-tracking branch 'tor-github/pr/289' src/feature/hs_common/shared_random_client.c | 21 +++++++++++++---- src/test/test_shared_random.c | 34 ++++++++++++++++++++++++++++ 2 files changed, 51 insertions(+), 4 deletions(-)

1 0

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

24 Aug '18

commit 15fc9dd00cb16e720e975b2594fc1afde42fc4be Author: Translation commit bot <translation(a)torproject.org> Date: Fri Aug 24 16:48:58 2018 +0000 Update translations for support-portal --- contents+pt_BR.po | 39 ++++++++++++++++++++++++++++++--------- 1 file changed, 30 insertions(+), 9 deletions(-) diff --git a/contents+pt_BR.po b/contents+pt_BR.po index 99362e784..e70c5d094 100644 --- a/contents+pt_BR.po +++ b/contents+pt_BR.po @@ -1413,6 +1413,8 @@ msgid "" "<img class=\"card-img-top\" src=\"/static/images/image1.png\" alt=\"New " "release alert\"><div class=\"card-body\">" msgstr "" +"<img class=\"card-img-top\" src=\"/static/images/image1.png\" alt=\"New " +"release alert\"><div class=\"card-body\">" #: http//localhost/tbb/tbb-29/ #: (content/tbb/tbb-29/contents+en.lrquestion.description) @@ -2208,6 +2210,9 @@ msgid "" "href=\"https://blog.torproject.org/sunsetting-tor-messenger\">Tor " "Messenger</a>." msgstr "" +"Não. Depois de onze lançamentos beta, nós descontinuaremos o suporte ao <a " +"href=\"https://blog.torproject.org/sunsetting-tor-messenger\">Tor " +"Messenger</a>." #: http//localhost/tormessenger/tormessenger-1/ #: (content/tormessenger/tormessenger-1/contents+en.lrquestion.description) @@ -2215,6 +2220,8 @@ msgid "" "We still believe in Tor's ability to be used in a messaging app, but we " "don't have the resources to make it happen right now." msgstr "" +"Nós ainda acreditamos na utilidade do Tor para se utilizando como aplicativo" +" de mensagens, mas não temos recursos para fazer isso agora." #: http//localhost/tormessenger/tormessenger-1/ #: (content/tormessenger/tormessenger-1/contents+en.lrquestion.description) @@ -2247,6 +2254,9 @@ msgid "" "<mark><a href=\"https://guardianproject.info/apps/orfox/\">Orfox</a></mark> " "web pages." msgstr "" +"Mais informações podem ser encontradas nas páginas <mark><a " +"href=\"https://guardianproject.info/apps/orbot/\">Orbot</a></mark> e " +"<mark><a href=\"https://guardianproject.info/apps/orfox/\">Orfox</a></mark>." #: http//localhost/tormobile/tormobile-1/ #: (content/tormobile/tormobile-1/contents+en.lrquestion.description) @@ -2449,7 +2459,7 @@ msgstr "" #: http//localhost/gettor/gettor-2/ #: (content/gettor/gettor-2/contents+en.lrquestion.seo_slug) msgid "to-use-gettor-via-email" -msgstr "" +msgstr "para-usar-gettor-via-email" #: http//localhost/gettor/gettor-3/ #: (content/gettor/gettor-3/contents+en.lrquestion.title) @@ -2488,7 +2498,7 @@ msgstr "* Windows" #: http//localhost/gettor/gettor-3/ #: (content/gettor/gettor-3/contents+en.lrquestion.seo_slug) msgid "to-use-gettor-via-twitter" -msgstr "" +msgstr "para-usar-gettor-via-twitter" #: http//localhost/gettor/gettor-4/ #: (content/gettor/gettor-4/contents+en.lrquestion.title) @@ -2507,7 +2517,7 @@ msgstr "" #: http//localhost/gettor/gettor-4/ #: (content/gettor/gettor-4/contents+en.lrquestion.seo_slug) msgid "to-use-gettor-via-xmpp" -msgstr "" +msgstr "para-usar-gettor-via-xmpp" #: http//localhost/connecting/connecting-1/ #: (content/connecting/connecting-1/contents+en.lrquestion.seo_slug) @@ -3028,16 +3038,19 @@ msgid "" "If the site you are visiting uses HTTPS, then the traffic leaving your exit " "relay will be encrypted, and won't be visible to eavesdroppers." msgstr "" +"Se o site que você está visitando utiliza HTTPS, então o tráfego deixando o " +"seu relay de saída será criptografado, e não será visível para " +"bisbilhoteiros." #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.description) msgid "<div class=\"row\">" -msgstr "" +msgstr "<div class=\"row\">" #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.description) msgid "<img class=\"card-img-top\" src=\"/static/images/image2.png\" alt=\"https\">" -msgstr "" +msgstr "<img class=\"card-img-top\" src=\"/static/images/image2.png\" alt=\"https\">" #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.description) @@ -3051,7 +3064,7 @@ msgstr "" #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.description) msgid "<img class=\"card-img-top\" src=\"/static/images/image6.png\" alt=\"https\">" -msgstr "" +msgstr "<img class=\"card-img-top\" src=\"/static/images/image6.png\" alt=\"https\">" #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.description) @@ -3060,11 +3073,14 @@ msgid "" "visible to eavesdroppers with and without Tor Browser and HTTPS " "encryption.</h4>" msgstr "" +"<h4 class=\"card-title\">Esta visualização mostra que informações são " +"visíveis para bisbilhoteiros com e sem a utilização do navegador Tor e " +"criptografia HTTPS.</h4>" #: http//localhost/https/https-1/ #: (content/https/https-1/contents+en.lrquestion.seo_slug) msgid "can-eavesdroppers-see-information-i-share" -msgstr "" +msgstr "bisbilhoteiros-podem-ver-informações-que-eu-compartilho" #: http//localhost/operators/operators-1/ #: (content/operators/operators-1/contents+en.lrquestion.title) @@ -3096,6 +3112,9 @@ msgid "" "* Make sure your clock, date, and timezone are set correctly. Install the " "ntp or openntpd (or similar) package to keep it that way." msgstr "" +"* Certifique-se que seu relógio, data e fuso horário estão configurados " +"corretamente. Instale o pacote ntp ou openntpd (ou similar) para sejam " +"mantidos corretos." #: http//localhost/operators/operators-1/ #: (content/operators/operators-1/contents+en.lrquestion.description) @@ -3124,7 +3143,7 @@ msgstr "" #: http//localhost/operators/operators-6/ #: (content/operators/operators-6/contents+en.lrquestion.description) msgid "#Address noname.example.com" -msgstr "" +msgstr "#Endereço noname.example.com" #: http//localhost/operators/operators-1/ #: (content/operators/operators-1/contents+en.lrquestion.description) @@ -3146,7 +3165,7 @@ msgstr "## Defina o nickname deste relay" #: http//localhost/operators/operators-6/ #: (content/operators/operators-6/contents+en.lrquestion.description) msgid "Nickname ididnteditheconfig" -msgstr "" +msgstr "Nickname ididnteditheconfig" #: http//localhost/operators/operators-1/ #: (content/operators/operators-1/contents+en.lrquestion.description) @@ -3710,6 +3729,8 @@ msgid "" "For example, the DuckDuckGo onion is <a " "href=\"http://3g2upl4pq6kufc4m.onion\">https://3g2upl4pq6kufc4m.onion</a>." msgstr "" +"Por exemplo, o serviço onion DuckDuckGO é <a " +"href=\"http://3g2upl4pq6kufc4m.onion\">https://3g2upl4pq6kufc4m.onion</a>." #: http//localhost/onionservices/onionservices-1/ #: (content/onionservices/onionservices-1/contents+en.lrquestion.description)

1 0

[tor/master] Merge remote-tracking branch 'teor/bug27237'
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 622231ce2e3abc033172d5c82df7fb6bfd374db0 Merge: b1d0fa04f 7a5896d5d Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Aug 24 12:44:46 2018 -0400 Merge remote-tracking branch 'teor/bug27237' changes/bug27237 | 4 ++++ src/feature/nodelist/nodelist.c | 11 ++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) diff --cc src/feature/nodelist/nodelist.c index a0f068cf9,07edc5aba..d6bc47448 --- a/src/feature/nodelist/nodelist.c +++ b/src/feature/nodelist/nodelist.c @@@ -2399,8 -2383,8 +2404,8 @@@ compute_frac_paths_available(const netw (int)(f_mid*100), (int)(f_exit*100), (router_have_consensus_path() == CONSENSUS_PATH_EXIT ? - "" : - " (no exits in consensus, using mid)"), + "exit bw" : - "end bw (no exits in consensus)"), ++ "end bw (no exits in consensus, using mid)"), (int)(f_path*100)); return f_path;

1 0

[tor/master] Add scripts/test/chutney-git-bisect.sh, for bisecting using chutney
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 4217dc0558c9fabfab1568b42dc5e101c69ddef7 Author: teor <teor(a)torproject.org> Date: Fri Aug 24 04:03:56 2018 +1000 Add scripts/test/chutney-git-bisect.sh, for bisecting using chutney Supports bisection on 0.3.4 and earlier. Recommend that users copy the script before bisecting. Implements ticket 27211. --- changes/ticket27211 | 3 ++ scripts/README | 6 ++++ scripts/test/chutney-git-bisect.sh | 62 ++++++++++++++++++++++++++++++++++++++ 3 files changed, 71 insertions(+) diff --git a/changes/ticket27211 b/changes/ticket27211 new file mode 100644 index 000000000..c3d661a01 --- /dev/null +++ b/changes/ticket27211 @@ -0,0 +1,3 @@ + o Minor features (testing): + - Add scripts/test/chutney-git-bisect.sh, for bisecting using chutney. + Implements ticket 27211. diff --git a/scripts/README b/scripts/README index 02faabe06..9cd6e74ac 100644 --- a/scripts/README +++ b/scripts/README @@ -30,6 +30,12 @@ orconfig.h files. Testing scripts --------------- +test/chutney-git-bisect.sh -- a git bisect run script that bisects using +chutney. The script builds tor and tor-gencert, then runs chutney. The script +takes optional arguments for out-of-tree builds, and specific chutney network +flavours. You should copy this script before using it with git bisect, so that +it doesn't change (or disappear) during bisection. + test/cov-blame -- Mash up the results of gcov with git blame. Mainly useful to find out who has been writing untested code. diff --git a/scripts/test/chutney-git-bisect.sh b/scripts/test/chutney-git-bisect.sh new file mode 100755 index 000000000..8a3f2c70c --- /dev/null +++ b/scripts/test/chutney-git-bisect.sh @@ -0,0 +1,62 @@ +#!/usr/bin/env bash + +# Compile tor and run chutney to find out if the current commit works +# +# Usage: +# # Copy the script, so it doesn't change during bisection +# cp scripts/test/chutney-git-bisect.sh . +# git bisect run \ +# ./chutney-git-bisect.sh [tries [build-dir [flavour [skip-flavour]]]] +# +# Runs chutney up to <tries> times (default 3), because some bugs involve race +# conditions. +# Changes to <build-dir> (default no cd) before running tests. +# Runs chutney network <flavour> (default make test-network-all) as the test. +# Skips the test if <skip-flavour> fails (default no skip). + +CHUTNEY_TRIES=3 +if [ ! -z "$1" ]; then + CHUTNEY_TRIES="$1" +fi + +if [ ! -z "$2" ]; then + cd "$2" +fi + +CHUTNEY_TEST_CMD="make test-network-all" +if [ ! -z "$3" ]; then + CHUTNEY_TEST_CMD="$CHUTNEY_PATH/tools/test-network.sh --flavour $3" +fi + +CHUTNEY_SKIP_ON_FAIL_CMD="true" +if [ ! -z "$4" ]; then + CHUTNEY_SKIP_ON_FAIL_CMD="$CHUTNEY_PATH/tools/test-network.sh --flavour $4" +fi + +CHUTNEY_BUILD_CMD_OR="make src/or/tor src/tools/tor-gencert" +CHUTNEY_BUILD_CMD_APP="make src/app/tor src/tools/tor-gencert" +if ! ( $CHUTNEY_BUILD_CMD_APP || $CHUTNEY_BUILD_CMD_OR ) ; then + echo "building '$CHUTNEY_BUILD_CMD_APP || $CHUTNEY_BUILD_CMD_OR' failed, skip" + exit 125 +fi + +if ! $CHUTNEY_SKIP_ON_FAIL_CMD ; then + echo "pre-condition '$CHUTNEY_SKIP_ON_FAIL_CMD' failed, skip" + exit 125 +fi + +i=1 +while [ "$i" -le "$CHUTNEY_TRIES" ]; do + echo + echo "Round $i/$CHUTNEY_TRIES:" + echo + if $CHUTNEY_TEST_CMD ; then + echo "test '$CHUTNEY_TEST_CMD' succeeded after $i/$CHUTNEY_TRIES attempts, good" + exit 0 + fi + i=$[$i+1] +done + +i=$[$i-1] +echo "test '$CHUTNEY_TEST_CMD' failed $i/$CHUTNEY_TRIES attempts, bad" +exit 1

1 0

[tor/master] Bootstrap: try harder to get descriptors in non-exit test networks
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 7a5896d5d444d2e32190063e38abb23030daae06 Author: teor <teor(a)torproject.org> Date: Fri Aug 24 11:59:47 2018 +1000 Bootstrap: try harder to get descriptors in non-exit test networks Use the mid weight for the third hop when there are no exits. Fixes bug 27237; bugfix on 0.2.6.2-alpha. --- changes/bug27237 | 4 ++++ src/feature/nodelist/nodelist.c | 11 ++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/changes/bug27237 b/changes/bug27237 new file mode 100644 index 000000000..6fa70d785 --- /dev/null +++ b/changes/bug27237 @@ -0,0 +1,4 @@ + o Minor bugfixes (bootstrap): + - Try harder to get descriptors in non-exit test networks, by + using the mid weight for the third hop when there are no exits. + Fixes bug 27237; bugfix on 0.2.6.2-alpha. diff --git a/src/feature/nodelist/nodelist.c b/src/feature/nodelist/nodelist.c index bf298337a..07edc5aba 100644 --- a/src/feature/nodelist/nodelist.c +++ b/src/feature/nodelist/nodelist.c @@ -2361,9 +2361,14 @@ compute_frac_paths_available(const networkstatus_t *consensus, f_exit = f_myexit; } - /* if the consensus has no exits, treat the exit fraction as 100% */ + /* if the consensus has no exits, we can only build onion service paths, + * which are G - M - M. So use the middle fraction for the exit fraction. */ if (router_have_consensus_path() != CONSENSUS_PATH_EXIT) { - f_exit = 1.0; + /* If there are no exits in the consensus, then f_exit is always 0, so + * it is safe to replace f_exit with f_mid. */ + if (!BUG(f_exit > 0.0)) { + f_exit = f_mid; + } } f_path = f_guard * f_mid * f_exit; @@ -2379,7 +2384,7 @@ compute_frac_paths_available(const networkstatus_t *consensus, (int)(f_exit*100), (router_have_consensus_path() == CONSENSUS_PATH_EXIT ? "" : - " (no exits in consensus)"), + " (no exits in consensus, using mid)"), (int)(f_path*100)); return f_path;

1 0

[tor/master] Merge remote-tracking branch 'teor/ticket27211'
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 4c3b43604b7dedf3456136a1ad71fa0802744b2e Merge: 622231ce2 4217dc055 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Aug 24 12:45:42 2018 -0400 Merge remote-tracking branch 'teor/ticket27211' changes/ticket27211 | 3 ++ scripts/README | 6 ++++ scripts/test/chutney-git-bisect.sh | 62 ++++++++++++++++++++++++++++++++++++++ 3 files changed, 71 insertions(+)

1 0

[tor/maint-0.3.2] Merge branch 'ticket27286_032_v2' into maint-0.3.2
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 98e1a1d106f9abe07d184bd4b0568bd50f91bf93 Merge: 36bb11a65 14be9cba4 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Aug 24 12:32:06 2018 -0400 Merge branch 'ticket27286_032_v2' into maint-0.3.2 changes/27286 | 4 ++++ src/or/dirserv.c | 8 ++++---- 2 files changed, 8 insertions(+), 4 deletions(-)

1 0

[tor/maint-0.3.3] Update the protocol versions recommendations to remove LinkAuth=1
by nickm＠torproject.org 24 Aug '18

24 Aug '18

commit 14be9cba4ee1c3ec96638f4870112848efad2503 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Aug 23 11:24:39 2018 -0400 Update the protocol versions recommendations to remove LinkAuth=1 LinkAuth method 1 is the one where we pull the TLS master secrets out of the OpenSSL data structures and authenticate them with RSA. Right now we list method 1 as required for clients and relays. That's a problem, since we can't reasonably support it with NSS. So let's remove it as a requirement and a recommendation. As for method 3: I'd like to recommend it it, but that would make 0.2.9 start warning. Let's not do that till at least some time after 0.3.5 (the next LTS) is stable. Closes ticket 27286 --- changes/27286 | 4 ++++ src/or/dirserv.c | 8 ++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/changes/27286 b/changes/27286 new file mode 100644 index 000000000..5f5f7a4ae --- /dev/null +++ b/changes/27286 @@ -0,0 +1,4 @@ + o Minor features (directory authorities): + - Authorities no longer vote to make the subprotocol version "LinkAuth=1" + a requirement: it is unsupportable with NSS, and hasn't been needed + since Tor 0.3.0.1-alpha. Closes ticket 27286. diff --git a/src/or/dirserv.c b/src/or/dirserv.c index 08557a6a1..a1ccf03e9 100644 --- a/src/or/dirserv.c +++ b/src/or/dirserv.c @@ -3082,16 +3082,16 @@ dirserv_generate_networkstatus_vote_obj(crypto_pk_t *private_key, /* These are hardwired, to avoid disaster. */ v3_out->recommended_relay_protocols = tor_strdup("Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 " - "Link=4 LinkAuth=1 Microdesc=1-2 Relay=2"); + "Link=4 Microdesc=1-2 Relay=2"); v3_out->recommended_client_protocols = tor_strdup("Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 " - "Link=4 LinkAuth=1 Microdesc=1-2 Relay=2"); + "Link=4 Microdesc=1-2 Relay=2"); v3_out->required_client_protocols = tor_strdup("Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 " - "Link=4 LinkAuth=1 Microdesc=1-2 Relay=2"); + "Link=4 Microdesc=1-2 Relay=2"); v3_out->required_relay_protocols = tor_strdup("Cons=1 Desc=1 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 " - "Link=3-4 LinkAuth=1 Microdesc=1 Relay=1-2"); + "Link=3-4 Microdesc=1 Relay=1-2"); /* We are not allowed to vote to require anything we don't have. */ tor_assert(protover_all_supported(v3_out->required_relay_protocols, NULL));

1 0