February 2014 - tor-commits - lists.torproject.org

[translation/tor-launcher-network-settings_completed] Update translations for tor-launcher-network-settings_completed
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 09a5eedec48568251a2132f8d104ec862ed1f48c Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 18:45:39 2014 +0000 Update translations for tor-launcher-network-settings_completed --- ru/network-settings.dtd | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/ru/network-settings.dtd b/ru/network-settings.dtd index 8940e07..68a6b25 100644 --- a/ru/network-settings.dtd +++ b/ru/network-settings.dtd @@ -22,7 +22,9 @@ <!ENTITY torSettings.firewallQuestion "Защищено ли соединение брандмауэром, разрешающим связь только через некоторые порты?"> <!ENTITY torSettings.firewallHelp "Если вы не уверены как отвечать, выберите нет. Если возникнут проблемы соединения с сетью Tor, измените эту настройку."> <!ENTITY torSettings.enterFirewall "Введите список портов через запятую, которые брандмауэр не блокирует."> -<!ENTITY torSettings.bridgeQuestion "Если интернет-соединение этого компьютера цензурируется, вам понадобится использовать ретрансляторы типа мост.&#160; Если нет, просто нажмите Соединение."> +<!ENTITY torSettings.bridgeQuestion "Ваш провайдер (ISP) блокирует или как-либо цензурирует подключения к сети Tor?"> +<!ENTITY torSettings.bridgeHelp "Если вы не знаете, как ответить на этот вопрос, выбирайте Нет.&#160; Если вы выберете Да, вас попросят настроить мосты Tor, которые являются неопубликованными маршрутизаторами, что затрудняет их блокировку."> +<!ENTITY torSettings.bridgeSettingsPrompt "Вы можете использовать стандартный набор мостов или получить и ввести список мостов вручную.">  @@ -44,13 +46,15 @@ <!ENTITY torsettings.firewall.checkbox "Мой сетевой экран позволяет мне подключиться только к определенным портам"> <!ENTITY torsettings.firewall.allowedPorts "Разрешенные порты:"> <!ENTITY torsettings.useBridges.checkbox "Мой провайдер блокирует доступ к сети Tor"> +<!ENTITY torsettings.useBridges.default "По умолчанию использовать мосты типа"> +<!ENTITY torsettings.useBridges.custom "Использовать мосты, настроенные вручную"> <!ENTITY torsettings.useBridges.label "Введите один или несколько ретрансляторов типа мост (один на строку)"> -<!ENTITY torsettings.useBridges.placeholder "address:port ИЛИ transport address:port"> +<!ENTITY torsettings.useBridges.placeholder "введите адрес:порт"> <!ENTITY torsettings.copyLog "Скопировать журнал Tor в буфер обмена"> <!ENTITY torsettings.bridgeHelpTitle "Помощь по ретрансляторам типа мост"> <!ENTITY torsettings.bridgeHelp1 "Если вы не можете подключиться к сети Tor, возможно ваш провайдер (ISP) или иная организация блокирует Tor.&#160; Часто эту проблему можно обойти при помощи мостов Tor, не перечисленных в публичных списках, которые сложнее заблокировать."> -<!ENTITY torsettings.bridgeHelp1B "Существует 3 способа получить адреса мостов:"> +<!ENTITY torsettings.bridgeHelp1B "Вы можете использовать стандартный набор мостов или получить и ввести список мостов вручную при помощи одного из этих трёх методов:"> <!ENTITY torsettings.bridgeHelp2Heading "Из Веб"> <!ENTITY torsettings.bridgeHelp2 "Откройте в веб-браузере https://bridges.torproject.org"> <!ENTITY torsettings.bridgeHelp3Heading "Через автоответчик электронной почты">

1 0

[translation/tor-launcher-network-settings] Update translations for tor-launcher-network-settings
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 1ff405777d435effa71884dc100ed6c558b94bcd Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 18:45:36 2014 +0000 Update translations for tor-launcher-network-settings --- ru/network-settings.dtd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/ru/network-settings.dtd b/ru/network-settings.dtd index 10e23a9..68a6b25 100644 --- a/ru/network-settings.dtd +++ b/ru/network-settings.dtd @@ -22,9 +22,9 @@ <!ENTITY torSettings.firewallQuestion "Защищено ли соединение брандмауэром, разрешающим связь только через некоторые порты?"> <!ENTITY torSettings.firewallHelp "Если вы не уверены как отвечать, выберите нет. Если возникнут проблемы соединения с сетью Tor, измените эту настройку."> <!ENTITY torSettings.enterFirewall "Введите список портов через запятую, которые брандмауэр не блокирует."> -<!ENTITY torSettings.bridgeQuestion "Does your Internet Service Provider (ISP) block or otherwise censor connections to the Tor Network?"> -<!ENTITY torSettings.bridgeHelp "If you are not sure how to answer this question, choose No.&#160; If you choose Yes, you will be asked to configure Tor Bridges, which are unlisted relays that make it more difficult to block connections to the Tor Network."> -<!ENTITY torSettings.bridgeSettingsPrompt "You may use the default set of bridges or you may obtain and enter a custom set of bridges."> +<!ENTITY torSettings.bridgeQuestion "Ваш провайдер (ISP) блокирует или как-либо цензурирует подключения к сети Tor?"> +<!ENTITY torSettings.bridgeHelp "Если вы не знаете, как ответить на этот вопрос, выбирайте Нет.&#160; Если вы выберете Да, вас попросят настроить мосты Tor, которые являются неопубликованными маршрутизаторами, что затрудняет их блокировку."> +<!ENTITY torSettings.bridgeSettingsPrompt "Вы можете использовать стандартный набор мостов или получить и ввести список мостов вручную.">  @@ -46,15 +46,15 @@ <!ENTITY torsettings.firewall.checkbox "Мой сетевой экран позволяет мне подключиться только к определенным портам"> <!ENTITY torsettings.firewall.allowedPorts "Разрешенные порты:"> <!ENTITY torsettings.useBridges.checkbox "Мой провайдер блокирует доступ к сети Tor"> -<!ENTITY torsettings.useBridges.default "Use Default Bridges of Type"> -<!ENTITY torsettings.useBridges.custom "Use Custom Bridges"> +<!ENTITY torsettings.useBridges.default "По умолчанию использовать мосты типа"> +<!ENTITY torsettings.useBridges.custom "Использовать мосты, настроенные вручную"> <!ENTITY torsettings.useBridges.label "Введите один или несколько ретрансляторов типа мост (один на строку)"> -<!ENTITY torsettings.useBridges.placeholder "type address:port"> +<!ENTITY torsettings.useBridges.placeholder "введите адрес:порт"> <!ENTITY torsettings.copyLog "Скопировать журнал Tor в буфер обмена"> <!ENTITY torsettings.bridgeHelpTitle "Помощь по ретрансляторам типа мост"> <!ENTITY torsettings.bridgeHelp1 "Если вы не можете подключиться к сети Tor, возможно ваш провайдер (ISP) или иная организация блокирует Tor.&#160; Часто эту проблему можно обойти при помощи мостов Tor, не перечисленных в публичных списках, которые сложнее заблокировать."> -<!ENTITY torsettings.bridgeHelp1B "You may use the preconfigured, default set of bridge addresses or you may obtain a custom set of addresses by using one of these three methods:"> +<!ENTITY torsettings.bridgeHelp1B "Вы можете использовать стандартный набор мостов или получить и ввести список мостов вручную при помощи одного из этих трёх методов:"> <!ENTITY torsettings.bridgeHelp2Heading "Из Веб"> <!ENTITY torsettings.bridgeHelp2 "Откройте в веб-браузере https://bridges.torproject.org"> <!ENTITY torsettings.bridgeHelp3Heading "Через автоответчик электронной почты">

