tor-commits February 2014

tor-commits@lists.torproject.org

23 participants
1529 discussions

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

28 Feb '14

commit 219b02d08d6cde36afdfde696dabc5d62495a2a3 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 16:45:47 2014 +0000 Update translations for tor-launcher-network-settings --- pt_BR/network-settings.dtd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pt_BR/network-settings.dtd b/pt_BR/network-settings.dtd index decdafd..b84d542 100644 --- a/pt_BR/network-settings.dtd +++ b/pt_BR/network-settings.dtd @@ -22,9 +22,9 @@ <!ENTITY torSettings.firewallQuestion "A conexão Internet deste computador é filtrada por uma firewall que autoriza conexões somente para certas portas?"> <!ENTITY torSettings.firewallHelp "Se você não tiver certeza sobre como responder a esta questão, escolha Não. Em caso de dificuldades de conexão à rede Tor, modifique esta configuração."> <!ENTITY torSettings.enterFirewall "Insira, separando-a por vírgulas, uma lista de portas habilitadas pelo firewall. "> -<!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 "Seu provedor de serviços de internet (ISP) bloqueiam ou censuram conexões à rede Tor?"> +<!ENTITY torSettings.bridgeHelp "Se você não está seguro de como responder esta questão, escolha No.&#160; Se você escolher Sim, você será perguntado para configurar pontes Tor, que são relays não listados que dificultam o bloqueio a rede Tor."> +<!ENTITY torSettings.bridgeSettingsPrompt "Você pode usar as configurações padrões de pontes ou obter e entrar com uma configuração personalizada.">  @@ -46,15 +46,15 @@ <!ENTITY torsettings.firewall.checkbox "A conexão Internet deste computador é filtrada por uma firewall que autoriza conexões somente para determinadas portas."> <!ENTITY torsettings.firewall.allowedPorts "Portas habilitadas:"> <!ENTITY torsettings.useBridges.checkbox "Meu Provedor de Serviços Internet (ISP) bloqueia as conexões à rede Tor"> -<!ENTITY torsettings.useBridges.default "Use Default Bridges of Type"> -<!ENTITY torsettings.useBridges.custom "Use Custom Bridges"> +<!ENTITY torsettings.useBridges.default "Usar pontes padrões do Tipo"> +<!ENTITY torsettings.useBridges.custom "Usar pontes personalizadas"> <!ENTITY torsettings.useBridges.label "Insira um ou mais retransmissores de pontes (um por linha)."> -<!ENTITY torsettings.useBridges.placeholder "type address:port"> +<!ENTITY torsettings.useBridges.placeholder "tipo endereço:porta"> <!ENTITY torsettings.copyLog "Copiar o Log do Tor na área de transferência"> <!ENTITY torsettings.bridgeHelpTitle "Ajuda Retransmissor de Ponte"> <!ENTITY torsettings.bridgeHelp1 "Se for impossível conectar-se à rede Tor, talvez o seu Provedor de Internet (ISP) ou outra instância esteja bloqueando o Tor.&#160; Normalmente, é possível contornar esse problema utilizando Pontes Tor, que são retransmissores ocultos, mais difíceis de bloquear."> -<!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 "Você pode usar uma faixa de endereços de ponte pré-configuradas ou pode obter uma faixa de endereços personalizados usando um desses três métodos:"> <!ENTITY torsettings.bridgeHelp2Heading "Através da Web"> <!ENTITY torsettings.bridgeHelp2 "Use um navegador de internet e visite "> <!ENTITY torsettings.bridgeHelp3Heading "Através do Email Autoresponder">

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 0f5d6a18e32e8aede6742fe7feb9a03a1aab2c3e Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 16:45:42 2014 +0000 Update translations for tor-launcher-properties_completed --- pt_BR/torlauncher.properties | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/pt_BR/torlauncher.properties b/pt_BR/torlauncher.properties index 6b338a0..5976139 100644 --- a/pt_BR/torlauncher.properties +++ b/pt_BR/torlauncher.properties @@ -7,6 +7,7 @@ torlauncher.tor_exited=Tor fechou inesperadamente. torlauncher.please_restart_app=Por favor, reinicie esta aplicação. torlauncher.tor_controlconn_failed=Não foi possível conectar-se à porta de controle Tor. torlauncher.tor_failed_to_start=Falha ao iniciar Tor. +torlauncher.tor_control_failed=Falha ao receber controle do Tor. torlauncher.tor_bootstrap_failed=Falha ao tentar estabelecer uma conexão com a rede Tor. torlauncher.tor_bootstrap_failed_details=%1$S falhou (%2$S). @@ -23,6 +24,10 @@ torlauncher.ensure_tor_is_running=Por favor, verifique que Tor esteja rodando. torlauncher.error_proxy_addr_missing=Você deve especificar um endereço IP ou um servidor, e um número de porta para configurar Tor para usar um proxy de acesso a Internet. torlauncher.error_proxy_type_missing=Você deve selecionar um tipo de proxy. torlauncher.error_bridges_missing=Você deve especificar uma ou mais pontes. +torlauncher.error_default_bridges_type_missing=Você deve selecionar o tipo de transporte para as pontes padrão. +torlauncher.error_bridge_bad_default_type=Nenhuma ponte padrão disponível para transporte %S está disponível. Por favor ajuste suas configurações. + +torlauncher.recommended_bridge=(recomendado) torlauncher.connect=Conectar torlauncher.quit=Encerrar

