- tor-commits - lists.torproject.org

[torspec/master] prop224: Revisit how overlap periods work.
by asn＠torproject.org 08 May '16

08 May '16

commit 30aad19107646ddd8e4b44bb9cc2c3aece754c4f Author: George Kadianakis <desnacked(a)riseup.net> Date: Wed Apr 13 14:47:49 2016 +0300 prop224: Revisit how overlap periods work. Now overlap periods start 6 hours before the start of the next time period. --- proposals/224-rend-spec-ng.txt | 65 ++++++++++++++++++++++++------------------ 1 file changed, 37 insertions(+), 28 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index e270f1d..32d29de 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -639,38 +639,47 @@ Status: Draft the public key and the period. The time at which a key might first become valid is determined by the - consensus parameter "hsdir-overlap-begins", which is an integer in - range [1,100] with default value 80. This parameter denotes a - percentage of the interval for which no overlap occurs. So for the - default interval (1500 minutes) and default overlap-begins value - (80%), new keys do not become valid for the first 1200 minutes of the - interval. - - The new shared random value must be published *before* the start of - the next overlap interval by at least enough time to ensure that - clients all get it. [TODO: how much earlier?] + consensus parameter "hsdir-overlap-begins", which is an integer in range + [1,100] with default value 75. This parameter denotes a percentage of the + interval for which no overlap occurs. So for the default interval (24 + hours) and default overlap-begins value (75%), new keys do not become valid + for the first 18 hours of the interval. Instead, keys become valid at a + random point in the last 6 hours of the 24 hours interval. The time at which a key from the next interval becomes valid is determined by taking the first two bytes of - OFFSET = H("interval-offset" | Key | INT_8(Next_Period_Num)) + OFFSET = H("interval-offset" | KEY | INT_8(NEXT_PERIOD_NUM)) as a big-endian integer, dividing by 65536, and treating that as a fraction of the overlap interval. - For example, if the period is 1500 minutes long, and overlap interval - is 300 minutes long, and OFFSET begins with [90 50], then the next - key becomes valid at 1200 + 300 * (0x9050 / 65536) minutes, or - approximately 22 hours and 49 minutes after the beginning of the + For example, if the period is 1440 minutes long, and overlap interval + is 360 minutes long, and OFFSET begins with [90 50], then the next + key becomes valid at 1080 + 360 * (0x9050 / 65536) minutes, or + approximately 21 hours and 38 minutes after the beginning of the period. - Hidden service directories should accept descriptors at least [TODO: - how much?] minutes before they would become valid, and retain them - for at least [TODO: how much?] minutes after the end of the period. + The new shared random value MUST be published *before* the overlap interval + starts so that hidden services have access to the new shared random values + in time and can calculate the upcoming set of responsible HSDirs. In our + system, new shared random values get published at 00:00UTC every day, whereas + the overlap period starts at 06:00 and finishes at 12:00UTC. + + Here is an illustration of the system: + + +------------------------------------------------------------------+ + | | + | 00:00 12:00 00:00 12:00 00:00 12:00 | + | SRV#1 TP#1 SRV#2 TP#2 SRV#3 TP#3 | + | | + | $ |-----------$-----======|-----------$-----======| | + | overlap12 overlap23 | + | | + +------------------------------------------------------------------+ - When a client is looking for a service, it must calculate its key - both for the current and for the subsequent period, to decide whether - the next period's key is valid yet. + Legend: [TP#1 = Time Period #1] + [SRV#1 = Shared Random Value #1] 2.2.3. Where to publish a service descriptor @@ -737,14 +746,14 @@ Status: Draft Again, nodes from lower-numbered replicas are disregarded when choosing the spread for a replica. - An HSDir should reject a descriptor if that HSDir is not one of the - first hsdir_spread_accept HSDirs for that node. Since HSDirs can't - derive other replicas of a service, hsdir_spread_accept must be at - least hsdir_n_replicas * hsdir_spread_store. + HSDirs MUST retain hidden service descriptors for 33 hours before expiring + them. That's 24 hours for the time period duration, plus 6 hours for the + maximum overlap period span, plus 3 hours for the maximum acceptable client + clock skew. - [TODO: Incorporate the findings from proposal 143 here. But watch - out: proposal 143 did not analyze how much the set of nodes changes - over time, or how much client and host knowledge might diverge.] + Hidden services should keep their old introduction circuits open for at + least 3 hours after the descriptor expiration, so that clients with skewed + clocks can still visit them through outdated descriptors. 2.2.4. URLs for anonymous uploading and downloading

1 0

[torspec/master] prop224: Clarify descriptor upload section.
by asn＠torproject.org 08 May '16

