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

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

15 Jan '22

commit dcc3006d06903371b5f2d4881415360f1ba2f0ca Author: Translation commit bot <translation(a)torproject.org> Date: Sat Jan 15 06:17:34 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 4e97d7018f..7b61bd30e8 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10723,6 +10723,8 @@ msgid "" "relays/2016-September/010173.html) to see how fast tor can get on your " "network/CPU." msgstr "" +"* [透過洋蔥路由執行此測試](https://lists.torproject.org/pipermail/tor-" +"relays/2016-September/010173.html)可以得知，在您的網路環境以及中央處理器上能夠達到多快的速度。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) @@ -10732,16 +10734,18 @@ msgid "" "find out how fast tor can get on your CPU. Keep increasing the data volume " "until the bandwidth stops increasing." msgstr "" +"* " +"在[chutney](https://gitweb.torproject.org/chutney.git/tree/README.md#n105)上以…" #: https//support.torproject.org/relay-operators/why-isnt-my-relay-being-used-more/ #: (content/relay-operators/why-isnt-my-relay-being-used-more/contents+en.lrquestion.title) msgid "Why isn't my relay being used more?" -msgstr "" +msgstr "為什麼我的中繼節點都沒有被使用？" #: https//support.torproject.org/relay-operators/why-isnt-my-relay-being-used-more/ #: (content/relay-operators/why-isnt-my-relay-being-used-more/contents+en.lrquestion.description) msgid "If your relay is relatively new then give it time." -msgstr "" +msgstr "如果是新架設的中繼節點的話，請再等一段時間，" #: https//support.torproject.org/relay-operators/why-isnt-my-relay-being-used-more/ #: (content/relay-operators/why-isnt-my-relay-being-used-more/contents+en.lrquestion.description) @@ -10751,6 +10755,7 @@ msgid "" "capacity and, over time, directs more traffic there until it reaches an " "optimal load." msgstr "" +"洋蔥路由軟體是依據頻寬主管機構廣播的資訊，再利用推估模式來決定要使用哪些中繼節點的，這些主管機構會去量測您的中繼節點的可容載量，然後才會漸漸的將流量導入您的中繼節點，直到它達到最佳負載量為止。" #: https//support.torproject.org/relay-operators/why-isnt-my-relay-being-used-more/ #: (content/relay-operators/why-isnt-my-relay-being-used-more/contents+en.lrquestion.description) @@ -10758,6 +10763,8 @@ msgid "" "The lifecycle of a new relay is explained in more depth in [this blog " "post](https://blog.torproject.org/blog/lifecycle-of-a-new-relay)." msgstr "" +"對於新架設的中繼節點生命週期，在這篇[部落格貼文](https://blog.torproject.org/blog/lifecycle-of-a-" +"new-relay)有較詳細的深入解說。" #: https//support.torproject.org/relay-operators/why-isnt-my-relay-being-used-more/ #: (content/relay-operators/why-isnt-my-relay-being-used-more/contents+en.lrquestion.description) @@ -10766,11 +10773,13 @@ msgid "" "asking on the [tor-relays list](https://lists.torproject.org/cgi-" "bin/mailman/listinfo/tor-relays/)." msgstr "" +"若您的中繼節點已經上線運行一段時間，但是仍然有問題的話，可以試著在[洋蔥路由中繼節點的郵件通訊清單](https://lists.torproject…" +"bin/mailman/listinfo/tor-relays/)尋求協助。" #: https//support.torproject.org/relay-operators/wrong-ip/ #: (content/relay-operators/wrong-ip/contents+en.lrquestion.title) msgid "My relay is picking the wrong IP address." -msgstr "" +msgstr "我的中繼節點選用了錯誤的IP位址。" #: https//support.torproject.org/relay-operators/wrong-ip/ #: (content/relay-operators/wrong-ip/contents+en.lrquestion.description) @@ -10779,6 +10788,7 @@ msgid "" " resolving that hostname. Often people have old entries in their /etc/hosts " "file that point to old IP addresses." msgstr "" +"洋蔥路由軟體猜測自身IP位址的方式，是先查得該電腦本身的主機名稱，再去解析該名稱的位址，有時候是因為主機本身的/etc/hosts設定檔裡仍然記錄舊的IP位址造成的。" #: https//support.torproject.org/relay-operators/wrong-ip/ #: (content/relay-operators/wrong-ip/contents+en.lrquestion.description) @@ -10788,6 +10798,7 @@ msgid "" "only has an internal IP address, see the following Support entry on dynamic " "IP addresses." msgstr "" +"如果這樣還是無法解決問題的話，您就應該要利用「Address」設定選項來直接指定要使用的IP位址，而如果您的電腦是位於NAT網路中，並且只有一個外部IP位址的話，那請依照技術支援說明裡有關動態IP位址的設定。" #: https//support.torproject.org/relay-operators/wrong-ip/ #: (content/relay-operators/wrong-ip/contents+en.lrquestion.description) @@ -10796,11 +10807,12 @@ msgid "" "\"OutboundBindAddress\" so external connections come from the IP you intend " "to present to the world." msgstr "" +"然而，如果您擁有多個位址的話，或許可以調整「OutboundBindAddress」的設定值，這樣可以讓所有外部連線中所暴露出來的IP位址，就是您希望讓外界網路看見的位址。" #: https//support.torproject.org/onionservices/client-auth/ #: (content/onionservices/client-auth/contents+en.lrquestion.title) msgid "What's a client or onion authentication?" -msgstr "" +msgstr "什麼是客戶端或洋蔥認證？" #: https//support.torproject.org/onionservices/client-auth/ #: (content/onionservices/client-auth/contents+en.lrquestion.description) @@ -10808,21 +10820,21 @@ msgid "" "An authenticated onion service is an onion service that requires you to " "provide an authentication token (in this case, a private key) before " "accessing the service." -msgstr "" +msgstr "所謂的認證洋蔥服務是洋蔥服務的一種，它會需要您先提供認證權杖(這裡會是一把私密金鑰)才允許存取其服務，" #: https//support.torproject.org/onionservices/client-auth/ #: (content/onionservices/client-auth/contents+en.lrquestion.description) msgid "" "The private key is not transmitted to the service, and it's only used to " "decrypt its descriptor locally." -msgstr "" +msgstr "這把私密金鑰並不會被傳送到該服務主機中，而是會在本地電腦裡用於解密該服務的描述子。" #: https//support.torproject.org/onionservices/client-auth/ #: (content/onionservices/client-auth/contents+en.lrquestion.description) msgid "" "You can get the access credentials from the onion service operator. Reach " "out to the operator and request access." -msgstr "" +msgstr "您通常需要直接聯繫該洋蔥服務的管理員，才能取得該服務的存取授權。" #: https//support.torproject.org/onionservices/client-auth/ #: (content/onionservices/client-auth/contents+en.lrquestion.description)

1 0

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

15 Jan '22

commit 56eeba5f6069182adee539a136269e9cfced5e8a Author: Translation commit bot <translation(a)torproject.org> Date: Sat Jan 15 05:47:37 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 53 ++++++++++++++++++++++++++++++----------------------- 1 file changed, 30 insertions(+), 23 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 426bc1bd6f..4e97d7018f 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10555,46 +10555,46 @@ msgstr "* 請確認中繼節點主機的記憶體、中央處理器、網路接 msgid "" "Tor logs some of these when it starts. Others can be viewed using top or " "similar tools." -msgstr "" +msgstr "這些資訊有些在洋蔥路由啟動時會被記錄於歷程記錄中，另外有些資訊則可利用像是top之類的工具軟體查得。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "#### Provider Limits" -msgstr "" +msgstr "#### 網路服務供應商的限制" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "* Check the Internet peering (bandwidth, latency) from your relay's provider" " to other relays." -msgstr "" +msgstr "* 確認您的中繼節點通往其他節點的網路連線(頻寬與延遲率)。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "Relays transiting via Comcast have been slow at times." -msgstr "" +msgstr "有時候中繼節點透過Comcast公司的網路傳輸會較慢，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "Relays outside North America and Western Europe are usually slower." -msgstr "" +msgstr "位處於北美洲或西歐地區以外的中繼節點也通常會比較慢。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "#### Tor Network Limits" -msgstr "" +msgstr "#### 洋蔥路由網路限制" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Relay bandwidth can be limited by a relay's own observed bandwidth, or by " "the directory authorities' measured bandwidth." -msgstr "" +msgstr "中繼節點的頻寬會受到節點主機本身觀測到的頻寬，或是目錄主管機構的量測值所限制。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "Here's how to find out which measurement is limiting your relay:" -msgstr "" +msgstr "底下方式可以查出到底是哪個量測值限制造成的：" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) @@ -10603,46 +10603,48 @@ msgid "" "page)](https://consensus-health.torproject.org/consensus-health.html) and " "check the median." msgstr "" +"* 查閱[consensus-health(超大網頁)](https://consensus-" +"health.torproject.org/consensus-health.html)上各個節點針對您的中繼節點所作的投票結果，尤其是它們的平均值。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "If your relay is not marked Running by some directory authorities:" -msgstr "" +msgstr "如果您的中繼節點被部份目錄主管機構標記為停機狀態的話：" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "* Does it have the wrong IPv4 or IPv6 address?" -msgstr "" +msgstr "* 請確認IPv4或IPv6的位址是否設定錯誤？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "* Is its IPv4 or IPv6 address unreachable from some networks?" -msgstr "" +msgstr "* 它的IPv4或IPv6位址是否無法由某些地區的網路存取到？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "* Are there more than 2 relays on its IPv4 address?" -msgstr "" +msgstr "* 是否有多臺中繼節點使用同一個IPv4位址？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Otherwise, check your relay's observed bandwidth and bandwidth rate (limit)." -msgstr "" +msgstr "或者是確認您的中繼節點所觀測到的頻寬與速率(限制)。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Look up your relay on " "[Metrics](https://metrics.torproject.org/rs.html#search/)." -msgstr "" +msgstr "到[Metrics](https://metrics.torproject.org/rs.html#search/)查詢您的中繼節點，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Then mouse over the bandwidth heading to see the observed bandwidth and " "relay bandwidth rate." -msgstr "" +msgstr "將滑鼠游標移至頻寬標頭，可以得知中繼節點觀測到的頻寬值與資料傳輸率。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) @@ -10653,18 +10655,21 @@ msgid "" "relay](https://lists.torproject.org/pipermail/tor-" "relays/2016-October/010784.html)." msgstr "" +"這裡有幾個比較細節的範例可參考：[共識權重下降](https://lists.torproject.org/pipermail/tor-" +"relays/2016-November/010913.html)以及[出口節點速率提昇](https://lists.torproject.org/…" +"relays/2016-October/010784.html)。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "#### How to fix it" -msgstr "" +msgstr "#### 要如何解決" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "The smallest of these figures is limiting the bandwidth allocated to the " "relay." -msgstr "" +msgstr "此圖表中的最小數值會限制該中繼節點被配得的頻寬。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) @@ -10672,42 +10677,44 @@ msgid "" "* If it's the bandwidth rate, increase the BandwidthRate/Burst or " "RelayBandwidthRate/Burst in your torrc." msgstr "" +"* " +"如果是頻寬資料傳輸率造成的話，那可以增加您的torrc設定檔裡有關BandwidthRate、Burst或RelayBandwidthRate、Burst的相關設定值。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "* If it's the observed bandwidth, your relay won't ask for more bandwidth " "until it sees itself getting faster." -msgstr "" +msgstr "* 如果是受觀測到的頻寬限制的話，那除非中繼節點軟體的觀測值提昇，否則它是不會調昇頻寬限制量的，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "You need to work out why it is slow." -msgstr "" +msgstr "此時您就必須要更深入追查此值低落的原因。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "* If it's the median measured bandwidth, your relay looks slow from a " "majority of bandwidth authorities." -msgstr "" +msgstr "* 如果是量測頻寬的平均值偏低的話，那就表示您的中繼節點通往大部分的頻寬主管機構主機的連線較慢所導致，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "You need to work out why they measure it slow." -msgstr "" +msgstr "此時您就必須要更深入追查量測值低落的原因。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "### Doing Your Own Relay Measurements" -msgstr "" +msgstr "### 對中繼節點做自我量測" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "If your relay thinks it is slow, or the bandwidth authorities think it is " "slow, you can test the bandwidth yourself:" -msgstr "" +msgstr "如果您的中繼節點軟體判定自己的速度較慢，或是被頻寬主管機構主機認定較慢的話，您可以用這種方式自行量測自己的頻寬值：" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description)

1 0

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

15 Jan '22

commit 45afdc50cbe0564860ee6e9a8c2adfd9ad30d47b Author: Translation commit bot <translation(a)torproject.org> Date: Sat Jan 15 05:17:28 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 52 +++++++++++++++++++++++++++------------------------- 1 file changed, 27 insertions(+), 25 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 0ca9c5c18c..426bc1bd6f 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10392,6 +10392,7 @@ 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 "" +"另一個可能的原因是，有些專門掃描尋找開放代理伺服器的人會發現，有些洋蔥路由中繼節點會將Socks連接埠暴露在網路上，我們建議您將您的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) @@ -10401,152 +10402,153 @@ msgid "" "relays](https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/Securit…" " for more suggestions." msgstr "" +"不論無何，您都應該要隨時關注自身的安全，請參閱[洋蔥路由中繼節點安全性](https://trac.torproject.org/projects/t…" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.title) msgid "My relay is slow, how can I fix it?" -msgstr "" +msgstr "我的中繼節點速度很慢，該如何解決？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "### Why Relay Load Varies" -msgstr "" +msgstr "### 為什麼中繼節點的負載量差異會很大" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Tor manages bandwidth across the entire network. It does a reasonable job " "for most relays." -msgstr "" +msgstr "洋蔥路由會管理調節整個網路上的頻寬用量，它的現行策略對於大多數的中繼節點來說，都可以運作良好。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "But Tor's goals are different to protocols like BitTorrent." -msgstr "" +msgstr "然而，洋蔥路由的目標與其他像是位元洪流之類的通訊協定不同，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Tor wants low-latency web pages, which requires fast connections with " "headroom." -msgstr "" +msgstr "洋蔥路由的主要目標是提供低延遲率的網頁載入服務，因此會需要預留頻寬以提昇連線速率，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "BitTorrent wants bulk downloads, which requires using all the bandwidth." -msgstr "" +msgstr "而位元洪流的目標是提供整批下載服務，因此就會盡可能的耗盡所有可用頻寬。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "We're working on a [new bandwidth scanner](https://sbws.readthedocs.io/), " "which is easier to understand and maintain." -msgstr "" +msgstr "我們目前正在開發一個[新的頻寬掃描器](https://sbws.readthedocs.io/)，以使這個部份更容易理解與維護，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "It will have diagnostics for relays that don't get measured, and relays that" " have low measurements." -msgstr "" +msgstr "它會針對未被量測或是量測率偏低的中繼節點進行診斷。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "### Why does Tor need bandwidth scanners?" -msgstr "" +msgstr "### 為什麼洋蔥路由會需要頻寬掃描器？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "Most providers tell you the maximum speed of your local connection." -msgstr "" +msgstr "大多數的網路服務供應商會告知您網路的最大速率，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "But Tor has users all over the world, and our users connect to one or two " "Guard relays at random." -msgstr "" +msgstr "但是洋蔥路由的使用者是來自世界各地，並且他們每次都會以隨機的方式選定一兩個護衛節點來連線。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "So we need to know how well each relay can connect to the entire world." -msgstr "" +msgstr "因此，我們必須要知道每個中繼節點實際上與全世界的網路連通速度是如何，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "So even if all relay operators set their advertised bandwidth to their local" -msgstr "" +msgstr "所以即使所有的中繼節點架設者都誠實的廣播它們本地端的網路頻寬" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "connection speed, we would still need bandwidth authorities to balance the " "load" -msgstr "" +msgstr "連線速度，我們仍然還是需要頻寬主管機構來調控與平衡整體負載量，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "between different parts of the Internet." -msgstr "" +msgstr "特別是針對不同區域的網路空間。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "### What is a normal relay load?" -msgstr "" +msgstr "### 正常的中繼節點負載量是多少？" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "It's normal for most relays to be loaded at 30%-80% of their capacity." -msgstr "" +msgstr "正常的中繼節點負載量是可用容載量的30%-80%，" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "This is good for clients: an overloaded relay has high latency." -msgstr "" +msgstr "這樣對於使用者來說是最佳狀態，因為負荷超載的中繼節點其延遲率會偏高。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "(We want enough relays to so that each relay is loaded at 10%. Then Tor " "would be almost as fast as the wider Internet)." -msgstr "" +msgstr "(我們的期望是能夠擁有足夠的中繼節點，以便讓每個節點的平均負載量都落在10%左右，這樣洋蔥路由的網路速度就會幾乎跟普通網際網路一樣快)" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Sometimes, a relay is slow because its processor is slow or its connections " "are limited." -msgstr "" +msgstr "有些時候，中繼節點速度降慢的原因，是因為中央處理器效能不足或是網路連線受到限制。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "" "Other times, it is the network that is slow: the relay has bad peering to " "most other tor relays, or is a long distance away." -msgstr "" +msgstr "也有些時候是因為網路速度太慢造成的，例如說該中繼節點與其他節點間的連線有瓶頸，或是位處於較遙遠的地段。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "### Finding Out what is Limiting a Relay" -msgstr "" +msgstr "### 找出中繼節點速度緩慢的原因" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "Lots of things can slow down a relay. Here's how to track them down." -msgstr "" +msgstr "造成中繼節點速度緩慢的可能原因有很多，底下逐一說明追查的方式。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "#### System Limits" -msgstr "" +msgstr "#### 系統限制" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description) msgid "* Check RAM, CPU, and socket/file descriptor usage on your relay" -msgstr "" +msgstr "* 請確認中繼節點主機的記憶體、中央處理器、網路接套以及檔案描述子的使用量。" #: https//support.torproject.org/relay-operators/why-is-my-relay-slow/ #: (content/relay-operators/why-is-my-relay-slow/contents+en.lrquestion.description)

1 0

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

15 Jan '22

commit 4a94f9c1992ecfd32ec071975492c1d5eb2b8e87 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Jan 15 04:47:16 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 18e66bd6f7..0ca9c5c18c 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10319,7 +10319,7 @@ msgstr "您必須要把這兩把金鑰都備份起來，以便在遷移或重建 #: https//support.torproject.org/relay-operators/what-is-the-bad-exit-flag/ #: (content/relay-operators/what-is-the-bad-exit-flag/contents+en.lrquestion.title) msgid "What is the BadExit flag?" -msgstr "" +msgstr "BadExit旗標是什麼意思？" #: https//support.torproject.org/relay-operators/what-is-the-bad-exit-flag/ #: (content/relay-operators/what-is-the-bad-exit-flag/contents+en.lrquestion.description) @@ -10328,6 +10328,7 @@ msgid "" "This tells Tor to avoid exiting through that relay. In effect, relays with " "this flag become non-exits." msgstr "" +"當出口節點的設定錯誤，或者是屬於惡意人士架設的主機，它就會被標記上BadExit的旗標，因此可以防止洋蔥路由程式將該它作為迴路的出口節點來使用，實際上來說，中繼節點只要被標記上這個旗標，就等於是變成非出口節點。" #: https//support.torproject.org/relay-operators/what-is-the-bad-exit-flag/ #: (content/relay-operators/what-is-the-bad-exit-flag/contents+en.lrquestion.description) @@ -10338,11 +10339,13 @@ msgid "" "team](https://community.torproject.org/relay/community-resources/bad-" "relays/) so we can sort out the issue." msgstr "" +"如果我們發現您的出口節點有問題，或者是當網路流量通過您的節點時有可疑的現象，但是又無法跟您取得聯繫以釐清問題時，就會把您的節點標上此旗標。因此請您直接…" +"resources/bad-relays/)聯絡，以便解決此問題。" #: 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.title) msgid "What type of relays are most needed?" -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) @@ -10350,24 +10353,24 @@ msgid "" "* The exit relay is the most needed relay type but it also comes with the " "highest legal exposure and risk (and **you should NOT run them from your " "home**)." -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 "" "* 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 "為什麼我架設洋蔥路由中繼節點後，常常遭受到連接埠號掃描活動？" #: 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) @@ -10380,6 +10383,7 @@ 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連接埠以記錄哪個使用者已建立連線。(這種行為對它們來說其實沒有用，因為洋蔥路由並不會揭露這些資訊，但是它們的服務還是會嘗試。)還有一種可能的情況是，當使用者透過您的節點連上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)

1 0

[bridgedb/main] Bring back the bridges per distributor metrics
by meskio＠torproject.org 14 Jan '22

14 Jan '22

commit 65f6e392eb38affc1617de59cc72791217984301 Author: meskio <meskio(a)torproject.org> Date: Mon Dec 13 10:16:16 2021 +0100 Bring back the bridges per distributor metrics The right place to do that will be rdsys, but let's keep the metrics as well in bridgedb so the migration for the metrics team is more smooth. With the migration to rdsys we loose the metrics of the unasigned bridges and any distributor not managed by bridgedb. Related: rdsys#67 --- bridgedb/metrics.py | 21 +++++++++++++++++++++ bridgedb/rdsys.py | 17 ++++++++++++++--- 2 files changed, 35 insertions(+), 3 deletions(-) diff --git a/bridgedb/metrics.py b/bridgedb/metrics.py index c56b945..7751e94 100644 --- a/bridgedb/metrics.py +++ b/bridgedb/metrics.py @@ -422,6 +422,27 @@ class InternalMetrics(Metrics): self.set("{}.lower-whisker".format(handoutsPrefix), lowerWhisker) self.set("{}.upper-whisker".format(handoutsPrefix), upperWhisker) + def recordBridgesInHashring(self, ringName, subRingName, numBridges): + """ + Record the number of bridges per hashring. + + :param str ringName: The name of the ring, e.g., "https". + :param str subRingName: The name of the subring, e.g., + "byIPv6-bySubring1of4". + :param int numBridges: The number of bridges in the given subring. + """ + + if not ringName or not subRingName: + logging.warning("Ring name ({}) and subring name ({}) cannot be " + "empty.".format(ringName, subRingName)) + return + + logging.info("Recording metrics for bridge (sub)rings: %s/%s/%d." % + (ringName, subRingName, numBridges)) + # E.g, concatenate "https" with "byipv6-bysubring1of4". + key = "{}.{}.{}".format(self.keyPrefix, ringName, subRingName.lower()) + self.set(key, numBridges) + class HTTPSMetrics(Metrics): diff --git a/bridgedb/rdsys.py b/bridgedb/rdsys.py index f90cf54..56fcc4c 100644 --- a/bridgedb/rdsys.py +++ b/bridgedb/rdsys.py @@ -1,5 +1,4 @@ import json -import secrets import logging from io import BytesIO from twisted.internet import reactor @@ -8,6 +7,7 @@ from twisted.internet.protocol import Protocol from twisted.web.client import Agent, FileBodyProducer from twisted.web.http_headers import Headers +from bridgedb import metrics from bridgedb.bridges import Bridge, MalformedBridgeInfo @@ -15,13 +15,15 @@ inter_message_delimiter = b"\r" class RdsysProtocol(Protocol): - def __init__(self, finished, hashring): + def __init__(self, finished, hashring, distributor): """ :type hashring: :class:`bridgedb.bridgerings.FilteredBridgeSplitter` """ self.finished = finished self.hashring = hashring + self.distributor = distributor self.buff = b"" + self.metrix = metrics.InternalMetrics() def dataReceived(self, data): """ @@ -40,6 +42,7 @@ class RdsysProtocol(Protocol): self.buff += parts[0] for part in parts[1:]: self._updateResources() + self._updateMetrics() self.buff = part def _updateResources(self): @@ -64,6 +67,14 @@ class RdsysProtocol(Protocol): logging.warning("Got a malformed bridge: %s" % e) fn(bridge) + def _updateMetrics(self): + filterRings = self.hashring.filterRings + for (ringName, (_, subring)) in filterRings.items(): + subRingName = "-".join(self.hashring.extractFilterNames(ringName)) + self.metrix.recordBridgesInHashring(self.distributor, + subRingName, + len(subring)) + def connectionLost(self, reason): logging.info("Connection lost with rdsys backend: %s" % reason) self.finished.callback(None) @@ -86,7 +97,7 @@ def start_stream(distributor, token, rdsys_address, hashring): def cbResponse(r): finished = Deferred() - r.deliverBody(RdsysProtocol(finished, hashring)) + r.deliverBody(RdsysProtocol(finished, hashring, distributor)) return finished def connect():

1 0

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

14 Jan '22

commit 401194c0a5ed3faef75afa0fd91495ca14ae1ee4 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 14 17:47:39 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 01de4aff0a..18e66bd6f7 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10307,13 +10307,14 @@ msgid "" "file: keys/ed25519_master_id_secret_key) and a RSA identity (identity key " "file: keys/secret_id_key)." msgstr "" +"在全面替換完成之前，每個中繼節點都會同時擁有ed25519識別金鑰(金鑰檔：keys/ed25519_master_id_secret_key)以及RSA識別金鑰(金鑰檔：keys/secret_id_key)，" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) msgid "" "You need to copy / backup both of them in order to restore your relay, " "change your DataDirectory or migrate the relay on a new computer." -msgstr "" +msgstr "您必須要把這兩把金鑰都備份起來，以便在遷移或重建中繼節點時可繼續沿用。" #: https//support.torproject.org/relay-operators/what-is-the-bad-exit-flag/ #: (content/relay-operators/what-is-the-bad-exit-flag/contents+en.lrquestion.title)

1 0

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

14 Jan '22

commit b302ef65fafa96118b9ba781fd0b2d2a7cab613e Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 14 17:17:38 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 32 +++++++++++++++++++++++--------- 1 file changed, 23 insertions(+), 9 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 4a2f18e5a9..01de4aff0a 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10154,7 +10154,7 @@ msgstr "若您有開啟DirPort旗標的話，那洋蔥路由客戶端程式就 msgid "" "The request they make (an HTTP GET) is quite small, and the response is " "sometimes quite large." -msgstr "這種索取目錄的請求(HTTP GET)資料量都很少，但須回覆的資料量則通常相對龐大，" +msgstr "這種索取目錄的請求(HTTP GET)資料量都很少，但須回覆的資料量則相對龐大，" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) @@ -10176,12 +10176,12 @@ msgstr "" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.title) msgid "How do I run a relay in Windows?" -msgstr "" +msgstr "如何在Windows系統中架設中繼節點？" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.description) msgid "You can run a relay in Windows following this tutorials:" -msgstr "" +msgstr "您可以依照下面這份教學，在Windows系統中架設中繼節點：" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.description) @@ -10190,6 +10190,9 @@ msgid "" "of-relays/#guard-and-middle-relay) in Windows, please read: " "<https://community.torproject.org/relay/setup/guard/windows/>" msgstr "" +"- 若要在Windows系統中架設[護衛節點](https://community.torproject.org/relay/types-of-" +"relays/#guard-and-middle-" +"relay)的話，請參閱：<https://community.torproject.org/relay/setup/guard/windows/>" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.description) @@ -10198,11 +10201,13 @@ msgid "" "of-relays/#bridge) in Windows, please read: " "<https://community.torproject.org/relay/setup/bridge/windows/>" msgstr "" +"- 若要在Windows系統中架設[橋接中繼站](https://community.torproject.org/relay/types-of-" +"relays/#bridge)的話，請參閱：<https://community.torproject.org/relay/setup/bridge/windows/>" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.description) msgid "You should **only run a Windows relay if you can run it 24/7**." -msgstr "" +msgstr "**只有在您能夠讓它24/7不停運行的情況下，再來架設Windows中繼節點**，" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.description) @@ -10211,11 +10216,12 @@ msgid "" "[Snowflake](https://snowflake.torproject.org/) is a better way to contribute" " your resources to the Tor network." msgstr "" +"若您無法保證做到的話，使用[Snowflake](https://snowflake.torproject.org/)會是一個貢獻洋蔥路由網路的較好方…" #: https//support.torproject.org/relay-operators/should-i-run-a-relay/ #: (content/relay-operators/should-i-run-a-relay/contents+en.lrquestion.title) msgid "How do I decide if I should run a relay?" -msgstr "" +msgstr "我該如何決定是否要架設中繼節點？" #: https//support.torproject.org/relay-operators/should-i-run-a-relay/ #: (content/relay-operators/should-i-run-a-relay/contents+en.lrquestion.description) @@ -10225,6 +10231,8 @@ msgid "" " please consider [running a Tor " "relay](https://community.torproject.org/relay/)." msgstr "" +"我們希望的是能夠擁有相對穩定的網路連線品質，且其上行與下行的頻寬分別都至少有10 Mbit/s " +"(Mbps)以上，若您擁有這樣的網路環境的話，請考慮[架設洋蔥路由中繼節點](https://community.torproject.org/rela…" #: https//support.torproject.org/relay-operators/should-i-run-a-relay/ #: (content/relay-operators/should-i-run-a-relay/contents+en.lrquestion.description) @@ -10234,11 +10242,14 @@ msgid "" "support](https://community.torproject.org/relay/setup/bridge). In that case " "you should have at least 1 MBit/s of available bandwidth." msgstr "" +"即使您的網路可用頻寬不到10 " +"Mbit/s，也仍然可以架設[支援Obfs4的洋蔥路由橋接中繼站](https://community.torproject.org/relay/se…" +" MBit/s以上的頻寬即可。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.title) msgid "I want to upgrade/move my relay. How do I keep the same key?" -msgstr "" +msgstr "若需要升級或遷移我的中繼節點主機，我要如何繼續沿用相同的金鑰？" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) @@ -10248,6 +10259,7 @@ msgid "" "\"keys/ed25519_master_id_secret_key\" and \"keys/secret_id_key\" in your " "DataDirectory)." msgstr "" +"當要將洋蔥路由中繼節點主機升級，或者是遷移至不同的電腦上時，維持使用同樣的識別金鑰是非常重要的(位於您的DataDirectory裡的「keys/ed25519_master_id_secret_key」以及「keys/secret_id_key」)。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) @@ -10255,7 +10267,7 @@ msgid "" "Keeping backups of the identity keys so you can restore a relay in the " "future is the recommended way to ensure the reputation of the relay won't be" " wasted." -msgstr "" +msgstr "藉由將識別金鑰備份，可讓未來要重新架設中繼節點時，確保先前所經營累計的聲譽值不會消失，" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) @@ -10264,6 +10276,7 @@ msgid "" "torrc and the same DataDirectory, then the upgrade should just work and your" " relay will keep using the same key." msgstr "" +"意思就是說，如果您在升級洋蔥路由中繼節點時有保留其torrc設定檔以及DataDirectory目錄的話，那升級後應該還是可以繼續使用相同的金鑰。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) @@ -10271,20 +10284,21 @@ msgid "" "If you need to pick a new DataDirectory, be sure to copy your old " "keys/ed25519_master_id_secret_key and keys/secret_id_key over." msgstr "" +"如果您需要置換一個新的DataDirectory目錄的話，請確認有先將舊目錄中的「keys/ed25519_master_id_secret_key」以及「keys/secret_id_key」兩個檔案複製過去。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) msgid "" "Note: As of Tor 0.2.7 we are using new generation identities for relays " "based on ed25519 elliptic curve cryptography." -msgstr "" +msgstr "注意：從洋蔥路由第0.2.7版開始，我們改用新一代的中繼節點身份識別，它是以ed25519橢圓曲線為基礎的密碼學金鑰。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description) msgid "" "Eventually they will replace the old RSA identities, but that will happen in" " time, to ensure compatibility with older versions." -msgstr "" +msgstr "最終目標是要全部替換掉RSA識別金鑰，但為了保持相容性，這會有一個轉移過渡時期。" #: https//support.torproject.org/relay-operators/upgrade-or-move/ #: (content/relay-operators/upgrade-or-move/contents+en.lrquestion.description)

1 0

[tor-browser-spec/master] Merge remote-tracking branch 'gitlab-tpo/merge-requests/15'
by boklm＠torproject.org 14 Jan '22

14 Jan '22

commit e4f44d36b4118edaed5bd2158864289549ee4a90 Merge: 67f8b30 4663f9b Author: Nicolas Vigier <boklm(a)torproject.org> Date: Fri Jan 14 18:02:20 2022 +0100 Merge remote-tracking branch 'gitlab-tpo/merge-requests/15' processes/ReleaseProcess | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-)