1 0

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

28 Feb '14

commit b3afff3140832f6ffdd3d9d6574531462d51e336 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 16:45:38 2014 +0000 Update translations for tor-launcher-properties --- pt_BR/torlauncher.properties | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pt_BR/torlauncher.properties b/pt_BR/torlauncher.properties index c4c3a8f..5976139 100644 --- a/pt_BR/torlauncher.properties +++ b/pt_BR/torlauncher.properties @@ -7,7 +7,7 @@ torlauncher.tor_exited=Tor fechou inesperadamente. torlauncher.please_restart_app=Por favor, reinicie esta aplicação. torlauncher.tor_controlconn_failed=Não foi possível conectar-se à porta de controle Tor. torlauncher.tor_failed_to_start=Falha ao iniciar Tor. -# torlauncher.tor_control_failed=Failed to take control of Tor. +torlauncher.tor_control_failed=Falha ao receber controle do Tor. torlauncher.tor_bootstrap_failed=Falha ao tentar estabelecer uma conexão com a rede Tor. torlauncher.tor_bootstrap_failed_details=%1$S falhou (%2$S). @@ -24,10 +24,10 @@ torlauncher.ensure_tor_is_running=Por favor, verifique que Tor esteja rodando. torlauncher.error_proxy_addr_missing=Você deve especificar um endereço IP ou um servidor, e um número de porta para configurar Tor para usar um proxy de acesso a Internet. torlauncher.error_proxy_type_missing=Você deve selecionar um tipo de proxy. torlauncher.error_bridges_missing=Você deve especificar uma ou mais pontes. -# 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=Você deve selecionar o tipo de transporte para as pontes padrão. +torlauncher.error_bridge_bad_default_type=Nenhuma ponte padrão disponível para transporte %S está disponível. Por favor ajuste suas configurações. -# torlauncher.recommended_bridge=(recommended) +torlauncher.recommended_bridge=(recomendado) torlauncher.connect=Conectar torlauncher.quit=Encerrar