1 0

[translation/tor-launcher-properties_completed] Update translations for tor-launcher-properties_completed
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 7002644743ce70caa906d0e6135e9eee42828c9a Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 18:45:32 2014 +0000 Update translations for tor-launcher-properties_completed --- ru/torlauncher.properties | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ru/torlauncher.properties b/ru/torlauncher.properties index 59899a1..b5766ee 100644 --- a/ru/torlauncher.properties +++ b/ru/torlauncher.properties @@ -7,6 +7,7 @@ torlauncher.tor_exited=Tor неожиданно завершился. torlauncher.please_restart_app=Пожалуйста, перезапустите приложение torlauncher.tor_controlconn_failed=Невозможно соединиться с портом управления Tor. torlauncher.tor_failed_to_start=Невозможно запустить Tor. +torlauncher.tor_control_failed=Не удалось взять контроль над Tor. torlauncher.tor_bootstrap_failed=Тор не удалось установить подключение к сети Tor. torlauncher.tor_bootstrap_failed_details=%1$S неудачно (%2$S). @@ -23,6 +24,10 @@ torlauncher.ensure_tor_is_running=Убедитесь что Tor запущен. torlauncher.error_proxy_addr_missing=Вы должны указать IP-адрес или имя хоста и порт, чтобы настроить Tor и использовать прокси для доступа в Интернет. torlauncher.error_proxy_type_missing=Необходимо выбрать тип прокси. torlauncher.error_bridges_missing=Необходимо задать один или несколько мостов. +torlauncher.error_default_bridges_type_missing=Вы должны выбрать тип транспорта для мостов по умолчанию. +torlauncher.error_bridge_bad_default_type=Мосты по умолчанию не поддерживают тип транспорта %S. Пожалуйста, исправьте ваши настройки. + +torlauncher.recommended_bridge=(рекомендуемый) torlauncher.connect=Соединиться torlauncher.quit=Выйти

1 0

[translation/tor-launcher-properties] Update translations for tor-launcher-properties
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 5584bbcbc4f9184f41731f1f437a47d84ba2d18d Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 18:45:29 2014 +0000 Update translations for tor-launcher-properties --- ru/torlauncher.properties | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ru/torlauncher.properties b/ru/torlauncher.properties index bef2e05..b5766ee 100644 --- a/ru/torlauncher.properties +++ b/ru/torlauncher.properties @@ -7,7 +7,7 @@ torlauncher.tor_exited=Tor неожиданно завершился. torlauncher.please_restart_app=Пожалуйста, перезапустите приложение torlauncher.tor_controlconn_failed=Невозможно соединиться с портом управления Tor. torlauncher.tor_failed_to_start=Невозможно запустить Tor. -# torlauncher.tor_control_failed=Failed to take control of Tor. +torlauncher.tor_control_failed=Не удалось взять контроль над Tor. torlauncher.tor_bootstrap_failed=Тор не удалось установить подключение к сети Tor. torlauncher.tor_bootstrap_failed_details=%1$S неудачно (%2$S). @@ -24,10 +24,10 @@ torlauncher.ensure_tor_is_running=Убедитесь что Tor запущен. torlauncher.error_proxy_addr_missing=Вы должны указать IP-адрес или имя хоста и порт, чтобы настроить Tor и использовать прокси для доступа в Интернет. torlauncher.error_proxy_type_missing=Необходимо выбрать тип прокси. torlauncher.error_bridges_missing=Необходимо задать один или несколько мостов. -# torlauncher.error_default_bridges_type_missing=You must select a transport type for the default bridges. -# torlauncher.error_bridge_bad_default_type=No default bridges that have the transport type %S are available. Please adjust your settings. +torlauncher.error_default_bridges_type_missing=Вы должны выбрать тип транспорта для мостов по умолчанию. +torlauncher.error_bridge_bad_default_type=Мосты по умолчанию не поддерживают тип транспорта %S. Пожалуйста, исправьте ваши настройки. -# torlauncher.recommended_bridge=(recommended) +torlauncher.recommended_bridge=(рекомендуемый) torlauncher.connect=Соединиться torlauncher.quit=Выйти

1 0

[tor-browser-bundle/master] Relocate bridges from torrc appendices to a prefs file.
by mikeperry＠torproject.org 28 Feb '14

28 Feb '14

