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

[translation/torbutton-branddtd] https://gitweb.torproject.org/translation.git/commit/?h=torbutton-branddtd
by translation＠torproject.org 14 Oct '21

14 Oct '21

commit b391c78611faac1e44308d293ffce5600267eb4a Author: Translation commit bot <translation(a)torproject.org> Date: Thu Oct 14 13:47:21 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=torbutton-branddtd --- sv-SE/brand.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv-SE/brand.dtd b/sv-SE/brand.dtd index de5e4f1564..6f4af0ff48 100644 --- a/sv-SE/brand.dtd +++ b/sv-SE/brand.dtd @@ -6,7 +6,7 @@ <!ENTITY brandShortName "Tor Browser"> <!ENTITY brandFullName "Tor Browser"> <!ENTITY vendorShortName "Tor-projektet"> -<!ENTITY trademarkInfo.part1 "'Tor' och 'Onion-logotypen' är registerade varumärken av Tor Project, Inc."> +<!ENTITY trademarkInfo.part1 "'Tor' och 'Onion Logo' är registrerade varumärken av Tor Project, Inc.">

1 0

[tor/main] man: Detail onion service DDoS mitigation measure
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit 86f880d756013e0f4455ffcf27b938d945f72535 Author: David Goulet <dgoulet(a)torproject.org> Date: Thu Sep 9 14:30:52 2021 -0400 man: Detail onion service DDoS mitigation measure Move the options into the DDoS section with a series of explanations. Closes #40456 Signed-off-by: David Goulet <dgoulet(a)torproject.org> --- doc/man/tor.1.txt | 100 ++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 71 insertions(+), 29 deletions(-) diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt index 2b5a1d9df7..88160dec64 100644 --- a/doc/man/tor.1.txt +++ b/doc/man/tor.1.txt @@ -2833,11 +2833,15 @@ details.) == DENIAL OF SERVICE MITIGATION OPTIONS -Tor has three built-in mitigation options that can be individually -enabled/disabled and fine-tuned, but by default Tor directory authorities will -define reasonable values for relays and no explicit configuration is required -to make use of these protections. The mitigations take place at relays, -and are as follows: +Tor has a series of built-in denial of service mitigation options that can be +individually enabled/disabled and fine-tuned, but by default Tor directory +authorities will define reasonable values for the network and no explicit +configuration is required to make use of these protections. + +The following is a series of configuration options for relays and then options +for onion services and how they work. + +The mitigations take place at relays, and are as follows: 1. If a single client address makes too many concurrent connections (this is configurable via DoSConnectionMaxConcurrentCount), hang up on further @@ -2988,6 +2992,68 @@ Denial of Service mitigation subsystem described above. (Default: auto) +As for onion services, only one possible mitigation exists. It was intended to +protect the network first and thus do not help the service availability or +reachability. + +The mitigation we put in place is a rate limit of the amount of introduction +that happens at the introduction point for a service. In other words, it rates +limit the number of clients that are attempting to reach the service at the +introduction point instead of at the service itself. + +The following options are per onion service: + +[[HiddenServiceEnableIntroDoSDefense]] **HiddenServiceEnableIntroDoSDefense** **0**|**1**:: + Enable DoS defense at the intropoint level. When this is enabled, the + rate and burst parameter (see below) will be sent to the intro point which + will then use them to apply rate limiting for introduction request to this + service. + + + The introduction point honors the consensus parameters except if this is + specifically set by the service operator using this option. The service + never looks at the consensus parameters in order to enable or disable this + defense. (Default: 0) + +//Out of order because it logically belongs after HiddenServiceEnableIntroDoSDefense. +[[HiddenServiceEnableIntroDoSBurstPerSec]] **HiddenServiceEnableIntroDoSBurstPerSec** __NUM__:: + The allowed client introduction burst per second at the introduction + point. If this option is 0, it is considered infinite and thus if + **HiddenServiceEnableIntroDoSDefense** is set, it then effectively + disables the defenses. (Default: 200) + +[[HiddenServiceEnableIntroDoSRatePerSec]] **HiddenServiceEnableIntroDoSRatePerSec** __NUM__:: + The allowed client introduction rate per second at the introduction + point. If this option is 0, it is considered infinite and thus if + **HiddenServiceEnableIntroDoSDefense** is set, it then effectively + disables the defenses. (Default: 25) + +The rate is the maximum number of clients a service will ask its introduction +points to allow every seconds. And the burst is a parameter that allows that +many within one second. + +For example, the default values of 25 and 200 respectively means that for every +introduction points a service has (default 3 but can be configured with +**HiddenServiceNumIntroductionPoints**), 25 clients per seconds will be allowed +to reach the service and 200 at most within 1 second as a burst. This means +that if 200 clients are seen within 1 second, it will take 8 seconds (200/25) +for another client to be able to be allowed to introduce due to the rate of 25 +per second. + +This might be too much for your use case or not, fine tuning these values is +hard and are likely different for each service operator. + +Why is this not helping reachability of the service? Because the defenses are +at the introduction point, an attacker can easily flood all introduction point +rendering the service unavailable due to no client being able to pass through. +But, the service itself is not overwhelmed with connetions allowing it to +function properly for the few clients that were able to go through or other any +services running on the same tor instance. + +The bottom line is that this protects the network by preventing an onion +service to flood the network with new rendezvous circuits that is reducing load +on the network. + + == DIRECTORY AUTHORITY SERVER OPTIONS The following options enable operation as a directory authority, and @@ -3266,30 +3332,6 @@ The next section describes the per service options that can only be set only owner is able to read the hidden service directory. (Default: 0) Has no effect on Windows. -[[HiddenServiceEnableIntroDoSDefense]] **HiddenServiceEnableIntroDoSDefense** **0**|**1**:: - Enable DoS defense at the intropoint level. When this is enabled, the - rate and burst parameter (see below) will be sent to the intro point which - will then use them to apply rate limiting for introduction request to this - service. - + - The introduction point honors the consensus parameters except if this is - specifically set by the service operator using this option. The service - never looks at the consensus parameters in order to enable or disable this - defense. (Default: 0) - -//Out of order because it logically belongs after HiddenServiceEnableIntroDoSDefense. -[[HiddenServiceEnableIntroDoSBurstPerSec]] **HiddenServiceEnableIntroDoSBurstPerSec** __NUM__:: - The allowed client introduction burst per second at the introduction - point. If this option is 0, it is considered infinite and thus if - **HiddenServiceEnableIntroDoSDefense** is set, it then effectively - disables the defenses. (Default: 200) - -[[HiddenServiceEnableIntroDoSRatePerSec]] **HiddenServiceEnableIntroDoSRatePerSec** __NUM__:: - The allowed client introduction rate per second at the introduction - point. If this option is 0, it is considered infinite and thus if - **HiddenServiceEnableIntroDoSDefense** is set, it then effectively - disables the defenses. (Default: 25) - [[HiddenServiceExportCircuitID]] **HiddenServiceExportCircuitID** __protocol__:: The onion service will use the given protocol to expose the global circuit identifier of each inbound client circuit. The only

