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

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 20 May '18

20 May '18

commit d6de69cfd0adb15647ffbd9082be1589c10096a5 Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 20 11:15:31 2018 +0000 Update translations for https_everywhere --- ar/https-everywhere.dtd | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/ar/https-everywhere.dtd b/ar/https-everywhere.dtd index 33c910a67..2eece7ce5 100644 --- a/ar/https-everywhere.dtd +++ b/ar/https-everywhere.dtd @@ -2,39 +2,39 @@ <!ENTITY https-everywhere.about.ext_name "HTTPS Everywhere"> <!ENTITY https-everywhere.about.ext_description "شفر شبكة الإنترنت! استخدم تلقائيا تقنية HTTPS للأمان مع الكثير من المواقع."> <!ENTITY https-everywhere.about.version "النسخة"> -<!ENTITY https-everywhere.about.rulesets_version "Rulesets version for"> -<!ENTITY https-everywhere.about.add_new_rule "اضافة قانون جديد"> +<!ENTITY https-everywhere.about.rulesets_version "إصدارة مجموعة قواعد"> +<!ENTITY https-everywhere.about.add_new_rule "أضف قاعدة جديدة"> <!ENTITY https-everywhere.menu.donate_eff_imperative "تبرع لإي إف إف "> <!ENTITY https-everywhere.menu.observatory "خيارات مرصد SSL"> <!ENTITY https-everywhere.menu.globalEnable "فعّل HTTPS Everywhere"> -<!ENTITY https-everywhere.menu.blockUnencryptedRequests "منع جميع الطلبات الغير مشفرة"> +<!ENTITY https-everywhere.menu.blockUnencryptedRequests "احجب جميع الطلبات غير المشفرة"> <!ENTITY https-everywhere.menu.showCounter "أظهر العداد"> <!ENTITY https-everywhere.menu.viewAllRules "عرض جميع القواعد"> -<!ENTITY https-everywhere.options.generalSettings "الإعدادات العامّة"> +<!ENTITY https-everywhere.options.generalSettings "إعدادات عامّة"> <!ENTITY https-everywhere.options.advancedSettings "إعدادات متقدمة "> -<!ENTITY https-everywhere.options.importSettings "استيراد اﻹعدادات"> -<!ENTITY https-everywhere.options.import "إستيراد"> -<!ENTITY https-everywhere.options.enableMixedRulesets "Enable mixed content rulesets"> -<!ENTITY https-everywhere.options.showDevtoolsTab "Show Devtools tab"> -<!ENTITY https-everywhere.options.autoUpdateRulesets "Auto-update rulesets"> -<!ENTITY https-everywhere.options.imported "تم إستيراد الاعدادت الخاصة بك"> +<!ENTITY https-everywhere.options.importSettings "استورد الإعدادات"> +<!ENTITY https-everywhere.options.import "استورد"> +<!ENTITY https-everywhere.options.enableMixedRulesets "فعّل مجموعة قواعد المحتوى المختلِط"> +<!ENTITY https-everywhere.options.showDevtoolsTab "اعرض لسان أدوات المطورين"> +<!ENTITY https-everywhere.options.autoUpdateRulesets "حدث مجموعات القواعد تلقائيا"> +<!ENTITY https-everywhere.options.imported "تم استيراد إعداداتك"> -<!ENTITY https-everywhere.prefs.export_settings "تصدير اﻹعدادات"> +<!ENTITY https-everywhere.prefs.export_settings "صدّر الإعدادات"> <!ENTITY https-everywhere.prefs.reset_defaults "استعادة الإعدادات الافتراضية"> -<!ENTITY https-everywhere.chrome.stable_rules "قوانين متوازنة."> -<!ENTITY https-everywhere.chrome.stable_rules_description "اجبار المواقع التالية بالقيام باتصالات مشفرة:"> -<!ENTITY https-everywhere.chrome.experimental_rules "قوانين تجريبية"> -<!ENTITY https-everywhere.chrome.experimental_rules_description "قد يسبب تحذيرات او اخطاء. الوضع الافتراضي معطل."> -<!ENTITY https-everywhere.chrome.add_rule "اضف استثناء لهذا الموقع"> -<!ENTITY https-everywhere.chrome.add_new_rule "اضف استثناء جديد لهذا الموقع"> +<!ENTITY https-everywhere.chrome.stable_rules "قواعد ثابتة"> +<!ENTITY https-everywhere.chrome.stable_rules_description "افرض الاتصالات المشفرة على المواقع التالية:"> +<!ENTITY https-everywhere.chrome.experimental_rules "قواعد تجريبية"> +<!ENTITY https-everywhere.chrome.experimental_rules_description "قد يسبب تحذيرات أو أخطاء. معطّل مبدئيا:"> +<!ENTITY https-everywhere.chrome.add_rule "أضف قاعدة لهذا الموقع"> +<!ENTITY https-everywhere.chrome.add_new_rule "أضف قاعدة جديدة لهذا الموقع"> <!ENTITY https-everywhere.chrome.always_https_for_host "استخدم HTTPS دائما لهذا المضيف"> <!ENTITY https-everywhere.chrome.host "المضيف"> -<!ENTITY https-everywhere.chrome.show_advanced "اظهار الاعدادت المتقدمه"> -<!ENTITY https-everywhere.chrome.hide_advanced "اخفاء الاعدادات المتقدمه"> -<!ENTITY https-everywhere.chrome.rule_name "اسم الشرط"> +<!ENTITY https-everywhere.chrome.show_advanced "أظهر الإعدادات المتقدمة"> +<!ENTITY https-everywhere.chrome.hide_advanced "أخفِ الإعدادات المتقدمة"> +<!ENTITY https-everywhere.chrome.rule_name "اسم القاعدة"> <!ENTITY https-everywhere.chrome.regex "مطابقة regex"> -<!ENTITY https-everywhere.chrome.redirect_to "اعادة التوجيه لـ"> -<!ENTITY https-everywhere.chrome.status_cancel_button "إلغاء"> +<!ENTITY https-everywhere.chrome.redirect_to "أعِد التوجيه إلى"> +<!ENTITY https-everywhere.chrome.status_cancel_button "ألغِ">

