tor-commits March 2022

tor-commits@lists.torproject.org

9 participants
398 discussions

[translation/support-portal] new translations in support-portal
by translation＠torproject.org 15 Mar '22

15 Mar '22

commit 30907fa78a1cb1359f7ddc479bac492d677b6953 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Mar 15 04:47:35 2022 +0000 new translations in support-portal --- contents+ko.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents+ko.po b/contents+ko.po index 3bc200a290..75404af1a4 100644 --- a/contents+ko.po +++ b/contents+ko.po @@ -15326,7 +15326,7 @@ msgstr "" #: https//support.torproject.org/alternate-designs/transport-all-ip-packets/ #: (content/alternate-designs/transport-all-ip-packets/contents+en.lrquestion.description) msgid "It could solve the whole need to socksify applications." -msgstr "" +msgstr "애플리케이션에 SKCOS를 적용하는 데 필요한 사항이 모두 해결됩니다." #: https//support.torproject.org/alternate-designs/transport-all-ip-packets/ #: (content/alternate-designs/transport-all-ip-packets/contents+en.lrquestion.description)

1 0

[tor-browser/geckoview-96.0-11.0-1] Bug 1758156 - Check the pref when creating PWebGPU parent actors. r=aosmond a=pascalc
by boklm＠torproject.org 14 Mar '22

14 Mar '22

commit d7efc93e7eabe63ca5381fb07a1786e2d55e69c6 Author: Nicolas Silva <nsilva(a)mozilla.com> Date: Thu Mar 10 10:41:29 2022 +0000 Bug 1758156 - Check the pref when creating PWebGPU parent actors. r=aosmond a=pascalc Differential Revision: https://phabricator.services.mozilla.com/D140539 --- gfx/layers/ipc/ContentCompositorBridgeParent.cpp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/gfx/layers/ipc/ContentCompositorBridgeParent.cpp b/gfx/layers/ipc/ContentCompositorBridgeParent.cpp index 9b3a641ad0e6..03f5e68cd241 100644 --- a/gfx/layers/ipc/ContentCompositorBridgeParent.cpp +++ b/gfx/layers/ipc/ContentCompositorBridgeParent.cpp @@ -14,6 +14,7 @@ # include "mozilla/gfx/DeviceManagerDx.h" // for DeviceManagerDx # include "mozilla/layers/ImageDataSerializer.h" #endif +#include "mozilla/StaticPrefs_dom.h" #include "mozilla/ipc/Transport.h" // for Transport #include "mozilla/layers/AnimationHelper.h" // for CompositorAnimationStorage #include "mozilla/layers/APZCTreeManagerParent.h" // for APZCTreeManagerParent @@ -206,6 +207,10 @@ bool ContentCompositorBridgeParent::DeallocPWebRenderBridgeParent( } webgpu::PWebGPUParent* ContentCompositorBridgeParent::AllocPWebGPUParent() { + if (!StaticPrefs::dom_webgpu_enabled()) { + return nullptr; + } + webgpu::WebGPUParent* parent = new webgpu::WebGPUParent(); parent->AddRef(); // IPDL reference return parent;

1 0

[tor-browser/geckoview-96.0-11.5-1] Bug 1758156 - Check the pref when creating PWebGPU parent actors. r=aosmond a=pascalc
by boklm＠torproject.org 14 Mar '22

14 Mar '22