1 0

[tor/main] Merge remote-tracking branch 'tor-gitlab/mr/432' into main
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit 0ec08b06439e78cd7c2557ef39163949c62f7fbf Merge: c81901fd39 86f880d756 Author: Alexander Færøy <ahf(a)torproject.org> Date: Thu Oct 14 13:03:03 2021 +0000 Merge remote-tracking branch 'tor-gitlab/mr/432' into main doc/man/tor.1.txt | 100 ++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 71 insertions(+), 29 deletions(-)

1 0

[tor/main] Fix compilation error when __NR_time is not defined. #40465
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit 7a06b8713dde2cf736c5fa0c70dae0f43fac81f1 Author: Daniel Pinto <danielpinto52(a)gmail.com> Date: Thu Sep 9 23:55:49 2021 +0100 Fix compilation error when __NR_time is not defined. #40465 --- changes/bug40465 | 3 +++ src/lib/sandbox/sandbox.c | 9 +++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/changes/bug40465 b/changes/bug40465 new file mode 100644 index 0000000000..d4d225c62e --- /dev/null +++ b/changes/bug40465 @@ -0,0 +1,3 @@ + o Minor bugfixes (compilation): + - Fix compilation error when __NR_time is not defined. Fixes bug + 40465; bugfix on 0.2.5.5-alpha. Patch by Daniel Pinto. diff --git a/src/lib/sandbox/sandbox.c b/src/lib/sandbox/sandbox.c index 02222e5a1c..091234e6b9 100644 --- a/src/lib/sandbox/sandbox.c +++ b/src/lib/sandbox/sandbox.c @@ -339,6 +339,7 @@ sb_rt_sigaction(scmp_filter_ctx ctx, sandbox_cfg_t *filter) return rc; } +#ifdef __NR_time /** * Function responsible for setting up the time syscall for * the seccomp filter sandbox. @@ -347,13 +348,11 @@ static int sb_time(scmp_filter_ctx ctx, sandbox_cfg_t *filter) { (void) filter; -#ifdef __NR_time + return seccomp_rule_add_1(ctx, SCMP_ACT_ALLOW, SCMP_SYS(time), SCMP_CMP(0, SCMP_CMP_EQ, 0)); -#else - return 0; -#endif /* defined(__NR_time) */ } +#endif /* defined(__NR_time) */ /** * Function responsible for setting up the accept4 syscall for @@ -1192,7 +1191,9 @@ sb_kill(scmp_filter_ctx ctx, sandbox_cfg_t *filter) static sandbox_filter_func_t filter_func[] = { sb_rt_sigaction, sb_rt_sigprocmask, +#ifdef __NR_time sb_time, +#endif sb_accept4, #ifdef __NR_mmap2 sb_mmap2,