1 0

[tor-browser-spec/master] Bug 40009: Update signing process documentation
by boklm＠torproject.org 14 Jan '22

14 Jan '22

commit 4663f9bfc956e43ff2153e69a7b4996f9e53b5dc Author: Matthew Finkel <sysrqb(a)torproject.org> Date: Tue Nov 17 03:24:20 2020 +0000 Bug 40009: Update signing process documentation --- processes/ReleaseProcess | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-) diff --git a/processes/ReleaseProcess b/processes/ReleaseProcess index 563f263..3dee1e9 100644 --- a/processes/ReleaseProcess +++ b/processes/ReleaseProcess @@ -50,28 +50,41 @@ # For stable releases put tails-dev(a)boum.org into Cc. #. Codesign the macOS dmg files. - # XXX: Update with Notarization bits once they are included in our signing # setup torsocks ssh mac-signer "mkdir $TORBROWSER_VERSION" torsocks rsync -avP $TORBROWSER_BUILDDIR/*.dmg mac-signer:$TORBROWSER_VERSION/ torsocks ssh mac-signer # Unlock the keychain and then... cd $TORBROWSER_VERSION + # Enable networking + networksetup -setsecurewebproxystate Ethernet on # Sign the bundles. ../gatekeeper-signing.sh $TORBROWSER_VERSION + # notarize and staple + ../notarization.sh $TORBROWSER_VERSION + ../stapler.sh $TORBROWSER_VERSION # Check that it worked. - tar xf torbrowser-$TORBROWSER_VERSION-osx_zh-CN-signed.tar.bz2 - spctl -a -t exec -vv TorBrowser.app/ - rm -rf TorBrowser.app + unzip -d test tb-$TORBROWSER_VERSION-osx_zh-CN-stapled.zip + pushd test + # Both should be "Tor Browser.app: Accepted" with "source=Notarized Developer ID" + spctl -vvvv --assess --type=exec --context context:primary-signature Tor\ Browser.app/ + spctl -vvvv --assess --type=open --context context:primary-signature Tor\ Browser.app/ + popd + rm -rf test + # Disable networking + networksetup -setsocksfirewallproxystate Ethernet off exit - torsocks rsync -avP mac-signer:$TORBROWSER_VERSION/*.bz2 . + torsocks rsync -avP mac-signer:$TORBROWSER_VERSION/tb-*-stapled.zip /path/to/builddir/$TORBROWSER_VERSION/ + + cp -rT tor-browser-build/projects/tor-browser/Bundle-Data/mac-applications.dmg dmg #. Regenerate macOS MAR files from code signed dmg files. # XXX Go to your directory prepared for recreating the .dmg files and containing - # the uploaded .bz2 files. + # the uploaded .zip files. ./gatekeeper-bundling.sh $TORBROWSER_VERSION - rsync -avP *.dmg $TORBROWSER_BUILDDIR/ + rsync -avP ../$TORBROWSER_VERSION-signed/*.dmg $TORBROWSER_BUILDDIR/ cd tor-browser-build + mv $TORBROWSER_BUILDDIR/ release/signed/ (or alpha) # The code signed dmg files should be in the $TORBROWSER_VERSION directory # Install a recent p7zip version (see ../tools/dmg2mar for instructions) make dmg2mar-release # or `make dmg2mar-alpha` @@ -107,13 +120,14 @@ export OSSLSIGNCODE=/path/to/osslsigncode /path/to/authenticode-timestamping.sh # Hashes of the signed bundles - ../tools/hash_signed_bundles.sh + ../../../tools/hash_signed_bundles.sh # All the GPG signatures at last torsocks rsync -avP $TORBROWSER_BUILDDIR/* signing-machine:tor-browser-bundle/gitian/$TORBROWSER_VERSION/ cd tor-browser-bundle/gitian/$TORBROWSER_VERSION /path/to/tbb-signing.sh exit torsocks rsync -avP signing-machine:tor-browser-bundle/gitian/$TORBROWSER_VERSION/ $TORBROWSER_BUILDDIR + # Fetch signatures on unsigned sha256sums from other builds #. Sync to people.torproject.org torsocks rsync -avP $TORBROWSER_BUILDDIR/ people.torproject.org:public_html/builds/$TORBROWSER_BUILDDIR