1 0

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 9e12b1c28f904fe3d00d0180422d05c83bd3da88 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 16:45:07 2014 +0000 Update translations for bridgedb_completed --- zh_TW/LC_MESSAGES/bridgedb.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh_TW/LC_MESSAGES/bridgedb.po b/zh_TW/LC_MESSAGES/bridgedb.po index 3fdd1a9..ccec1bd 100644 --- a/zh_TW/LC_MESSAGES/bridgedb.po +++ b/zh_TW/LC_MESSAGES/bridgedb.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2013-03-27 21:41+0000\n" -"PO-Revision-Date: 2014-02-28 09:41+0000\n" +"PO-Revision-Date: 2014-02-28 16:31+0000\n" "Last-Translator: 修銘張 <cges30901(a)gmail.com>\n" "Language-Team: Chinese (Taiwan) (http://www.transifex.com/projects/p/torproject/language/zh_TW/)\n" "MIME-Version: 1.0\n"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 28 Feb '14

28 Feb '14

commit 2e0eabfc87f9b43b9f0c835d0d4c81f0e4f672f0 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 16:45:03 2014 +0000 Update translations for bridgedb --- zh_TW/LC_MESSAGES/bridgedb.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh_TW/LC_MESSAGES/bridgedb.po b/zh_TW/LC_MESSAGES/bridgedb.po index 3fdd1a9..ccec1bd 100644 --- a/zh_TW/LC_MESSAGES/bridgedb.po +++ b/zh_TW/LC_MESSAGES/bridgedb.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2013-03-27 21:41+0000\n" -"PO-Revision-Date: 2014-02-28 09:41+0000\n" +"PO-Revision-Date: 2014-02-28 16:31+0000\n" "Last-Translator: 修銘張 <cges30901(a)gmail.com>\n" "Language-Team: Chinese (Taiwan) (http://www.transifex.com/projects/p/torproject/language/zh_TW/)\n" "MIME-Version: 1.0\n"

1 0

[torspec/master] Add socks5 extensions as proposal 229
by nickm＠torproject.org 28 Feb '14

28 Feb '14

commit ba8c74dc5ce221a58b668040cbd08e13fc0c789d Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Feb 28 11:44:12 2014 -0500 Add socks5 extensions as proposal 229 --- proposals/000-index.txt | 2 + proposals/229-further-socks5-extensions.txt | 238 +++++++++++++++++++++++++++ 2 files changed, 240 insertions(+) diff --git a/proposals/000-index.txt b/proposals/000-index.txt index c854980..a7a4287 100644 --- a/proposals/000-index.txt +++ b/proposals/000-index.txt @@ -149,6 +149,7 @@ Proposals by number: 226 "Scalability and Stability Improvements to BridgeDB: Switching to a Distributed Database System and RDBMS" [OPEN] 227 Include package fingerprints in consensus documents [OPEN] 228 Cross-certifying identity keys with onion keys [OPEN] +229 Further SOCKS5 extensions [DRAFT] Proposals by status: @@ -167,6 +168,7 @@ Proposals by status: 220 Migrate server identity keys to Ed25519 [for 0.2.x.x] 224 Next-Generation Hidden Services in Tor 225 Strawman proposal: commit-and-reveal shared rng + 229 Further SOCKS5 extensions NEEDS-REVISION: 131 Help users to verify they are using Tor 190 Bridge Client Authorization Based on a Shared Secret diff --git a/proposals/229-further-socks5-extensions.txt b/proposals/229-further-socks5-extensions.txt new file mode 100644 index 0000000..0371f02 --- /dev/null +++ b/proposals/229-further-socks5-extensions.txt @@ -0,0 +1,238 @@ +Filename: 229-further-socks5-extensions.txt +Title: Further SOCKS5 extensions +Author: Yawning Angel +Created: 25-Feb-2014 +Status: Draft + +0. Abstract + + We propose extending the SOCKS5 protocol to allow passing more + per-session metadata, and to allow returning more meaningful + reponse failure codes back to the client. + +1. Introduction + + The SOCKS5 protocol is used by Tor both as the primary interface + for applications to transfer data, and as the interface by which + Tor communicates with pluggable transport implementations. + + While the current specifications allow for passing a limited + amount of per-session metadata via hijacking the + Username/Password authentication method fields, this solution is + limited in that the amount of payload that can be conveyed is + restricted to 510 bytes, does not allow the SOCKS server to + return a response, and precludes using authentication on the + SOCKS port. + + The first part of this proposal defines a new authentication + method to overcome both of these limitations. + + The second part of this proposal defines a range of SOCKS5 + response codes that can be used to signal Tor specific error + conditions when processing SOCKS requests. + +2. Proposal + +2.1. Tor Extended SOCKS5 Authentication + + We introduce a new authentication method to the SOCKS5 protocol. + + The METHOD number to be returned to indicate support for or + select this method is X'97', which belongs to the "RESERVED FOR + PRIVATE METHODS" range in RFC 1928. + + After the authentication method has been negotiated following the + standard SOCKS5 protocol, the actual authentication phase begins. + + The initiator will send an Extended Authentication request: + + +----+----------+-------+-------------+-------+-------------+--- + |VER | NR PAIRS | KLEN1 | KEY1 | VLEN1 | VALUE1 | ... + +----+----------+-------+-------------+-------+-------------+--- + | 1 | 2 | 2 | KLEN1 bytes | 2 | VLEN1 bytes | ... + +----+----------+-------+-------------+-------+-------------+--- + + VER: 8 bits (unsigned integer) + + This field specifies the version of the authentication + method. It MUST be set to X'01'. + + NR PAIRS: 16 bits (unsigned integer) + + This field specifies the number of key/value pairs to follow. + The NR PAIRS field MUST be transmitted in network byte order. + + KLEN: 16 bits (unsigned integer) + + This field specifies the length of the key in bytes. It MUST + be transmitted in network byte order, and MUST be greater + than 0. + + KEY: variable length + + This field contains the key associated with the subsequent + VALUE field as an ASCII string, without a NULL terminator. + + VLEN: 16 bits (unsigned integer) + + This field specifies the length of the value in bytes. It + MUST be tramsmitted in network byte order. It MAY be + X'0000', in which case the corresponding VALUE field is + omitted. + + VALUE: variable length, optional + + The value corresponding to the KEY. + + + The responder will verify the contents of the Extended + Authentication request and send the followint response: + + +----+--------+----------+-------+-------------+-------+-------------+--- + |VER | STATUS | NR PAIRS | KLEN1 | KEY1 | VLEN1 | VALUE1 | ... + +----+--------+----------+-------+-------------+-------+-------------+--- + | 1 | 1 | 2 | 2 | KLEN1 bytes | 2 | VLEN1 bytes | ... + +----+--------+----------+-------+-------------+-------+-------------+--- + + VER: 8 bits (unsigned integer) + + This field specifies the version of the authentication + method. It MUST be set to X'01'. + + STATUS: 8 bits (unsigned integer) + + The status of the Extended Authentication request where: + + * X'00' SUCCESS + * X'01' AUTHENTICATION FAILED + * X'02' INVALID ARGUMENTS + + If a server sends a response indicating failure (STATUS value + other than X'00') it MUST close the connection. + + NR PAIRS: 16 bits (unsigned integer) + + This field specifies the number of key/value pairs to follow. + The NR PAIRS field MUST be transmitted in network byte order. + + KLEN: 16 bits (unsigned integer) + + This field specifies the length of the key in bytes. It MUST be + transmitted in network byte order, and MUST be greater than 0. + + KEY: variable length + + This field contains the key associated with the subsequent + VALUE field as an ASCII string, without a NULL terminator. + + VLEN: 16 bits (unsigned integer) + + This field specifies the length of the value in bytes. It + MUST be tramsmitted in network byte order. It MAY be + X'0000', in which case the corresponding VALUE field is + omitted. + + VALUE: variable length, optional + + The value corresponding to the KEY. + + The currently defined KEYs are: + + * "UNAME" The username for authentication. + * "PASSWD" The password for authentication. + + [XXX - Add some more here, Stream isolation?] + +2.2. Tor Extended SOCKS5 Reply Codes + + We introduce the following additional SOCKS5 reply codes to be + sent in the REP field of a SOCKS5 message. Implementations MUST + NOT send any of the extended codes unless the initiator has + indicated that it understands the "Tor Extended SOCKS5 + Authentication" as part of the version identifier/method + selection SOCKS5 message. + + Where: + + * X'E0' Hidden Service Not Found + + The requested Tor Hidden Service was not reachable. + + * X'E1' Hidden Service Not Reachable + + The requested Tor Hidden Service was not found. + + * X'F0' Temporary Pluggable Transport failure, retry immediately + + Pluggable transports SHOULD return this status code if the + connection attempt failed, but the pluggable transport + believes that subsequent connections with the same parameters + are likely to succeed. + + Example: + + The ScrambleSuit Session Ticket handshake failed, but + reconnecting is likely to succeed as it will use the + UniformDH handshake. + + * X'F1' Pluggable transport protocol failure, invalid bridge + + Pluggable transports MUST return this status code if the + connection attempt failed in a manner that indicates that the + remote peer is not likely to accept connections at a later + time. + + Example: + + The obfs3 handshake failed. + + * X'F2' Pluggable transport internal error + + Pluggable transports SHOULD return this status code if the + connection attempt failed due to an internal error in the + pluggable transport implementation. + + Tor might wish to restart the pluggable transport executable, + or retry after a delay. + +3. Compatibility + + SOCKS5 negotiates authentication methods so backward and forward + compatibility is obtained for free, assuming a non-broken SOCKS5 + implementation on the responder side that ignores unrecognised + authentication methods in the negotiation phase. + +4. Security Considerations + + Identical security considerations to RFC 1929 Username/Password + authentication applies when doing Username/Password + authentication using the keys reserved for such. As the + UNAME/PASSWD fields are carried in cleartext, this authentication + method MUST NOT be used in scenarios where sniffing is possible. + The authors of this proposal note that binding any of the Tor + (and associated) SOCKS5 servers to non-loopback interfaces is + strongly discouraged currently, so in the current model this is + believed to be acceptable. + +5. References + + Leech, M., Ganis, M., Lee, Y., Kuris, R., Koblas, D., Jones L., "SOCKS + Protocol Version 5", RFC 1928, March 1996. + + Tor Project, "Tor's extensions to the SOCKS protocol" + + Leech, M. "Username/Password Authentication for SOCKS V5", RFC 1929, + March 1996. + + Appelbaum, J., Mathewson, N., "Pluggable Transport Specification", + June 2012. + +[XXX - Changelog (Remove when accepted)] + + 2014-02-28 (Thanks to nickm/arma) + * Generalize to also support tor + * Add status codes for bug #6031 + * Switch from always having a username/password field to making them just + predefined keys. + * Change the auth method number to 0x97 +

1 0

r26628: {website} Dropping 'Make Chutney Do More, More Reliably' idea Dropping (website/trunk/getinvolved/en)
by Damian Johnson 28 Feb '14

28 Feb '14

Author: atagar Date: 2014-02-28 15:53:20 +0000 (Fri, 28 Feb 2014) New Revision: 26628 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping 'Make Chutney Do More, More Reliably' idea Dropping as per Nick's request. This is a duplicate of the idea to improve tor's test coverage. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2014-02-27 17:19:03 UTC (rev 26627) +++ website/trunk/getinvolved/en/volunteer.wml 2014-02-28 15:53:20 UTC (rev 26628) @@ -425,7 +425,6 @@ Project Ideas: <a href="#torCleanup">Tor Codebase Cleanup</a> - <a href="#chutneyExpansion">Make Chutney Do More, More Reliably</a> <a href="#improveTorTestCoverage">Improve test coverage in Tor</a> <a href="#useMoreCores">Have the Tor daemon use more cores</a> <a href="#improveHiddenServices">Help improve Tor hidden services</a> @@ -990,35 +989,6 @@ </li> - <a id="chutneyExpansion"></a> - <li> - Make Chutney Do More, More Reliably - - Effort Level: Medium to High, depending on scope of project - - Skill Level: Medium - - Likely Mentors: Nick (nickm) - - We have a little Python tool called <a - href="https://gitweb.torproject.org/nickm/chutney.git">Chutney</a> for - making small local test networks. It's small, not widely used, and not as - automated as it could be. - - - - It would be great to see chutney extended and a set of supporting tests - built to the point where we could use Chutney to exercise various Tor - features as an automated integration test. - - - - As part of your application for this project please submit a patch that - expands Chutney. - - - </li> - <a id="torCleanup"></a> <li> Tor Codebase Cleanup

1 0

[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 8a905c94b80befbdde13e97831f9c8e41a16f5bb Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 15:15:37 2014 +0000 Update translations for tor-launcher-network-settings_completed --- nb/network-settings.dtd | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/nb/network-settings.dtd b/nb/network-settings.dtd index 3f393d0..f023e81 100644 --- a/nb/network-settings.dtd +++ b/nb/network-settings.dtd @@ -22,7 +22,9 @@ <!ENTITY torSettings.firewallQuestion "Går denne datamaskinens Internett-tilkobling gjennom en brannmur som kun tillater forbindelser til visse porter?"> <!ENTITY torSettings.firewallHelp "Hvis du ikke er sikker på hvordan du skal svare på dette spørsmålet, velg nei. Hvis du støter på problemer med å koble til Tor-nettverket, endrer du denne innstillingen."> <!ENTITY torSettings.enterFirewall "Skriv inn en liste, adskilt med komma, over porter som er tillatt av brannmuren."> -<!ENTITY torSettings.bridgeQuestion "Hvis denne datamaskinens Internett-tilkobling er sensurert, vil du trenge å skaffe deg bro-reléer.&#160; Hvis ikke, bare klikk Koble til."> +<!ENTITY torSettings.bridgeQuestion "Blokkerer eller sensurerer internettleverandøren (ISP) din tilkoblinger til Tor-nettverket?"> +<!ENTITY torSettings.bridgeHelp "Hvis du er usikker på hva du skal svare på dette spørsmålet, velg Nei.&#160; Hvis du velger Ja, vil du bli bedt om å konfigurere Tor-broer, som er ulistede reléer som gjør det vanskeligere å blokkere tilkoblinger til Tor-nettverket."> +<!ENTITY torSettings.bridgeSettingsPrompt "Du kan bruke broene som er standard eller du kan skaffe deg egendefinerte broer.">  @@ -44,13 +46,15 @@ <!ENTITY torsettings.firewall.checkbox "Denne datamaskinen går gjennom en brannmur som kun tillater tilkoblinger til visse porter"> <!ENTITY torsettings.firewall.allowedPorts "Tillatte Porter:"> <!ENTITY torsettings.useBridges.checkbox "Min Internettleverandør (ISP) blokkerer tilkoblinger til Tor-nettverket"> +<!ENTITY torsettings.useBridges.default "Bruk standardbroer av typen"> +<!ENTITY torsettings.useBridges.custom "Bruk egendefinerte broer"> <!ENTITY torsettings.useBridges.label "Skriv inn en, eller fler bro-reléer (èn pr linje)."> -<!ENTITY torsettings.useBridges.placeholder "adresse:port, ELLER transport adresse:port"> +<!ENTITY torsettings.useBridges.placeholder "type adresse:port"> <!ENTITY torsettings.copyLog "Kopier Torloggen til Utklippstavlen"> <!ENTITY torsettings.bridgeHelpTitle "Bro-relé Hjelp"> <!ENTITY torsettings.bridgeHelp1 "Hvis du ikke får koblet til Tor-nettverket, kan det være at internettleverandøren din (ISP), eller et annet byrå/institusjon/etat blokkerer Tor.&#160; Som regel kan du omgå dette problemet ved å bruke Tor-broer, som er ulistede reléer og derfor vanskeligere å blokkere."> -<!ENTITY torsettings.bridgeHelp1B "Her er tre måter du kan skaffe bro-adresser på:"> +<!ENTITY torsettings.bridgeHelp1B "Du kan bruke de standard prekonfigurerte bro-adressene eller du kan skaffe deg egendefinerte adresser ved å bruke en av følgende tre metoder:"> <!ENTITY torsettings.bridgeHelp2Heading "Via nettet"> <!ENTITY torsettings.bridgeHelp2 "Bruk en nettleser for å besøke https://bridges.torproject.org"> <!ENTITY torsettings.bridgeHelp3Heading "Via e-post autosvar">

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 e27c27d52274f96af60041826a2389524233c6ba Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 15:15:35 2014 +0000 Update translations for tor-launcher-network-settings --- nb/network-settings.dtd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/nb/network-settings.dtd b/nb/network-settings.dtd index 91835b1..f023e81 100644 --- a/nb/network-settings.dtd +++ b/nb/network-settings.dtd @@ -22,9 +22,9 @@ <!ENTITY torSettings.firewallQuestion "Går denne datamaskinens Internett-tilkobling gjennom en brannmur som kun tillater forbindelser til visse porter?"> <!ENTITY torSettings.firewallHelp "Hvis du ikke er sikker på hvordan du skal svare på dette spørsmålet, velg nei. Hvis du støter på problemer med å koble til Tor-nettverket, endrer du denne innstillingen."> <!ENTITY torSettings.enterFirewall "Skriv inn en liste, adskilt med komma, over porter som er tillatt av brannmuren."> -<!ENTITY torSettings.bridgeQuestion "Does your Internet Service Provider (ISP) block or otherwise censor connections to the Tor Network?"> +<!ENTITY torSettings.bridgeQuestion "Blokkerer eller sensurerer internettleverandøren (ISP) din tilkoblinger til Tor-nettverket?"> <!ENTITY torSettings.bridgeHelp "Hvis du er usikker på hva du skal svare på dette spørsmålet, velg Nei.&#160; Hvis du velger Ja, vil du bli bedt om å konfigurere Tor-broer, som er ulistede reléer som gjør det vanskeligere å blokkere tilkoblinger til Tor-nettverket."> -<!ENTITY torSettings.bridgeSettingsPrompt "You may use the default set of bridges or you may obtain and enter a custom set of bridges."> +<!ENTITY torSettings.bridgeSettingsPrompt "Du kan bruke broene som er standard eller du kan skaffe deg egendefinerte broer.">  @@ -46,10 +46,10 @@ <!ENTITY torsettings.firewall.checkbox "Denne datamaskinen går gjennom en brannmur som kun tillater tilkoblinger til visse porter"> <!ENTITY torsettings.firewall.allowedPorts "Tillatte Porter:"> <!ENTITY torsettings.useBridges.checkbox "Min Internettleverandør (ISP) blokkerer tilkoblinger til Tor-nettverket"> -<!ENTITY torsettings.useBridges.default "Use Default Bridges of Type"> +<!ENTITY torsettings.useBridges.default "Bruk standardbroer av typen"> <!ENTITY torsettings.useBridges.custom "Bruk egendefinerte broer"> <!ENTITY torsettings.useBridges.label "Skriv inn en, eller fler bro-reléer (èn pr linje)."> -<!ENTITY torsettings.useBridges.placeholder "type address:port"> +<!ENTITY torsettings.useBridges.placeholder "type adresse:port"> <!ENTITY torsettings.copyLog "Kopier Torloggen til Utklippstavlen"> <!ENTITY torsettings.bridgeHelpTitle "Bro-relé Hjelp">

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 08c2c3e2e314e5ea7f91d7c2191194638f1f1ff8 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 28 15:15:31 2014 +0000 Update translations for tor-launcher-properties_completed --- nb/torlauncher.properties | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/nb/torlauncher.properties b/nb/torlauncher.properties index 9dac98a..5535bf8 100644 --- a/nb/torlauncher.properties +++ b/nb/torlauncher.properties @@ -7,6 +7,7 @@ torlauncher.tor_exited=Tor ble uventet avsluttet. torlauncher.please_restart_app=Vennligst start denne applikasjonen på nytt. torlauncher.tor_controlconn_failed=Kunne ikke koble til Tor kontrollport. torlauncher.tor_failed_to_start=Tor kunne ikke starte. +torlauncher.tor_control_failed=Feilet i ta kontroll over Tor. torlauncher.tor_bootstrap_failed=Tor fikk ikke etablert en forbindelse til Tor-nettverket. torlauncher.tor_bootstrap_failed_details=%1$S feilet (%2$S). @@ -23,6 +24,10 @@ torlauncher.ensure_tor_is_running=Vennligst sjekk at Tor kjører. torlauncher.error_proxy_addr_missing=Du må spesifisere både IP-adresse eller vertsnavn og et portnummer for å konfigurere Tor til å bruke en proxy for å koble til Internett. torlauncher.error_proxy_type_missing=Du må velge proxytypen torlauncher.error_bridges_missing=Du må velge én eller flere broer. +torlauncher.error_default_bridges_type_missing=Du må velge en tilkoblingstype for standardbroene. +torlauncher.error_bridge_bad_default_type=Ingen standardbroer av tilkoblingstypen %S er tilgjengelig. Vennligst juster innstillingene dine. + +torlauncher.recommended_bridge=(anbefalt) torlauncher.connect=Koble til torlauncher.quit=Avslutt

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits February 2014