1 0

[tor/main] Merge remote-tracking branch 'tor-gitlab/mr/433' into main
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit c81901fd398c31b827db29e4d080407764619471 Merge: d3c8008660 7a06b8713d Author: Alexander Færøy <ahf(a)torproject.org> Date: Thu Oct 14 13:01:41 2021 +0000 Merge remote-tracking branch 'tor-gitlab/mr/433' into main changes/bug40465 | 3 +++ src/lib/sandbox/sandbox.c | 9 +++++---- 2 files changed, 8 insertions(+), 4 deletions(-)

1 0

[tor/main] Merge remote-tracking branch 'tor-gitlab/mr/451' into main
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit d3c800866056575d5b115407d560c113104881df Merge: 4dfc5de509 0f7e0d5f2f Author: Alexander Færøy <ahf(a)torproject.org> Date: Thu Oct 14 12:59:25 2021 +0000 Merge remote-tracking branch 'tor-gitlab/mr/451' into main changes/ticket40480 | 3 +++ src/feature/dirauth/process_descs.c | 8 ++++---- src/test/test_process_descs.c | 14 +++++++++++--- 3 files changed, 18 insertions(+), 7 deletions(-)

1 0

[tor/main] dirauth: Reject EOL relays
by ahf＠torproject.org 14 Oct '21

14 Oct '21