1 0

[translation/support-tbb] Update translations for support-tbb
by translation＠torproject.org 20 May '18

20 May '18

commit b750109d8e64db1511af8c55fbfb022ad873f014 Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 20 05:49:32 2018 +0000 Update translations for support-tbb --- zh_CN.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/zh_CN.json b/zh_CN.json index 51f39d580..882005153 100644 --- a/zh_CN.json +++ b/zh_CN.json @@ -98,8 +98,8 @@ "tbb-16": { "id": "#tbb-16", "control": "tbb-16", - "title": "我可以选择我要出口的国家吗？", - "description": "<p class=\"mb-3\">Modifying the way that Tor creates its circuits is strongly discouraged. You get the best security that Tor can provide when you leave the route selection to Tor; overriding the entry / exit nodes can compromise your anonymity. If the outcome you want is simply to be able to access resources that are only available in one country, you may want to consider using a VPN instead of using Tor. Please note that VPNs do not have the same privacy properties as Tor, but they will help solve some geolocation restriction issues.</p>" + "title": "我可以选择出口节点的所在地吗？", + "description": "<p class=\"mb-3\">我们强烈反对您更改tor线路。使用tor为您选择的线路可以享受最佳的隐私防护。更改入口/出口节点可能会危害到您的匿名性。如果您所希望访问的资源只在允许特定国家的访问，您可以考虑使用VPN而不是tor。请注意，VPN无法提供与tor一样的隐私保护，不过它们能够帮助您解决地域限定问题。</p>" }, "tbb-17": { "id": "#tbb-17", @@ -111,7 +111,7 @@ "id": "#tbb-18", "control": "tbb-18", "title": "有对*BSD的支持吗?", - "description": "<p class=\"mb-3\">Sorry, but there is currently no official support for running Tor Browser on *BSD. There is something called the TorBSD project, but their Tor Browser is not officially supported.</p>" + "description": "<p class=\"mb-3\">抱歉，目前没有支持BSD平台的tor浏览器官方版本。有一个名为TorBSD的项目不过并没有得到Tor浏览器的官方支持。</p>" }, "tbb-19": { "id": "#tbb-19", @@ -128,8 +128,8 @@ "tbb-21": { "id": "#tbb-21", "control": "tbb-21", - "title": "How do I view Tor Browser message log?", - "description": "<p class=\"mb-3\">Click the button labelled \"Copy Tor Log To Clipboard\" that appears in the dialog window when Tor Browser is first connecting to the network. If Tor Browser is already open, click on the Torbutton icon (the small green onion at the top-left of the screen), then \"Open Network Settings\", then \"Copy Tor Log To Clipboard.\". Once you have copied the log, you will be able to paste it into a text editor or email client.</p>" + "title": "我该怎么查询tor浏览器的通讯日志？", + "description": "<p class=\"mb-3\">在首次开启tor浏览器并且连接到网络时，点击在对话框里出现的“复制tor日志到剪贴板”按钮。如果tor浏览器已经被打开了，点击Torbutton图标（在屏幕左上方出现的小型绿色洋葱），然后点击“打开网络设置”，“复制tor日志到剪贴板”。当您成功复制了日志后，您就可以将它们粘贴到文字编辑器或者email客户端。</p>" }, "tbb-22": { "id": "#tbb-22", @@ -218,7 +218,7 @@ "tbb-36": { "id": "#tbb-36", "control": "tbb-36", - "title": "Can I run multiple instances of Tor Browser?", + "title": "我能同时运行多个Tor浏览器吗？", "description": "<p class=\"mb-3\">We do not recommend running multiple instances of Tor Browser, and may not work as anticipated on many platforms.</p>" }, "tbb-37": {

1 0

[translation/support-https] Update translations for support-https
by translation＠torproject.org 20 May '18

20 May '18

commit a9d24fd369f1e417c3d7df3899dcb9e57fc14ed8 Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 20 03:19:33 2018 +0000 Update translations for support-https --- ta.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ta.json b/ta.json index 625e41dd5..55762388e 100644 --- a/ta.json +++ b/ta.json @@ -1,8 +1,8 @@ { "https-1": { - "id": "#https-1", - "control": "https-1", - "title": "When I'm using Tor, can eavesdroppers still see the information I share with websites, like login information and things I type into forms?", + "id": "#எச்டிடிபிஎஸ்-1", + "control": "எச்டிடிபிஎஸ்-1", + "title": "நான் Tor உபயோகப்படுத்தும்போதும், நான் வலைதளங்களில் பகிரும், உள்நுழை தகவல் மற்றும் படிவங்களில் நான் தட்டச்சிடும் விசயங்கள் போன்றவற்றை, ஒற்றுகேட்பவர்களால் காண இயலுமா? ", "description": "<p class=\"mb-3\">Tor protects eavesdroppers from learning sites that you visit. However, information sent unencrypted over the internet using plain HTTP can still be intercepted by exit relay operators or anyone observing the traffic between your exit relay and your destination website. If the site you are visiting uses HTTPS, then the traffic leaving your exit relay will be encrypted, and won't be visible to eavesdroppers.</p><div class=\"row\"><div class=\"col-md-6\"><div class=\"card\"><img class=\"card-img-top\" src=\"/static/images/image2.png\" alt=\"https\"><div class=\"card-body\"><h4 class=\"card-title\">If you are using HTTPS, your website URL will begin with \"https://\".</h4></div></div></div><div class=\"col-md-6\"><div class=\"card\"><img class=\"card-img-top\" src=\"/static/images/image6.png\" alt=\"https\"><div class=\"card-body\"><h4 class=\"card-title\">This visualization shows what information is visible to eavesdroppers with and without Tor Br owser and HTTPS encryption.</h4></div></div></div></div>" } }

1 0

[translation/tails-perl5lib_completed] Update translations for tails-perl5lib_completed
by translation＠torproject.org 20 May '18

20 May '18

commit 74bd1a0f6e311806bf0c69e81c424d603da3743e Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 20 03:17:42 2018 +0000 Update translations for tails-perl5lib_completed --- ta.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ta.po b/ta.po index 8eb622158..923595f05 100644 --- a/ta.po +++ b/ta.po @@ -3,14 +3,14 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: -# Senthil Kumar <paranthaba(a)gmail.com>, 2017 +# Senthil Kumar <paranthaba(a)gmail.com>, 2017-2018 # Khaleel Jageer <jskcse4(a)gmail.com>, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" -"POT-Creation-Date: 2017-05-20 10:59+0200\n" -"PO-Revision-Date: 2017-10-04 09:25+0000\n" +"POT-Creation-Date: 2018-03-15 12:15+0000\n" +"PO-Revision-Date: 2018-05-20 03:00+0000\n" "Last-Translator: Senthil Kumar <paranthaba(a)gmail.com>\n" "Language-Team: Tamil (http://www.transifex.com/otf/torproject/language/ta/)\n" "MIME-Version: 1.0\n" @@ -25,12 +25,12 @@ msgstr "பிழை" #: ../lib/Tails/RunningSystem.pm:161 msgid "" -"The device Tails is running from cannot be found. Maybe you used the `toram'" +"The device Tails is running from cannot be found. Maybe you used the 'toram'" " option?" -msgstr "Tails இருந்து இயங்கும் சாதனத்தை கண்டறிய முடியாது. ஒருவேளை நீங்கள் `toram' விருப்பத்தை பயன்படுத்தினால்?" +msgstr "Tails இருந்து இயங்கும் சாதனத்தை கண்டறிய முடியாது. ஒருவேளை நீங்கள் `toram' வகையினை பயன்படுத்தினதால்?" #: ../lib/Tails/RunningSystem.pm:192 msgid "" -"The drive Tails is running from cannot be found. Maybe you used the `toram' " +"The drive Tails is running from cannot be found. Maybe you used the 'toram' " "option?" msgstr "Tails இயங்கும் வட்டு காணப்பெறவில்லை. நீங்கள் 'toram' வகையினை பயன்படுத்தியிருக்கலாம்?"

1 0

[translation/tails-perl5lib] Update translations for tails-perl5lib
by translation＠torproject.org 20 May '18

20 May '18

commit a2d10cdfd1dc2c0407987f8bd629839f428e6dcc Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 20 03:17:37 2018 +0000 Update translations for tails-perl5lib --- ta.po | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/ta.po b/ta.po index af23b21d3..923595f05 100644 --- a/ta.po +++ b/ta.po @@ -3,15 +3,15 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: -# Senthil Kumar <paranthaba(a)gmail.com>, 2017 +# Senthil Kumar <paranthaba(a)gmail.com>, 2017-2018 # Khaleel Jageer <jskcse4(a)gmail.com>, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" "POT-Creation-Date: 2018-03-15 12:15+0000\n" -"PO-Revision-Date: 2018-03-31 13:21+0000\n" -"Last-Translator: carolyn <carolyn(a)anhalt.org>\n" +"PO-Revision-Date: 2018-05-20 03:00+0000\n" +"Last-Translator: Senthil Kumar <paranthaba(a)gmail.com>\n" "Language-Team: Tamil (http://www.transifex.com/otf/torproject/language/ta/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -27,10 +27,10 @@ msgstr "பிழை" msgid "" "The device Tails is running from cannot be found. Maybe you used the 'toram'" " option?" -msgstr "" +msgstr "Tails இருந்து இயங்கும் சாதனத்தை கண்டறிய முடியாது. ஒருவேளை நீங்கள் `toram' வகையினை பயன்படுத்தினதால்?" #: ../lib/Tails/RunningSystem.pm:192 msgid "" "The drive Tails is running from cannot be found. Maybe you used the 'toram' " "option?" -msgstr "" +msgstr "Tails இயங்கும் வட்டு காணப்பெறவில்லை. நீங்கள் 'toram' வகையினை பயன்படுத்தியிருக்கலாம்?"

1 0

[translation/support-connecting_completed] Update translations for support-connecting_completed
by translation＠torproject.org 19 May '18

19 May '18

commit c640b7bcec77cc7885b066f2e20a922d51b2f886 Author: Translation commit bot <translation(a)torproject.org> Date: Sat May 19 23:19:08 2018 +0000 Update translations for support-connecting_completed --- id.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id.json b/id.json index 0fdc118e3..16b8c9d23 100644 --- a/id.json +++ b/id.json @@ -9,7 +9,7 @@ "id": "#connecting-2", "control": "connecting-2", "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", - "description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS se rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\">Jika Anda mengalami masalah dalam terhubung ke jaringan Tor, pilih opsi \"copy Tor log to clipboard.\" Lalu paste Tor log ke Notepad atau dokumen lain. Anda seharusnya melihat log error yang umum (lihat baris-baris berikut di Tor log): </p><h5>Common log error #1: Kegagalan koneksi proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code> </pre></p><p class=\"mb-3\">Jika Anda melihat baris-baris ini, ini artinya Anda gagal terhubung ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan ANda, pastika Anda telah memasukkan detail proxy-nya dengan benar. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin, coba terhubung ke jaringan Tor tanpa proxy SOCKS. <p><h5>Common log error #2: Tidak dapat terhubung ke guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal terhubung ke node pertama di sirkuit. Ini artinya Anda berada di jaringan yang disensor. Silakan coba lagi dengan menggunakan bridge. Ini biasanya menyelesaikan masalah ini. </p><h5>Common log error #3: Gagal menyelesaikan TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal menyelesaikan TLS handshake dengan otoritas directory. Penggunaan bridge biasanya akan menyeles aikan masalah ini. </p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika Anda melihat ini, jam di komputer Anda tidak benar. Pastikan jamnya diatur dengan benar termasuk zona waktunya. Lalu restart Tor. </p>" }, "connecting-3": { "id": "#connecting-3",

1 0

[translation/support-connecting] Update translations for support-connecting
by translation＠torproject.org 19 May '18

19 May '18

commit 378ade1a2cf9ffe775b01a1af5a3c983fdc11fe3 Author: Translation commit bot <translation(a)torproject.org> Date: Sat May 19 23:19:04 2018 +0000 Update translations for support-connecting --- id.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id.json b/id.json index 9883c41bd..16b8c9d23 100644 --- a/id.json +++ b/id.json @@ -9,7 +9,7 @@ "id": "#connecting-2", "control": "connecting-2", "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", - "description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\">Jika Anda mengalami masalah dalam terhubung ke jaringan Tor, pilih opsi \"copy Tor log to clipboard.\" Lalu paste Tor log ke Notepad atau dokumen lain. Anda seharusnya melihat log error yang umum (lihat baris-baris berikut di Tor log): </p><h5>Common log error #1: Kegagalan koneksi proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code> </pre></p><p class=\"mb-3\">Jika Anda melihat baris-baris ini, ini artinya Anda gagal terhubung ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan ANda, pastika Anda telah memasukkan detail proxy-nya dengan benar. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin, coba terhubung ke jaringan Tor tanpa proxy SOCKS. <p><h5>Common log error #2: Tidak dapat terhubung ke guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal terhubung ke node pertama di sirkuit. Ini artinya Anda berada di jaringan yang disensor. Silakan coba lagi dengan menggunakan bridge. Ini biasanya menyelesaikan masalah ini. </p><h5>Common log error #3: Gagal menyelesaikan TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal menyelesaikan TLS handshake dengan otoritas directory. Penggunaan bridge biasanya akan menyeles aikan masalah ini. </p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika Anda melihat ini, jam di komputer Anda tidak benar. Pastikan jamnya diatur dengan benar termasuk zona waktunya. Lalu restart Tor. </p>" }, "connecting-3": { "id": "#connecting-3",

1 0

[translation/support-censorship_completed] Update translations for support-censorship_completed
by translation＠torproject.org 19 May '18

19 May '18

commit 52a80a57c8e761252fb169c8939f2b4a3237891a Author: Translation commit bot <translation(a)torproject.org> Date: Sat May 19 23:18:58 2018 +0000 Update translations for support-censorship_completed --- id.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/id.json b/id.json index 55c318a59..34bb31434 100644 --- a/id.json +++ b/id.json @@ -9,7 +9,7 @@ "id": "#censorship-2", "control": "censorship-2", "title": "Situs web favorit saya memblokir akses melalui Tor.", - "description": "<p class=\"mb-3\">Kami turut prihatin atas Anda tidak dapat melakukan akses ke situs web yang Anda inginkan! Kadang beberapa situs web memblokir pengguna Tor karena tidak dapat membedakan pengguna Tor biasa dan lalu-lintas otomatos. Hal terbaik yang dapat dilakukan adalah pengguna menghubungi langsung admin situsnya. Ini mungkin dapat menjadi contoh: <br />\"Halo! Saya berusaha melakukan akses terhadap situs xyz.com Anda melalui Tor Browser dan ternyata Anda tidak mengizinkan pengguna Tor untuk melakukan akses terhadap situs Anda. Saya mohon dengan sangat untuk mempertimbangkan hal ini; Tor digunakan orang-orang di seluruh dunia untuk melindungi privasi mereka dan melawan sensor. Dengan memblokir pengguna Tor, Anda akan memblokir orang-orang di negara-negara represif yang ingin menggunakan Internet secara bebas, wartawan, dan peneliti yang ingin melindungi diri sendiri dari penemuan, termasuk whistleblower, aktivis, dan orang-orang biasa yang ingin terbebas dari pel acakan menyeluruh yang dilakukan pihak lain. Mohon dukungan penuh terhadap privasi digital dan kebebasan Internet, dan izinkan pengguna Tor untuk melakukan akses ke xyz.com. Terima kasih.\"<br />Untuk situs web perbankan dan situs web lain yang sensitif, umumnya ada pemblokiran berdasarkan wilayah geografis (jika bank Anda mengetahui Anda biasanya melakukan akses terhadap jasa mereka dari suatu negara dan jika tiba-tiba Anda membuka situs web mereka dari exit relay di negara lain, akun Anda mungkin akan dikunci atau dibekukan). Jika Anda tidak dapat terhubung ke sebuah onion service, silakan lihat <a href=\"http://127.0.0.1:5000/#onionservices-3\">Saya tidak dapat menghubungi X.onion!</a></p>" + "description": "<p class=\"mb-3\">Kami turut prihatin atas Anda tidak dapat melakukan akses ke situs web yang Anda inginkan! Kadang beberapa situs web memblokir pengguna Tor karena tidak dapat membedakan pengguna Tor biasa dan lalu-lintas otomatos. Hal terbaik yang dapat dilakukan adalah pengguna menghubungi langsung admin situsnya. Ini mungkin dapat menjadi contoh: <br /> \"Halo! Saya berusaha melakukan akses terhadap situs xyz.com Anda melalui Tor Browser dan ternyata Anda tidak mengizinkan pengguna Tor untuk melakukan akses terhadap situs Anda. Saya mohon dengan sangat untuk mempertimbangkan hal ini; Tor digunakan orang-orang di seluruh dunia untuk melindungi privasi mereka dan melawan sensor. Dengan memblokir pengguna Tor, Anda akan memblokir orang-orang di negara-negara represif yang ingin menggunakan Internet secara bebas, wartawan, dan peneliti yang ingin melindungi diri sendiri dari penemuan, termasuk whistleblower, aktivis, dan orang-orang biasa yang ingin terbebas dari pe lacakan menyeluruh yang dilakukan pihak lain. Mohon dukungan penuh terhadap privasi digital dan kebebasan Internet, dan izinkan pengguna Tor untuk melakukan akses ke xyz.com. Terima kasih. <br />Untuk situs web perbankan dan situs web lain yang sensitif, umumnya ada pemblokiran berdasarkan wilayah geografis (jika bank Anda mengetahui Anda biasanya melakukan akses terhadap jasa mereka dari suatu negara dan jika tiba-tiba Anda membuka situs web mereka dari exit relay di negara lain, akun Anda mungkin akan dikunci atau dibekukan). Jika Anda tidak dapat terhubung ke sebuah onion service, silakan lihat <a href=\"#onionservices-3\">Saya tidak dapat menghubungi X.onion!</a></p>" }, "censorship-3": { "id": "#censorship-3", @@ -27,7 +27,7 @@ "id": "#censorship-5", "control": "censorship-5", "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", - "description": "<p class=\"mb-3\">Jika Anda mendapat masalah dalam terhubung ke Jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Jaringan Tor \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Tor gagal ter sambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.< /p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\">Jika Anda mengalami masalah dalam terhubung ke jaringan Tor, pilih opsi \"copy Tor log to clipboard.\" Lalu paste Tor log ke Notepad atau dokumen lain. Anda seharusnya melihat log error yang umum (lihat baris-baris berikut di Tor log): </p><h5>Common log error #1: Kegagalan koneksi proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code> </pre></p><p class=\"mb-3\">Jika Anda melihat baris-baris ini, ini artinya Anda gagal terhubung ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan ANda, pastika Anda telah memasukkan detail proxy-nya dengan benar. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin, coba terhubung ke jaringan Tor tanpa proxy SOCKS. <p><h5>Common log error #2: Tidak dapat terhubung ke guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal terhubung ke node pertama di sirkuit. Ini artinya Anda berada di jaringan yang disensor. Silakan coba lagi dengan menggunakan bridge. Ini biasanya menyelesaikan masalah ini. </p><h5>Common log error #3: Gagal menyelesaikan TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal menyelesaikan TLS handshake dengan otoritas directory. Penggunaan bridge biasanya akan menyeles aikan masalah ini. </p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika Anda melihat ini, jam di komputer Anda tidak benar. Pastikan jamnya diatur dengan benar termasuk zona waktunya. Lalu restart Tor. </p>" }, "censorship-6": { "id": "#censorship-6",

1 0

[translation/support-censorship] Update translations for support-censorship
by translation＠torproject.org 19 May '18

19 May '18

commit 6bf4d8312b9115ce2361bf0f41c30d6fb4698450 Author: Translation commit bot <translation(a)torproject.org> Date: Sat May 19 23:18:54 2018 +0000 Update translations for support-censorship --- id.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id.json b/id.json index 4ca5db7cc..34bb31434 100644 --- a/id.json +++ b/id.json @@ -27,7 +27,7 @@ "id": "#censorship-5", "control": "censorship-5", "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", - "description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\">Jika Anda mengalami masalah dalam terhubung ke jaringan Tor, pilih opsi \"copy Tor log to clipboard.\" Lalu paste Tor log ke Notepad atau dokumen lain. Anda seharusnya melihat log error yang umum (lihat baris-baris berikut di Tor log): </p><h5>Common log error #1: Kegagalan koneksi proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code> </pre></p><p class=\"mb-3\">Jika Anda melihat baris-baris ini, ini artinya Anda gagal terhubung ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan ANda, pastika Anda telah memasukkan detail proxy-nya dengan benar. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin, coba terhubung ke jaringan Tor tanpa proxy SOCKS. <p><h5>Common log error #2: Tidak dapat terhubung ke guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal terhubung ke node pertama di sirkuit. Ini artinya Anda berada di jaringan yang disensor. Silakan coba lagi dengan menggunakan bridge. Ini biasanya menyelesaikan masalah ini. </p><h5>Common log error #3: Gagal menyelesaikan TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris ini, Tor gagal menyelesaikan TLS handshake dengan otoritas directory. Penggunaan bridge biasanya akan menyeles aikan masalah ini. </p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika Anda melihat ini, jam di komputer Anda tidak benar. Pastikan jamnya diatur dengan benar termasuk zona waktunya. Lalu restart Tor. </p>" }, "censorship-6": { "id": "#censorship-6",

1 0

[translation/support-miscellaneous_completed] Update translations for support-miscellaneous_completed
by translation＠torproject.org 19 May '18

19 May '18

commit 6fe533e460e74e1e8a44d343a4b5544a97bad3c9 Author: Translation commit bot <translation(a)torproject.org> Date: Sat May 19 22:49:28 2018 +0000 Update translations for support-miscellaneous_completed --- id.json | 90 ++++++++++++++++++++++++++++++++--------------------------------- 1 file changed, 45 insertions(+), 45 deletions(-) diff --git a/id.json b/id.json index e1bec4592..11fc1896a 100644 --- a/id.json +++ b/id.json @@ -1,91 +1,91 @@ { - "miscellaneus-1": { - "id": "#miscellaneus-1", - "control": "miscellaneus-1", + "misc-1": { + "id": "#misc-1", + "control": "misc-1", "title": "Saya punya alasan kuat untuk melacak seorang pengguna Tor. Apakah Anda dapat membantu saya?", "description": "<p class=\"mb-3\"> Tidak ada yang dapat dilakukan oleh para pengembang Tor dalam melacak pengguna Tor. Perlindungan yang menghalangi orang jahat untuk merusak anonimitas Tor juga mencegah kami melacak pengguna.</p>" }, - "miscellaneus-2": { - "id": "#miscellaneus-2", - "control": "miscellaneus-2", + "misc-2": { + "id": "#misc-2", + "control": "misc-2", "title": "Kenapa kalian tidak mencegah orang jahat melakukan kejahatan menggunakan Tor?", "description": "<p class=\"mb-3\"> Tor dirancang untuk melindungi hak asasi manusia dan privasi dengan mencegah siapa saja dalam menyensor apapun, mencegah siapapun bahkan diri kami sendiri. Kami tidak suka kalau ada orang-orang yang menggunakan Tor untuk hal-hal buruk, tapi kami tidak dapat melakukan apapun dalam menyingkirkan mereka tanpa mengabaikan aktivis HAM, wartawan, orang-orang yang selamat dari pelecehan, dan orang lain yang menggunakan Tor untuk kebaikan. Jika kami menghalangi sebagian orang menggunakan Tor, kami pada dasarnya akan menambah pintu belakang di perangkat lunak ini, yang akan buka kelemahan pengguna kami kepada pemerintah yang tidak baik dan musuh-musuh lain.</p>" }, - "miscellaneus-3": { - "id": "#miscellaneus-3", - "control": "miscellaneus-3", + "misc-3": { + "id": "#misc-3", + "control": "misc-3", "title": "Siapa yang membiayai Tor?", "description": "<p class=\"mb-3\">Tor dibiayai beberapa sponsor termasuk lembaga federal Amerika Serikat, yayasan swasta, dan donor individu. Silakan lihat semua <mark><a href=\"https://www.torproject.org/about/sponsors.html.en\"> sponsors kami</a></mark> dan beberapa <mark><a href=\"https://blog.torproject.org/category/tags/form-990\">posting blog</a></mark>tentang laporan keuangan kami.</p>Menurut kami, mengumumkan tentang donor dan model pembiayaan kami adalah cara terbaik memelihara kepercayaan komunitas kami. Kami selalu mencara cara lain dalam pembiayaan, termasuk dari yayasan dan orang perorangan.<p class=\"mb-3\">" }, - "miscellaneus-4": { - "id": "#miscellaneus-4", - "control": "miscellaneus-4", + "misc-4": { + "id": "#misc-4", + "control": "misc-4", "title": "Apakah saya dapat menggunakan Tor dengan bittorent?", "description": "<p class=\"mb-3\"> Kami tidak menyarankan penggunaan Tor dengan bittorent. Untuk penjelasan lebih lanjut, silakan baca <mark><a href=\"https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea\">posting blog tentang hal ini</a></mark>.</p>" }, - "miscellaneus-5": { - "id": "#miscellaneus-5", - "control": "miscellaneus-5", + "misc-5": { + "id": "#misc-5", + "control": "misc-5", "title": "File-file di komputer saya terkunci dan seseorang menyuruh saya mengunduh peramban Tor Browser untuk membayar tebusan atas file-file saya!", "description": "<p class=\"mb-3\">Kami turut berduka atas terkenanya Anda oleh malware. Tor Project tidak menciptakan malware ini. Pencipta malware itu meminta Anda mengunduh Tor Browser supaya Anda dapat menghubungi mereka secara anonim dengan tebusannya. Jika ini adalah perkenalan pertama Anda dengan Tor Browser, kami paham kalau Anda berpikir kami adalah orang-orang jahat yang membantu orang-orang yang lebih jahat. Namu, mohon ketahui bahwa perangkat lunak kami digunakan untuk beragam tujuan oleh aktivis hak asasi manusia, wartawan, orang-orang yang selamat dari kekerasan rumah tangga, whistle blower, penegak hukum, dan banyak lain. Sayangnya, perlindungan yang disediakan perangkat lunak kami kepada orang-orang tersebut dapat disalahgunakan oleh penjahat dan pembuat malware. Tor Project tidak mendukung atau merestui penggunaan perangkat lunak kami untuk tujuan jahat.</p>" }, - "miscellaneus-6": { - "id": "#miscellaneus-6", - "control": "miscellaneus-6", + "misc-6": { + "id": "#misc-6", + "control": "misc-6", "title": "Apakah Tor menyimpan log?", "description": "<p class=\"mb-3\">Tor tidak menyimpan log apapun yang dapat mengidentifikasi pengguna tertentu. Kami melakukan beberapa langkah aman dalam cara jaringan Tor berfungsi, yang dapat Anda baca di <mark><a href=\"https://metrics.torproject.org/\">Tor Metrics</a></mark>.</p>" }, - "miscellaneus-7": { - "id": "#miscellaneus-7", - "control": "miscellaneus-7", + "misc-7": { + "id": "#misc-7", + "control": "misc-7", "title": "Apakah Tor Project menawarkan jasa email atau jasa web lain yang menawarkan perlindungan privasi?", "description": "<p class=\"mb-3\"> Tidak, kami tidak menawarkan jasa online. Daftar semua proyek perangkat lunak kami dapat ditemukan di <mark><a href=\"https://www.torproject.org/projects/projects.html.en\">halaman proyek </a></mark>.</p>" }, - "miscellaneus-8": { - "id": "#miscellaneus-8", - "control": "miscellaneus-8", + "misc-8": { + "id": "#misc-8", + "control": "misc-8", "title": "Apakah saya dapat menggunakan logo Tor di produk saya?", "description": "<p class=\"mb-3\">Anda dapat membaca semua tentang hal ini di <mark><a href=\"https://www.torproject.org/docs/trademark-faq.html\">halaman trademark faq</a></mark>.</p>" }, - "miscellaneus-9": { - "id": "#miscellaneus-9", - "control": "miscellaneus-9", + "misc-9": { + "id": "#misc-9", + "control": "misc-9", "title": "Saya mendapat masalah dalam memperbarui atau menggunakan Vidalia.", "description": "<p class=\"mb-3\">Vidalia sudah tidak dipelihara atau didukung. Sebagian besar fitur Vidalia sudah terintegrasi ke Tor Browser.</p>" }, - "miscellaneus-10": { - "id": "#miscellaneus-10", - "control": "miscellaneus-10", + "misc-10": { + "id": "#misc-10", + "control": "misc-10", "title": "Apakah Tor Project menawarkan jasa hosting situs web?", "description": "<p class=\"mb-3\">Tidak, Tor Project tidak menawarkan jasa hosting.</p>" }, - "miscellaneus-11": { - "id": "#miscellaneus-11", - "control": "miscellaneus-11", + "misc-11": { + "id": "#misc-11", + "control": "misc-11", "title": "Apakah saya dapat mengubah jumlah hop yang digunakan Tor?", "description": "<p class=\"mb-3\"> Saat ini panjangnya path terkode dalam 3 plus jumlah node di path Anda yang sensitif. Yaitu, di keadaan normal, adalah 3, tapi misalnya jika Anda mengakses sebuah onion service atau sebuah alamat \".exit\", jumlah ini dapat lebih besar.</p><p class=\"mb-3\"We don't want to encourage people to use paths longer than this as it increases load on the network without (as far as we can tell) providing any more security. Also, using paths longer than 3 could harm anonymity, first because it makes<mark><a href=\"https://www.freehaven.net/anonbib/#ccs07-doa\">serangan denial of security</a></mark> akan lebih mudah, dan juga karena bisa digunakan sebagai pengenal jika hanya ada sedikit pengguna yang menggunakan panjang path yang sama dengan Anda.</p>" }, - "miscellaneus-12": { - "id": "#miscellaneus-12", - "control": "miscellaneus-12", + "misc-12": { + "id": "#misc-12", + "control": "misc-12", "title": "Bagaimana berbagi file secara anonim melalui Tor?", "description": "<p class=\"mb-3\"> Banyak exit node diatur untuk menghalangi beberapa jenis lalu-lintas file sharing, seperti bittorent. Bittorent secara spesifik <mark><a href=\"https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea\">tidak anonim di Tor</a></mark>.</p><p class=\"mb-3\">Untuk berbagi file melalui Tor, <mark><a href=\"https://onionshare.org/\">OnionShare</a></mark>adalah pilihan yang tepat.</p>" }, - "miscellaneus-13": { - "id": "#miscellaneus-13", - "control": "miscellaneus-13", + "misc-13": { + "id": "#misc-13", + "control": "misc-13", "title": "Apa saya dapat menggunakan VPN dengan Tor?", "description": "<p class=\"mb-3\">Umumnya kami tidak menyarankan VPN dengan Tor kecuali Anda adalah pengguna tingkat lanjut yang dapat mengatur keduanya sehingga tidak mengurangi privasi Anda. Silakan cari tahu lebih tentang menggabungkan Tor + VPN di <mark><a href=\"https://trac.torproject.org/projects/tor/wiki/doc/TorPlusVPN\">wiki kami</a></mark>.</p>" }, - "miscellaneus-14": { - "id": "#miscellaneus-14", - "control": "miscellaneus-14", + "misc-14": { + "id": "#misc-14", + "control": "misc-14", "title": "Bagaimana cara menjadi relawan pada Tor Project?", "description": "<p class=\"mb-3\">Silakan lihat <mark><a href=\"https://www.torproject.org/getinvolved/volunteer.html.en\">halaman relawan</a></mark> untuk ikut terlibat!</p>" }, - "miscellaneus-15": { - "id": "#miscellaneus-15", - "control": "miscellaneus-15", + "misc-15": { + "id": "#misc-15", + "control": "misc-15", "title": "Bagaimana cara memberikan donasi kepada Tor Project?", "description": "<p class=\"mb-3\">Terima kasih atas dukungan Anda! Anda dapat menemukan lebih banyak info tentang sumbangan di <mark><a href=\"https://donate.torproject.org/donor-faq\">donor FAQe</a></mark>.</p>" }

1 0