- tor-commits - lists.torproject.org

[tor/master] Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair() invocation
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 7363eae13cb8febd85923957de19e2de7c186cea Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 17:46:43 2011 -0500 Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair() invocation In Tor 0.2.2, we never need the event base to be notifiable, since we don't call it from other threads. This is a workaround for bug 4457, which is not actually a Tor bug IMO. --- changes/bug4457 | 8 ++++++++ src/common/compat_libevent.c | 13 ++++++++++++- 2 files changed, 20 insertions(+), 1 deletions(-) diff --git a/changes/bug4457 b/changes/bug4457 new file mode 100644 index 0000000..d3d9eb3 --- /dev/null +++ b/changes/bug4457 @@ -0,0 +1,8 @@ + o Minor bugfixes: + - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so + that it doesn't attempt to allocate a socketpair. This could cause + some problems on windows systems with overzealous firewalls. Fix for + bug 4457; workaround for Libevent versions 2.0.1-alpha through + 2.0.15-stable. + + diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c index 6d89be8..3e35e09 100644 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@ -177,7 +177,18 @@ tor_libevent_initialize(void) #endif #ifdef HAVE_EVENT2_EVENT_H - the_event_base = event_base_new(); + { + struct event_config *cfg = event_config_new(); + + /* In 0.2.2, we don't use locking at all. Telling Libevent not to try to + * turn it on can avoid a needless socketpair() attempt. + */ + event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK); + + the_event_base = event_base_new_with_config(cfg); + + event_config_free(cfg); + } #else the_event_base = event_init(); #endif

1 0

[tor/master] Detect failure from event_init() or event_base_new_with_config()
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 0f6c02161793fa1022fe721ed9c1aac3538294b3 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 17:53:45 2011 -0500 Detect failure from event_init() or event_base_new_with_config() --- changes/bug4457 | 1 + src/common/compat_libevent.c | 6 ++++++ 2 files changed, 7 insertions(+), 0 deletions(-) diff --git a/changes/bug4457 b/changes/bug4457 index d3d9eb3..fe7c95f 100644 --- a/changes/bug4457 +++ b/changes/bug4457 @@ -5,4 +5,5 @@ bug 4457; workaround for Libevent versions 2.0.1-alpha through 2.0.15-stable. + - Detect failure to initialize Libevent. Better detection for bug 4457. diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c index 3e35e09..ddb2da6 100644 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@ -179,6 +179,7 @@ tor_libevent_initialize(void) #ifdef HAVE_EVENT2_EVENT_H { struct event_config *cfg = event_config_new(); + tor_assert(cfg); /* In 0.2.2, we don't use locking at all. Telling Libevent not to try to * turn it on can avoid a needless socketpair() attempt. @@ -193,6 +194,11 @@ tor_libevent_initialize(void) the_event_base = event_init(); #endif + if (!the_event_base) { + log_err(LD_GENERAL, "Unable to initialize Libevent: cannot continue."); + exit(1); + } + #if defined(HAVE_EVENT_GET_VERSION) && defined(HAVE_EVENT_GET_METHOD) /* Making this a NOTICE for now so we can link bugs to a libevent versions * or methods better. */

1 0