commit 0f7e0d5f2f4d2e472d1c5eeb47bbc61d4704acbb Author: David Goulet <dgoulet(a)torproject.org> Date: Fri Oct 8 11:04:11 2021 -0400 dirauth: Reject EOL relays Series 0.4.2.x, 0.4.3.x and 0.4.4.x will all be rejected at the authority level at this commit. Futhermore, the 0.4.5.x alphas and rc will also be rejected. Closes #40480 Signed-off-by: David Goulet <dgoulet(a)torproject.org> --- changes/ticket40480 | 3 +++ src/feature/dirauth/process_descs.c | 8 ++++---- src/test/test_process_descs.c | 14 +++++++++++--- 3 files changed, 18 insertions(+), 7 deletions(-) diff --git a/changes/ticket40480 b/changes/ticket40480 new file mode 100644 index 0000000000..525e848a1f --- /dev/null +++ b/changes/ticket40480 @@ -0,0 +1,3 @@ + o Minor feature (authority, relay): + - Reject End-Of-Life relays running version 0.4.2.x, 0.4.3.x, 0.4.4.x and + 0.4.5 alphas and rc. Closes ticket 40480. diff --git a/src/feature/dirauth/process_descs.c b/src/feature/dirauth/process_descs.c index eca987b8b5..5ea9d16850 100644 --- a/src/feature/dirauth/process_descs.c +++ b/src/feature/dirauth/process_descs.c @@ -412,11 +412,11 @@ dirserv_rejects_tor_version(const char *platform, return true; } - /* Series between Tor 0.3.6 and 0.4.1 inclusive are unsupported. Reject - * them. 0.3.6.0-alpha-dev only existed for a short time, before it was - * renamed to 0.4.0.0-alpha-dev. */ + /* Series between Tor 0.3.6.x and 0.4.5.5-rc inclusive are unsupported. + * Reject them. 0.3.6.0-alpha-dev only existed for a short time, before it + * was renamed to 0.4.0.0-alpha-dev. */ if (tor_version_as_new_as(platform,"0.3.6.0-alpha-dev") && - !tor_version_as_new_as(platform,"0.4.2.1-alpha")) { + !tor_version_as_new_as(platform,"0.4.5.6")) { if (msg) { *msg = please_upgrade_string; } diff --git a/src/test/test_process_descs.c b/src/test/test_process_descs.c index fa2657f6c2..5503fc69ee 100644 --- a/src/test/test_process_descs.c +++ b/src/test/test_process_descs.c @@ -39,12 +39,20 @@ test_process_descs_versions(void *arg) { "Tor 0.4.1.1-alpha", true }, { "Tor 0.4.1.4-rc", true }, { "Tor 0.4.1.5", true }, + { "Tor 0.4.2.1-alpha", true }, + { "Tor 0.4.2.4-rc", true }, + { "Tor 0.4.2.5", true }, + { "Tor 0.4.3.0-alpha-dev", true }, + { "Tor 0.4.3.8", true }, + { "Tor 0.4.4.9", true }, + { "Tor 0.4.5.5-rc", true }, // new enough to be supported { "Tor 0.3.5.7", false }, { "Tor 0.3.5.8", false }, - { "Tor 0.4.2.1-alpha", false }, - { "Tor 0.4.2.4-rc", false }, - { "Tor 0.4.3.0-alpha-dev", false }, + { "Tor 0.4.5.6", false }, + { "Tor 0.4.6.0-alpha-dev", false }, + { "Tor 0.4.6.5", false }, + { "Tor 0.4.7.0-alpha-dev", false }, // Very far in the future { "Tor 100.100.1.5", false }, };

1 0

[tor/main] Downgrade a PROTOCOL_WARN log message.
by dgoulet＠torproject.org 14 Oct '21

14 Oct '21

commit 3da455de0025f2d7a6ef97dcae849fefe3ba35fb Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Oct 13 16:51:46 2021 -0400 Downgrade a PROTOCOL_WARN log message. This one happens every time we get a failure from circuit_receive_relay_cell -- but for all the relevant failing cases in that function, we already log in that function. This resolves one case of #40400. Two cases remain. --- changes/bug40400 | 6 ++++++ src/core/or/command.c | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/changes/bug40400 b/changes/bug40400 new file mode 100644 index 0000000000..2ac5cf5dce --- /dev/null +++ b/changes/bug40400 @@ -0,0 +1,6 @@ + o Minor bugfixes (usability): + - Do not log "circuit_receive_relay_cell failed" at LOG_PROTOCOL_WARN; + instead log it at DEBUG. In every case where we would want to log + this as a protocol warning, we are already logging another warning + from inside circuit_receive_relay_cell. Fixes part of bug 40400; + bugfix on 0.1.1.9. diff --git a/src/core/or/command.c b/src/core/or/command.c index 622217a78e..40eb1554c0 100644 --- a/src/core/or/command.c +++ b/src/core/or/command.c @@ -563,7 +563,7 @@ command_process_relay_cell(cell_t *cell, channel_t *chan) } if ((reason = circuit_receive_relay_cell(cell, circ, direction)) < 0) { - log_fn(LOG_PROTOCOL_WARN,LD_PROTOCOL,"circuit_receive_relay_cell " + log_fn(LOG_DEBUG,LD_PROTOCOL,"circuit_receive_relay_cell " "(%s) failed. Closing.", direction==CELL_DIRECTION_OUT?"forward":"backward"); /* Always emit a bandwidth event for closed circs */

