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

[tor/master] Merge remote-tracking branch 'catalyst-github/bug25756'
by nickm＠torproject.org 11 May '18

11 May '18

commit aab626405c312a33d521c9ca3729552fd9ccca2e Merge: b3e591dca de343b4e4 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri May 11 18:15:43 2018 -0400 Merge remote-tracking branch 'catalyst-github/bug25756' changes/bug25756 | 7 ++ src/or/connection.c | 8 +- src/or/connection.h | 7 +- src/or/networkstatus.c | 71 +++++++++++++----- src/or/networkstatus.h | 2 + src/test/log_test_helpers.h | 4 + src/test/test_routerlist.c | 175 ++++++++++++++++++++++++++++++++++++++++++-- 7 files changed, 242 insertions(+), 32 deletions(-)

1 0

[tor/master] Add a CONTRIBUTING file
by nickm＠torproject.org 11 May '18

11 May '18

commit f7949a440f1356e08550d26da5c5749fa35f5b3d Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri May 11 13:19:37 2018 -0400 Add a CONTRIBUTING file This file contains pointers to other important top-level resources, and some info about acceptable licenses. Also, add that info to CodingStandards.md --- CONTRIBUTING | 39 +++++++++++++++++++++++++++++++++++++++ Makefile.am | 1 + doc/HACKING/CodingStandards.md | 18 ++++++++++++++++++ 3 files changed, 58 insertions(+) diff --git a/CONTRIBUTING b/CONTRIBUTING new file mode 100644 index 000000000..7d8bd0341 --- /dev/null +++ b/CONTRIBUTING @@ -0,0 +1,39 @@ +Contributing to Tor +------------------- + +### Getting started + +Welcome! + +We have a bunch of documentation about how to develop Tor in the +doc/HACKING/ directory. We recommend that you start with +doc/HACKING/README.1st.md , and then go from there. It will tell +you how to find your way around the source code, how to get +involved with the Tor community, how to write patches, and much +more! + +You don't have to be a C developer to help with Tor: have a look +at https://www.torproject.org/getinvolved/volunteer.html.en ! + +The Tor Project is committed to fostering a inclusive community +where people feel safe to engage, share their points of view, and +participate. For the latest version of our Code of Conduct, please +see + +https://gitweb.torproject.org/community/policies.git/plain/code_of_conduct.txt + + + +### License issues + +Tor is distributed under the license terms in the LICENSE -- in +brief, the "3-clause BSD license". If you send us code to +distribute with Tor, it needs to be code that we can distribute +under those terms. Please don't send us patches unless you agree +to allow this. + +Some compatible licenses include: + + - 3-clause BSD + - 2-clause BSD + - CC0 Public Domain Dedication diff --git a/Makefile.am b/Makefile.am index 97a39031a..58ff9fb3e 100644 --- a/Makefile.am +++ b/Makefile.am @@ -38,6 +38,7 @@ include contrib/include.am EXTRA_DIST+= \ ChangeLog \ + CONTRIBUTING \ INSTALL \ LICENSE \ Makefile.nmake \ diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index 79a6a9f0c..3711f7019 100644 --- a/doc/HACKING/CodingStandards.md +++ b/doc/HACKING/CodingStandards.md @@ -42,6 +42,23 @@ If you have changed build system components: - For example, if you have changed Makefiles, autoconf files, or anything else that affects the build system. +License issues +============== + +Tor is distributed under the license terms in the LICENSE -- in +brief, the "3-clause BSD license". If you send us code to +distribute with Tor, it needs to be code that we can distribute +under those terms. Please don't send us patches unless you agree +to allow this. + +Some compatible licenses include: + + - 3-clause BSD + - 2-clause BSD + - CC0 Public Domain Dedication + + + How we use Git branches ======================= @@ -417,3 +434,4 @@ the functions that call your function rely on it doing something, then your function should mention that it does that something in the documentation. If you rely on a function doing something beyond what is in its documentation, then you should watch out, or it might do something else later. +

1 0

[tor/master] Merge branch 'contributing'
by nickm＠torproject.org 11 May '18