commit 3279db32f147479af225d7106949e8dddd360dbb Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Fri Feb 28 10:02:10 2014 -0800 Relocate bridges from torrc appendices to a prefs file. --- Bundle-Data/beta/bridge_prefs.js | 15 ++++++++ Bundle-Data/beta/linux/torrc-defaults-appendix | 40 +++++----------------- Bundle-Data/beta/mac/torrc-defaults-appendix | 23 ------------- Bundle-Data/beta/windows/torrc-defaults-appendix | 22 ------------ 4 files changed, 23 insertions(+), 77 deletions(-) diff --git a/Bundle-Data/beta/bridge_prefs.js b/Bundle-Data/beta/bridge_prefs.js new file mode 100644 index 0000000..e3d6b69 --- /dev/null +++ b/Bundle-Data/beta/bridge_prefs.js @@ -0,0 +1,15 @@ +# Tor Launcher preferences (default bridges): +pref("extensions.torlauncher.default_bridge_recommended_type", "obfs3"); + +// Default bridges. +pref("extensions.torlauncher.default_bridge.obfs3.1", "obfs3 83.212.101.3:60475 A09D536DD1752D542E1FBB3C9CE4449D51298239"); +pref("extensions.torlauncher.default_bridge.obfs3.2", "obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); +pref("extensions.torlauncher.default_bridge.obfs3.3", "obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); +pref("extensions.torlauncher.default_bridge.obfs3.4", "obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2"); +pref("extensions.torlauncher.default_bridge.obfs3.5", "obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F"); +pref("extensions.torlauncher.default_bridge.obfs3.6", "obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD"); +pref("extensions.torlauncher.default_bridge.obfs3.7", "obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E"); + +pref("extensions.torlauncher.default_bridge.flashproxy.1", "flashproxy 0.0.1.0:1"); + +pref("extensions.torlauncher.default_bridge.fte.1", "fte bridges.fteproxy.org:8080"); diff --git a/Bundle-Data/beta/linux/torrc-defaults-appendix b/Bundle-Data/beta/linux/torrc-defaults-appendix index b43cd59..d0f621e 100644 --- a/Bundle-Data/beta/linux/torrc-defaults-appendix +++ b/Bundle-Data/beta/linux/torrc-defaults-appendix @@ -1,35 +1,11 @@ - ## fteproxy configuration -# Bridge fte bridges.fteproxy.org:8080 - ClientTransportPlugin fte exec ./Tor/PluggableTransports/fteproxy --managed -## obfsproxy configuration -# -# Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2 -# Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F -# Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD -# Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E -# -# Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80 -# Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41 -# Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35 -# Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496 -# Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D - -ClientTransportPlugin obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed - - -## flash proxy configuration -# -# # The flashproxy bridge address and port are ignored. -# Bridge flashproxy 0.0.1.0:1 - -# Change the second number here (9000) to the number of a port that can -# receive connections from the Internet (the port for which you -# configured port forwarding). -ClientTransportPlugin flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000 +## obfsproxy configuration +ClientTransportPlugin obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed +## flash proxy configuration +# +# Change the second number here (9000) to the number of a port that can +# receive connections from the Internet (the port for which you +# configured port forwarding). +ClientTransportPlugin flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/beta/mac/torrc-defaults-appendix b/Bundle-Data/beta/mac/torrc-defaults-appendix index d3e211d..e1ada73 100644 --- a/Bundle-Data/beta/mac/torrc-defaults-appendix +++ b/Bundle-Data/beta/mac/torrc-defaults-appendix @@ -1,34 +1,11 @@ - ## fteproxy configuration -# Bridge fte bridges.fteproxy.org:8080 - ClientTransportPlugin fte exec PluggableTransports/fteproxy --managed ## obfsproxy configuration -# -# Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2 -# Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F -# Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD -# Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E -# -# Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80 -# Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41 -# Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35 -# Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496 -# Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D - ClientTransportPlugin obfs2,obfs3 exec PluggableTransports/obfsproxy.bin managed - ## flash proxy configuration # -# # The flashproxy bridge address and port are ignored. -# Bridge flashproxy 0.0.1.0:1 - # Change the second number here (9000) to the number of a port that can # receive connections from the Internet (the port for which you # configured port forwarding). diff --git a/Bundle-Data/beta/windows/torrc-defaults-appendix b/Bundle-Data/beta/windows/torrc-defaults-appendix index 965b98a..049d2ff 100644 --- a/Bundle-Data/beta/windows/torrc-defaults-appendix +++ b/Bundle-Data/beta/windows/torrc-defaults-appendix @@ -1,33 +1,11 @@ ## fteproxy configuration -# Bridge fte bridges.fteproxy.org:8080 - ClientTransportPlugin fte exec Tor\PluggableTransports\fteproxy --managed ## obfsproxy configuration -# -# Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D -# Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9 -# Bridge obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2 -# Bridge obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F -# Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD -# Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E -# -# Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80 -# Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41 -# Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35 -# Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496 -# Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D - ClientTransportPlugin obfs2,obfs3 exec Tor\PluggableTransports\obfsproxy managed - ## flash proxy configuration # -# # The flashproxy bridge address and port are ignored. -# Bridge flashproxy 0.0.1.0:1 - # Change the second number here (9000) to the number of a port that can # receive connections from the Internet (the port for which you # configured port forwarding).

1 0

[tor-browser-bundle/master] Rename 'beta' to PTConfigs.
by mikeperry＠torproject.org 28 Feb '14

28 Feb '14