08 May '16

commit 3e6568939a43480786646eddc3eb4253a8164652 Author: George Kadianakis <desnacked(a)riseup.net> Date: Thu Apr 21 13:20:58 2016 +0300 prop224: Clarify descriptor upload section. Also specify that HSes should re-upload their descriptor every one hour. --- proposals/224-rend-spec-ng.txt | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index 32d29de..3bc1d97 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -660,11 +660,11 @@ Status: Draft approximately 21 hours and 38 minutes after the beginning of the period. - The new shared random value MUST be published *before* the overlap interval + New shared random values MUST be published *before* the overlap interval starts so that hidden services have access to the new shared random values in time and can calculate the upcoming set of responsible HSDirs. In our - system, new shared random values get published at 00:00UTC every day, whereas - the overlap period starts at 06:00 and finishes at 12:00UTC. + system, new shared random values get published at 00:00UTC every day, + whereas the overlap period starts at 06:00 and finishes at 12:00UTC. Here is an illustration of the system: @@ -706,24 +706,21 @@ Status: Draft hs_index(replicanum) = H("store-at-idx" | blinded_public_key | INT_8(replicanum) | - INT_8(periodnum) ) - - where blinded_public_key is specified in section KEYBLIND, and - periodnum is defined in section TIME-PERIODS. + INT_8(period_num) ) - where n_replicas is determined by the consensus parameter - "hsdir_n_replicas". + where blinded_public_key is specified in section KEYBLIND, and period_num is + defined in section [TIME-PERIODS]. - Then, for each node listed in the current consensus with the HSDir3 - flag, we compute a directory index for that node as: + Then, for each node listed in the current consensus with the HSDirV3 flag, + we compute a directory index for that node as: hsdir_index(node) = H("node-idx" | node_identity_digest | - shared_random | + shared_random_value | INT_8(period_num) ) - where shared_random is the shared value generated by the authorities - in section PUB-SHAREDRANDOM, and node_identity_digest is a SHA1 - digest of the node's RSA public key as described in tor-spec.txt. + where shared_random_value is the shared value generated by the authorities + in section [PUB-SHAREDRANDOM], and node_identity_digest is a SHA1 digest of + the node's RSA public key as described in tor-spec.txt. Finally, for replicanum in 1...hsdir_n_replicas, the hidden service host uploads descriptors to the first hsdir_spread_store nodes whose @@ -746,6 +743,11 @@ Status: Draft Again, nodes from lower-numbered replicas are disregarded when choosing the spread for a replica. + Hidden services MUST periodically re-publish their descriptor to the + responsible HSDirs. Specifically, hidden services re-publish their + descriptors every 1 hour (also controlled via the 'hs_rend_post_period' + consensus parameter). + HSDirs MUST retain hidden service descriptors for 33 hours before expiring them. That's 24 hours for the time period duration, plus 6 hours for the maximum overlap period span, plus 3 hours for the maximum acceptable client

1 0

[torspec/master] prop224: Clarify behavior when uploading/fetching descriptors.
by asn＠torproject.org 08 May '16

08 May '16