1 0

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

14 Jan '22

commit fdae1f2c3bb611e3560ffe536420bce3459f63b0 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 14 16:47:41 2022 +0000 new translations in support-portal --- contents+zh-TW.po | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/contents+zh-TW.po b/contents+zh-TW.po index 49762bb8f4..4a2f18e5a9 100644 --- a/contents+zh-TW.po +++ b/contents+zh-TW.po @@ -10044,21 +10044,21 @@ msgstr "為什麼我的洋蔥路由中繼節點的記憶體使用量這麼高？ msgid "" "If your Tor relay is using more memory than you'd like, here are some tips " "for reducing its footprint:" -msgstr "" +msgstr "如果您的洋蔥路由中繼節點使用的記憶體超過您的預期，可以嘗試以下方式來降低該使用率：" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "" "* If you're on Linux, you may be encountering memory fragmentation bugs in " "glibc's malloc implementation." -msgstr "" +msgstr "* 如果您是使用Linux系統的話，有可能是遭遇到了在Glibc的malloc函式裡的記憶體碎裂臭蟲。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "" "That is, when Tor releases memory back to the system, the pieces of memory " "are fragmented so they're hard to reuse." -msgstr "" +msgstr "也就是說，當洋蔥路由程式將記憶體釋放回作業系統後，出現破碎的記憶體空間，故難以被再度利用。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) @@ -10066,6 +10066,7 @@ msgid "" "The Tor tarball ships with OpenBSD's malloc implementation, which doesn't " "have as many fragmentation bugs (but the tradeoff is higher CPU load)." msgstr "" +"目前洋蔥路由的tarball套件包裡有預載OpenBSD版本的malloc函式，此版本的函式較少發生記憶體碎裂的問題(但是代價就是中央處理器的使用率會比較高)，" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) @@ -10073,6 +10074,7 @@ msgid "" "You can tell Tor to use this malloc implementation instead: `./configure " "--enable-openbsd-malloc`." msgstr "" +"您可以透過這個設定，來要求洋蔥路由程式使用此版本的malloc函式：`./configure --enable-openbsd-malloc`" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) @@ -10081,6 +10083,8 @@ msgid "" "open, you are probably losing a lot of memory to OpenSSL's internal buffers " "(38KB+ per socket)." msgstr "" +"* " +"若您架設的是較高速的中繼節點的話，那就會有很多條TLS的連線同時開通，此時OpenSSL的內部緩衝區就會佔用掉大量的記憶體空間(每個網路接套約須38KB的空間)。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) @@ -10089,44 +10093,46 @@ msgid "" "aggressively](https://lists.torproject.org/pipermail/tor-" "dev/2008-June/001519.html)." msgstr "" +"我們已有特別針對OpenSSL程式進行修補過，讓它會[更積極的釋放出緩衝區記憶體空間](https://lists.torproject.org/pi…" +"dev/2008-June/001519.html)。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "" "If you update to OpenSSL 1.0.0 or newer, Tor's build process will " "automatically recognize and use this feature." -msgstr "" +msgstr "若您把OpenSSL更新到1.0.0或更新的版本，洋蔥路由行程就會自動識別並且啟用該功能。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "" "* If you still can't handle the memory load, consider reducing the amount of" " bandwidth your relay advertises." -msgstr "" +msgstr "* 如果您還是無法控制記憶體使用量的話，可以考慮調降中繼節點的額定頻寬。" #: https//support.torproject.org/relay-operators/relay-memory/ #: (content/relay-operators/relay-memory/contents+en.lrquestion.description) msgid "" "Advertising less bandwidth means you will attract fewer users, so your relay" " shouldn't grow as large." -msgstr "" +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) msgid "" "All of this said, fast Tor relays do use a lot of ram. It is not unusual for" " a fast exit relay to use 500-1000 MB of memory." -msgstr "" +msgstr "總而言之，高速的洋蔥路由中繼節點通常都會使用較多的主記憶體空間，因此它在運行狀態中佔用掉500-1000MB的記憶體空間是很常見的現象。" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.title) msgid "Why does my relay write more bytes onto the network than it reads?" -msgstr "" +msgstr "為什麼我的中繼節點在網路上傳送了比實際需求量還要多的位元組數？" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) @@ -10134,27 +10140,28 @@ msgid "" "You're right, for the most part a byte into your Tor relay means a byte out," " and vice versa. But there are a few exceptions:" msgstr "" +"您的觀念並沒有錯，在大多數的情況下，當有一個位元組的資料流進您的洋蔥路由中繼節點，就代表也會有一個位元組的資料流出，反之也是亦然，但是仍會有少數幾個例外情況：" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) msgid "" "If you open your DirPort, then Tor clients will ask you for a copy of the " "directory." -msgstr "" +msgstr "若您有開啟DirPort旗標的話，那洋蔥路由客戶端程式就會對您的主機索取目錄清單資料，" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) msgid "" "The request they make (an HTTP GET) is quite small, and the response is " "sometimes quite large." -msgstr "" +msgstr "這種索取目錄的請求(HTTP GET)資料量都很少，但須回覆的資料量則通常相對龐大，" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) msgid "" "This probably accounts for most of the difference between your \"write\" " "byte count and your \"read\" byte count." -msgstr "" +msgstr "通常這就是讓您的主機對網路「寫入」與「讀取」資料量會有差異的主要原因。" #: https//support.torproject.org/relay-operators/relay-write-more-bytes/ #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description) @@ -10164,6 +10171,7 @@ msgid "" "or ssh connection) and wrap it up into an entire 512 byte cell for transport" " through the Tor network." msgstr "" +"另一個小例外則是當您架設的是出口節點時，您的主機會從連線出口端(例如即時通訊軟體或SSH連線)接收少量的位元組資料，再將之組裝成512位元組的資料包後，送入洋蔥路由網路中。" #: https//support.torproject.org/relay-operators/run-relay-in-windows/ #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.title)

1 0