11 May '18

commit cbb13df8080b660e5d20962c31c8744ed190d2e9 Merge: f6c96fd0c f7949a440 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri May 11 17:59:09 2018 -0400 Merge branch 'contributing' CONTRIBUTING | 39 +++++++++++++++++++++++++++++++++++++++ Makefile.am | 1 + doc/HACKING/CodingStandards.md | 18 ++++++++++++++++++ 3 files changed, 58 insertions(+)

1 0

[tor/master] improve a URL
by nickm＠torproject.org 11 May '18

11 May '18

commit b3e591dca1a7343a49bc949e8f75a242efb7fb72 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri May 11 18:00:30 2018 -0400 improve a URL --- CONTRIBUTING | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index 7d8bd0341..3569f45a8 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -13,7 +13,7 @@ involved with the Tor community, how to write patches, and much more! You don't have to be a C developer to help with Tor: have a look -at https://www.torproject.org/getinvolved/volunteer.html.en ! +at https://www.torproject.org/getinvolved/volunteer ! The Tor Project is committed to fostering a inclusive community where people feel safe to engage, share their points of view, and

1 0

[tor/master] Merge remote-tracking branch 'public/bug25994'
by nickm＠torproject.org 11 May '18

11 May '18

commit f6c96fd0cacfb44b4a97ac2a9887a80920937da1 Merge: 962c2f877 24299d385 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri May 11 17:57:59 2018 -0400 Merge remote-tracking branch 'public/bug25994' changes/ticket25994 | 5 +++++ src/test/test_channel.c | 6 ++++++ 2 files changed, 11 insertions(+)

1 0

[tor/master] Hold monotonic time constant during channel/outbound_cell test
by nickm＠torproject.org 11 May '18

11 May '18