[tor/master] Merge remote-tracking branch 'public/bug4457_022' into bug4457_master
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit cf8117136c1b206e727d582a4c378ce53e058414 Merge: 8592126 0f6c021 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 17:59:42 2011 -0500 Merge remote-tracking branch 'public/bug4457_022' into bug4457_master Conflicts: src/common/compat_libevent.c Resolving conflict by not taking 7363eae13cb8 ("Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair() invocation"): in Tor 0.2.3.x, we _do_ sometimes use notifiable event bases. changes/bug4457 | 9 +++++++++ src/common/compat_libevent.c | 6 ++++++ 2 files changed, 15 insertions(+), 0 deletions(-) diff --cc src/common/compat_libevent.c index 3201738,ddb2da6..c533461 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@@ -196,25 -179,12 +196,26 @@@ tor_libevent_initialize(tor_libevent_cf #ifdef HAVE_EVENT2_EVENT_H { struct event_config *cfg = event_config_new(); + tor_assert(cfg); - /* In 0.2.2, we don't use locking at all. Telling Libevent not to try to - * turn it on can avoid a needless socketpair() attempt. - */ - event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK); +#if defined(MS_WINDOWS) && defined(USE_BUFFEREVENTS) + if (! torcfg->disable_iocp) { + evthread_use_windows_threads(); + event_config_set_flag(cfg, EVENT_BASE_FLAG_STARTUP_IOCP); + using_iocp_bufferevents = 1; + } +#endif + +#if defined(LIBEVENT_VERSION_NUMBER) && LIBEVENT_VERSION_NUMBER >= V(2,0,7) + if (torcfg->num_cpus > 0) + event_config_set_num_cpus_hint(cfg, torcfg->num_cpus); +#endif + +#if LIBEVENT_VERSION_NUMBER >= V(2,0,9) + /* We can enable changelist support with epoll, since we don't give + * Libevent any dup'd fds. This lets us avoid some syscalls. */ + event_config_set_flag(cfg, EVENT_BASE_FLAG_EPOLL_USE_CHANGELIST); +#endif the_event_base = event_base_new_with_config(cfg);

1 0

[tor/master] Disable IOCP and retry event_base_new_with_config once on failure
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 7be50c26e8b2ec0bd0121d5e8b2dc55de977cf5a Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 18:12:29 2011 -0500 Disable IOCP and retry event_base_new_with_config once on failure This is a fancier bug4457 workaround for 0.2.3. In 0.2.2, we could just tell Libevent "Don't enable locking!" so it wouldn't try to make the event_base notifiable. But for IOCP, we need a notifiable base. (Eventually, we'll want a notifiable base for other stuff, like multithreaded crypto.) So the solution is to try a full-featured initialization, and then retry with all the options turned off if that fails. --- changes/bug4457_master | 6 ++++++ src/common/compat_libevent.c | 37 ++++++++++++++++++++++++++++++++++++- 2 files changed, 42 insertions(+), 1 deletions(-) diff --git a/changes/bug4457_master b/changes/bug4457_master new file mode 100644 index 0000000..d394643 --- /dev/null +++ b/changes/bug4457_master @@ -0,0 +1,6 @@ + o Minor features: + - When we fail to initialize Libevent, retry with IOCP disabled so we + don't need to turn on multi-threading support in Libevent, which in + turn requires a working socketpair(). This is a workaround for bug + 4457, which affects Libevent versions from 2.0.1-alpha through + 2.0.15-stable. diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c index c533461..7a28c9b 100644 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@ -195,7 +195,14 @@ tor_libevent_initialize(tor_libevent_cfg *torcfg) #ifdef HAVE_EVENT2_EVENT_H { - struct event_config *cfg = event_config_new(); + int attempts = 0; + int using_threads; + struct event_config *cfg; + + retry: + ++attempts; + using_threads = 0; + cfg = event_config_new(); tor_assert(cfg); #if defined(MS_WINDOWS) && defined(USE_BUFFEREVENTS) @@ -203,9 +210,18 @@ tor_libevent_initialize(tor_libevent_cfg *torcfg) evthread_use_windows_threads(); event_config_set_flag(cfg, EVENT_BASE_FLAG_STARTUP_IOCP); using_iocp_bufferevents = 1; + using_threads = 1; + } else { + using_iocp_bufferevents = 0; } #endif + if (!using_threads) { + /* Telling Libevent not to try to turn locking on can avoid a needless + * socketpair() attempt. */ + event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK); + } + #if defined(LIBEVENT_VERSION_NUMBER) && LIBEVENT_VERSION_NUMBER >= V(2,0,7) if (torcfg->num_cpus > 0) event_config_set_num_cpus_hint(cfg, torcfg->num_cpus); @@ -220,6 +236,25 @@ tor_libevent_initialize(tor_libevent_cfg *torcfg) the_event_base = event_base_new_with_config(cfg); event_config_free(cfg); + + if (using_threads && the_event_base == NULL && attempts < 2) { + /* This could be a socketpair() failure, which can happen sometimes on + * windows boxes with obnoxious firewall rules. Downgrade and try + * again. */ +#if defined(MS_WINDOWS) && defined(USE_BUFFEREVENTS) + if (torcfg->disable_iocp == 0) { + log_warn(LD_GENERAL, "Unable to initialize Libevent. Trying again with " + "IOCP disabled."); + } else +#endif + { + log_warn(LD_GENERAL, "Unable to initialize Libevent. Trying again."); + } + + torcfg->disable_iocp = 1; + goto retry; + } + } #else the_event_base = event_init();

1 0

[tor/master] Merge branch 'bug4457_022' into maint-0.2.2
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 5a02406ae0d8059d3b0bbff51d37fcb92650274b Merge: 5bea660 0f6c021 Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 16 16:22:47 2011 -0500 Merge branch 'bug4457_022' into maint-0.2.2 changes/bug4457 | 9 +++++++++ src/common/compat_libevent.c | 19 ++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletions(-)

1 0