commit 68e69fd248a255694bf2344f9f80125a708f5dc5 Author: Nicolas Silva <nsilva(a)mozilla.com> Date: Thu Mar 10 10:41:29 2022 +0000 Bug 1758156 - Check the pref when creating PWebGPU parent actors. r=aosmond a=pascalc Differential Revision: https://phabricator.services.mozilla.com/D140539 --- gfx/layers/ipc/ContentCompositorBridgeParent.cpp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/gfx/layers/ipc/ContentCompositorBridgeParent.cpp b/gfx/layers/ipc/ContentCompositorBridgeParent.cpp index 9b3a641ad0e6..03f5e68cd241 100644 --- a/gfx/layers/ipc/ContentCompositorBridgeParent.cpp +++ b/gfx/layers/ipc/ContentCompositorBridgeParent.cpp @@ -14,6 +14,7 @@ # include "mozilla/gfx/DeviceManagerDx.h" // for DeviceManagerDx # include "mozilla/layers/ImageDataSerializer.h" #endif +#include "mozilla/StaticPrefs_dom.h" #include "mozilla/ipc/Transport.h" // for Transport #include "mozilla/layers/AnimationHelper.h" // for CompositorAnimationStorage #include "mozilla/layers/APZCTreeManagerParent.h" // for APZCTreeManagerParent @@ -206,6 +207,10 @@ bool ContentCompositorBridgeParent::DeallocPWebRenderBridgeParent( } webgpu::PWebGPUParent* ContentCompositorBridgeParent::AllocPWebGPUParent() { + if (!StaticPrefs::dom_webgpu_enabled()) { + return nullptr; + } + webgpu::WebGPUParent* parent = new webgpu::WebGPUParent(); parent->AddRef(); // IPDL reference return parent;

1 0

[translation/tails-misc_release] new translations in tails-misc_release
by translation＠torproject.org 14 Mar '22

14 Mar '22

commit 8387dcf61c08614b33817746420c85871e214743 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Mar 14 19:46:40 2022 +0000 new translations in tails-misc_release --- zh_CN.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh_CN.po b/zh_CN.po index ec38a530b9..bdfe6efff1 100644 --- a/zh_CN.po +++ b/zh_CN.po @@ -3,7 +3,7 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: -# Zhui Shen <12231252(a)bjtu.edu.cn>, 2020 +# shenzhui007 <12231252(a)bjtu.edu.cn>, 2020 # khi, 2013 # c0conut, 2020 # Andy Lyu <baiqinglyu(a)gmail.com>, 2018 @@ -36,7 +36,7 @@ # YFdyh000 <yfdyh000(a)gmail.com>, 2016 # YFdyh000 <yfdyh000(a)gmail.com>, 2013-2016 # ff98sha, 2019 -# Zhui Shen <12231252(a)bjtu.edu.cn>, 2019 +# shenzhui007 <12231252(a)bjtu.edu.cn>, 2019 # 狂男风 <CrazyBoyFeng(a)Live.Com>, 2021 # 耀石徐 <xuyaoshix(a)gmail.com>, 2019 # ヨイツの賢狼ホロ, 2018

1 0

[torspec/main] Add congestion control fields to CIRC_BW
by dgoulet＠torproject.org 14 Mar '22

14 Mar '22

