July 2021 - tor-commits - lists.torproject.org

[tor/main] Add layer2_guard_free()
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 9b464cdc364755fb00b544c31a1e75500a3b84d3 Author: George Kadianakis <desnacked(a)riseup.net> Date: Fri Jul 9 16:54:24 2021 +0300 Add layer2_guard_free() --- src/feature/client/entrynodes.c | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/src/feature/client/entrynodes.c b/src/feature/client/entrynodes.c index fddb7b8f0f..1e9416c9cf 100644 --- a/src/feature/client/entrynodes.c +++ b/src/feature/client/entrynodes.c @@ -3944,6 +3944,19 @@ typedef struct layer2_guard_t { time_t expire_on_date; } layer2_guard_t; +#define layer2_guard_free(val) \ + FREE_AND_NULL(layer2_guard_t, layer2_guard_free_, (val)) + +static void +layer2_guard_free_(layer2_guard_t *l2) +{ + if (!l2) { + return; + } + + tor_free(l2); +} + /** Global list and routerset of L2 guards. They are both synced and they get * updated periodically. We need both the list and the routerset: we use the * smartlist to keep track of expiration times and the routerset is what we @@ -4029,7 +4042,7 @@ maintain_layer2_guards(void) safe_str_client(hex_str(g->identity, DIGEST_LEN))); // Nickname may be gone from consensus and doesn't matter anyway control_event_guard("None", g->identity, "BAD_L2"); - tor_free(g); + layer2_guard_free(g); SMARTLIST_DEL_CURRENT_KEEPORDER(layer2_guards, g); continue; } @@ -4040,7 +4053,7 @@ maintain_layer2_guards(void) safe_str_client(hex_str(g->identity, DIGEST_LEN))); // Nickname may be gone from consensus and doesn't matter anyway control_event_guard("None", g->identity, "BAD_L2"); - tor_free(g); + layer2_guard_free(g); SMARTLIST_DEL_CURRENT_KEEPORDER(layer2_guards, g); continue; } @@ -4110,7 +4123,7 @@ purge_vanguards_lite(void) /* Go through the list and perform any needed expirations */ SMARTLIST_FOREACH_BEGIN(layer2_guards, layer2_guard_t *, g) { - tor_free(g); + layer2_guard_free(g); } SMARTLIST_FOREACH_END(g); smartlist_clear(layer2_guards); @@ -4158,7 +4171,7 @@ entry_guards_free_all(void) } SMARTLIST_FOREACH_BEGIN(layer2_guards, layer2_guard_t *, g) { - tor_free(g); + layer2_guard_free(g); } SMARTLIST_FOREACH_END(g); smartlist_free(layer2_guards);

1 0