[tor/maint-0.2.2] Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair() invocation
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 7363eae13cb8febd85923957de19e2de7c186cea Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 17:46:43 2011 -0500 Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair() invocation In Tor 0.2.2, we never need the event base to be notifiable, since we don't call it from other threads. This is a workaround for bug 4457, which is not actually a Tor bug IMO. --- changes/bug4457 | 8 ++++++++ src/common/compat_libevent.c | 13 ++++++++++++- 2 files changed, 20 insertions(+), 1 deletions(-) diff --git a/changes/bug4457 b/changes/bug4457 new file mode 100644 index 0000000..d3d9eb3 --- /dev/null +++ b/changes/bug4457 @@ -0,0 +1,8 @@ + o Minor bugfixes: + - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so + that it doesn't attempt to allocate a socketpair. This could cause + some problems on windows systems with overzealous firewalls. Fix for + bug 4457; workaround for Libevent versions 2.0.1-alpha through + 2.0.15-stable. + + diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c index 6d89be8..3e35e09 100644 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@ -177,7 +177,18 @@ tor_libevent_initialize(void) #endif #ifdef HAVE_EVENT2_EVENT_H - the_event_base = event_base_new(); + { + struct event_config *cfg = event_config_new(); + + /* In 0.2.2, we don't use locking at all. Telling Libevent not to try to + * turn it on can avoid a needless socketpair() attempt. + */ + event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK); + + the_event_base = event_base_new_with_config(cfg); + + event_config_free(cfg); + } #else the_event_base = event_init(); #endif

1 0

[tor/maint-0.2.2] Detect failure from event_init() or event_base_new_with_config()
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 0f6c02161793fa1022fe721ed9c1aac3538294b3 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 14 17:53:45 2011 -0500 Detect failure from event_init() or event_base_new_with_config() --- changes/bug4457 | 1 + src/common/compat_libevent.c | 6 ++++++ 2 files changed, 7 insertions(+), 0 deletions(-) diff --git a/changes/bug4457 b/changes/bug4457 index d3d9eb3..fe7c95f 100644 --- a/changes/bug4457 +++ b/changes/bug4457 @@ -5,4 +5,5 @@ bug 4457; workaround for Libevent versions 2.0.1-alpha through 2.0.15-stable. + - Detect failure to initialize Libevent. Better detection for bug 4457. diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c index 3e35e09..ddb2da6 100644 --- a/src/common/compat_libevent.c +++ b/src/common/compat_libevent.c @@ -179,6 +179,7 @@ tor_libevent_initialize(void) #ifdef HAVE_EVENT2_EVENT_H { struct event_config *cfg = event_config_new(); + tor_assert(cfg); /* In 0.2.2, we don't use locking at all. Telling Libevent not to try to * turn it on can avoid a needless socketpair() attempt. @@ -193,6 +194,11 @@ tor_libevent_initialize(void) the_event_base = event_init(); #endif + if (!the_event_base) { + log_err(LD_GENERAL, "Unable to initialize Libevent: cannot continue."); + exit(1); + } + #if defined(HAVE_EVENT_GET_VERSION) && defined(HAVE_EVENT_GET_METHOD) /* Making this a NOTICE for now so we can link bugs to a libevent versions * or methods better. */

1 0

[tor/maint-0.2.2] Merge branch 'bug4457_022' into maint-0.2.2
by nickm＠torproject.org 16 Nov '11

16 Nov '11

commit 5a02406ae0d8059d3b0bbff51d37fcb92650274b Merge: 5bea660 0f6c021 Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 16 16:22:47 2011 -0500 Merge branch 'bug4457_022' into maint-0.2.2 changes/bug4457 | 9 +++++++++ src/common/compat_libevent.c | 19 ++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletions(-)

1 0

[translation/tsum] Update translations for tsum
by translation＠torproject.org 16 Nov '11

16 Nov '11