commit e38527978a3fa03e58f7e528593f1fac761584e3 Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Thu Mar 3 21:14:08 2022 +0000 Add congestion control fields to CIRC_BW --- control-spec.txt | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/control-spec.txt b/control-spec.txt index 0e2add3..b277d03 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -3430,14 +3430,21 @@ Table of Contents "WRITTEN=" BytesWritten SP "TIME=" Time SP "DELIVERED_READ=" DeliveredBytesRead SP "OVERHEAD_READ=" OverheadBytesRead SP - "DELIVERED_WRITTEN=" DeliveredBytesWritten CRLF + "DELIVERED_WRITTEN=" DeliveredBytesWritten SP "OVERHEAD_WRITTEN=" OverheadBytesWritten SP + "SS=" SlowStartState SP + "CWND=" CWNDCells SP + "RTT=" RTTMilliseconds SP + "MIN_RTT=" RTTMilliseconds CRLF BytesRead = 1*DIGIT BytesWritten = 1*DIGIT OverheadBytesRead = 1*DIGIT OverheadBytesWritten = 1*DIGIT DeliveredBytesRead = 1*DIGIT DeliveredBytesWritten = 1*DIGIT + SlowStartState = 0 or 1 + CWNDCells = 1*DIGIT + RTTMilliseconds= 1*DIGIT Time = ISOTime2Frac BytesRead and BytesWritten are the number of bytes read and written @@ -3465,6 +3472,16 @@ Table of Contents The Time field is provided only in versions 0.3.2.1-alpha and later. It records when Tor created the bandwidth event. + The SS, CWND, RTT, and MIN_RTT fields are present only if the circuit + has negotiated congestion control to an onion service or Exit hop (any + intermediate leaky pipe congestion control hops are not examined here). + SS provides an indication if the circuit is in slow start (1), or not (0). + CWND is the size of the congestion window in terms of number of cells. + RTT is the N_EWMA smoothed current RTT value, and MIN_RTT is the minimum + RTT value of the circuit. The SS and CWND fields apply only to the + upstream direction of the circuit. The slow start state and CWND values + of the other endpoint may be different. + These events are generated about once per second per circuit; no events are generated for circuits that had no attached stream writing or reading. @@ -3474,6 +3491,8 @@ Table of Contents [DELIVERED_READ, OVERHEAD_READ, DELIVERED_WRITTEN, and OVERHEAD_WRITTEN were added in Tor 0.3.4.0-alpha] + [SS, CWND, RTT, and MIN_RTT were added in Tor 0.4.7.5-alpha] + 4.1.23. Per-circuit cell stats The syntax is:

1 0

[torspec/main] Remove comma from STATUS format specification.
by dgoulet＠torproject.org 14 Mar '22

14 Mar '22

commit ec77ae643f3e47bea0292d125a51f8786bf33fb9 Author: David Fifield <dcf(a)torproject.org> Date: Mon Feb 28 07:38:36 2022 +0000 Remove comma from STATUS format specification. --- pt-spec.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pt-spec.txt b/pt-spec.txt index 05421c1..45b4c31 100644 --- a/pt-spec.txt +++ b/pt-spec.txt @@ -1,4 +1,3 @@ - Pluggable Transport Specification (Version 1) Abstract @@ -668,7 +667,7 @@ Table of Contents The format of the message: - STATUS TRANSPORT=Transport <K_1>=<V_1> [<K_2>=<V_2>, ...] + STATUS TRANSPORT=Transport <K_1>=<V_1> [<K_2>=<V_2> ...] The TRANSPORT value indicates a hint on what the PT is such has the name or the protocol used for instance. As an example, obfs4proxy would use

1 0

[tor/main] Add congestion control fields to CIRC_BW control port event
by dgoulet＠torproject.org 14 Mar '22

14 Mar '22