commit f8e7d91b4ed2e2d8f263b8b9898ce31ac28abfba Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Fri Feb 28 10:04:36 2014 -0800 Rename 'beta' to PTConfigs. --- Bundle-Data/PTConfigs/bridge_prefs.js | 15 +++++++++++++++ Bundle-Data/PTConfigs/linux/torrc-defaults-appendix | 11 +++++++++++ Bundle-Data/PTConfigs/mac/torrc-defaults-appendix | 12 ++++++++++++ Bundle-Data/PTConfigs/windows/torrc-defaults-appendix | 12 ++++++++++++ Bundle-Data/beta/bridge_prefs.js | 15 --------------- Bundle-Data/beta/linux/torrc-defaults-appendix | 11 ----------- Bundle-Data/beta/mac/torrc-defaults-appendix | 12 ------------ Bundle-Data/beta/windows/torrc-defaults-appendix | 12 ------------ 8 files changed, 50 insertions(+), 50 deletions(-) diff --git a/Bundle-Data/PTConfigs/bridge_prefs.js b/Bundle-Data/PTConfigs/bridge_prefs.js new file mode 100644 index 0000000..e3d6b69 --- /dev/null +++ b/Bundle-Data/PTConfigs/bridge_prefs.js @@ -0,0 +1,15 @@ +# Tor Launcher preferences (default bridges): +pref("extensions.torlauncher.default_bridge_recommended_type", "obfs3"); + +// Default bridges. +pref("extensions.torlauncher.default_bridge.obfs3.1", "obfs3 83.212.101.3:60475 A09D536DD1752D542E1FBB3C9CE4449D51298239"); +pref("extensions.torlauncher.default_bridge.obfs3.2", "obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); +pref("extensions.torlauncher.default_bridge.obfs3.3", "obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); +pref("extensions.torlauncher.default_bridge.obfs3.4", "obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2"); +pref("extensions.torlauncher.default_bridge.obfs3.5", "obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F"); +pref("extensions.torlauncher.default_bridge.obfs3.6", "obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD"); +pref("extensions.torlauncher.default_bridge.obfs3.7", "obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E"); + +pref("extensions.torlauncher.default_bridge.flashproxy.1", "flashproxy 0.0.1.0:1"); + +pref("extensions.torlauncher.default_bridge.fte.1", "fte bridges.fteproxy.org:8080"); diff --git a/Bundle-Data/PTConfigs/linux/torrc-defaults-appendix b/Bundle-Data/PTConfigs/linux/torrc-defaults-appendix new file mode 100644 index 0000000..d0f621e --- /dev/null +++ b/Bundle-Data/PTConfigs/linux/torrc-defaults-appendix @@ -0,0 +1,11 @@ +## fteproxy configuration +ClientTransportPlugin fte exec ./Tor/PluggableTransports/fteproxy --managed + +## obfsproxy configuration +ClientTransportPlugin obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed +## flash proxy configuration +# +# Change the second number here (9000) to the number of a port that can +# receive connections from the Internet (the port for which you +# configured port forwarding). +ClientTransportPlugin flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/PTConfigs/mac/torrc-defaults-appendix b/Bundle-Data/PTConfigs/mac/torrc-defaults-appendix new file mode 100644 index 0000000..e1ada73 --- /dev/null +++ b/Bundle-Data/PTConfigs/mac/torrc-defaults-appendix @@ -0,0 +1,12 @@ +## fteproxy configuration +ClientTransportPlugin fte exec PluggableTransports/fteproxy --managed + +## obfsproxy configuration +ClientTransportPlugin obfs2,obfs3 exec PluggableTransports/obfsproxy.bin managed + +## flash proxy configuration +# +# Change the second number here (9000) to the number of a port that can +# receive connections from the Internet (the port for which you +# configured port forwarding). +ClientTransportPlugin flashproxy exec PluggableTransports/flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/PTConfigs/windows/torrc-defaults-appendix b/Bundle-Data/PTConfigs/windows/torrc-defaults-appendix new file mode 100644 index 0000000..049d2ff --- /dev/null +++ b/Bundle-Data/PTConfigs/windows/torrc-defaults-appendix @@ -0,0 +1,12 @@ +## fteproxy configuration +ClientTransportPlugin fte exec Tor\PluggableTransports\fteproxy --managed + +## obfsproxy configuration +ClientTransportPlugin obfs2,obfs3 exec Tor\PluggableTransports\obfsproxy managed + +## flash proxy configuration +# +# Change the second number here (9000) to the number of a port that can +# receive connections from the Internet (the port for which you +# configured port forwarding). +ClientTransportPlugin flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/beta/bridge_prefs.js b/Bundle-Data/beta/bridge_prefs.js deleted file mode 100644 index e3d6b69..0000000 --- a/Bundle-Data/beta/bridge_prefs.js +++ /dev/null @@ -1,15 +0,0 @@ -# Tor Launcher preferences (default bridges): -pref("extensions.torlauncher.default_bridge_recommended_type", "obfs3"); - -// Default bridges. -pref("extensions.torlauncher.default_bridge.obfs3.1", "obfs3 83.212.101.3:60475 A09D536DD1752D542E1FBB3C9CE4449D51298239"); -pref("extensions.torlauncher.default_bridge.obfs3.2", "obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); -pref("extensions.torlauncher.default_bridge.obfs3.3", "obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9"); -pref("extensions.torlauncher.default_bridge.obfs3.4", "obfs3 209.141.36.236:45496 58D91C3A631F910F32E18A55441D5A0463BA66E2"); -pref("extensions.torlauncher.default_bridge.obfs3.5", "obfs3 208.79.90.242:35658 BA61757846841D64A83EA2514C766CB92F1FB41F"); -pref("extensions.torlauncher.default_bridge.obfs3.6", "obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD"); -pref("extensions.torlauncher.default_bridge.obfs3.7", "obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E"); - -pref("extensions.torlauncher.default_bridge.flashproxy.1", "flashproxy 0.0.1.0:1"); - -pref("extensions.torlauncher.default_bridge.fte.1", "fte bridges.fteproxy.org:8080"); diff --git a/Bundle-Data/beta/linux/torrc-defaults-appendix b/Bundle-Data/beta/linux/torrc-defaults-appendix deleted file mode 100644 index d0f621e..0000000 --- a/Bundle-Data/beta/linux/torrc-defaults-appendix +++ /dev/null @@ -1,11 +0,0 @@ -## fteproxy configuration -ClientTransportPlugin fte exec ./Tor/PluggableTransports/fteproxy --managed - -## obfsproxy configuration -ClientTransportPlugin obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed -## flash proxy configuration -# -# Change the second number here (9000) to the number of a port that can -# receive connections from the Internet (the port for which you -# configured port forwarding). -ClientTransportPlugin flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/beta/mac/torrc-defaults-appendix b/Bundle-Data/beta/mac/torrc-defaults-appendix deleted file mode 100644 index e1ada73..0000000 --- a/Bundle-Data/beta/mac/torrc-defaults-appendix +++ /dev/null @@ -1,12 +0,0 @@ -## fteproxy configuration -ClientTransportPlugin fte exec PluggableTransports/fteproxy --managed - -## obfsproxy configuration -ClientTransportPlugin obfs2,obfs3 exec PluggableTransports/obfsproxy.bin managed - -## flash proxy configuration -# -# Change the second number here (9000) to the number of a port that can -# receive connections from the Internet (the port for which you -# configured port forwarding). -ClientTransportPlugin flashproxy exec PluggableTransports/flashproxy-client --register :0 :9000 diff --git a/Bundle-Data/beta/windows/torrc-defaults-appendix b/Bundle-Data/beta/windows/torrc-defaults-appendix deleted file mode 100644 index 049d2ff..0000000 --- a/Bundle-Data/beta/windows/torrc-defaults-appendix +++ /dev/null @@ -1,12 +0,0 @@ -## fteproxy configuration -ClientTransportPlugin fte exec Tor\PluggableTransports\fteproxy --managed - -## obfsproxy configuration -ClientTransportPlugin obfs2,obfs3 exec Tor\PluggableTransports\obfsproxy managed - -## flash proxy configuration -# -# Change the second number here (9000) to the number of a port that can -# receive connections from the Internet (the port for which you -# configured port forwarding). -ClientTransportPlugin flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000

1 0

[tor-browser-bundle/master] Append bridge lines to PT bundles.
by mikeperry＠torproject.org 28 Feb '14

28 Feb '14