[tor/main] Add a switch to toggle the feature on/off
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 7f701794e7d8ce5cb4feb0b6fb1d4b00b68e5c5b Author: George Kadianakis <desnacked(a)riseup.net> Date: Mon Jul 12 11:45:31 2021 +0300 Add a switch to toggle the feature on/off --- doc/man/tor.1.txt | 7 +++++++ src/app/config/config.c | 1 + src/app/config/or_options_st.h | 3 +++ src/core/or/circuitbuild.c | 5 +++++ src/feature/client/entrynodes.c | 26 +++++++++++++++++++++++++- src/feature/client/entrynodes.h | 1 + src/test/test_entrynodes.c | 17 ++++++++++++++++- 7 files changed, 58 insertions(+), 2 deletions(-) diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt index 89afe59582..2b5a1d9df7 100644 --- a/doc/man/tor.1.txt +++ b/doc/man/tor.1.txt @@ -1749,6 +1749,13 @@ The following options are useful only for clients (that is, if the guard-n-primary-guards consensus parameter, and default to 3 if the consensus parameter isn't set. (Default: 0) +[[VanguardsLiteEnabled]] **VanguardsLiteEnabled** **0**|**1**|**auto**:: + This option specifies whether clients should use the vanguards-lite + subsystem to protect against guard discovery attacks. If it's set to + 'auto', clients will do what the vanguards-lite-enabled consensus parameter + tells them to do, and will default to enable the subsystem if the consensus + parameter isn't set. (Default: auto) + [[UseMicrodescriptors]] **UseMicrodescriptors** **0**|**1**|**auto**:: Microdescriptors are a smaller version of the information that Tor needs in order to build its circuits. Using microdescriptors makes Tor clients diff --git a/src/app/config/config.c b/src/app/config/config.c index 078df50677..15b4585954 100644 --- a/src/app/config/config.c +++ b/src/app/config/config.c @@ -669,6 +669,7 @@ static const config_var_t option_vars_[] = { VAR("UseEntryGuards", BOOL, UseEntryGuards_option, "1"), OBSOLETE("UseEntryGuardsAsDirGuards"), V(UseGuardFraction, AUTOBOOL, "auto"), + V(VanguardsLiteEnabled, AUTOBOOL, "auto"), V(UseMicrodescriptors, AUTOBOOL, "auto"), OBSOLETE("UseNTorHandshake"), V_IMMUTABLE(User, STRING, NULL), diff --git a/src/app/config/or_options_st.h b/src/app/config/or_options_st.h index b289865983..812fa92cae 100644 --- a/src/app/config/or_options_st.h +++ b/src/app/config/or_options_st.h @@ -594,6 +594,9 @@ struct or_options_t { * If 0, use value from NumEntryGuards. */ int NumPrimaryGuards; /**< How many primary guards do we want? */ + /** Boolean: Switch to toggle the vanguards-lite subsystem */ + int VanguardsLiteEnabled; + int RephistTrackTime; /**< How many seconds do we keep rephist info? */ /** Should we always fetch our dir info on the mirror schedule (which * means directly from the authorities) no matter our other config? */ diff --git a/src/core/or/circuitbuild.c b/src/core/or/circuitbuild.c index 84a8bec421..31e3868b65 100644 --- a/src/core/or/circuitbuild.c +++ b/src/core/or/circuitbuild.c @@ -2254,6 +2254,11 @@ middle_node_must_be_vanguard(const or_options_t *options, return 0; } + /* Don't even bother if the feature is disabled */ + if (!vanguards_lite_is_enabled()) { + return 0; + } + /* If we are a hidden service circuit, always use either vanguards-lite * or HSLayer2Nodes for 2nd hop. */ if (cur_len == 1) { diff --git a/src/feature/client/entrynodes.c b/src/feature/client/entrynodes.c index 1e9416c9cf..33de8a6b10 100644 --- a/src/feature/client/entrynodes.c +++ b/src/feature/client/entrynodes.c @@ -3932,7 +3932,7 @@ guard_selection_free_(guard_selection_t *gs) /**********************************************************************/ -/** Layer2 guard subsystem used for onion service circuits. */ +/** Layer2 guard subsystem (vanguards-lite) used for onion service circuits */ /** A simple representation of a layer2 guard. We just need its identity so * that we feed it into a routerset, and a sampled timestamp to do expiration @@ -3947,6 +3947,30 @@ typedef struct layer2_guard_t { #define layer2_guard_free(val) \ FREE_AND_NULL(layer2_guard_t, layer2_guard_free_, (val)) +/** Return true if the vanguards-lite subsystem is enabled */ +bool +vanguards_lite_is_enabled(void) +{ + /* First check torrc option and then maybe also the consensus parameter. */ + const or_options_t *options = get_options(); + + /* If the option is explicitly disabled, that's the final word here */ + if (options->VanguardsLiteEnabled == 0) { + return false; + } + + /* If the option is set to auto, then check the consensus parameter */ + if (options->VanguardsLiteEnabled == -1) { + return networkstatus_get_param(NULL, "vanguards-lite-enabled", + 1, /* default to "on" */ + 0, 1); + } + + /* else it's enabled */ + tor_assert_nonfatal(options->VanguardsLiteEnabled == 1); + return options->VanguardsLiteEnabled; +} + static void layer2_guard_free_(layer2_guard_t *l2) { diff --git a/src/feature/client/entrynodes.h b/src/feature/client/entrynodes.h index 9c38c2b5f8..08fd7cf745 100644 --- a/src/feature/client/entrynodes.h +++ b/src/feature/client/entrynodes.h @@ -651,6 +651,7 @@ guard_get_guardfraction_bandwidth(guardfraction_bandwidth_t *guardfraction_bw, int orig_bandwidth, uint32_t guardfraction_percentage); +bool vanguards_lite_is_enabled(void); const routerset_t *get_layer2_guards(void); void maintain_layer2_guards(void); void purge_vanguards_lite(void); diff --git a/src/test/test_entrynodes.c b/src/test/test_entrynodes.c index 4d353e8480..118b66dfa7 100644 --- a/src/test/test_entrynodes.c +++ b/src/test/test_entrynodes.c @@ -3099,7 +3099,22 @@ test_entry_guard_layer2_guards(void *arg) (void) arg; MOCK(router_have_minimum_dir_info, mock_router_have_minimum_dir_info); - /* Create the guardset */ + /* First check the enable/disable switch */ + get_options_mutable()->VanguardsLiteEnabled = 0; + tt_int_op(vanguards_lite_is_enabled(), OP_EQ, 0); + + get_options_mutable()->VanguardsLiteEnabled = 1; + tt_int_op(vanguards_lite_is_enabled(), OP_EQ, 1); + + get_options_mutable()->VanguardsLiteEnabled = -1; + tt_int_op(vanguards_lite_is_enabled(), OP_EQ, 1); + + /* OK now let's move to actual testing */ + + /* Remove restrictions to route around Big Fake Network restrictions */ + get_options_mutable()->EnforceDistinctSubnets = 0; + + /* Create the L2 guardset */ maintain_layer2_guards(); const routerset_t *l2_guards = get_layer2_guards();

1 0

[tor/main] Add stricter limits to the number of L2 nodes
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 5949a70b58918568eca7d64d6881a10a5ec745ff Author: George Kadianakis <desnacked(a)riseup.net> Date: Mon Jul 12 12:10:43 2021 +0300 Add stricter limits to the number of L2 nodes --- src/feature/client/entrynodes.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/feature/client/entrynodes.c b/src/feature/client/entrynodes.c index 33de8a6b10..9583a4db71 100644 --- a/src/feature/client/entrynodes.c +++ b/src/feature/client/entrynodes.c @@ -3990,6 +3990,10 @@ static routerset_t *layer2_routerset = NULL; /** Number of L2 guards */ #define NUMBER_SECOND_GUARDS 4 +/** Make sure that the number of L2 guards is less than the number of + * MAX_SANE_RESTRICTED_NODES */ +CTASSERT(NUMBER_SECOND_GUARDS < 20); + /** Lifetime of L2 guards: * 1 to 12 days, for an average of a week using the max(x,x) distribution */ #define MIN_SECOND_GUARD_LIFETIME (3600*24) @@ -4002,7 +4006,7 @@ get_number_of_layer2_hs_guards(void) return (int) networkstatus_get_param(NULL, "guard-hs-l2-number", NUMBER_SECOND_GUARDS, - 1, INT32_MAX); + 1, 19); } /** Return the minimum lifetime of L2 guards */

1 0

[tor/main] Merge branch 'vanguards-lite-dev-rebased'
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 4f68fe3e6c09881af46bfedadfdcd892b026adf3 Merge: a9b287fbcc 43a725797b Author: George Kadianakis <desnacked(a)riseup.net> Date: Wed Jul 28 12:00:37 2021 +0300 Merge branch 'vanguards-lite-dev-rebased' changes/ticket40363 | 9 ++ doc/man/tor.1.txt | 7 + src/app/config/config.c | 1 + src/app/config/or_options_st.h | 3 + src/core/mainloop/mainloop.c | 20 +++ src/core/or/circuitbuild.c | 40 +++--- src/core/or/circuituse.c | 48 ++----- src/feature/client/entrynodes.c | 258 +++++++++++++++++++++++++++++++++++ src/feature/client/entrynodes.h | 5 + src/feature/nodelist/networkstatus.c | 3 + src/test/test_circuitbuild.c | 2 +- src/test/test_entrynodes.c | 40 ++++++ 12 files changed, 383 insertions(+), 53 deletions(-)

1 0

[tor/main] Update changes file with the new proposal number #333.
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 43a725797bf1fcd596e2d664bc975751ad2588d2 Author: George Kadianakis <desnacked(a)riseup.net> Date: Wed Jul 21 12:43:52 2021 +0300 Update changes file with the new proposal number #333. --- changes/ticket40363 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changes/ticket40363 b/changes/ticket40363 index 240cbf8680..713f943020 100644 --- a/changes/ticket40363 +++ b/changes/ticket40363 @@ -6,4 +6,4 @@ services such as OnionShare. Long-lived onion services that need high security should still use the Vanguards addon (https://github.com/mikeperry-tor/vanguards) Closes ticket 40363; - implements proposal 332. + implements proposal 333.

1 0

[tor/main] Increase frequency of vg-lite callback to 15 minutes
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 30a97d9bb3c41e8e526afcb2ac4e1a073944cd66 Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Jul 20 13:03:32 2021 +0300 Increase frequency of vg-lite callback to 15 minutes --- src/core/mainloop/mainloop.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/core/mainloop/mainloop.c b/src/core/mainloop/mainloop.c index 68e8ee8f20..37b53db92a 100644 --- a/src/core/mainloop/mainloop.c +++ b/src/core/mainloop/mainloop.c @@ -1668,14 +1668,14 @@ mainloop_schedule_shutdown(int delay_sec) } /** - * Update vanguards-lite layer2 nodes, once per hour + * Update vanguards-lite layer2 nodes, once every 15 minutes */ static int manage_vglite_callback(time_t now, const or_options_t *options) { (void)now; (void)options; -#define VANGUARDS_LITE_INTERVAL (60*60) +#define VANGUARDS_LITE_INTERVAL (15*60) maintain_layer2_guards();

1 0

[torspec/main] First iteration of vanguards lite proposal.
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit 49196be6b76058d68837a6f3f5ed6e4a0dc55f38 Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Jun 1 12:56:15 2021 +0300 First iteration of vanguards lite proposal. --- proposals/332-vanguards-lite.md | 60 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) diff --git a/proposals/332-vanguards-lite.md b/proposals/332-vanguards-lite.md new file mode 100644 index 0000000..3971b75 --- /dev/null +++ b/proposals/332-vanguards-lite.md @@ -0,0 +1,60 @@ +``` +Filename: 332-vanguards-lite.md +Title: Vanguards lite +Author: George Kadianakis, Mike Perry +Created: 2021-05-20 +Status: Draft +``` + +# 0. Introduction & Motivation + + This proposal specifies a simplified version of Proposal 292 "Mesh-based + vanguards" for the purposes of implementing it directly into the C Tor + codebase. + + For more details on guard discovery attacks and how vanguards defend against + it, we refer to Proposal 292 [PROP292_REF]. + +# 1. Overview + + We propose an identical system to the Mesh-based Vanguards from proposal 292, + but with the following differences: + + - No third layer of guards is used. + - The Layer2 lifetime uses the max(x,x) distribution with a minimum of one + day and maximum of 12 days. This makes the average lifetime approximately a + week. We let NUM_LAYER2_GUARDS=4. + - We don't write guards on disk. This means that the guard topology resets + when tor restarts. + + By avoiding a third-layer of guards we reduce the linkability issues + of Proposal 292, which means that we don't have to add an extra hop on top of + our paths. This simplifies engineering. + +# 2. Rotation Period Analysis + + From the table in Section 3.1 of Proposal 292, with NUM_LAYER2_GUARDS=4 it + can be seen that this means that the Sybil attack on Layer2 will complete + with 50% chance in 18*7 days (126 days) for the 1% adversary, 4*7 days (one + month) for the 5% adversary, and 2*7 days (two weeks) for the 10% adversary. + +# 3. Tradeoffs from Proposal 292 + + This proposal has several advantages over Proposal 292: + + By avoiding a third-layer of guards we reduce the linkability issues of + Proposal 292, which means that we don't have to add an extra hop on top of + our paths. This simplifies engineering and makes paths shorter by default: + this means less latency and quicker page load times. + + This proposal also comes with disadvantages: + + The lack of third-layer guards makes it easier to launch guard discovery + attacks against clients and onion services. Long-lived services are not well + protected, and this proposal might provide those services with a false sense + of security. Such services should still use the vanguards addon [VANGUARDS_REF]. + +# 4. References + + [PROP292_REF]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/292-me… + [VANGUARDS_REF]: https://github.com/mikeperry-tor/vanguards

1 0

[torspec/main] Improve vanguard-lite proposal.
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit aec36da1cdd75978c7a323739d592a11e0354c4a Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Jul 20 13:46:53 2021 +0300 Improve vanguard-lite proposal. - Mention that an extra hop is added on service-side intro circs - Add circuit path length diagram - Mention max number of L2 guards - Add control port events to control spec --- control-spec.txt | 2 ++ proposals/332-vanguards-lite.md | 26 ++++++++++++++++++++------ 2 files changed, 22 insertions(+), 6 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 70f9b20..9b51715 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -3097,6 +3097,8 @@ "DOWN" -- The guard now seems to be unreachable. "BAD" -- Because of flags set in the consensus and/or values in the configuration, this node is now unusable as a guard. + "BAD_L2" -- This layer2 guard has expired or got removed from the + consensus. This node is removed from the layer2 guard set. "GOOD" -- Because of flags set in the consensus and/or values in the configuration, this node is now usable as a guard. diff --git a/proposals/332-vanguards-lite.md b/proposals/332-vanguards-lite.md index 3971b75..1e567c5 100644 --- a/proposals/332-vanguards-lite.md +++ b/proposals/332-vanguards-lite.md @@ -23,22 +23,36 @@ Status: Draft - No third layer of guards is used. - The Layer2 lifetime uses the max(x,x) distribution with a minimum of one day and maximum of 12 days. This makes the average lifetime approximately a - week. We let NUM_LAYER2_GUARDS=4. + week. + - We let NUM_LAYER2_GUARDS=4. We also introduce a consensus parameter + `guard-hs-l2-number` that controls the number of layer2 guards (with a + maximum of 19 layer2 guards). - We don't write guards on disk. This means that the guard topology resets when tor restarts. - By avoiding a third-layer of guards we reduce the linkability issues - of Proposal 292, which means that we don't have to add an extra hop on top of - our paths. This simplifies engineering. + By avoiding a third-layer of guards we avoid most of the linkability issues + of Proposal 292. This means that we don't add an extra hop on top of most of + our onion service paths, which increases performance. However, we do add an + extra middle hop at the end of service-side introduction circuits to avoid + linkability of L2s by the intro points. -# 2. Rotation Period Analysis + This is how onion service circuits look like with this proposal: + + Client rend: C -> G -> L2 -> Rend + Client intro: C -> G -> L2 -> M -> Intro + Client hsdir: C -> G -> L2 -> M -> HSDir + Service rend: C -> G -> L2 -> M -> Rend + Service intro: C -> G -> L2 -> M -> Intro + Service hsdir: C -> G -> L2 -> M -> HSDir + +# 3. Rotation Period Analysis From the table in Section 3.1 of Proposal 292, with NUM_LAYER2_GUARDS=4 it can be seen that this means that the Sybil attack on Layer2 will complete with 50% chance in 18*7 days (126 days) for the 1% adversary, 4*7 days (one month) for the 5% adversary, and 2*7 days (two weeks) for the 10% adversary. -# 3. Tradeoffs from Proposal 292 +# 4. Tradeoffs from Proposal 292 This proposal has several advantages over Proposal 292:

1 0

[torspec/main] Move 332-vanguards-lite.md to 333-vanguards-lite.md.
by asn＠torproject.org 28 Jul '21

28 Jul '21

commit df6af4fe150505473931d751abbe62526f817f1b Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Jul 20 13:48:52 2021 +0300 Move 332-vanguards-lite.md to 333-vanguards-lite.md. Since 332-ntor-v3-with-extra-data.md was faster than us --- proposals/{332-vanguards-lite.md => 333-vanguards-lite.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/332-vanguards-lite.md b/proposals/333-vanguards-lite.md similarity index 98% rename from proposals/332-vanguards-lite.md rename to proposals/333-vanguards-lite.md index 1e567c5..998bb4a 100644 --- a/proposals/332-vanguards-lite.md +++ b/proposals/333-vanguards-lite.md @@ -1,5 +1,5 @@ ``` -Filename: 332-vanguards-lite.md +Filename: 333-vanguards-lite.md Title: Vanguards lite Author: George Kadianakis, Mike Perry Created: 2021-05-20

1 0

[translation/tpo-web] https://gitweb.torproject.org/translation.git/commit/?h=tpo-web
by translation＠torproject.org 28 Jul '21

28 Jul '21

commit 84749bd4c89140f98a50d489a03c3ac940fadae7 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jul 28 08:47:45 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tpo-web --- contents+fr.po | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/contents+fr.po b/contents+fr.po index 04f1dacc6e..467d273119 100644 --- a/contents+fr.po +++ b/contents+fr.po @@ -3,12 +3,12 @@ # Martus Translations <translations(a)martus.org>, 2019 # ducki2p <ducki2p(a)gmail.com>, 2019 # Curtis Baltimore <curtisbaltimore(a)protonmail.com>, 2019 -# Emma Peel, 2019 # Gus, 2020 # walking <walking(a)i2pmail.org>, 2021 # erinm, 2021 # AO <ao(a)localizationlab.org>, 2021 # Matburnx <matboury(a)gmail.com>, 2021 +# Emma Peel, 2021 # msgid "" msgstr "" @@ -16,7 +16,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-07-07 19:01+CET\n" "PO-Revision-Date: 2019-03-09 10:41+0000\n" -"Last-Translator: Matburnx <matboury(a)gmail.com>, 2021\n" +"Last-Translator: Emma Peel, 2021\n" "Language-Team: French (https://www.transifex.com/otf/teams/1519/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -965,8 +965,8 @@ msgid "" "This release includes important [security updates to " "Firefox](https://www.mozilla.org/en-US/security/advisories/mfsa2020-43/)." msgstr "" -"Cette version inclut des importantes [mises à jour de sécurité à Firefox] " -"(https://www.mozilla.org/en-US/security/advisories/mfsa2020-43/)" +"Cette version inclut des importantes [mises à jour de sécurité à " +"Firefox](https://www.mozilla.org/en-US/security/advisories/mfsa2020-43/)." #: https//www.torproject.org/releases/tor-browser-10-0/ #: (content/releases/tor-browser-10-0/contents+en.lrpage.body) @@ -996,9 +996,9 @@ msgid "" "series](https://gitlab.torproject.org/tpo/applications/tor-" "browser/-/issues/40089) supporting CentOS 6." msgstr "" -"**Note :** le navigateur Tor 10.0 est la [dernière série du navigateur Tor] " -"(https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40089) " -"supportant CentOS 6." +"**Note :** le navigateur Tor 10.0 est la [dernière série du navigateur " +"Tor](https://gitlab.torproject.org/tpo/applications/tor-" +"browser/-/issues/40089) supportant CentOS 6." #: https//www.torproject.org/releases/tor-browser-10-0/ #: (content/releases/tor-browser-10-0/contents+en.lrpage.body)

1 0