commit 646a1d5f9ae481667f0ec43e45879b94ea2dd28a Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Thu Mar 3 20:06:38 2022 +0000 Add congestion control fields to CIRC_BW control port event --- src/core/or/congestion_control_common.c | 42 +++++++++++++++++++++++++++++++++ src/core/or/congestion_control_common.h | 1 + src/feature/control/control_events.c | 12 ++++++++-- 3 files changed, 53 insertions(+), 2 deletions(-) diff --git a/src/core/or/congestion_control_common.c b/src/core/or/congestion_control_common.c index 93d3a9f2c5..36099cc1c6 100644 --- a/src/core/or/congestion_control_common.c +++ b/src/core/or/congestion_control_common.c @@ -1442,3 +1442,45 @@ congestion_control_parse_ext_response(const uint8_t *msg, return (int)ret; } + +/** + * Returns a formatted string of fields containing congestion + * control information, for the CIRC_BW control port event. + * + * An origin circuit can have a ccontrol object directly on it, + * if it is an onion service, or onion client. Exit-bound clients + * will have the ccontrol on the cpath associated with their exit + * (the last one in the cpath list). + * + * WARNING: This function does not support leaky-pipe topology. It + * is to be used for control port information only. + */ +char * +congestion_control_get_control_port_fields(const origin_circuit_t *circ) +{ + const congestion_control_t *ccontrol = NULL; + char *ret = NULL; + int len; + + if (TO_CIRCUIT(circ)->ccontrol) { + ccontrol = TO_CIRCUIT(circ)->ccontrol; + } else if (circ->cpath && circ->cpath->prev->ccontrol) { + /* Get ccontrol for last hop (exit) if it exists */ + ccontrol = circ->cpath->prev->ccontrol; + } + + if (!ccontrol) + return NULL; + + len = tor_asprintf(&ret, + " SS=%d CWND=%"PRIu64" RTT=%"PRIu64" MIN_RTT=%"PRIu64, + ccontrol->in_slow_start, ccontrol->cwnd, + ccontrol->ewma_rtt_usec/1000, + ccontrol->min_rtt_usec/1000); + if (len < 0) { + log_warn(LD_BUG, "Unable to format event for controller."); + return NULL; + } + + return ret; +} diff --git a/src/core/or/congestion_control_common.h b/src/core/or/congestion_control_common.h index 1a57d71331..71e984f914 100644 --- a/src/core/or/congestion_control_common.h +++ b/src/core/or/congestion_control_common.h @@ -80,6 +80,7 @@ int congestion_control_parse_ext_response(const uint8_t *msg, const size_t msg_len, circuit_params_t *params_out); bool congestion_control_validate_sendme_increment(uint8_t sendme_inc); +char *congestion_control_get_control_port_fields(const origin_circuit_t *); /* Ugh, C.. these are private. Use the getter instead, when * external to the congestion control code. */ diff --git a/src/feature/control/control_events.c b/src/feature/control/control_events.c index e2aca6c03e..f9b7caf934 100644 --- a/src/feature/control/control_events.c +++ b/src/feature/control/control_events.c @@ -21,6 +21,7 @@ #include "core/or/command.h" #include "core/or/connection_edge.h" #include "core/or/connection_or.h" +#include "core/or/congestion_control_common.h" #include "core/or/reasons.h" #include "feature/control/control.h" #include "feature/control/control_events.h" @@ -1075,10 +1076,12 @@ control_event_circ_bandwidth_used_for_circ(origin_circuit_t *ocirc) tor_gettimeofday(&now); format_iso_time_nospace_usec(tbuf, &now); + + char *ccontrol_buf = congestion_control_get_control_port_fields(ocirc); send_control_event(EVENT_CIRC_BANDWIDTH_USED, "650 CIRC_BW ID=%d READ=%lu WRITTEN=%lu TIME=%s " "DELIVERED_READ=%lu OVERHEAD_READ=%lu " - "DELIVERED_WRITTEN=%lu OVERHEAD_WRITTEN=%lu\r\n", + "DELIVERED_WRITTEN=%lu OVERHEAD_WRITTEN=%lu%s\r\n", ocirc->global_identifier, (unsigned long)ocirc->n_read_circ_bw, (unsigned long)ocirc->n_written_circ_bw, @@ -1086,11 +1089,16 @@ control_event_circ_bandwidth_used_for_circ(origin_circuit_t *ocirc) (unsigned long)ocirc->n_delivered_read_circ_bw, (unsigned long)ocirc->n_overhead_read_circ_bw, (unsigned long)ocirc->n_delivered_written_circ_bw, - (unsigned long)ocirc->n_overhead_written_circ_bw); + (unsigned long)ocirc->n_overhead_written_circ_bw, + ccontrol_buf ? ccontrol_buf : ""); + ocirc->n_written_circ_bw = ocirc->n_read_circ_bw = 0; ocirc->n_overhead_written_circ_bw = ocirc->n_overhead_read_circ_bw = 0; ocirc->n_delivered_written_circ_bw = ocirc->n_delivered_read_circ_bw = 0; + if (ccontrol_buf) + tor_free(ccontrol_buf); + return 0; }

1 0

[translation/support-portal] new translations in support-portal
by translation＠torproject.org 14 Mar '22