commit f29ec39f7bd73fcadf83f051c9add246e4d0c4f4 Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Fri Feb 28 10:11:16 2014 -0800 Append bridge lines to PT bundles. --- gitian/descriptors/linux/gitian-bundle.yml | 2 ++ gitian/descriptors/mac/gitian-bundle.yml | 2 ++ gitian/descriptors/windows/gitian-bundle.yml | 2 ++ gitian/mkbundle-linux.sh | 3 ++- gitian/mkbundle-mac.sh | 3 ++- gitian/mkbundle-windows.sh | 3 ++- 6 files changed, 12 insertions(+), 3 deletions(-) diff --git a/gitian/descriptors/linux/gitian-bundle.yml b/gitian/descriptors/linux/gitian-bundle.yml index 36c2efc..3fa79cc 100644 --- a/gitian/descriptors/linux/gitian-bundle.yml +++ b/gitian/descriptors/linux/gitian-bundle.yml @@ -31,6 +31,7 @@ files: - "pluggable-transports-linux32-gbuilt.zip" - "pluggable-transports-linux64-gbuilt.zip" - "torrc-defaults-appendix-linux" +- "bridge_prefs.js" - "relativelink-src.zip" - "linux-skeleton.zip" - "linux-langpacks.zip" @@ -106,6 +107,7 @@ script: | if [ $BUILD_PT_BUNDLES ]; then unzip ~/build/pluggable-transports-linux$GBUILD_BITS-gbuilt.zip cat ~/build/torrc-defaults-appendix-linux >> Data/Tor/torrc-defaults + cat ~/build/bridge_prefs.js >> Data/Browser/profile.default/preferences/extension-overrides.js fi chmod 700 Data/Browser chmod 700 Data/Tor diff --git a/gitian/descriptors/mac/gitian-bundle.yml b/gitian/descriptors/mac/gitian-bundle.yml index da7e918..63c0a96 100644 --- a/gitian/descriptors/mac/gitian-bundle.yml +++ b/gitian/descriptors/mac/gitian-bundle.yml @@ -33,6 +33,7 @@ files: - "tor-mac32-gbuilt.zip" - "pluggable-transports-mac32-gbuilt.zip" - "torrc-defaults-appendix-mac" +- "bridge_prefs.js" - "relativelink-src.zip" - "mac-skeleton.zip" - "mac-dmg.zip" @@ -125,6 +126,7 @@ script: | unzip ~/build/tbb-docs.zip if [ $BUILD_PT_BUNDLES ]; then cat ~/build/torrc-defaults-appendix-mac >> Data/Tor/torrc-defaults + cat ~/build/bridge_prefs.js >> Data/Browser/profile.default/preferences/extension-overrides.js fi # Install a "tor" shim that sets the working directory. See #10030. mv Tor/tor Tor/tor.real diff --git a/gitian/descriptors/windows/gitian-bundle.yml b/gitian/descriptors/windows/gitian-bundle.yml index 8cf2f05..c8b29c9 100644 --- a/gitian/descriptors/windows/gitian-bundle.yml +++ b/gitian/descriptors/windows/gitian-bundle.yml @@ -28,6 +28,7 @@ files: - "tor-win32-gbuilt.zip" - "pluggable-transports-win32-gbuilt.zip" - "torrc-defaults-appendix-windows" +- "bridge_prefs.js" - "relativelink-src.zip" - "windows-skeleton.zip" - "win32-langpacks.zip" @@ -108,6 +109,7 @@ script: | if [ $BUILD_PT_BUNDLES ]; then unzip ~/build/pluggable-transports-win32-gbuilt.zip cat ~/build/torrc-defaults-appendix-windows >> Data/Tor/torrc-defaults + cat ~/build/bridge_prefs.js >> Data/Browser/profile.default/preferences/extension-overrides.js fi cd .. # diff --git a/gitian/mkbundle-linux.sh b/gitian/mkbundle-linux.sh index 34485ae..b4e635d 100755 --- a/gitian/mkbundle-linux.sh +++ b/gitian/mkbundle-linux.sh @@ -56,7 +56,8 @@ $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/relativelink-src.zip ./Rel cd ./Bundle-Data/ rm -f $GITIAN_DIR/inputs/tbb-docs.zip $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/tbb-docs.zip ./Docs/ -cp beta/linux/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-linux +cp PTConfigs/linux/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-linux +cp PTConfigs/bridge_prefs.js $GITIAN_DIR/inputs/ cd linux rm -f $GITIAN_DIR/inputs/linux-skeleton.zip diff --git a/gitian/mkbundle-mac.sh b/gitian/mkbundle-mac.sh index d6bffce..18e0f8a 100755 --- a/gitian/mkbundle-mac.sh +++ b/gitian/mkbundle-mac.sh @@ -56,7 +56,8 @@ $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/relativelink-src.zip ./Rel cd ./Bundle-Data/ rm -f $GITIAN_DIR/inputs/tbb-docs.zip $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/tbb-docs.zip ./Docs/ -cp beta/mac/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-mac +cp PTConfigs/mac/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-mac +cp PTConfigs/bridge_prefs.js $GITIAN_DIR/inputs/ cp mac-tor.sh $GITIAN_DIR/inputs/ cd mac diff --git a/gitian/mkbundle-windows.sh b/gitian/mkbundle-windows.sh index 037b031..7ab0aa6 100755 --- a/gitian/mkbundle-windows.sh +++ b/gitian/mkbundle-windows.sh @@ -58,7 +58,8 @@ $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/relativelink-src.zip ./Rel cd ./Bundle-Data/ rm -f $GITIAN_DIR/inputs/tbb-docs.zip $WRAPPER_DIR/build-helpers/dzip.sh $GITIAN_DIR/inputs/tbb-docs.zip ./Docs/ -cp beta/windows/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-windows +cp PTConfigs/windows/torrc-defaults-appendix $GITIAN_DIR/inputs/torrc-defaults-appendix-windows +cp PTConfigs/bridge_prefs.js $GITIAN_DIR/inputs/ cd windows rm -f $GITIAN_DIR/inputs/windows-skeleton.zip

1 0

[torspec/master] Bring proposal-status.txt up to date
by nickm＠torproject.org 28 Feb '14

28 Feb '14