commit c2345f4c80bf0a8b785406e85a02676a8210a8f6 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 16 21:15:05 2011 +0000 Update translations for tsum --- zh/tsum.po | 32 +++++++++++++++++++++++--------- 1 files changed, 23 insertions(+), 9 deletions(-) diff --git a/zh/tsum.po b/zh/tsum.po index 24a5d8c..5cb4966 100644 --- a/zh/tsum.po +++ b/zh/tsum.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2011-11-05 17:16+0000\n" -"PO-Revision-Date: 2011-11-16 20:37+0000\n" +"PO-Revision-Date: 2011-11-16 21:14+0000\n" "Last-Translator: LEMONed <lemoned(a)live.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -384,8 +384,8 @@ msgid "" "*Message Log* and select the *Advanced* tab. It may be that Tor won't " "connect because:" msgstr "" -"如果你的普通互联网连接运作正常，而 Tor 却无法连接到网络，请尝试以下步骤；打开 Vidalia 的设置面板，点击 *Message Log* 并选择" -" *Advanced* 标签页。Tor 无法连接到网络也许是因为：" +"如果你的普通互联网连接运作正常，而 Tor 却无法连接到网络，请尝试以下步骤；打开 Vidalia 的设置面板，点击 *消息日志* 并选择 *高级* " +"标签页。Tor 无法连接到网络也许是因为：" #. type: Plain text #: en/tsum.text:178 @@ -405,9 +405,8 @@ msgid "" "*Network*, and tick the box that says *My firewall only lets me connect\n" "to certain ports*. \n" msgstr "" -"**你受限于防火墙软件**：让 Tor 仅尝试 80 和 443 端口，打开 Vidalia 控制面板，点击 " -"*Settings*，*Network*，然后选中 *My firewall only lets me connect to certain " -"ports* 的选项框。\n" +"**你受限于防火墙软件**：让 Tor 仅尝试 80 和 443 端口，打开 Vidalia 控制面板，点击 *设置*，*网络*，然后选中 " +"*我的防火墙只允许我连接到指定端口* 的选项框。\n" #. type: Plain text #: en/tsum.text:187 @@ -471,17 +470,17 @@ msgstr "" msgid "" "The steps below assume you have a functional Tor/Vidalia configuration, and " "you have found a list of HTTPS, SOCKS4, or SOCKS5 proxies." -msgstr "" +msgstr "以下步骤假设你已有一套配置正确的 Tor/Vidalia ，并找到了一份 HTTPS、SOCKS4 或 SOCKS5 代理服务器的列表。" #. type: Bullet: '1. ' #: en/tsum.text:235 msgid "Open the Vidalia control panel, click on *Settings*." -msgstr "" +msgstr "打开 Vidalia 控制面板，点击 *设置*。" #. type: Bullet: '2. ' #: en/tsum.text:235 msgid "Click *Network*. Select *I use a proxy to access the Internet*." -msgstr "" +msgstr "点击 *网络*，选择 *我使用代理服务器连接到网络*。" #. type: Plain text #: en/tsum.text:235 @@ -497,6 +496,11 @@ msgid "" "7. Push the *OK* button. Vidalia and Tor are now configured to use a\n" "proxy to access the rest of the Tor network.\n" msgstr "" +"3. 在 *Address* 一栏里填上代理服务器的地址，这可以是主机名或IP地址。\n" +"4. 填上代理服务器的端口。\n" +"5. 一般来说，你并不需要用户名和密码。如果需要，则也相应地填上。\n" +"6. 选择你在使用的代理服务器的 *Type*，可以是 HTTP/HTTPS，SOCKS4 或 SOCKS5。\n" +"7. 点击 *OK* 按钮。Vidalia 和 Tor 现已成功配置为使用代理服务器连接到 Tor 网络。\n" #. type: Plain text #: en/tsum.text:240 @@ -582,6 +586,9 @@ msgid "" "case, you will need to close the old Vidalia and Tor before you can run\n" "this one.\n" msgstr "" +"**Vidalia 和 Tor 已在运行**：\n" +"举个例子，假如你已安装过 Vidalia 软件包而你现在正尝试运行 Tor 浏览器软件包，这种情况就有可能发生。\n" +"这样的话你将需要先关闭旧版的 Vidalia 和 Tor。\n" #. type: Plain text #: en/tsum.text:294 @@ -594,6 +601,11 @@ msgid "" "is unable to restart Tor for you; go into your process or task manager,\n" "and terminate the Tor process. Then use Vidalia to restart Tor.\n" msgstr "" +"**Vidalia 崩溃了，但 Tor 仍在运行**：\n" +"如果提示输入控制密码的对话框里有一个“重置”按钮，\n" +"你可以点击该按钮，Vidalia 会以一个新的随机控制密码重启 Tor。\n" +"如果你没有看到“重置”按钮，或者 Vidalia 无法重启 Tor，\n" +"请前往你的进程或任务管理器，终止 Tor 的进程。然后再用 Vidalia 来重启 Tor。\n" #. type: Plain text #: en/tsum.text:298 @@ -602,6 +614,8 @@ msgid "" "[FAQ](https://torproject.org/docs/faq.html#VidaliaPassword) on the Tor " "Project website." msgstr "" +"要了解更多，请参阅 Tor Project 网站上的 " +"[FAQ](https://torproject.org/docs/faq.html#VidaliaPassword)。" #. type: Plain text #: en/tsum.text:303