14 Mar '22

commit bb11ac50c695aa1cfae7096e52981aac42521e7d Author: Translation commit bot <translation(a)torproject.org> Date: Mon Mar 14 18:17:46 2022 +0000 new translations in support-portal --- contents+ko.po | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/contents+ko.po b/contents+ko.po index 8424242974..3bc200a290 100644 --- a/contents+ko.po +++ b/contents+ko.po @@ -6424,6 +6424,9 @@ msgid "" "manual.html.en#Socks4Proxy). Using a SOCKS 5 proxy with authentication might" " look like this:" msgstr "" +"SOCKS 프록시를 사용하려면, `Socks4Proxy`, `Socks5Proxy`, 그리고 관련 torrc 옵션을 [매뉴얼 " +"페이지](https://2019.www.torproject.org/docs/tor-manual.html.en#Socks4Proxy)에서 " +"확인하세요. 인증 기능이 추가된 SOCKS 5 프록시는 이거 같습니다:" #: https//support.torproject.org/tbb/tbb-47/ #: (content/tbb/tbb-47/contents+en.lrquestion.description) @@ -6753,6 +6756,7 @@ msgid "" "Configuration is simple, editing your torrc file's SocksListenAddress " "according to the following examples:" msgstr "" +"구성방법은 간단합니다. torrc 파일에 있는 SocksListenAddress 를 수정하면 됩니다. 다음 예제를 따라 설정해보세요:" #: https//support.torproject.org/tbb/tbb-install-tor-central-server/ #: (content/tbb/tbb-install-tor-central-server/contents+en.lrquestion.description) @@ -6793,20 +6797,22 @@ msgid "" "a socks proxy with the address and port you specified SocksListenAddress to " "be." msgstr "" +"이후 각 네트워크/부분망 내 클라이언트가 귀하가 SocksListenAddress 설정에서 지정한 바에 따라 주소와 포트를 설정해 " +"socks 프록시를 규정할 것입니다." #: https//support.torproject.org/tbb/tbb-install-tor-central-server/ #: (content/tbb/tbb-install-tor-central-server/contents+en.lrquestion.description) msgid "" "Please note that the SocksPort configuration option gives the port ONLY for " "localhost (127.0.0.1)." -msgstr "" +msgstr "SocksPort 구성 옵션엔 localhost (127.0.0.1) 포트'만' 있음을 유의하세요." #: https//support.torproject.org/tbb/tbb-install-tor-central-server/ #: (content/tbb/tbb-install-tor-central-server/contents+en.lrquestion.description) msgid "" "When setting up your SocksListenAddress(es), you need to give the port with " "the address, as shown above." -msgstr "" +msgstr "SocksListenAddress(es) 설정을 마치면, 상기한 바와 같이 포트에 주소를 부여해야 합니다." #: https//support.torproject.org/tbb/tbb-install-tor-central-server/ #: (content/tbb/tbb-install-tor-central-server/contents+en.lrquestion.description) @@ -12030,7 +12036,7 @@ msgstr "sub 4096R/C00942E4 2017-03-13" #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.title) msgid "" "How do I check if my application that uses SOCKS is leaking DNS requests?" -msgstr "" +msgstr "SOCKS를 사용하는 제 애플리케이션에서 DNS 요청이 유출되고 있음을 어떻게 확인하나요?" #: https//support.torproject.org/misc/check-socks-dns-leaks/ #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) @@ -12038,6 +12044,8 @@ msgid "" "Even if your application is using the correct variant of the SOCKS protocol," " there is still a risk that it could be leaking DNS queries." msgstr "" +"설사 귀하의 애플리케이션에서 올바른 SOCKS 프로토콜 변종을 쓰고 있다고 하더라도, DNS 쿼리가 거기서 유출되고 있을 리스크가 여전히" +" 존재합니다." #: https//support.torproject.org/misc/check-socks-dns-leaks/ #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) @@ -12058,7 +12066,7 @@ msgstr "" #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) msgid "" "1. Add `TestSocks 1` to your [torrc file](../../tbb/tbb-editing-torrc/)." -msgstr "" +msgstr "1. [torrc 파일](../../tbb/tbb-editing-torrc/)에 `TestSocks 1` 을 추가하세요." #: https//support.torproject.org/misc/check-socks-dns-leaks/ #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) @@ -12066,6 +12074,8 @@ msgid "" "1. Start Tor, and point your program's SOCKS proxy settings to Tor's SOCKS5 " "server (`socks5://127.0.0.1:9050` by default)." msgstr "" +"1. Tor를 시작한 후 애플리케이션의 SOCKS 프록시 설정을 Tor의 SOCKS5 서버(`socks5://127.0.0.1:9050`" +" by default) 설정에 맞추세요" #: https//support.torproject.org/misc/check-socks-dns-leaks/ #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) @@ -12074,13 +12084,15 @@ msgid "" "Tor will log a `notice` for safe connections, and a `warn` for connections " "leaking DNS requests." msgstr "" +"1. 애플리케이션을 사용하면서 로그를 주시하세요. 매 socks 연결마다 Tor는 안전한 연결일 경우 `notice` 로그를 남깁니다. " +"그리고 DNS 요청이 유출되고 있는 연결의 경우 `warn` 로그를 남깁니다." #: https//support.torproject.org/misc/check-socks-dns-leaks/ #: (content/misc/check-socks-dns-leaks/contents+en.lrquestion.description) msgid "" "If you want to automatically disable all connections leaking DNS requests, " "set `SafeSocks 1` in your torrc file." -msgstr "" +msgstr "DNS 요청이 유출되고 있는 연결 모두를 자동으로 비활성화하려면, torrc 파일에 `SafeSocks 1`을 추가하세요." #: https//support.torproject.org/misc/hide-exits/ #: (content/misc/hide-exits/contents+en.lrquestion.title)