commit 4203039b103551b946fb0c586bc305626d032257 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Feb 25 11:19:11 2014 -0500 Bring proposal-status.txt up to date This is the version I'm sending out today. --- proposals/proposal-status.txt | 82 ++++++++++++++++++++++++++++++++--------- 1 file changed, 65 insertions(+), 17 deletions(-) diff --git a/proposals/proposal-status.txt b/proposals/proposal-status.txt index 36f9fdc..43c8e4a 100644 --- a/proposals/proposal-status.txt +++ b/proposals/proposal-status.txt @@ -4,35 +4,49 @@ December[0], based on the one I did in November[1] based on the one I did in June of 2012[2], based on the one I did in May[3] of 2011. Future versions of this document will be maintained in the torspec -repository. +repository as "proposals/proposal-status.txt". I'll still send them +to tor-dev periodically. If you're looking for something to review, think about, or comment on: Review 212 (using older consensuses) or 215 (obsoleting - consensus methods) if you understand the directory system even a - little bit; they are quite simple. + consensus methods) if you understand the directory system even + a little bit; they are quite simple. Review 219 if you're a DNS geek, or you'd like Tor to work better with more DNS types. - Review 220 (ed25519 identity keys) if you like designing - signature things, if you have good ideas about future-proofing - key type migration, or if you care about making Tor servers' - identity keys stronger. + Review 220 (ed25519 identity keys) and 228 + (cross-certification) if you like designing signature things, + if you have good ideas about future-proofing key type + migration, or if you care about making Tor servers' identity + keys stronger. - Review 223 (ACE handshake) if you're a cryptographer, or a cryptography - implementer, and you'd like an even faster replacement for the - ntor handshake. + Review 223 (ACE handshake) if you're a cryptographer, or a + cryptography implementer, and you'd like an even faster + replacement for the ntor handshake. Review 224 if you want to look through a big, complex protocol with a lot of pieces. Also review it if you care about hidden services and making them better. + Review 226 if you're interested in bridgedb development. + Review something else if you want to take a possibly good idea that needs more momentum and promote it, fix it up, or finally kill it off. +I note in passing that many of the proposals below seem stalled, +perhaps permanently: some because we don't know how to answer their +open questions, others because we're not sure if they're a good +idea, others because they don't seem implementable yet. Is that the +best way to characterize it? Should we have a new "stalled" +proposal status or something? Should we have a +"rejected-pending-revision" status that we use effectively for +everything that doesn't seem likely to get revised or implemented +any time soon? Other suggestions would be welcome. + Finally: if you've sent something to tor-dev or to me that should have a proposal number, but doesn't have one yet, please ping me again to remind me! @@ -386,17 +400,17 @@ again to remind me! 220 Migrate server identity keys to Ed25519 - This one is an intial design to migrate server identity keys to + This one is a design to migrate server identity keys to Ed25519 for improved security margin. It needs more analysis of long-term migration to other signing key types -- what do we do - if we want to add support for EdDSA over Curve2617 or something? + if we want to add support for EdDSA over Curve3617 or something? Can we make it easier than this? And it also needs analysis to make sure it enables us to eventually drop RSA1024 keys entirely. I've started building this, though, so we'd better figure out out fairly soon. Other proposals, like 224, depend on this one. - (12/2013) + (2/2014) 223 Ace: Improved circuit-creation key exchange @@ -436,12 +450,46 @@ again to remind me! something better. Some alternatives have already been discussed on tor-dev; more work is needed, though. (12/2013) -226 (writeme) +226 Scalability and Stability Improvements to BridgeDB: + Switching to a Distributed Database System and RDBMS + + This one outlines design and behavior changes for a seriously + refactored bridgedb. (2/2014) + +227 Include package fingerprints in consensus documents + + Here we outline a scheme for including the digests of the latest + versions of Tor software in consensuses, to help with update + security. (2/2014) + +228 Cross-certifying identity keys with onion keys + + This proposal signs each server's identity key with its onion + keys, to prove onion key ownership in the router descriptor. + It's not clear that this actually improves security, but it + fixes an annoying gap in our key authentication. (2/2014) +229 Further SOCKS5 extensions -227 (writeme) + Here's a nice idea for how we can support a new SOCKS5 protocol + extension to relay information between clients and Tor, and + between Tor and pluggable transports, more effectively. It + also adds some additional SOCKS5 error codes. There are some + open questions to answer. (2/2014) Since last time: - 147 was closed as unnecessary. See discussion in the new "Reasons for - Rejection" section at the end of that proprosal. + 147 was closed as unnecessary. See discussion in the new "Reasons + for Rejection" section at the end of that proprosal. + + 165 got clarified a little. + + 185 has been tweaked based on commentary from Karsten: the flag it + proposes now works a little differently. + + 220 has been revised to have a more unified certificate format. + + 224 has been cleaned up, expanded, revised, and tightened. + + Proposals 226, 227, 228, and 229 are new. +

1 0

[torspec/master] Put proposal-status under version control. some edits have happened since december.
by nickm＠torproject.org 28 Feb '14

28 Feb '14