1 0

[translation/tsum] Update translations for tsum
by translation＠torproject.org 16 Nov '11

16 Nov '11

commit efa4ebbdb4fe251613ec6365501f876c4ac3e42d Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 16 20:45:04 2011 +0000 Update translations for tsum --- zh/tsum.po | 19 +++++++++++++++---- 1 files changed, 15 insertions(+), 4 deletions(-) diff --git a/zh/tsum.po b/zh/tsum.po index 4dc70ad..24a5d8c 100644 --- a/zh/tsum.po +++ b/zh/tsum.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2011-11-05 17:16+0000\n" -"PO-Revision-Date: 2011-11-16 20:13+0000\n" +"PO-Revision-Date: 2011-11-16 20:37+0000\n" "Last-Translator: LEMONed <lemoned(a)live.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -357,6 +357,9 @@ msgid "" "[https://check.torproject.org/](https://check.torproject.org/). You can now " "browse the Internet through Tor." msgstr "" +"当你运行 Tor 浏览器软件包，你会首先看到 Vidalia 启动并把你接入到 Tor " +"网络。之后你会看到一个浏览器显示出[https://check.torproject.org/](https://check.torproject.o…" +" Tor。现在你可以开始通过 Tor 来浏览互联网了。" #. type: Plain text #: en/tsum.text:163 @@ -364,7 +367,7 @@ msgstr "" msgid "" "*Please note that it is important that you use the browser that comes\n" "with the bundle, and not your own browser.*\n" -msgstr "" +msgstr "*请注意，你必须使用软件包里的浏览器，而不是你自己的浏览器。这至关重要。*\n" #. type: Plain text #: en/tsum.text:169 @@ -381,6 +384,8 @@ msgid "" "*Message Log* and select the *Advanced* tab. It may be that Tor won't " "connect because:" msgstr "" +"如果你的普通互联网连接运作正常，而 Tor 却无法连接到网络，请尝试以下步骤；打开 Vidalia 的设置面板，点击 *Message Log* 并选择" +" *Advanced* 标签页。Tor 无法连接到网络也许是因为：" #. type: Plain text #: en/tsum.text:178 @@ -389,7 +394,7 @@ msgid "" "**Your system clock is off**: Make sure that the date and time on your\n" "system is correct, and restart Tor. You may need to synchronize your\n" "system clock with an Internet time server. \n" -msgstr "" +msgstr "**你的系统时钟不准确**：请确保你的系统中的日期与时间正确，然后重启 Tor。你也许需要把系统时钟与某台网络时间服务器进行同步。\n" #. type: Plain text #: en/tsum.text:183 @@ -400,6 +405,9 @@ msgid "" "*Network*, and tick the box that says *My firewall only lets me connect\n" "to certain ports*. \n" msgstr "" +"**你受限于防火墙软件**：让 Tor 仅尝试 80 和 443 端口，打开 Vidalia 控制面板，点击 " +"*Settings*，*Network*，然后选中 *My firewall only lets me connect to certain " +"ports* 的选项框。\n" #. type: Plain text #: en/tsum.text:187 @@ -408,7 +416,7 @@ msgid "" "**Your anti-virus program is blocking Tor**: Make sure that your\n" "anti-virus program is not preventing Tor from making network\n" "connections.\n" -msgstr "" +msgstr "**你的反病毒软件正在阻挡 Tor**：请确保你的反病毒软件没有阻止 Tor 进行网络连接。\n" #. type: Plain text #: en/tsum.text:191 @@ -417,6 +425,8 @@ msgid "" "(ISP) is blocking Tor. Very often this can be worked around with **Tor " "bridges**, hidden relays that aren't as easy to block." msgstr "" +"如果 Tor 仍然不能工作，那么可能是你的互联网服务提供商（ISP）正在阻挡 Tor。这通常可以使用 **Tor " +"桥接**，不易被阻挡的隐蔽中继服务器，来绕开阻挡。" #. type: Plain text #: en/tsum.text:195 @@ -440,6 +450,7 @@ msgid "" "guarantee that the bridge you are using now will work tomorrow, so you " "should make a habit of updating your list of bridges every so often." msgstr "" +"配置一个以上的桥接地址，能让 Tor 的连接在某些桥接无法访问时更加稳定。你无法保证今天能使用的桥接明天仍然能用，所以你应该养成时常更新桥接列表的习惯。" #. type: Plain text #: en/tsum.text:214

1 0