1 0

[translation/support-portal] new translations in support-portal
by translation＠torproject.org 14 Mar '22

14 Mar '22

commit c1b159795504dbe6e00abc9ffef19a470c948625 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Mar 14 17:47:53 2022 +0000 new translations in support-portal --- contents+ko.po | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/contents+ko.po b/contents+ko.po index ce0f86f915..8424242974 100644 --- a/contents+ko.po +++ b/contents+ko.po @@ -6353,7 +6353,7 @@ msgstr "" #: https//support.torproject.org/tbb/tbb-47/ #: (content/tbb/tbb-47/contents+en.lrquestion.title) msgid "My internet connection requires an HTTP or SOCKS Proxy" -msgstr "" +msgstr "제 인터넷 연결에 HTTP나 SOCKS 프록시가 요구됩니다." #: https//support.torproject.org/tbb/tbb-47/ #: (content/tbb/tbb-47/contents+en.lrquestion.description) @@ -10628,23 +10628,25 @@ msgid "" "highest legal exposure and risk (and **you should NOT run them from your " "home**)." msgstr "" +"* 중계서버 종류 중 가장 필요한 건 출구 중게서버입니다. 하지만 해당 서버는 가장 큰 법적 노출과 위험을 안고 있기도 합니다. (따라서" +" **절대 귀하의 집에서 출구 중계서버를 돌리면 안 됩니다**)" #: https//support.torproject.org/relay-operators/what-type-of-relays-are-most-needed/ #: (content/relay-operators/what-type-of-relays-are-most-needed/contents+en.lrquestion.description) msgid "" "* If you are looking to run a relay with minimal effort, fast guard relays " "are also very useful" -msgstr "" +msgstr "* 최소한의 노력으로 중계서버를 운영할 방법을 찾고 계시다면, '빠른 가드 중계서버' 또한 유용합니다." #: https//support.torproject.org/relay-operators/what-type-of-relays-are-most-needed/ #: (content/relay-operators/what-type-of-relays-are-most-needed/contents+en.lrquestion.description) msgid "* Followed by bridges." -msgstr "" +msgstr "* 브리지 다음으로" #: https//support.torproject.org/relay-operators/why-i-get-portscanned-more-often/ #: (content/relay-operators/why-i-get-portscanned-more-often/contents+en.lrquestion.title) msgid "Why do I get portscanned more often when I run a Tor relay?" -msgstr "" +msgstr "Tor 중계서버를 운영하고나서 부터 '가상 사서함 서비스'에서의 메일이 더 많이 옵니다. 왜 그런가요?" #: https//support.torproject.org/relay-operators/why-i-get-portscanned-more-often/ #: (content/relay-operators/why-i-get-portscanned-more-often/contents+en.lrquestion.description) @@ -10657,6 +10659,11 @@ msgid "" "from you might attract the attention of other users on the IRC server, " "website, etc. who want to know more about the host they're relaying through." msgstr "" +"귀하가 출구 연결을 허용할 경우, 귀하의 중계서버를 통해 사람들이 접속하는 몇몇 서비스에서 귀하의 정보를 수집하기 위해 연결을 " +"역추적합니다. 예를 들어, IRC 서버에서 귀하의 identd 포트로 역으로 연결해 어떤 사용자가 연결했는지를 기록합니다(Tor에서 " +"사용자 정보를 알 수 없으므로, IRC 서버에서 시도한 해당 방식은 유효하지 않습니다만, 아무튼 시도는 합니다). 또한 귀하의 " +"중계서버를 거쳐 나가는 사용자는 IRC 서버, 웹사이트와 같은 곳에 있는 사용자의 관심을 끌게 됩니다. 그들을 중계해온 호스트가 누군자 " +"알고 싶어 하기 때문입니다." #: https//support.torproject.org/relay-operators/why-i-get-portscanned-more-often/ #: (content/relay-operators/why-i-get-portscanned-more-often/contents+en.lrquestion.description) @@ -10665,6 +10672,8 @@ msgid "" " learned that sometimes Tor relays expose their socks port to the world. We " "recommend that you bind your socksport to local networks only." msgstr "" +"다른 이유는 인터넷에서 개방 프록시를 스캔하는 집단이 Tor 중계서버가 가끔 socks 포트를 대외적으로 노출시킨다는 걸 파악했기 " +"때문입니다. Tor 프로젝트에선 귀하의 socks 포트를 근거리 통신망에서만 바인딩 해두길 권장합니다." #: https//support.torproject.org/relay-operators/why-i-get-portscanned-more-often/ #: (content/relay-operators/why-i-get-portscanned-more-often/contents+en.lrquestion.description)

1 0

[translation/communitytpo-contentspot] new translations in communitytpo-contentspot
by translation＠torproject.org 14 Mar '22

14 Mar '22

commit e22f63a256aa77e8ec431e87437c7ee775628c1c Author: Translation commit bot <translation(a)torproject.org> Date: Mon Mar 14 17:45:10 2022 +0000 new translations in communitytpo-contentspot --- contents+es.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contents+es.po b/contents+es.po index e1ed12029e..e92cd3c19b 100644 --- a/contents+es.po +++ b/contents+es.po @@ -11258,12 +11258,12 @@ msgstr "" #: https//community.torproject.org/training/resources/all-about-tor/ #: (content/training/resources/all-about-tor/contents+en.lrslide.description) msgid "- Do you teach others about Tor?" -msgstr "" +msgstr "- ¿Enseñas a otras personas acerca de Tor?" #: https//community.torproject.org/training/resources/all-about-tor/ #: (content/training/resources/all-about-tor/contents+en.lrslide.title) msgid "Why do we need Tor?" -msgstr "" +msgstr "¿Por qué necesitamos Tor?" #: https//community.torproject.org/training/resources/all-about-tor/ #: (content/training/resources/all-about-tor/contents+en.lrslide.description)

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2022