commit 2f9156263dde7db016f2a030d3d75ad415356705 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Feb 24 16:03:06 2014 -0500 Put proposal-status under version control. some edits have happened since december. --- proposals/proposal-status.txt | 447 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 447 insertions(+) diff --git a/proposals/proposal-status.txt b/proposals/proposal-status.txt new file mode 100644 index 0000000..36f9fdc --- /dev/null +++ b/proposals/proposal-status.txt @@ -0,0 +1,447 @@ + +This list of open Tor proposals is based on one I sent out back in +December[0], based on the one I did in November[1] based on the +one I did in June of 2012[2], based on the one I did in May[3] of 2011. + +Future versions of this document will be maintained in the torspec +repository. + +If you're looking for something to review, think about, or comment +on: + + Review 212 (using older consensuses) or 215 (obsoleting + consensus methods) if you understand the directory system even a + little bit; they are quite simple. + + Review 219 if you're a DNS geek, or you'd like Tor to work + better with more DNS types. + + Review 220 (ed25519 identity keys) if you like designing + signature things, if you have good ideas about future-proofing + key type migration, or if you care about making Tor servers' + identity keys stronger. + + Review 223 (ACE handshake) if you're a cryptographer, or a cryptography + implementer, and you'd like an even faster replacement for the + ntor handshake. + + Review 224 if you want to look through a big, complex protocol + with a lot of pieces. Also review it if you care about hidden + services and making them better. + + Review something else if you want to take a possibly good idea + that needs more momentum and promote it, fix it up, or finally + kill it off. + +Finally: if you've sent something to tor-dev or to me that should +have a proposal number, but doesn't have one yet, please ping me +again to remind me! + +[0] https://lists.torproject.org/pipermail/tor-dev/2013-December/005957.html +[1] https://lists.torproject.org/pipermail/tor-dev/2013-November/005798.html +[2] https://lists.torproject.org/pipermail/tor-dev/2012-June/003641.html +[3] https://lists.torproject.org/pipermail/tor-dev/2011-May/002637.html + +**NOTE**: The dates after each paragraph indicate when I last + revised the paragraph. + + +127 Relaying dirport requests to Tor download site / website + + The idea here was to make it easier to fetch and learn about + Tor by making it easy for relays to automatically act as + proxies to the Tor website. It needs more discussion, and + there are some significant details to work out. It's not at + all clear whether this is actually a good idea or not. + Probably, there are better choices when it comes to + distributing software and updates. (11/2013) + +131 Help users to verify they are using Tor [NEEDS-REVISION] + + This one is not a crazy idea, but I marked it as + needs-revision since it doesn't seem to work so well with + our current designs. It seems mostly superseded by proposal + 211. (11/2013) + +132 A Tor Web Service For Verifying Correct Browser Configuration + + This proposal was meant to give users a way to see if their + browser and privoxy (yes, it was a while ago) are correctly + configured by running a local webserver on 127.0.0.1. I'm not + sure the status here. Generally, I'm skeptical of designs + that run webservers on localhost, since they become a target + for cross-site attacks. (11/2013) + +133 Incorporate Unreachable ORs into the Tor Network + + This proposal had an idea for letting ORs that can only make + outgoing connections still relay data usefully in the network. + It's something we should keep in mind, and it's a pretty neat + idea, but it radically changes the network topology. Anybody + who wants to analyze new network topologies should definitely + have a look. (5/2011) + +140 Provide diffs between consensuses + + This proposal describes a way to transmit less directory + traffic by sending only differences between consensuses, rather + than the consensuses themselves. It is mainly languishing for + lack of an appropriately licensed, well-written, very small, + pure-C implementation of the "diff" and "patch" algorithms. + (The good diffs seem to be GPL (which we can't use without + changing Tor's license), or spaghetti code, or not easily + usable as a library, or not written in C, or very large, or + some combination of those.) (5/2011) + +141 Download server descriptors on demand + + The idea of this proposal was for clients to only download the + consensus, and later ask nodes for their own server descriptors + while building the circuit through them. It would make each + circuit more time-consuming to build, but make bootstrapping + much cheaper. + + Microdescriptors obsolete a lot of this proposal, and present + some difficulties in using in a way compatible with + it. (6/2012) + +143 Improvements of Distributed Storage for Tor Hidden Service + Descriptors + + Here's a proposal from Karsten about making the hidden + service DHT more reliable and secure to use. It could use + more discussion and analysis. We should look into it as part + of efforts to improve designs for the next generation of + hidden services. + + One problem with the analysis here, though, is that it + assumes a fixed set of servers that doesn't change. One + reason that we upload to N servers at each chosen point in + the ring is that the hidden service host and the hidden + service client may have different views of which servers + exist. We need to re-do the analysis with some fraction of + recent consensuses. (11/2013) + + +144 Increase the diversity of circuits by detecting nodes + belonging the same provider + + This is a version of the good idea, "Let's do routing in a way + that tries to keep from routing traffic through the same + provider too much!" There are complex issues here that the + proposal doesn't completely address, but I think it might be a + fine idea for somebody to see how much more we know now than we + did in 2008, particularly in light of the relevant paper(s) by + Matt Edmann and Paul Syverson. (5/2011) + +145 Separate "suitable as a guard" from "suitable as a new guard" + [NEEDS-RESEARCH] + + Currently, the Guard flag means both "You can use this node as a + guard if you need to pick a new guard" and "If this node is + currently your guard, you can keep using it as a guard." This + proposal tries to separate these two concepts, so that clients can + stop picking a router once it is full of existing clients using it + as a guard, but the clients currently on it won't all drop it. + + It's not clear whether this has anonymity issues, and it's not + clear whether the imagined performance gains are actually + worthwhile. (5/2011) + +156 Tracking blocked ports on the client side + + This proposal provides a way for clients to learn which ports + they are (and aren't) able to connect to, and connect to the + ones that work. It comes with a patch, too. It also lets + routers track ports that _they_ can't connect to. + + I'm a little unconvinced that this will help a great deal: most + clients that have some ports blocked will need bridges, not + just restriction to a smaller set of ports. This could be good + behind restrictive firewalls, though. + + The router-side part is a little iffy: routers that can't + connect to each other violate one of our network topology + assumptions, and even if we do want to track failed + router->router connections, the routers need to be sure that + they aren't fooled into trying to connect repeatedly to a + series of nonexistent addresses in an attempt to make them + believe that (say) they can't reach port 443. + + This one is a paradigmatic "open" proposal: it needs more + discussion. The patch probably also needs to be ported to + 0.2.3.x; it touches some code that has changed. (5/2011) + +159 Exit Scanning + + This is an overview of SoaT, with some ideas for how to integrate + it into Tor. (5/2011) + +164 Reporting the status of server votes + + This proposal explains a way for authorities to provide a + slightly more verbose document that relay operators can use to + diagnose reasons that their router was or was not listed in the + consensus. These documents would be like slightly more verbose + versions of the authorities' votes, and would explain *why* the + authority voted as it did. It wouldn't be too hard to + implement, and would be a fine project for somebody who wants + to get to know the directory code. (5/2011) + +165 Easy migration for voting authority sets + + This is a design for how to change the set of authorities without + having a flag day where the authority operators all reconfigure + their authorities at once. It needs more discussion. One + difficulty here is that we aren't talking much about changing the + set of authorities, but that may be a chicken-and-egg issue, since + changing the set is so onerous. + + If anybody is interested, it would be great to move the discussion + ahead here. (5/2011) + +168 Reduce default circuit window + + This proposal reduces the default window for circuit sendme + cells. I think it's implemented (or mostly implemented) in + 0.2.1.20? If so, we should make sure that tor-spec.txt is + updated and close it. (11/2013) + +172 GETINFO controller option for circuit information +173 GETINFO Option Expansion + + These would help controllers (particularly arm) provide more + useful information about a running Tor process. They're + accepted and some parts of 173 are even implemented: somebody + just needs to implement the rest. (5/2011) + +175 Automatically promoting Tor clients to nodes + + Here's Steven's proposal for adding a mode between "client + mode" and "relay mode" for "self-test to see if you would be a + good relay, and if so become one." It didn't get enough + attention when it was posted to the list; more people should + review it. (5/2011) + +177 Abstaining from votes on individual flags + + Here's my proposal for letting authorities have opinions about some + (flag,router) combinations without voting on whether _every_ router + should have that flag. It's simple, and I think it's basically + right. With more discussion and review, somebody could/should + build it, I think. (11/2013) + +182 Credit Bucket + + This proposal suggests an alternative approach to our current + token-bucket based rate-limiting, that promises better + performance, less buffering insanity, and a possible end to + double-gating issues. (6/2012) + +185 Directory caches without DirPort + + The old HTTP directory port feature is no longer used by + clients and relays under most circumstances. The proposal + explains how we can get rid of the requirement that non-bridge + directories have an open directory port. (6/2012) + +188 Bridge Guards and other anti-enumeration defenses + + This proposal suggests some ways to make it harder for a relay + on the Tor network to enumerate a list of Tor bridges. Worth + investigating and possibly implementing. (6/2012) + +189 AUTHORIZE and AUTHORIZED cells +190 Bridge Client Authorization Based on a Shared Secret [NEEDS-REVISION] +191 Bridge Detection Resistance against MITM-capable Adversaries + + Proposal 187 reserved the AUTHORIZE cell type; these + proposals suggests how it could work to try to make it + harder to probe for Tor bridges. They need more alternatives + and attention, and possibly some revision and analysis. + Number 190 needs revision, since its protocol isn't actually + so great. (11/2013) + +192 Automatically retrieve and store information about bridges + + This proposal gives an enhancement to the bridge information + protocol, where clients remember more things about bridges, and + are able to update what they know about them over time. Could + help a lot with bridge churn. (6/2012) + +194 Mnemonic .onion URLs + + Here's one of several competing "let's make .onion URLs + human-usable" proposals. This one makes sentences using a + fixed map. This kind of approach is likely to obsoleted if + we go ahead with current plans for hidden services that + would make .onion addresses much longer, though. (11/2013) + +195 TLS certificate normalization for Tor 0.2.4.x + + Here's the followup to proposal 179, containing all the parts + of proposal 179 that didn't get built, and a couple of other + tricks besides to try to make Tor's default protocol less + detectable. I'm pretty psyched about the part where we let + relays drop in any any self-signed or CA-issued certificate + that they like. Some of this is done in ticket #7145; + we should decide, however, how much we want to push towards + normalizing the main Tor protocol. (11/2013) + +196 Extended ORPort and TransportControlPort + + Here are some remaining pieces of the pluggable transport + protocol that give Tor finer control over the behavior of + its transports. Much of this is implemented in 0.2.5 + now; we should figure out what's left, and whether we want + to build that. (11/2013) + +197 Message-based Inter-Controller IPC Channel + + This proposal is for an architectural enhancement in Tor + deployments, where Tor coordinates communications between the + various programs (Vidalia, TorBrowser, etc) that are using + it. (6/2012) + +199 Integration of BridgeFinder and BridgeFinderHelper + + Here's a proposal for how Tor can integrate with a client + program that finds bridges for it. I've seen some work being + done on things called "BridgeFinder"; I don't know what the + status of the current proposal is, though. (11/2013) + +201 Make bridges report statistics on daily v3 network status requests + + Here's a proposal for bridges to better estimate the number of + bridge users. (6/2012) + +202 Two improved relay encryption protocols for Tor cells + + Here's a sketch of the two broad classes of alternatives for + improving how relay encryption works. Right now, progress on + this proposal is stalled waiting for the ideal wide-block + construction to come along the line. (11/2013) + +203 Avoiding censorship by impersonating an HTTPS server + + This one is a design for making a bridge that acts like an + HTTPS server (by *being* an HTTPS server) until the user + proves they know it's a bridge. (11/2013) + +209 Tuning the Parameters for the Path Bias Defense + + In this proposal, Mike discusses alternative parameters for + getting better result out of the path-bias-attack detection + code. (11/2013) + +210 Faster Headless Consensus Bootstrapping + + This proposal suggests that we get our initial consensus by + launching multiple connections in parallel, and fetching the + consensus from whichever one completes. In my opinion, that + would be a fine idea when we're fetching our initial + consensus from non-Authority DirSources, but we shouldnt' do + anything to increase the load on authorities. (11/2013) + +211 Internal Mapaddress for Tor Configuration Testing + + Here, the idea is to serve an XML document over HTTP that + would let the know when it's using Tor. The XML document + would be returned when you make a request over Tor for a + magic address in 127.0.0.0/8. I think we need to do + _something_to solve this problem, but I'm not thrilled with + the idea of having any more magical addresses like this; we + got rid of .noconnect for a reason, after all. (11/2013) + +212 Increase Acceptable Consensus Age + + This proposal suggests that we increase the maximum age of a + consensus that clients are willing to use when they can't + find a new one, in order to make the network robust for + longer against a failure to reach consensus. In my + opinion, we should do that. If I recall correctly, there + was some tor-dev discussion on this one that should get + incorporated into a final, implementable version. (11/2013) + +215 Let the minimum consensus method change with time + + This proposal describes how we can raise the minimum + allowable consensus method that all authorities must + support, since the ancient "consensus method 1" would not + actually be viable to keep the Tor network running. We + should do this; see ticket #10163. (11/2013) + +219 Support for full DNS and DNSSEC resolution in Tor + + Here's a design to allow Tor to support a full range of DNS + request types. It probably isn't adequate on its to make + DNSSEC work realistically, since naive DNSSEC requires many + round trips that wouldn't be practical over Tor. It has a + ton of inline discussion that needs to get resolved before + this is buildable. + + One thing to consider here is whether we can get the server-side + done with reasonable confidence, and figure out the client side + once more servers have upgraded. (12/2013) + +220 Migrate server identity keys to Ed25519 + + This one is an intial design to migrate server identity keys to + Ed25519 for improved security margin. It needs more analysis of + long-term migration to other signing key types -- what do we do + if we want to add support for EdDSA over Curve2617 or something? + Can we make it easier than this? And it also needs analysis to + make sure it enables us to eventually drop RSA1024 keys + entirely. + + I've started building this, though, so we'd better figure out + out fairly soon. Other proposals, like 224, depend on this one. + (12/2013) + +223 Ace: Improved circuit-creation key exchange + + Here's an interesting one. It proposes a replacement for the + ntor handshake, using the multi-exponentiation optimization, to + run a bit faster at an equivalent security level. + + Assuming that more cryptographers like the security proof, and + that the ntor handshake winds up being critical-path in profiles + as more clients upgrade to 0.2.4 or 0.2.5, this is something we + should consider. (12/2013) + +224 Next-Generation Hidden Services in Tor + + This proposal outlines a more or less completely revised version + of the Tor hidden services protocol, improved to accomodate + better cryptography, better scalability, and defenses for + several attacks we'd never considered when we did the original + design. + + Some parts of this one are clearly right; some (like + scalability) are entirely unwritten. This proposal needs a lot + of attention and improvements to get it done right. I hope to + implement this over the course of 2014. (12/2013) + +225 Strawman proposal: commit-and-reveal shared rng + + Proposal 224's solutions for bug #8244 require that authorities + regularly agree upon a shared random value which none of them + could have influenced or predicted in advance. This proposal + outlines a simple one that isn't perfect (it's vulnerable to DOS + and to limited influence by one or more collaborating hostile + authorities), but it's quite simple, and it's meant to start + discussion. + + I hope that we never build this, but instead replace it with + something better. Some alternatives have already been discussed + on tor-dev; more work is needed, though. (12/2013) + +226 (writeme) + + +227 (writeme) + +Since last time: + + 147 was closed as unnecessary. See discussion in the new "Reasons for + Rejection" section at the end of that proprosal.

1 0

[tor-browser-bundle/master] Bug 9353: Fix ibus issues on some Linux systems.
by mikeperry＠torproject.org 28 Feb '14

28 Feb '14

commit c05c7728ef352e598750993190b76485addc26a2 Author: Georg Koppen <gk(a)torproject.org> Date: Fri Feb 28 09:55:55 2014 +0000 Bug 9353: Fix ibus issues on some Linux systems. --- RelativeLink/RelativeLink.sh | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/RelativeLink/RelativeLink.sh b/RelativeLink/RelativeLink.sh index 9bab08c..0d25a28 100755 --- a/RelativeLink/RelativeLink.sh +++ b/RelativeLink/RelativeLink.sh @@ -189,6 +189,13 @@ fi mydir="`dirname "$myname"`" test -d "$mydir" && cd "$mydir" +# This is a fix for an ibus issue on some Linux systems. See #9353 for more +# details. The symlink needs to be created before we change HOME. +if [ ! -d ".config/ibus" ]; then + mkdir -p .config/ibus + ln -nsf ~/.config/ibus/bus .config/ibus +fi + # If ${PWD} results in a zero length HOME, we can try something else... if [ ! "${PWD}" ]; then # "hacking around some braindamage"

1 0