1 0

[tor/main] Merge branch 'tor-gitlab/mr/455'
by dgoulet＠torproject.org 14 Oct '21

14 Oct '21

commit 4dfc5de509302e009f4137035cacbb687537c1fe Merge: 028b52f1ef 3da455de00 Author: David Goulet <dgoulet(a)torproject.org> Date: Thu Oct 14 08:40:38 2021 -0400 Merge branch 'tor-gitlab/mr/455' changes/bug40400 | 6 ++++++ src/core/or/command.c | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-)

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 14 Oct '21

14 Oct '21

commit ccbb64f5f203447d047cd3b8e6b33fa690aa5a93 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Oct 14 11:48:04 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 39 +++++++++++++++++++-------------------- 1 file changed, 19 insertions(+), 20 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index 7b0717f252..4de4586daf 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -16,8 +16,8 @@ # Ahmed A., 2021 # William Ward <will(a)industryarabic.com>, 2021 # erinm, 2021 -# Emma Peel, 2021 # NASI₿ <nomadweb(a)protonmail.ch>, 2021 +# Emma Peel, 2021 # msgid "" msgstr "" @@ -25,7 +25,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-10-11 15:59+CET\n" "PO-Revision-Date: 2018-10-02 22:41+0000\n" -"Last-Translator: NASI₿ <nomadweb(a)protonmail.ch>, 2021\n" +"Last-Translator: Emma Peel, 2021\n" "Language-Team: Arabic (https://www.transifex.com/otf/teams/1519/ar/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -6911,7 +6911,7 @@ msgid "" "through malicious configuration of your `torrc`." msgstr "" "يمكن أن يؤدي القيام بذلك إلى السماح للمهاجم بخرق أمنك وإخفاء هويتك من خلال " -"التكوين الضار لـ \"torrc\"." +"التكوين الضار لـ `torrc`." #: https//support.torproject.org/tbb/tbb-editing-torrc/ #: (content/tbb/tbb-editing-torrc/contents+en.lrquestion.description) @@ -6919,8 +6919,8 @@ msgid "" "Tor uses a text file called `torrc` that contains configuration instructions" " for how Tor should behave." msgstr "" -"يستخدم Tor ملفًا نصيًا يسمى \"torrc\" يحتوي على تعليمات التكوين الخاصة " -"بكيفية تصرف Tor." +"يستخدم Tor ملفًا نصيًا يسمى `torrc` يحتوي على تعليمات التكوين الخاصة بكيفية " +"تصرف Tor." #: https//support.torproject.org/tbb/tbb-editing-torrc/ #: (content/tbb/tbb-editing-torrc/contents+en.lrquestion.description) @@ -6937,8 +6937,8 @@ msgid "" "To find your Tor Browser `torrc`, follow the instructions for your operating" " system below." msgstr "" -"للعثور على متصفح Tor الخاص بك \"torrc\" ، اتبع التعليمات الخاصة بنظام " -"التشغيل أدناه." +"للعثور على متصفح Tor الخاص بك `torrc` ، اتبع التعليمات الخاصة بنظام التشغيل " +"أدناه." #: https//support.torproject.org/tbb/tbb-editing-torrc/ #: (content/tbb/tbb-editing-torrc/contents+en.lrquestion.description) @@ -6951,8 +6951,8 @@ msgid "" "* The `torrc` is in the Tor Browser Data directory at " "`Browser/TorBrowser/Data/Tor` inside your Tor Browser directory." msgstr "" -"* يوجد \"torrc\" في دليل بيانات متصفح Tor في \"Browser / TorBrowser / Data /" -" Tor\" داخل دليل متصفح Tor." +"* يوجد `torrc` في دليل بيانات متصفح Tor في `Browser / TorBrowser / Data / " +"Tor` داخل دليل متصفح Tor." #: https//support.torproject.org/tbb/tbb-editing-torrc/ #: (content/tbb/tbb-editing-torrc/contents+en.lrquestion.description) @@ -6965,8 +6965,8 @@ msgid "" "* The `torrc` is in the Tor Browser Data directory at `~/Library/Application" " Support/TorBrowser-Data/Tor`." msgstr "" -"* يوجد \"torrc\" في دليل بيانات متصفح Tor في \"~ / Library / Application " -"Support / TorBrowser-Data / Tor\"." +"* يوجد `torrc` في دليل بيانات متصفح Tor في `~ / Library / Application " +"Support / TorBrowser-Data / Tor`." #: https//support.torproject.org/tbb/tbb-editing-torrc/ #: (content/tbb/tbb-editing-torrc/contents+en.lrquestion.description) @@ -7007,7 +7007,7 @@ msgid "" " file for hints on common configurations." msgstr "" "ألق نظرة على ملف [نموذج " -"\"torrc\"](https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in)" +"`torrc`](https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in)" " للحصول على تلميحات حول التكوينات الشائعة." #: https//support.torproject.org/tbb/tbb-editing-torrc/ @@ -9384,8 +9384,8 @@ msgid "" "* Modify the Tor client and relay startup scripts to include `-f " "/path/to/correct/torrc`." msgstr "" -"* قم بتعديل عميل Tor وترحيل البرامج النصية لبدء التشغيل لتشمل \"-f / path / " -"to / correct / torrc\"." +"* قم بتعديل عميل Tor وترحيل البرامج النصية لبدء التشغيل لتشمل `-f / path / " +"to / correct / torrc`." #: https//support.torproject.org/relay-operators/hibernation/ #: (content/relay-operators/hibernation/contents+en.lrquestion.description) @@ -9394,8 +9394,7 @@ msgid "" "`Tor.relay` may make separation of configs easier." msgstr "" "* في لينكس / بي اس دي / نظام التشغيل ماك او اس اكس ، قد يؤدي تغيير البرامج " -"النصية لبدء التشغيل إلى \"Tor.client\" و \"Tor.relay\" إلى تسهيل فصل " -"التكوينات." +"النصية لبدء التشغيل إلى `Tor.client` و `Tor.relay` إلى تسهيل فصل التكوينات." #: https//support.torproject.org/relay-operators/ipv6-relay/ #: (content/relay-operators/ipv6-relay/contents+en.lrquestion.title) @@ -10068,8 +10067,8 @@ msgid "" "* Your `ulimit -n` gets set to 32768 high enough for Tor to keep open all " "the connections it needs." msgstr "" -"* يتم ضبط \"ulimit -n\" الخاص بك على 32768 مرتفعًا بما يكفي ليحافظ Tor على " -"فتح جميع الاتصالات التي يحتاجها." +"* يتم ضبط `ulimit -n` الخاص بك على 32768 مرتفعًا بما يكفي ليحافظ Tor على فتح" +" جميع الاتصالات التي يحتاجها." #: https//support.torproject.org/relay-operators/packaged-tor/ #: (content/relay-operators/packaged-tor/contents+en.lrquestion.description) @@ -10090,7 +10089,7 @@ msgid "" "* Tor runs with `--verify-config`, so that most problems with your config " "file get caught." msgstr "" -"* يعمل Tor مع \"--verify-config\" ، بحيث يتم اكتشاف معظم المشاكل مع ملف " +"* يعمل Tor مع `--verify-config` ، بحيث يتم اكتشاف معظم المشاكل مع ملف " "التكوين الخاص بك." #: https//support.torproject.org/relay-operators/packaged-tor/ @@ -11084,7 +11083,7 @@ msgstr "" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "See the `MaxAdvertisedBandwidth` option in the man page." -msgstr "راجع خيار \"الحد الأقصى لعرض النطاق الترددي المعلن عنه\" في صفحة الدليل." +msgstr "راجع خيار `MaxAdvertisedBandwidth` في صفحة الدليل." #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)

1 0