commit d21a06c00de5ddb461414f3c845d429a0f4b9712 Author: George Kadianakis <desnacked(a)riseup.net> Date: Thu Apr 21 14:15:21 2016 +0300 prop224: Clarify behavior when uploading/fetching descriptors. Specifically concering time periods and SRVs. --- proposals/224-rend-spec-ng.txt | 68 ++++++++++++++++++++++++++++++++---------- 1 file changed, 52 insertions(+), 16 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index 3bc1d97..bad3a47 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -666,21 +666,6 @@ Status: Draft system, new shared random values get published at 00:00UTC every day, whereas the overlap period starts at 06:00 and finishes at 12:00UTC. - Here is an illustration of the system: - - +------------------------------------------------------------------+ - | | - | 00:00 12:00 00:00 12:00 00:00 12:00 | - | SRV#1 TP#1 SRV#2 TP#2 SRV#3 TP#3 | - | | - | $ |-----------$-----======|-----------$-----======| | - | overlap12 overlap23 | - | | - +------------------------------------------------------------------+ - - Legend: [TP#1 = Time Period #1] - [SRV#1 = Shared Random Value #1] - 2.2.3. Where to publish a service descriptor The following consensus parameters control where a hidden service @@ -757,7 +742,55 @@ Status: Draft least 3 hours after the descriptor expiration, so that clients with skewed clocks can still visit them through outdated descriptors. -2.2.4. URLs for anonymous uploading and downloading +2.2.4. Using time periods and SRVs to fetch/upload HS descriptors + + Hidden services and clients need to make correct use of time periods and + shared random values (SRVs) to successfuly fetch and upload descriptors. + + As [PUB-SHAREDRANDOM] specifies, consensuses contain two shared random + values (the current one and the previous one). Hidden services and clients + are asked to match these shared random values with descriptor time periods + and use the right SRV when fetching/uploading descriptors. This section + attempts to precisely specify how this works. + + Let's start with an illustration of the system: + + +------------------------------------------------------------------+ + | | + | 00:00 12:00 00:00 12:00 00:00 12:00 | + | SRV#1 TP#1 SRV#2 TP#2 SRV#3 TP#3 | + | | + | $ |-----------$-----======|-----------$-----======| | + | overlap12 overlap23 | + | | + +------------------------------------------------------------------+ + + Legend: [TP#1 = Time Period #1] + [SRV#1 = Shared Random Value #1] + + First of all, during overlap periods, hidden services always use the + _current_ SRV for publishing overlap descriptors. Clients MUST ignore the + overlap period and instead always fetch the current descriptor as described + below. + + The rest of the time, hidden services and clients need to choose the right SRV + to use based on the current time period to upload/fetch the current descriptor. + + Looking at the diagram above, SRV#1 gets published 12 hours before TP#1 + starts and TP#1 lasts 24 hours. By defining the lifetime of SRV#1 to be 36 + hours, we can pair SRV#1 with TP#1. + + Hence, when clients and hidden services first see an SRV for the first time, + they calculate its expiry date (using a 36 hour lifetime) and use that SRV + for uploading/fetching descriptors till it expires. When that SRV expires, + they switch to the next SRV in the consensus. + + During overlap periods, hidden services upload both normal descriptors and + overlap descriptors as described above. + + For more examples and discussion on this technique, please see [SRV-TP-REFS]. + +2.2.5. URLs for anonymous uploading and downloading Hidden service descriptors conforming to this specification are uploaded with an HTTP POST request to the URL @@ -1607,6 +1640,9 @@ References: http://projectbullrun.org/dual-ec/ext-rand.html https://lists.torproject.org/pipermail/tor-dev/2015-November/009954.html +[SRV-TP-REFS]: + https://lists.torproject.org/pipermail/tor-dev/2016-April/010759.html + Appendix A. Signature scheme with key blinding [KEYBLIND] As described in [IMD:DIST] and [SUBCRED] above, we require a "key

1 0

[translation/torbutton-torbuttonproperties] Update translations for torbutton-torbuttonproperties
by translation＠torproject.org 08 May '16

08 May '16