commit 24299d385d38a254eabde531a8f4f7830ecb088d Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue May 1 18:44:11 2018 -0400 Hold monotonic time constant during channel/outbound_cell test This change should make it impossible for the monotonic time to roll over from one EWMA tick to the next during this test, and make it so that this test never invokes scale_active_circuits() (which it doesn't test). (Earlier changes during the 0.3.4 series should make this call even rarer than it was before, since we fixed #25927 and removed cached_gettimeofday. Because this test didn't update cached_gettimeofday, the chance of rolling over a 10-second interval was much higher.) Closes ticket 25994; bugfix on 0.3.3.1-alpha when this test was introduced. --- changes/ticket25994 | 5 +++++ src/test/test_channel.c | 6 ++++++ 2 files changed, 11 insertions(+) diff --git a/changes/ticket25994 b/changes/ticket25994 new file mode 100644 index 000000000..135417401 --- /dev/null +++ b/changes/ticket25994 @@ -0,0 +1,5 @@ + o Minor bugfixes (tests): + - Change the behavior of the "channel/outbound" test so that it never + causes a 10-second rollover for the EWMA circuitmux code. Previously, + this behavior would happen randomly, and result in fluctuating test + coverage. Fixes bug 25994; bugfix on 0.3.3.1-alpha. diff --git a/src/test/test_channel.c b/src/test/test_channel.c index 7d5018ef5..b20063c85 100644 --- a/src/test/test_channel.c +++ b/src/test/test_channel.c @@ -544,6 +544,11 @@ test_channel_outbound_cell(void *arg) (void) arg; + /* Set the test time to be mocked, since this test assumes that no + * time will pass, ewma values will not need to be re-scaled, and so on */ + monotime_enable_test_mocking(); + monotime_set_mock_time_nsec(U64_LITERAL(1000000000) * 12345); + cmux_ewma_set_options(NULL,NULL); /* The channel will be freed so we need to hijack this so the scheduler @@ -660,6 +665,7 @@ test_channel_outbound_cell(void *arg) tor_free(p_cell); channel_free_all(); UNMOCK(scheduler_release_channel); + monotime_disable_test_mocking(); } /* Test inbound cell. The callstack is:

1 0

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

11 May '18

commit 53066f5fcb15038f923029472cbe353f79ad215d Author: Translation commit bot <translation(a)torproject.org> Date: Fri May 11 20:49:43 2018 +0000 Update translations for support-tbb --- ru.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru.json b/ru.json index 384d205d3..1cbaa7fb0 100644 --- a/ru.json +++ b/ru.json @@ -39,7 +39,7 @@ "id": "#tbb-7", "control": "tbb-7", "title": "ÐÐŸÐ¹ Ð»ÑÐ±ÐžÐŒÑÐ¹ ÑÐ°Ð¹Ñ Ð±Ð»ÐŸÐºÐžÑÑÐµÑ ÐŽÐŸÑÑÑÐ¿ ÑÐµÑÐµÐ· Tor.", - "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"#onionservices-3\">I cannot reach X.onion!</a></p>" + "description": "<p class=\"mb-3\">ÐÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ»ÑÑÐ°ÑÑ, ÑÑÐŸ Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÑÐµÑÐžÑÑ Ð²ÐµÐ±-ÑÐ°Ð¹Ñ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ð°ÐŒ ÐœÑÐ¶ÐµÐœ! ÐÐœÐŸÐ³ÐŽÐ° Ð²ÐµÐ±-ÑÐ°Ð¹ÑÑ Ð±Ð»ÐŸÐºÐžÑÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž ÐœÐµ ÐŒÐŸÐ³ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐ°Ð·ÐœÐžÑÑ ÐŒÐµÐ¶ÐŽÑ ÐŸÐ±ÑÑÐœÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ Tor Ðž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐžÐŒ ÑÑÐ°ÑÐžÐºÐŸÐŒ. ÐÐ°ÐžÐ»ÑÑÑÐžÐŒ ÐžÐ·Ð²ÐµÑÑÐœÑÐŒ ÐœÐ°ÐŒ Ð²ÑÑÐŸÐŽÐŸÐŒ ÐŽÐ»Ñ ÑÐ°Ð·Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor Ð±ÑÐŽÐµÑ ÑÐ»ÐµÐŽÑÑÑÐµÐµ: Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÐœÐ°ÐŽÐ»ÐµÐ¶ÐžÑ ÐœÐ°Ð¿ÑÑÐŒÑÑ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÐ°ÐŒ ÑÐ°Ð¹ÑÐ°. ÐÐœÐŸÐ³ÐŽÐ° ÑÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐ°ÐºÐŸÐ¹ ÑÑÑÐº:<br />\"ÐÑÐžÐ²ÐµÑ! Ð¯ Ð¿ÐŸÐ¿ÑÑÐ°Ð»ÑÑ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð²Ð°ÑÐµÐŒÑ ÑÐ°Ð¹ÑÑ xyz.com ÑÐµÑÐµÐ· Tor Browser Ðž ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐžÐ», ÑÑÐŸ Ð²Ñ ÐœÐµ ÑÐ°Ð·ÑÐµÑÐ°ÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐ Œ Tor Ð·Ð°ÑÐŸÐŽÐžÑÑ ÐœÐ° ÐœÐµÐ³ÐŸ. Ð¯ ÐœÐ°ÑÑÐŸÑÑÐµÐ»ÑÐœÐŸ Ð¿ÑÐžÐ·ÑÐ²Ð°Ñ Ð²Ð°Ñ Ð¿ÐµÑÐµÑÐŒÐŸÑÑÐµÑÑ ÑÑÐŸ ÑÐµÑÐµÐœÐžÐµ: Tor ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð»ÑÐŽÑÐŒÐž Ð²ÐŸ Ð²ÑÐµÐŒ ÐŒÐžÑÐµ ÐŽÐ»Ñ Ð·Ð°ÑÐžÑÑ ÐžÑ ÐºÐŸÐœÑÐžÐŽÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÑÑÐž Ðž Ð±ÐŸÑÑÐ±Ñ Ñ ÑÐµÐœÐ·ÑÑÐŸÐ¹. ÐÐ»ÐŸÐºÐžÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor, Ð²Ñ ÐœÐ°Ð²ÐµÑÐœÑÐºÐ° Ð±Ð»ÐŸÐºÐžÑÑÐµÑÐµ Ð»ÑÐŽÐµÐ¹ Ð² ÑÐµÐ¿ÑÐµÑÑÐžÐ²ÐœÑÑ ÑÑÑÐ°ÐœÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÑÐ¹ ÐžÐœÑÐµÑÐœÐµÑ, Ð¶ÑÑÐœÐ°Ð»ÐžÑÑÐŸÐ² Ðž ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ Ð·Ð°ÑÐžÑÐžÑÑ ÑÐµÐ±Ñ ÐŸÑ ÑÐ»ÐµÐ¶ÐºÐž Ðž ÐŸÑÐ²ÐµÐŽÐŸÐŒÐžÑÐµÐ»ÐµÐ¹, Ð°ÐºÑÐžÐ²ÐžÑÑÐŸÐ² Ðž ÐŸÐ±ÑÑÐœÑÑ Ð»ÑÐŽÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ ÐŸÑÐºÐ°Ð·Ð°ÑÑÑÑ ÐŸÑ ÐžÐœÐ²Ð°Ð·ÐžÐ²ÐœÐŸÐ³ÐŸ ÐŸÑÑÐ»ÐµÐ¶ÐžÐ²Ð°ÐœÐžÑ ÑÑÐµÑÑÐµÐ¹ ÑÑÐŸÑÐŸÐœÐŸÐ¹. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°Ð¹ÑÐµÑÑ ÑÐµÑÐžÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿ÐŸÐ·ÐžÑÐžÐž Ð² Ð¿ÐŸÐ»ÑÐ·Ñ ÐºÐŸÐœÑÐž ÐŽÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÑÑÐž ÑÐžÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐºÐŸÐœÑÐµÐœÑÐ° Ðž ÑÐ²ÐŸÐ±ÐŸÐŽÑ Ð² ÐžÐœÑÐµÑÐœÐµÑÐµ Ðž ÑÐ°Ð·ÑÐµÑÐ°Ð¹ÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ Tor Ð·Ð°ÑÐŸÐŽÐžÑÑ ÐœÐ° xyz.com. Ð¡Ð¿Ð°ÑÐžÐ±ÐŸ.\"<br />Ð ÑÐ»ÑÑÐ°Ðµ Ñ Ð±Ð°ÐœÐºÐ°ÐŒÐž Ðž ÐŽÑÑÐ³ÐžÐŒÐž ÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÑÐŒÐž Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐ°ÐŒÐž ÑÐ°ÐºÐ¶Ðµ ÑÐ°ÑÑÐŸ ÐœÐ°Ð±Ð»ÑÐŽÐ°ÐµÑÑÑ Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ (ÐµÑÐ»Ðž Ð±Ð°ÐœÐº Ð·ÐœÐ°ÐµÑ, ÑÑÐŸ Ð²Ñ ÐŸÐ±ÑÑÐœÐŸ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÐµÑÑ Ðº ÐžÑ ÑÑÐ»ÑÐ³Ð°ÐŒ ÐžÐ· ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐ°ÐœÑ Ðž Ð²ÐŽÑÑÐ³ Ð²Ñ Ð¿ÐŸÐŽÐºÐ»ÑÑÐ°ÐµÑÐµÑÑ ÑÐµÑÐµÐ· ÑÐµÑÑÐ°ÐœÑÐ»ÑÑÐŸÑ ÐœÐ° ÐŽÑÑÐ³ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÐµ ÐŒÐžÑÐ°, Ð²Ð°ÑÐ° ÑÑÑÑÐœÐ°Ñ Ð·Ð°Ð¿ÐžÑÑ Ðž ÑÑÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÑ ÐžÐ»Ðž Ð·Ð°ÐŒÐŸÑÐŸÐ¶ÐµÐœÑ). ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐŽÐºÐ»ÑÑÐžÑÑÑÑ Ðº onion-ÑÐ°Ð¹ÑÑ, ÑÐŒ. <a href=\"#onionservices-3\">Ð¯ ÐœÐµ ÐŒÐŸÐ³Ñ ÐŸÑÐºÑÑÑÑ X.onion!</a></p>" }, "tbb-7-1": { "id": "#tbb-7-1",

1 0

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

11 May '18

commit 321117aa729fa8340dbb94328728e6886d6848bf Author: Translation commit bot <translation(a)torproject.org> Date: Fri May 11 20:49:20 2018 +0000 Update translations for support-gettor --- ru.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru.json b/ru.json index 65995023b..7a0de4033 100644 --- a/ru.json +++ b/ru.json @@ -9,7 +9,7 @@ "id": "#gettor-2", "control": "gettor-2", "title": "ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ GetTor ÑÐµÑÐµÐ· ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ Ð¿ÐŸÑÑÑ.", - "description": "<p class=\"mb-3\">Send an email to gettor(a)torproject.org. Write your operating system (such as windows, MacOS (OS X), or linux) in the body of the message and send. GetTor will respond with an email containing links from which you can download Tor Browser, the cryptographic signature (needed for verifying the download) [link to glossary definition of cryptographic signature; instructions for verification], the fingerprint of the key used to make the signature, and the packageâs checksum. You may be offered a choice of \"32-bit\" or \"64-bit\" software: this depends on the model of the computer you are using; consult documentation about your computer to find out more.</p>" + "description": "<p class=\"mb-3\">ÐÐ°Ð¿ÐžÑÐžÑÐµ Ð¿ÐžÑÑÐŒÐŸ ÐœÐ° Ð°ÐŽÑÐµÑ gettor(a)torproject.org. Ð£ÐºÐ°Ð¶ÐžÑÐµ Ð² ÑÐµÐ»Ðµ Ð¿ÐžÑÑÐŒÐ° ÑÐ²ÐŸÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÑÑ ÑÐžÑÑÐµÐŒÑ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, windows, MacOS (OS X) ÐžÐ»Ðž linux) Ðž ÐŸÑÐ¿ÑÐ°Ð²ÑÑÐµ. GetTor ÐŸÑÐ²ÐµÑÐžÑ Ð¿ÐŸ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÐµ Ð¿ÐžÑÑÐŒÐŸÐŒ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐŒ ÑÑÑÐ»ÐºÐž, Ð¿ÐŸ ÐºÐŸÑÐŸÑÑÐŒ Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°ÑÐ°ÑÑ Tor Browser, ÐºÑÐžÐ¿ÑÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÑÑ Ð¿ÐŸÐŽÐ¿ÐžÑÑ (ÐœÐµÐŸÐ±ÑÐŸÐŽÐžÐŒÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÐ²ÐµÑÐºÐž Ð·Ð°Ð³ÑÑÐ·ÐºÐž) [ÑÑÑÐ»ÐºÐ° ÐœÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ Ð³Ð»ÐŸÑÑÐ°ÑÐžÑ ÐºÑÐžÐ¿ÑÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÐŸÐŽÐ¿ÐžÑÐž; ÐžÐœÑÑÑÑÐºÑÐžÐž Ð¿ÐŸ Ð¿ÑÐŸÐ²ÐµÑÐºÐµ], ÐŸÑÐ¿ÐµÑÐ°ÑÐŸÐº ÐºÐ»ÑÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ³ÐŸ ÐŽÐ»Ñ Ð¿ÐŸÐŽÐ¿ÐžÑÐž, Ðž ÐºÐŸÐœÑÑÐŸÐ»ÑÐœÑÐµ ÑÑÐŒÐŒÑ Ð¿Ð°ÐºÐµÑÐ°. ÐÐ°ÐŒ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœ Ð²ÑÐ±ÐŸÑ 32- ÐžÐ»Ðž 64-Ð±ÐžÑÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐ žÑ: ÑÑÐŸ Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÐŒÐŸÐŽÐµÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°; ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž ÐŸ Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, ÑÑÐŸÐ±Ñ ÑÐ·ÐœÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ.</p>" }, "gettor-3": { "id": "#gettor-3",

1 0

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

11 May '18

commit 108b378081e7a37669e81034a83dd55f8d508ca9 Author: Translation commit bot <translation(a)torproject.org> Date: Fri May 11 20:49:05 2018 +0000 Update translations for support-connecting --- ru.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru.json b/ru.json index 4d3e7f911..e8844d077 100644 --- a/ru.json +++ b/ru.json @@ -8,7 +8,7 @@ "connecting-2": { "id": "#connecting-2", "control": "connecting-2", - "title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.", + "title": "У меня проблемы с подключением к Tor и я не могу понять, что не так.", "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>" }, "connecting-3": {

1 0

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

11 May '18

commit 603db85bb53dd1dc71697735b2f4193fabaf9874 Author: Translation commit bot <translation(a)torproject.org> Date: Fri May 11 20:48:56 2018 +0000 Update translations for support-censorship --- ru.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ru.json b/ru.json index cf1b6877a..1947a5841 100644 --- a/ru.json +++ b/ru.json @@ -9,13 +9,13 @@ "id": "#censorship-2", "control": "censorship-2", "title": "ÐÐŸÐ¹ Ð»ÑÐ±ÐžÐŒÑÐ¹ ÑÐ°Ð¹Ñ Ð±Ð»ÐŸÐºÐžÑÑÐµÑ ÐŽÐŸÑÑÑÐ¿ ÑÐµÑÐµÐ· Tor.", - "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"#onionservices-3\">I cannot reach X.onion!</a></p>" + "description": "<p class=\"mb-3\">ÐÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ»ÑÑÐ°ÑÑ, ÑÑÐŸ Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÑÐµÑÐžÑÑ Ð²ÐµÐ±-ÑÐ°Ð¹Ñ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ð°ÐŒ ÐœÑÐ¶ÐµÐœ! ÐÐœÐŸÐ³ÐŽÐ° Ð²ÐµÐ±-ÑÐ°Ð¹ÑÑ Ð±Ð»ÐŸÐºÐžÑÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž ÐœÐµ ÐŒÐŸÐ³ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐ°Ð·ÐœÐžÑÑ ÐŒÐµÐ¶ÐŽÑ ÐŸÐ±ÑÑÐœÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ Tor Ðž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐžÐŒ ÑÑÐ°ÑÐžÐºÐŸÐŒ. ÐÐ°ÐžÐ»ÑÑÑÐžÐŒ ÐžÐ·Ð²ÐµÑÑÐœÑÐŒ ÐœÐ°ÐŒ Ð²ÑÑÐŸÐŽÐŸÐŒ ÐŽÐ»Ñ ÑÐ°Ð·Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor Ð±ÑÐŽÐµÑ ÑÐ»ÐµÐŽÑÑÑÐµÐµ: Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÐœÐ°ÐŽÐ»ÐµÐ¶ÐžÑ ÐœÐ°Ð¿ÑÑÐŒÑÑ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÐ°ÐŒ ÑÐ°Ð¹ÑÐ°. ÐÐœÐŸÐ³ÐŽÐ° ÑÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐ°ÐºÐŸÐ¹ ÑÑÑÐº:<br />\"ÐÑÐžÐ²ÐµÑ! Ð¯ Ð¿ÐŸÐ¿ÑÑÐ°Ð»ÑÑ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð²Ð°ÑÐµÐŒÑ ÑÐ°Ð¹ÑÑ xyz.com ÑÐµÑÐµÐ· Tor Browser Ðž ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐžÐ», ÑÑÐŸ Ð²Ñ ÐœÐµ ÑÐ°Ð·ÑÐµÑÐ°ÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐ Œ Tor Ð·Ð°ÑÐŸÐŽÐžÑÑ ÐœÐ° ÐœÐµÐ³ÐŸ. Ð¯ ÐœÐ°ÑÑÐŸÑÑÐµÐ»ÑÐœÐŸ Ð¿ÑÐžÐ·ÑÐ²Ð°Ñ Ð²Ð°Ñ Ð¿ÐµÑÐµÑÐŒÐŸÑÑÐµÑÑ ÑÑÐŸ ÑÐµÑÐµÐœÐžÐµ: Tor ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð»ÑÐŽÑÐŒÐž Ð²ÐŸ Ð²ÑÐµÐŒ ÐŒÐžÑÐµ ÐŽÐ»Ñ Ð·Ð°ÑÐžÑÑ ÐžÑ ÐºÐŸÐœÑÐžÐŽÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÑÑÐž Ðž Ð±ÐŸÑÑÐ±Ñ Ñ ÑÐµÐœÐ·ÑÑÐŸÐ¹. ÐÐ»ÐŸÐºÐžÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Tor, Ð²Ñ ÐœÐ°Ð²ÐµÑÐœÑÐºÐ° Ð±Ð»ÐŸÐºÐžÑÑÐµÑÐµ Ð»ÑÐŽÐµÐ¹ Ð² ÑÐµÐ¿ÑÐµÑÑÐžÐ²ÐœÑÑ ÑÑÑÐ°ÐœÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÑÐ¹ ÐžÐœÑÐµÑÐœÐµÑ, Ð¶ÑÑÐœÐ°Ð»ÐžÑÑÐŸÐ² Ðž ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ Ð·Ð°ÑÐžÑÐžÑÑ ÑÐµÐ±Ñ ÐŸÑ ÑÐ»ÐµÐ¶ÐºÐž Ðž ÐŸÑÐ²ÐµÐŽÐŸÐŒÐžÑÐµÐ»ÐµÐ¹, Ð°ÐºÑÐžÐ²ÐžÑÑÐŸÐ² Ðž ÐŸÐ±ÑÑÐœÑÑ Ð»ÑÐŽÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑÑÑ ÐŸÑÐºÐ°Ð·Ð°ÑÑÑÑ ÐŸÑ ÐžÐœÐ²Ð°Ð·ÐžÐ²ÐœÐŸÐ³ÐŸ ÐŸÑÑÐ»ÐµÐ¶ÐžÐ²Ð°ÐœÐžÑ ÑÑÐµÑÑÐµÐ¹ ÑÑÐŸÑÐŸÐœÐŸÐ¹. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°Ð¹ÑÐµÑÑ ÑÐµÑÐžÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿ÐŸÐ·ÐžÑÐžÐž Ð² Ð¿ÐŸÐ»ÑÐ·Ñ ÐºÐŸÐœÑÐž ÐŽÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÑÑÐž ÑÐžÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐºÐŸÐœÑÐµÐœÑÐ° Ðž ÑÐ²ÐŸÐ±ÐŸÐŽÑ Ð² ÐžÐœÑÐµÑÐœÐµÑÐµ Ðž ÑÐ°Ð·ÑÐµÑÐ°Ð¹ÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ Tor Ð·Ð°ÑÐŸÐŽÐžÑÑ ÐœÐ° xyz.com. Ð¡Ð¿Ð°ÑÐžÐ±ÐŸ.\"<br />Ð ÑÐ»ÑÑÐ°Ðµ Ñ Ð±Ð°ÐœÐºÐ°ÐŒÐž Ðž ÐŽÑÑÐ³ÐžÐŒÐž ÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÑÐŒÐž Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐ°ÐŒÐž ÑÐ°ÐºÐ¶Ðµ ÑÐ°ÑÑÐŸ ÐœÐ°Ð±Ð»ÑÐŽÐ°ÐµÑÑÑ Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ (ÐµÑÐ»Ðž Ð±Ð°ÐœÐº Ð·ÐœÐ°ÐµÑ, ÑÑÐŸ Ð²Ñ ÐŸÐ±ÑÑÐœÐŸ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÐµÑÑ Ðº ÐžÑ ÑÑÐ»ÑÐ³Ð°ÐŒ ÐžÐ· ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐ°ÐœÑ Ðž Ð²ÐŽÑÑÐ³ Ð²Ñ Ð¿ÐŸÐŽÐºÐ»ÑÑÐ°ÐµÑÐµÑÑ ÑÐµÑÐµÐ· ÑÐµÑÑÐ°ÐœÑÐ»ÑÑÐŸÑ ÐœÐ° ÐŽÑÑÐ³ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÐµ ÐŒÐžÑÐ°, Ð²Ð°ÑÐ° ÑÑÑÑÐœÐ°Ñ Ð·Ð°Ð¿ÐžÑÑ Ðž ÑÑÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÑ ÐžÐ»Ðž Ð·Ð°ÐŒÐŸÑÐŸÐ¶ÐµÐœÑ). ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐŽÐºÐ»ÑÑÐžÑÑÑÑ Ðº onion-ÑÐ°Ð¹ÑÑ, ÑÐŒ. <a href=\"#onionservices-3\">Ð¯ ÐœÐµ ÐŒÐŸÐ³Ñ ÐŸÑÐºÑÑÑÑ X.onion!</a></p>" }, "censorship-3": { "id": "#censorship-3", "control": "censorship-3", "title": "ÐÐ°Ðº Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Tor, ÐµÑÐ»Ðž torproject.org Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°Ðœ?", - "description": "<p class=\"mb-3\">ÐÑÐ»Ðž ÐÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°ÑÐ°ÑÑ Tor ÑÐµÑÐµÐ· ÐœÐ°Ñ <mark><a href=\"https://www.torproject.org\">ÑÐ°Ð¹Ñ</a></mark>, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐºÐŸÐ¿ÐžÑ Tor ÑÐµÑÐµÐ· GetTor. GetTor - ÑÑÐŸ ÑÑÐ»ÑÐ³Ð°, ÐºÐŸÑÐŸÑÐ°Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÑÐ²ÐµÑÐ°ÐµÑ ÐœÐ° ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ ÑÑÑÐ»ÐºÐ°ÐŒÐž ÐœÐ° Ð¿ÐŸÑÐ»ÐµÐŽÐœÑÑ Ð²ÐµÑÑÐžÑ Tor Browser, ÑÐ°Ð·ÐŒÐµÑÐµÐœÐœÑÐµ Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ ÐŒÐµÑÑÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐµÐœÐµÐµ Ð²ÐµÑÐŸÑÑÐœÐŸ Ð¿ÐŸÐŽÐ²ÐµÑÐ³Ð°ÑÑÑÑ ÑÐµÐœÐ·ÑÑÐµ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº Dropbox, Google ÐÐžÑÐº Ðž Github.</p>" + "description": "<p class=\"mb-3\">ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°ÑÐ°ÑÑ Tor ÑÐµÑÐµÐ· ÐœÐ°Ñ <mark><a href=\"https://www.torproject.org\">ÑÐ°Ð¹Ñ</a></mark>, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐºÐŸÐ¿ÐžÑ Tor ÑÐµÑÐµÐ· GetTor. GetTor - ÑÑÐŸ ÑÑÐ»ÑÐ³Ð°, ÐºÐŸÑÐŸÑÐ°Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÑÐ²ÐµÑÐ°ÐµÑ ÐœÐ° ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ ÑÑÑÐ»ÐºÐ°ÐŒÐž ÐœÐ° Ð¿ÐŸÑÐ»ÐµÐŽÐœÑÑ Ð²ÐµÑÑÐžÑ Tor Browser, ÑÐ°Ð·ÐŒÐµÑÐµÐœÐœÑÐµ Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ ÐŒÐµÑÑÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐµÐœÐµÐµ Ð²ÐµÑÐŸÑÑÐœÐŸ Ð¿ÐŸÐŽÐ²ÐµÑÐ³Ð°ÑÑÑÑ ÑÐµÐœÐ·ÑÑÐµ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº Dropbox, Google ÐÐžÑÐº Ðž Github.</p>" }, "censorship-4": { "id": "#censorship-4", @@ -26,7 +26,7 @@ "censorship-5": { "id": "#censorship-5", "control": "censorship-5", - "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "title": "Ð£ ÐŒÐµÐœÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ Ñ Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœÐžÐµÐŒ Ðº Tor Ðž Ñ ÐœÐµ ÐŒÐŸÐ³Ñ Ð¿ÐŸÐœÑÑÑ, ÑÑÐŸ ÐœÐµ ÑÐ°Ðº.", "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>" }, "censorship-6": {

1 0