commit 15af3af7b99e4a5e2502a6bef78a52fc45e6ea7c Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 21:15:53 2016 +0000 Update translations for torbutton-torbuttonproperties --- sr(a)latin/torbutton.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr(a)latin/torbutton.properties b/sr(a)latin/torbutton.properties index c19b2e9..928db66 100644 --- a/sr(a)latin/torbutton.properties +++ b/sr(a)latin/torbutton.properties @@ -15,8 +15,8 @@ torbutton.panel.plugins.enabled = Klikni da onemogućiš plugin-ove torbutton.panel.label.disabled = Tor onemogućen torbutton.panel.label.enabled = Tor omogućen extensions.torbutton(a)torproject.org.description = Torbutton omogućuje dugme za konfiguraciju Tor podešavanja i brzo, lako i jasno briše privatne podatke o pretraživanju -torbutton.popup.history.warning = Torbutton blocked activity from a tab loaded in a different Tor state.\n\nThis is to work around Firefox Bugs 409737 and 417869.\n\nIf this popup seemed to happen for no reason, one of your tabs is attempting to reload itself in the background, and this was blocked.\n\nTo reload the tab in this Tor state, hit 'enter' in the URL location box.\n\n -torbutton.popup.plugin.warning = Torbutton blocked direct Tor load of plugin content.\n\nUse Save-As instead.\n\n +torbutton.popup.history.warning = Torbutton blokirana aktivnost u posebnom jezičku za drugačije Tor stanje\nOvo će raditi za Firefox Bug 409737 i 417869.\nUkoliko se ovaj popup prozor pojavi bez nekog posebnog razloga, jedan od vaših jezičaka pokušava da se podigne u pozadini, a ta aktivnost je blokirana.\nDa ponovo podignete tab u trenutnom Tor stanju, pritisnite 'enter' u polju za URL\n +torbutton.popup.plugin.warning = Torbutton je blokirao direktno podizanje Tor-a od strane nekog plugin dodatka.\nKoristite Sačuvaj-Kao\n torbutton.popup.confirm_ca_certs = Torbutton Note: It appears you have no custom Certificate Authorities. Examining the Certificate Authority list is a slow operation and slows down Tor toggle. Would you like to disable the isolation of Certificate Authority certificates? (If you don't understand this, it is safe to click OK) torbutton.popup.ff3.warning = Warning!\n\nTorbutton on Firefox 3 is known to leak your timezone and livemarks via Tor.\n\nDo you wish to continue anyway? torbutton.popup.toggle.warning = You need to toggle Tor or restart for your settings to take effect.

1 0

[translation/torbutton-torbuttonproperties] Update translations for torbutton-torbuttonproperties
by translation＠torproject.org 08 May '16

08 May '16

commit 21335d4e7aa4bd078713dcc71fa5870b9d849aba Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 20:45:52 2016 +0000 Update translations for torbutton-torbuttonproperties --- sr(a)latin/torbutton.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr(a)latin/torbutton.properties b/sr(a)latin/torbutton.properties index 26901c5..c19b2e9 100644 --- a/sr(a)latin/torbutton.properties +++ b/sr(a)latin/torbutton.properties @@ -14,7 +14,7 @@ torbutton.panel.plugins.disabled = Klikni da omogućiš plugin-ove torbutton.panel.plugins.enabled = Klikni da onemogućiš plugin-ove torbutton.panel.label.disabled = Tor onemogućen torbutton.panel.label.enabled = Tor omogućen -extensions.torbutton(a)torproject.org.description = Torbutton provides a button to configure Tor settings and quickly and easily clear private browsing data. +extensions.torbutton(a)torproject.org.description = Torbutton omogućuje dugme za konfiguraciju Tor podešavanja i brzo, lako i jasno briše privatne podatke o pretraživanju torbutton.popup.history.warning = Torbutton blocked activity from a tab loaded in a different Tor state.\n\nThis is to work around Firefox Bugs 409737 and 417869.\n\nIf this popup seemed to happen for no reason, one of your tabs is attempting to reload itself in the background, and this was blocked.\n\nTo reload the tab in this Tor state, hit 'enter' in the URL location box.\n\n torbutton.popup.plugin.warning = Torbutton blocked direct Tor load of plugin content.\n\nUse Save-As instead.\n\n torbutton.popup.confirm_ca_certs = Torbutton Note: It appears you have no custom Certificate Authorities. Examining the Certificate Authority list is a slow operation and slows down Tor toggle. Would you like to disable the isolation of Certificate Authority certificates? (If you don't understand this, it is safe to click OK)

1 0

[stem/master] Tutorial example of resuming an ephemeral hidden service
by atagar＠torproject.org 08 May '16

08 May '16

commit 3818c9a75221014caa1e84696164cdbe18b7cd96 Author: Damian Johnson <atagar(a)torproject.org> Date: Sun May 8 11:21:52 2016 -0700 Tutorial example of resuming an ephemeral hidden service On irc umoukun requested an example of how to reuse a *.onion address. Great idea! --- .../example/resuming_ephemeral_hidden_service.py | 23 ++++++++++++++++++++++ docs/change_log.rst | 1 + docs/download.rst | 2 +- docs/tutorials/over_the_river.rst | 11 +++++++---- 4 files changed, 32 insertions(+), 5 deletions(-) diff --git a/docs/_static/example/resuming_ephemeral_hidden_service.py b/docs/_static/example/resuming_ephemeral_hidden_service.py new file mode 100644 index 0000000..d2073f0 --- /dev/null +++ b/docs/_static/example/resuming_ephemeral_hidden_service.py @@ -0,0 +1,23 @@ +import os +from stem.control import Controller + +key_path = os.path.expanduser('~/my_service_key') + +with Controller.from_port() as controller: + controller.authenticate() + + if not os.path.exists(key_path): + service = controller.create_ephemeral_hidden_service({80: 5000}, await_publication = True) + print("Started a new hidden service with the address of %s.onion" % service.service_id) + + with open(key_path, 'w') as key_file: + key_file.write('%s:%s' % (service.private_key_type, service.private_key)) + else: + with open(key_path) as key_file: + key_type, key_content = key_file.read().split(':', 1) + + service = controller.create_ephemeral_hidden_service({80: 5000}, key_type = key_type, key_content = key_content, await_publication = True) + print("Resumed %s.onion" % service.service_id) + + raw_input('press any key to shut the service down...') + controller.remove_ephemeral_hidden_service(service.service_id) diff --git a/docs/change_log.rst b/docs/change_log.rst index 13824b2..b443c69 100644 --- a/docs/change_log.rst +++ b/docs/change_log.rst @@ -97,6 +97,7 @@ The following are only available within Stem's `git repository * `Comparison of our descriptor parsing libraries <tutorials/mirror_mirror_on_the_wall.html#are-there-any-other-parsing-libraries>`_ * Example for `custom path selection for circuits <tutorials/to_russia_with_love.html#custom-path-selection>`_ (:trac:`8728`) + * Example for `persisting ephemeral hidden service keys <<tutorials/over_the_river.html#ephemeral-hidden-services>`_ .. _version_1.4: diff --git a/docs/download.rst b/docs/download.rst index 64a3ca7..dfa234d 100644 --- a/docs/download.rst +++ b/docs/download.rst @@ -127,7 +127,7 @@ Download :target: https://apps.fedoraproject.org/packages/python-stem Packages maintained by Juan for Fedora. These include **python-stem** - (Stem for Python 2.x), **python3-stem** (Stem for Python 3.x), and + (for Python 2.x), **python3-stem** (for Python 3.x), and **python-stem-doc** (this website). :: diff --git a/docs/tutorials/over_the_river.rst b/docs/tutorials/over_the_river.rst index 67ff2e1..3f8ae0c 100644 --- a/docs/tutorials/over_the_river.rst +++ b/docs/tutorials/over_the_river.rst @@ -86,10 +86,6 @@ This has been a limitation of hidden services for years. However, as of version 0.2.7.1 Tor offers another style for making services called **ephemeral hidden services**. -Ephemeral hidden services do not touch disk, and as such are easier to work -with but require you to persist your service's private key yourself if you want -to reuse a '.onion' address. - Ephemeral services can only be created through the controller, and only exist as long as your controller is attached unless you provide the **detached** flag. Controllers can only see their own ephemeral services, and ephemeral @@ -107,6 +103,13 @@ For example, with a ephemeral service our earlier example becomes as simple as.. .. literalinclude:: /_static/example/ephemeral_hidden_services.py :language: python +Ephemeral hidden services do not touch disk, and as such are easier to work +with but require you to persist your service's private key yourself if you want +to reuse a '.onion' address... + +.. literalinclude:: /_static/example/resuming_ephemeral_hidden_service.py + :language: python + .. _hidden-service-descriptors: Hidden service descriptors

1 0

[translation/tor-launcher-network-settings_completed] Update translations for tor-launcher-network-settings_completed
by translation＠torproject.org 08 May '16

08 May '16

commit b4ab254e57c111a3d13e88c7f77131081c91ea3f Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 17:45:48 2016 +0000 Update translations for tor-launcher-network-settings_completed --- fr/network-settings.dtd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fr/network-settings.dtd b/fr/network-settings.dtd index 16bdfac..7368863 100644 --- a/fr/network-settings.dtd +++ b/fr/network-settings.dtd @@ -13,7 +13,7 @@ <!ENTITY torSettings.firstQuestion "Laquelle des phrases suivantes décrit le mieux votre situation ?"> <!ENTITY torSettings.configurePrompt1 "Le connexion internet de cet ordinateur est restreinte (censurée) ou passe par un proxy."> -<!ENTITY torSettings.configurePrompt2 "Je dois configurer le pont réseau ou les paramètres du proxy avant de me connecter au réseau Tor."> +<!ENTITY torSettings.configurePrompt2 "Je dois configurer le bridge ou les paramètres du proxy avant de me connecter au réseau Tor."> <!ENTITY torSettings.configure "Configurer"> <!ENTITY torSettings.connectPrompt2 "Je voudrais faire une connexion directe au réseau Tor."> <!ENTITY torSettings.connectPrompt3 "Cela fonctionnera dans la plupart des situations."> @@ -55,15 +55,15 @@ <!ENTITY torsettings.firewall.checkbox "Cet ordinateur passe par un pare-feu qui autorise uniquement les connexions à certains ports"> <!ENTITY torsettings.firewall.allowedPorts "Ports autorisés :"> <!ENTITY torsettings.useBridges.checkbox "Mon Fournisseur d'Accès à Internet (FAI) bloque les connexions au réseau Tor"> -<!ENTITY torsettings.useBridges.default "Se connecter en utilisant les ponts pré-configurés"> -<!ENTITY torsettings.useBridges.note "Chaque type de pont utilise une méthode différente pour éviter la censure. Si un pont ne marche pas, essayez de nouveau avec un autre."> +<!ENTITY torsettings.useBridges.default "Se connecter en utilisant les bridges pré-configurés"> +<!ENTITY torsettings.useBridges.note "Chaque type de bridge utilise une méthode différente pour éviter la censure. Si un bridge ne marche pas, essayez de nouveau avec un autre."> <!ENTITY torsettings.useBridges.type "Mode de transport:"> <!ENTITY torsettings.useBridges.custom "Entrez vos ponts personnels"> <!ENTITY torsettings.useBridges.label "Saisir un ou davantage de ponts relais (un par ligne)."> <!ENTITY torsettings.useBridges.placeholder "tapez adresse:port"> <!ENTITY torsettings.copyLog "Copier le journal des messages de Tor dans le presse-papier"> -<!ENTITY torsettings.bridgeHelpTitle "Aide pour les ponts"> +<!ENTITY torsettings.bridgeHelpTitle "Aide pour les bridges"> <!ENTITY torsettings.bridgeHelp1 "Si vous ne pouvez pas vous connecter au réseau Tor, il se pourrait que votre fournisseur d'accès à Internet (FAI) ou une autre agence bloque le Tor.  Souvent, vous pouvez contourner ce problème en utilisant des bridges Tor, qui sont des relais non listés qui sont plus difficiles à bloquer."> <!ENTITY torsettings.bridgeHelp1B "Vous pouvez utiliser la liste fournie et pré-configurée d'adresses de bridges, ou alors obtenir une liste personnalisée d'adresses en utilisant une de ces méthodes :"> <!ENTITY torsettings.bridgeHelp2Heading "Par le Web">

1 0

[translation/tor-launcher-network-settings] Update translations for tor-launcher-network-settings
by translation＠torproject.org 08 May '16

08 May '16

commit 92a5b3a50fca8bda1309b501aa43fd83871189df Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 17:45:45 2016 +0000 Update translations for tor-launcher-network-settings --- fr/network-settings.dtd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fr/network-settings.dtd b/fr/network-settings.dtd index 16bdfac..7368863 100644 --- a/fr/network-settings.dtd +++ b/fr/network-settings.dtd @@ -13,7 +13,7 @@ <!ENTITY torSettings.firstQuestion "Laquelle des phrases suivantes décrit le mieux votre situation ?"> <!ENTITY torSettings.configurePrompt1 "Le connexion internet de cet ordinateur est restreinte (censurée) ou passe par un proxy."> -<!ENTITY torSettings.configurePrompt2 "Je dois configurer le pont réseau ou les paramètres du proxy avant de me connecter au réseau Tor."> +<!ENTITY torSettings.configurePrompt2 "Je dois configurer le bridge ou les paramètres du proxy avant de me connecter au réseau Tor."> <!ENTITY torSettings.configure "Configurer"> <!ENTITY torSettings.connectPrompt2 "Je voudrais faire une connexion directe au réseau Tor."> <!ENTITY torSettings.connectPrompt3 "Cela fonctionnera dans la plupart des situations."> @@ -55,15 +55,15 @@ <!ENTITY torsettings.firewall.checkbox "Cet ordinateur passe par un pare-feu qui autorise uniquement les connexions à certains ports"> <!ENTITY torsettings.firewall.allowedPorts "Ports autorisés :"> <!ENTITY torsettings.useBridges.checkbox "Mon Fournisseur d'Accès à Internet (FAI) bloque les connexions au réseau Tor"> -<!ENTITY torsettings.useBridges.default "Se connecter en utilisant les ponts pré-configurés"> -<!ENTITY torsettings.useBridges.note "Chaque type de pont utilise une méthode différente pour éviter la censure. Si un pont ne marche pas, essayez de nouveau avec un autre."> +<!ENTITY torsettings.useBridges.default "Se connecter en utilisant les bridges pré-configurés"> +<!ENTITY torsettings.useBridges.note "Chaque type de bridge utilise une méthode différente pour éviter la censure. Si un bridge ne marche pas, essayez de nouveau avec un autre."> <!ENTITY torsettings.useBridges.type "Mode de transport:"> <!ENTITY torsettings.useBridges.custom "Entrez vos ponts personnels"> <!ENTITY torsettings.useBridges.label "Saisir un ou davantage de ponts relais (un par ligne)."> <!ENTITY torsettings.useBridges.placeholder "tapez adresse:port"> <!ENTITY torsettings.copyLog "Copier le journal des messages de Tor dans le presse-papier"> -<!ENTITY torsettings.bridgeHelpTitle "Aide pour les ponts"> +<!ENTITY torsettings.bridgeHelpTitle "Aide pour les bridges"> <!ENTITY torsettings.bridgeHelp1 "Si vous ne pouvez pas vous connecter au réseau Tor, il se pourrait que votre fournisseur d'accès à Internet (FAI) ou une autre agence bloque le Tor.  Souvent, vous pouvez contourner ce problème en utilisant des bridges Tor, qui sont des relais non listés qui sont plus difficiles à bloquer."> <!ENTITY torsettings.bridgeHelp1B "Vous pouvez utiliser la liste fournie et pré-configurée d'adresses de bridges, ou alors obtenir une liste personnalisée d'adresses en utilisant une de ces méthodes :"> <!ENTITY torsettings.bridgeHelp2Heading "Par le Web">

1 0

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 08 May '16

08 May '16

commit 573a9dbd6357857aef9a9ec2cc84822e65e677a1 Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 17:45:07 2016 +0000 Update translations for bridgedb_completed --- fr/LC_MESSAGES/bridgedb.po | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/fr/LC_MESSAGES/bridgedb.po b/fr/LC_MESSAGES/bridgedb.po index 8306247..024726c 100644 --- a/fr/LC_MESSAGES/bridgedb.po +++ b/fr/LC_MESSAGES/bridgedb.po @@ -20,14 +20,14 @@ # syl_, 2016 # themen <themen2004(a)gmail.com>, 2014 # Towinet, 2014-2015 -# Trans-fr, 2015 +# French language coordinator <yahoe.001(a)gmail.com>, 2015 # Yannick Heintz, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2016-03-21 16:27+0000\n" +"PO-Revision-Date: 2016-05-08 17:38+0000\n" "Last-Translator: syl_\n" "Language-Team: French (http://www.transifex.com/otf/torproject/language/fr/)\n" "MIME-Version: 1.0\n" @@ -242,7 +242,7 @@ msgid "" "difficult for anyone watching your internet traffic to determine that you are\n" "using Tor.\n" "\n" -msgstr "BridgeDB peut fournir des ponts avec plusieurs %stypes de transports enfichables%s, qui peuvent aider à brouiller vos connexions au réseau Tor, ce qui rend plus difficile pour tous ceux qui regardent votre trafic Internet de déterminer que vous utilisez Tor.\n" +msgstr "BridgeDB peut fournir des bridges avec plusieurs %stypes de transports enfichables%s, qui peuvent aider à brouiller vos connexions au réseau Tor, ce qui rend plus difficile pour tous ceux qui regardent votre trafic Internet de déterminer que vous utilisez Tor.\n" #. TRANSLATORS: Please DO NOT translate "Pluggable Transports". #: bridgedb/strings.py:79 @@ -250,7 +250,7 @@ msgid "" "Some bridges with IPv6 addresses are also available, though some Pluggable\n" "Transports aren't IPv6 compatible.\n" "\n" -msgstr "Certains ponts avec les adresses IPv6 sont également disponibles, bien que certains Transports soient enfichables ; ils ne sont pas compatibles avec l'IPv6.\n" +msgstr "Certains bridges avec des adresses IPv6 sont également disponibles, bien que certains Transports soient enfichables ; ils ne sont pas compatibles avec l'IPv6.\n" #. TRANSLATORS: Please DO NOT translate "BridgeDB". #. TRANSLATORS: The phrase "plain-ol'-vanilla" means "plain, boring, @@ -273,7 +273,7 @@ msgstr "Que sont les bridges ?" #: bridgedb/strings.py:102 #, python-format msgid "%s Bridges %s are Tor relays that help you circumvent censorship." -msgstr "%s Les ponts %s sont des relais Tor qui vous aident à contourner la censure." +msgstr "%s Les bridges %s sont des relais Tor qui vous aident à contourner la censure." #: bridgedb/strings.py:107 msgid "I need an alternative way of getting bridges!" @@ -305,7 +305,7 @@ msgid "" "Try including as much info about your case as you can, including the list of\n" "bridges and Pluggable Transports you tried to use, your Tor Browser version,\n" "and any messages which Tor gave out, etc." -msgstr "Essayez d'inclure autant d'infos que possible concernant votre cas, y compris la liste des ponts et des Transports Enfichables (Pluggable Transports) que vous avez essayé d'utiliser, votre version de Tor Browser, et n'importe quel autres messages que Tor vous a sorti, etc." +msgstr "Essayez d'inclure autant d'infos que possible concernant votre cas, y compris la liste des bridges et des Transports Enfichables (Pluggable Transports) que vous avez essayé d'utiliser, votre version de Tor Browser, et n'importe quel autres messages que Tor vous a sorti, etc." #: bridgedb/strings.py:128 msgid "Here are your bridge lines:" @@ -317,7 +317,7 @@ msgstr "Obtenez des ponts !" #: bridgedb/strings.py:133 msgid "Please select options for bridge type:" -msgstr "Sélectionnez vos choix pour le type de pont, s'il vous plaît:" +msgstr "Sélectionnez vos choix pour le type de bridge, s'il vous plaît :" #: bridgedb/strings.py:134 msgid "Do you need IPv6 addresses?"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 08 May '16

08 May '16

commit ecf287dcfaafe6b7414c65f1200657749f69844e Author: Translation commit bot <translation(a)torproject.org> Date: Sun May 8 17:45:04 2016 +0000 Update translations for bridgedb --- fr/LC_MESSAGES/bridgedb.po | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/fr/LC_MESSAGES/bridgedb.po b/fr/LC_MESSAGES/bridgedb.po index 8306247..024726c 100644 --- a/fr/LC_MESSAGES/bridgedb.po +++ b/fr/LC_MESSAGES/bridgedb.po @@ -20,14 +20,14 @@ # syl_, 2016 # themen <themen2004(a)gmail.com>, 2014 # Towinet, 2014-2015 -# Trans-fr, 2015 +# French language coordinator <yahoe.001(a)gmail.com>, 2015 # Yannick Heintz, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2016-03-21 16:27+0000\n" +"PO-Revision-Date: 2016-05-08 17:38+0000\n" "Last-Translator: syl_\n" "Language-Team: French (http://www.transifex.com/otf/torproject/language/fr/)\n" "MIME-Version: 1.0\n" @@ -242,7 +242,7 @@ msgid "" "difficult for anyone watching your internet traffic to determine that you are\n" "using Tor.\n" "\n" -msgstr "BridgeDB peut fournir des ponts avec plusieurs %stypes de transports enfichables%s, qui peuvent aider à brouiller vos connexions au réseau Tor, ce qui rend plus difficile pour tous ceux qui regardent votre trafic Internet de déterminer que vous utilisez Tor.\n" +msgstr "BridgeDB peut fournir des bridges avec plusieurs %stypes de transports enfichables%s, qui peuvent aider à brouiller vos connexions au réseau Tor, ce qui rend plus difficile pour tous ceux qui regardent votre trafic Internet de déterminer que vous utilisez Tor.\n" #. TRANSLATORS: Please DO NOT translate "Pluggable Transports". #: bridgedb/strings.py:79 @@ -250,7 +250,7 @@ msgid "" "Some bridges with IPv6 addresses are also available, though some Pluggable\n" "Transports aren't IPv6 compatible.\n" "\n" -msgstr "Certains ponts avec les adresses IPv6 sont également disponibles, bien que certains Transports soient enfichables ; ils ne sont pas compatibles avec l'IPv6.\n" +msgstr "Certains bridges avec des adresses IPv6 sont également disponibles, bien que certains Transports soient enfichables ; ils ne sont pas compatibles avec l'IPv6.\n" #. TRANSLATORS: Please DO NOT translate "BridgeDB". #. TRANSLATORS: The phrase "plain-ol'-vanilla" means "plain, boring, @@ -273,7 +273,7 @@ msgstr "Que sont les bridges ?" #: bridgedb/strings.py:102 #, python-format msgid "%s Bridges %s are Tor relays that help you circumvent censorship." -msgstr "%s Les ponts %s sont des relais Tor qui vous aident à contourner la censure." +msgstr "%s Les bridges %s sont des relais Tor qui vous aident à contourner la censure." #: bridgedb/strings.py:107 msgid "I need an alternative way of getting bridges!" @@ -305,7 +305,7 @@ msgid "" "Try including as much info about your case as you can, including the list of\n" "bridges and Pluggable Transports you tried to use, your Tor Browser version,\n" "and any messages which Tor gave out, etc." -msgstr "Essayez d'inclure autant d'infos que possible concernant votre cas, y compris la liste des ponts et des Transports Enfichables (Pluggable Transports) que vous avez essayé d'utiliser, votre version de Tor Browser, et n'importe quel autres messages que Tor vous a sorti, etc." +msgstr "Essayez d'inclure autant d'infos que possible concernant votre cas, y compris la liste des bridges et des Transports Enfichables (Pluggable Transports) que vous avez essayé d'utiliser, votre version de Tor Browser, et n'importe quel autres messages que Tor vous a sorti, etc." #: bridgedb/strings.py:128 msgid "Here are your bridge lines:" @@ -317,7 +317,7 @@ msgstr "Obtenez des ponts !" #: bridgedb/strings.py:133 msgid "Please select options for bridge type:" -msgstr "Sélectionnez vos choix pour le type de pont, s'il vous plaît:" +msgstr "Sélectionnez vos choix pour le type de bridge, s'il vous plaît :" #: bridgedb/strings.py:134 msgid "Do you need IPv6 addresses?"

1 0