August 2015 - tor-commits - lists.torproject.org

[translation/tails-misc] Update translations for tails-misc
by translation＠torproject.org 23 Aug '15

23 Aug '15

commit dd9d0fa22b379ac4b49bd9e84090d04b457c1551 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Aug 23 18:45:41 2015 +0000 Update translations for tails-misc --- el.po | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/el.po b/el.po index 6edb83c..7daea80 100644 --- a/el.po +++ b/el.po @@ -4,7 +4,7 @@ # # Translators: # Adrian Pappas <pappasadrian(a)gmail.com>, 2013,2015 -# Aikaterini Katmada <aikaterini.katmada(a)gmail.com>, 2015 +# Aikaterini Katmada, 2015 # Alex <hestia(a)riseup.net>, 2013 # andromeas <andromeas(a)hotmail.com>, 2014 # andromeas <andromeas(a)hotmail.com>, 2014 @@ -20,10 +20,10 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-06-28 19:40+0200\n" -"PO-Revision-Date: 2015-07-27 23:54+0000\n" -"Last-Translator: Aikaterini Katmada <aikaterini.katmada(a)gmail.com>\n" -"Language-Team: Greek (http://www.transifex.com/projects/p/torproject/language/el/)\n" +"POT-Creation-Date: 2015-08-10 18:53+0200\n" +"PO-Revision-Date: 2015-08-23 18:35+0000\n" +"Last-Translator: Aikaterini Katmada\n" +"Language-Team: Greek (http://www.transifex.com/otf/torproject/language/el/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -381,19 +381,19 @@ msgid "" " more...</a>" msgstr "<a href='file:///usr/share/doc/tails/website/doc/advanced_topics/virtualization.en.html#security'>Μάθετε περισσότερα (Αγγλικά)...</a>" -#: config/chroot_local-includes/usr/local/bin/tor-browser:24 +#: config/chroot_local-includes/usr/local/bin/tor-browser:29 msgid "Tor is not ready" msgstr "Το Tor δεν είναι έτοιμο" -#: config/chroot_local-includes/usr/local/bin/tor-browser:25 +#: config/chroot_local-includes/usr/local/bin/tor-browser:30 msgid "Tor is not ready. Start Tor Browser anyway?" msgstr "Το Tor δεν είναι έτοιμο. Εκκίνηση του Tor Browser όπως και να 'χει;" -#: config/chroot_local-includes/usr/local/bin/tor-browser:26 +#: config/chroot_local-includes/usr/local/bin/tor-browser:31 msgid "Start Tor Browser" msgstr "Εκκίνηση του Tor Browser" -#: config/chroot_local-includes/usr/local/bin/tor-browser:27 +#: config/chroot_local-includes/usr/local/bin/tor-browser:32 msgid "Cancel" msgstr "Άκυρον"

1 0

[torspec/master] Add 251-netflow-padding.txt
by nickm＠torproject.org 23 Aug '15

23 Aug '15

commit 595a08cb6cfa93addade3ee7bee137b7b298fb8f Author: Nick Mathewson <nickm(a)torproject.org> Date: Sun Aug 23 10:09:38 2015 -0400 Add 251-netflow-padding.txt --- proposals/000-index.txt | 10 +- proposals/251-netflow-padding.txt | 359 +++++++++++++++++++++++++++++++++++++ 2 files changed, 365 insertions(+), 4 deletions(-) diff --git a/proposals/000-index.txt b/proposals/000-index.txt index 5341899..f00f3f0 100644 --- a/proposals/000-index.txt +++ b/proposals/000-index.txt @@ -140,7 +140,7 @@ Proposals by number: 217 Tor Extended ORPort Authentication [FINISHED] 218 Controller events to better understand connection/circuit usage [CLOSED] 219 Support for full DNS and DNSSEC resolution in Tor [DRAFT] -220 Migrate server identity keys to Ed25519 [DRAFT] +220 Migrate server identity keys to Ed25519 [OPEN] 221 Stop using CREATE_FAST [CLOSED] 222 Stop sending client timestamps [CLOSED] 223 Ace: Improved circuit-creation key exchange [OPEN] @@ -148,7 +148,7 @@ Proposals by number: 225 Strawman proposal: commit-and-reveal shared rng [DRAFT] 226 "Scalability and Stability Improvements to BridgeDB: Switching to a Distributed Database System and RDBMS" [OPEN] 227 Include package fingerprints in consensus documents [CLOSED] -228 Cross-certifying identity keys with onion keys [OPEN] +228 Cross-certifying identity keys with onion keys [CLOSED] 229 Further SOCKS5 extensions [DRAFT] 230 How to change RSA1024 relay identity keys [DRAFT] 231 Migrating authority RSA1024 identity keys [DRAFT] @@ -171,6 +171,7 @@ Proposals by number: 248 Remove all RSA identity keys [DRAFT] 249 Allow CREATE cells with >505 bytes of handshake data [DRAFT] 250 Random Number Generation During Tor Voting [DRAFT] +251 Padding for netflow record resolution reduction [DRAFT] Proposals by status: @@ -186,7 +187,6 @@ Proposals by status: 195 TLS certificate normalization for Tor 0.2.4.x [for 0.2.4.x] 203 Avoiding censorship by impersonating an HTTPS server 219 Support for full DNS and DNSSEC resolution in Tor [for 0.2.5.x] - 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 @@ -202,6 +202,7 @@ Proposals by status: 248 Remove all RSA identity keys 249 Allow CREATE cells with >505 bytes of handshake data 250 Random Number Generation During Tor Voting + 251 Padding for netflow record resolution reduction NEEDS-REVISION: 131 Help users to verify they are using Tor 190 Bridge Client Authorization Based on a Shared Secret @@ -227,9 +228,9 @@ Proposals by status: 210 Faster Headless Consensus Bootstrapping [for 0.2.4.x+] 211 Internal Mapaddress for Tor Configuration Testing [for 0.2.4.x+] 212 Increase Acceptable Consensus Age [for 0.2.4.x+] + 220 Migrate server identity keys to Ed25519 [for 0.2.x.x] 223 Ace: Improved circuit-creation key exchange 226 "Scalability and Stability Improvements to BridgeDB: Switching to a Distributed Database System and RDBMS" - 228 Cross-certifying identity keys with onion keys 233 Making Tor2Web mode faster 234 Adding remittance field to directory specification 236 The move to a single guard node @@ -315,6 +316,7 @@ Proposals by status: 221 Stop using CREATE_FAST [for 0.2.5.x] 222 Stop sending client timestamps [in 0.2.4.18] 227 Include package fingerprints in consensus documents [in 0.2.6.3-alpha] + 228 Cross-certifying identity keys with onion keys SUPERSEDED: 112 Bring Back Pathlen Coin Weight 113 Simplifying directory authority administration diff --git a/proposals/251-netflow-padding.txt b/proposals/251-netflow-padding.txt new file mode 100644 index 0000000..c934610 --- /dev/null +++ b/proposals/251-netflow-padding.txt @@ -0,0 +1,359 @@ +Filename: 251-netflow-padding.txt +Title: Padding for netflow record resolution reduction +Authors: Mike Perry +Created: 20 August 2015 +Status: Draft + + +0. Motivation + + It is common practice by many ISPs to record data about the activity of + endpoints that use their uplink, if nothing else for billing purposes, but + sometimes also for monitoring for attacks and general failure. + + Unfortunately, Tor node operators typically have no control over the data + recorded and retained by their ISP. They are often not even informed about + their ISP's retention policy, or the associated data sharing policy of those + records (which tends to be "give them to whoever asks" in practice[1]). + + It is also likely that defenses for this problem will prove useful against + proposed data retention plans in the EU and elsewhere, since these schemes + will likely rely on the same technology. + +0.1. Background + + At the ISP level, this data typically takes the form of Netflow, jFlow, + Netstream, or IPFIX flow records. These records are emitted by gateway + routers in a raw form and then exported (often over plaintext) to a + "collector" that either records them verbatim, or reduces their granularity + further[2]. + + Netflow records and the associated data collection and retention tools are + very configurable, and have many modes of operation, especially when + configured to handle high throughput. However, at ISP scale, per-flow records + are very likely to be employed, since they are the default, and also provide + very high resolution in terms of endpoint activity, second only to full packet + and/or header capture. + + Per-flow records record the endpoint connection 5-tuple, as well as the + total number of bytes sent and received by that 5-tuple during a particular + time period. They can store additional fields as well, but it is primarily + timing and bytecount information that concern us. + + When configured to provide per-flow data, routers emit these raw flow + records periodically for all active connections passing through them + based on two parameters: the "active flow timeout" and the "inactive + flow timeout". + + The "active flow timeout" causes the router to emit a new record + periodically for every active TCP session that continuously sends data. The + default active flow timeout for most routers is 30 minutes, meaning that a + new record is created for every TCP session at least every 30 minutes, no + matter what. This value can be configured to be from 1 minute to 60 minutes + on major routers. + + The "inactive flow timeout" is used by routers to create a new record if a + TCP session is inactive for some number of seconds. It allows routers to + avoid the need to track a large number of idle connections in memory, and + instead emit a separate record only when there is activity. This value + ranges from 10 seconds to 600 seconds on common routers. It appears as + though no routers support a value lower than 10 seconds. + +0.2. Default timeout values of major routers + + For reference, here are default values and ranges (in parenthesis when + known) for common routers, along with citations to their manuals. + + Some routers speak other collection protocols than Netflow, and in the + case of Juniper, use different timeouts for these protocols. Where this + is known to happen, it has been noted. + + Inactive Timeout Active Timeout + Cisco IOS[3] 15s (10-600s) 30min (1-60min) + Cisco Catalyst[4] 5min 32min + Juniper (jFlow)[5] 15s (10-600s) 30min (1-60min) + Juniper (Netflow)[6,7] 60s (10-600s) 30min (1-30min) + H3C (Netstream)[8] 60s (60-600s) 30min (1-60min) + Fortinet[9] 15s 30min + MicroTik[10] 15s 30min + + +1. Proposal Overview + + The combination of the active and inactive netflow record timeouts allow us + to devise a low-cost padding defense that causes what would otherwise be + split records to "collapse" at the router even before they are exported to + the collector for storage. So long as a connection transmits data before the + "inactive flow timeout" expires, then the router will continue to count the + total bytes on that flow before finally emitting a record at the "active + flow timeout". + + This means that for a minimal amount of padding that prevents the "inactive + flow timeout" from expiring, it is possible to reduce the resolution of raw + per-flow netflow data to the total amount of bytes send and received in a 30 + minute window. This is a vast reduction in resolution for HTTP, IRC, XMPP, + SSH, and other intermittent interactive traffic, especially when all + user traffic in that time period is multiplexed over a single connection + (as it is with Tor). + + +2. Implementation + + Tor clients currently maintain one TLS connection to their Guard node to + carry actual application traffic, and make up to 3 additional connections to + other nodes to retrieve directory information. + + We propose to pad only the client's connection to the Guard node, and not + any other connection. We propose to treat Bridge node connections to the Tor + network as client connections, and pad them, but otherwise not pad between + normal relays. + + Both clients and Guards will maintain a timer for all application (ie: + non-directory) TLS connections. Every time a non-padding packet is sent or + received by either end, that endpoint will sample a timeout value from + between 4 seconds and 14 seconds. If the connection becomes active for any + reason before this timer expires, the timer is reset to a new random value + between 4 and 14 seconds. If the connection remains inactive until the timer + expires, a single CELL_PADDING cell will be sent on that connection. + + In this way, the connection will only be padded in the event that it is idle. + +2.1. Tunable parameters + + We propose that the defense be controlled by the following consensus + parameters: + + * nf_ito_low + - The low end of the range to send padding when inactive, in ms. + - Default: 4000 + * nf_ito_high + - The high end of the range to send padding, in ms. + - Default: 14000 + + * nf_pad_relays + - If set to 1, we also pad inactive relay-to-relay connections + - Default: 0 + + * conn_timeout_low + - The low end of the range to decide when we should close an idle + connection (not counting padding). + - Default: 900 seconds after last circuit closes + + * conn_timeout_high + - The high end of the range to decide when we should close an idle + connection. + - Default: 1800 seconds after last circuit close + + If nf_ito_low == nf_ito_high == 0, padding will be disabled. + +2.2. Maximum overhead bounds + + With the default parameters, we expect a padded connection to send one + padding cell every 8 seconds (see Appendix A for the statistical analysis of + expected padding packet rate on an idle link). This averages to 63 bytes per + second, assuming a 512 byte cell and 55 bytes of TLS+TCP+IP headers. For a + connection that remains idle for a full 30 minutes of inactivity, this is + about 112KB of overhead. + + With 2.5M completely idle clients connected simultaneously, 63 bytes per + second still amounts to only 157MB/second network-wide, which is roughly + 1.5X the current amount of Tor directory traffic[11]. Of course, our 2.5M + daily users will neither be connected simultaneously, nor entirely idle, + so we expect the actual overhead to be much lower than this. + + If we choose to set the range such it is no longer even possible to + configure an inactive timeout low enough such that a new record would be + generated, (for example: 6.5 to 9.5 seconds for an average of 8 seconds), + then the maximum possible overhead is 70 bytes/second, 125KB per connection, + and 175MB/sec network-wide. + +2.3. Measuring actual overhead + + To measure the actual padding overhead in practice, we propose to export + the following statistics in extra-info descriptors for the previous (fixed, + non-rolling) 24 hour period: + + * Total cells read (padding and non-padding) + * Total cells written (padding and non-padding) + * Total CELL_PADDING cells read + * Total CELL_PADDING cells written + * Total RELAY_COMMAND_DROP cells read + * Total RELAY_COMMAND_DROP cells written + + These values will be rounded to 100 cells each, and no values are reported if + the relay has read or written less than 10000 cells in the previous period. + + RELAY_COMMAND_DROP cells are circuit-level padding not used by this defense, + but we may as well start recording statistics about them now, too, to aid in + the development of future defenses. + +2.4. Load balancing considerations + + Eventually, we will likely want to update the consensus weights to properly + load balance the selection of Guard nodes that must carry this overhead. + + We propose that we use the extra-info documents to get a more accurate value + for the total average Guard and Guard+Exit node overhead of this defense in + practice, and then use that value to fractionally reduce the consensus + selection weights for Guard nodes and Guard+Exit nodes, to reflect their + reduced capacity relative to middle nodes. + + +3. Threat model and adversarial considerations + + This defense does not assume fully adversarial behavior on the part of the + upstream network administrator, as that administrator typically has no + specific interest in trying to deanonymize Tor, but only in monitoring their + own network for signs of overusage, attack, or failure. + + Therefore, in a manner closer to the "honest but curious" threat model, we + assume that the netflow collector will be using standard equipment not + specifically tuned to capturing Tor traffic. We want to reduce the resolution + of logs that are collected incidentally, so that if they happen to fall into + the wrong hands, we can be more certain will not be useful. + + We feel that this assumption is a fair one because correlation attacks (and + statistical attacks in general) will tend to accumulate false positives very + quickly if the adversary loses resolution at any observation points. It is + especially unlikely for the the attacker to benefit from only a few + high-resolution collection points while the remainder of the Tor network + is only subject to connection-level netflow configuration data retention, + or even less data retention than that. + + Nonetheless, it is still worthwhile to consider what the adversary is capable + of, especially in light of looming data retention regulation. + + Because no major router appears to have the ability to set the inactive + flow timeout below 10 seconds, it would seem as though the adversary is left + with three main options: reduce the active record timeout to the minimum (1 + minute), begin logging full packet and/or header data, or develop a custom + solution. + + It is an open question to what degree these approaches would help the + adversary, especially if only some of its observation points implemented + these changes. + +3.1 What about sampled data? + + At scale, it is known that some Internet backbone routers at AS boundaries + and exchanges perform sampled packet header collection and/or produce + netflow records based on a subset of the packets that pass through their + infrastructure. + + The effects of this against Tor were studied before against the (much + smaller) Tor network as it was in 2007[12]. At sampling rate of 1 out of + every 2000 packets, the attack did not achieve high accuracy until over + 100MB of data were transmitted, even when correlating only 500 flows in + a closed-world lab setting. + + We suspect that this type of attack is unlikely to be effective at scale on + the Tor network today, but we make no claims that this defense will make any + impact upon sampled correlation, primarily because the amount of padding + that this defense introduces is comparatively low relative to the amount of + transmitted traffic that sampled correlation attacks require to attain + any accuracy. + +3.2. What about long-term statistical disclosure? + + This defense similarly does not claim to defeat long-term correlation + attacks involving many observations over large amounts of time. + + However, we do believe it will significantly increase the amount of traffic + and the number of independent observations required to attain the same + accuracy if the adversary uses default per-flow netflow records. + +3.3. What about prior information/confirmation? + + In truth, the most dangerous aspect of these netflow logs is not actually + correlation at all, but confirmation. + + If the adversary has prior information about the location of a target, and/or + when and how that target is expected to be using Tor, then the effectiveness + of this defense will be very situation-dependent (on factors such as the + number of other tor users in the area at that time, etc). + + In any case, the odds that there is other concurrent activity (to + create a false positive) within a single 30 minute record are much higher + than the odds that there is concurrent activity that aligns with a + subset of a series of smaller, more frequent inactive timeout records. + + +4. Synergistic effects with future padding and other changes + + Because this defense only sends padding when the OR connection is completely + idle, it should still operate optimally when combined with other forms of + padding (such as padding for website traffic fingerprinting and hidden + service circuit fingerprinting). If those future defenses choose to send + padding for any reason at any layer of Tor, then this defense + automatically will not. + + In addition to interoperating optimally with any future padding defenses, + simple changes to Tor network usage can serve to further reduce the + usefulness of any data retention, as well as reduce the overhead from this + defense. + + For example, if all directory traffic were also tunneled through the main + Guard node instead of independent directory guards, then the adversary + would lose additional resolution in terms of the ability to differentiate + directory traffic from normal usage, especially when it is occurs within + the same netflow record. As written and specified, the defense will pad + such tunneled directory traffic optimally. + + Similarly, if bridge guards[13] are implemented such that bridges use their + own guard node to route all of their connecting client traffic through, then + users who run bridges bridges will also benefit from the concurrent traffic of + their connected clients, which will also be optimally padded when it is + concurrent with their own. + + +Appendix A: Padding Cell Timeout Distribution Statistics + + It turns out that because the padding is bidirectional, and because both + endpoints are maintaining timers, this creates the situation where the time + before sending a padding packet in either direction is actually + min(client_timeout, server_timeout). + + If client_timeout and server_timeout are uniformly sampled, then the + distribution of min(client_timeout,server_timeout) is no longer uniform, and + the resulting average timeout (Exp[min(X,X)]) is much lower than the + midpoint of the timeout range. + + To compensate for this, instead of sampling each endpoint timeout uniformly, + we instead sample it from max(X,X), where X is uniformly distributed. + + If X is a random variable uniform from 0..R-1 (where R=high-low), then the + random variable Y = max(X,X) has Prob(Y == i) = (2.0*i + 1)/(R*R). + + Then, when both sides apply timeouts sampled from Y, the resulting + bidirectional padding packet rate is now third random variable: + Z = min(Y,Y). + + The distribution of Z is slightly bell-shaped, but mostly flat around the + mean. It also turns out that Exp[Z] ~= Exp[X]. Here's a table of average + values for each random variable: + + R Exp[X] Exp[Z] Exp[min(X,X)] Exp[Y=max(X,X)] + 5000 2499.5 2662 1666.2 3332.8 + 6000 2999.5 3195 1999.5 3999.5 + 10000 4999.5 5328 3332.8 6666.2 + 15000 7499.5 7995 4999.5 9999.5 + 20000 9900.5 10661 6666.2 13332.8 + + In this way, we maintain the property that the midpoint of the timeout range + is the expected mean time before a padding packet is sent in either + direction. + + +1. https://lists.torproject.org/pipermail/tor-relays/2015-August/007575.html +2. https://en.wikipedia.org/wiki/NetFlow +3. http://www.cisco.com/en/US/docs/ios/12_3t/netflow/command/reference/nfl_a1g… +4. http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-swi… +5. https://www.juniper.net/techpubs/software/erx/junose60/swconfig-routing-vol… +6. http://www.jnpr.net/techpubs/en_US/junos15.1/topics/reference/configuration… +7. http://www.jnpr.net/techpubs/en_US/junos15.1/topics/reference/configuration… +8. http://www.h3c.com/portal/Technical_Support___Documents/Technical_Documents… +9. http://docs-legacy.fortinet.com/fgt/handbook/cli52_html/FortiOS%205.2%20CLI… +10. http://wiki.mikrotik.com/wiki/Manual:IP/Traffic_Flow +11. https://metrics.torproject.org/dirbytes.html +12. http://freehaven.net/anonbib/cache/murdoch-pet2007.pdf +13. https://gitweb.torproject.org/torspec.git/tree/proposals/188-bridge-guards.…

1 0

[translation/torbutton-brandproperties_completed] Update translations for torbutton-brandproperties_completed
by translation＠torproject.org 23 Aug '15

23 Aug '15

commit d991537b6914e7b72f63a0fde5f78ba697da48a9 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Aug 23 10:45:51 2015 +0000 Update translations for torbutton-brandproperties_completed --- id/brand.properties | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/id/brand.properties b/id/brand.properties index f8a9f20..8b36aae 100644 --- a/id/brand.properties +++ b/id/brand.properties @@ -2,14 +2,15 @@ # License, v. 2.0. If a copy of the MPL was not distributed with this # file, You can obtain one at http://mozilla.org/MPL/2.0/. +brandShorterName=Peramban Tor brandShortName=Peramban Tor brandFullName=Peramban Tor vendorShortName=Proyek Tor homePageSingleStartMain=Firefox Start, halaman muka yang cepat dengan pencarian bawaan -homePageImport=Impor home pagealaman muka dari %S +homePageImport=Impor halaman beranda Anda dari %S homePageMigrationPageTitle=Pemilihan Halaman Muka -homePageMigrationDescription=Silakan pilih halaman muka yang ingin Anda gunakan: +homePageMigrationDescription=Silahkan pilih halaman beranda yang ingin Anda gunakan: syncBrandShortName=Sinkronkan

1 0

[translation/torbutton-brandproperties] Update translations for torbutton-brandproperties
by translation＠torproject.org 23 Aug '15

23 Aug '15

commit be845944ff600355b06470c8a990fb20d82d85e9 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Aug 23 10:45:47 2015 +0000 Update translations for torbutton-brandproperties --- id/brand.properties | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/id/brand.properties b/id/brand.properties index 8fa1092..8b36aae 100644 --- a/id/brand.properties +++ b/id/brand.properties @@ -2,15 +2,15 @@ # License, v. 2.0. If a copy of the MPL was not distributed with this # file, You can obtain one at http://mozilla.org/MPL/2.0/. -brandShorterName=Tor Browser +brandShorterName=Peramban Tor brandShortName=Peramban Tor brandFullName=Peramban Tor vendorShortName=Proyek Tor homePageSingleStartMain=Firefox Start, halaman muka yang cepat dengan pencarian bawaan -homePageImport=Impor home pagealaman muka dari %S +homePageImport=Impor halaman beranda Anda dari %S homePageMigrationPageTitle=Pemilihan Halaman Muka -homePageMigrationDescription=Silakan pilih halaman muka yang ingin Anda gunakan: +homePageMigrationDescription=Silahkan pilih halaman beranda yang ingin Anda gunakan: syncBrandShortName=Sinkronkan

1 0

[translation/tails-misc_completed] Update translations for tails-misc_completed
by translation＠torproject.org 23 Aug '15

23 Aug '15

commit f574058acb41a10dbfd7b3741e39c023c18dfa15 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Aug 23 10:45:42 2015 +0000 Update translations for tails-misc_completed --- id.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id.po b/id.po index 16b64ab..e806873 100644 --- a/id.po +++ b/id.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2015-08-10 18:53+0200\n" -"PO-Revision-Date: 2015-08-19 08:01+0000\n" +"PO-Revision-Date: 2015-08-23 10:25+0000\n" "Last-Translator: Zamani Karmana <zamani.karmana(a)gmail.com>\n" "Language-Team: Indonesian (http://www.transifex.com/otf/torproject/language/id/)\n" "MIME-Version: 1.0\n"

1 0

[translation/tails-misc] Update translations for tails-misc
by translation＠torproject.org 23 Aug '15

23 Aug '15

commit f491fdb4de2f020690a0c5013f5a9f44605cea24 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Aug 23 10:45:36 2015 +0000 Update translations for tails-misc --- id.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/id.po b/id.po index 16b64ab..e806873 100644 --- a/id.po +++ b/id.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2015-08-10 18:53+0200\n" -"PO-Revision-Date: 2015-08-19 08:01+0000\n" +"PO-Revision-Date: 2015-08-23 10:25+0000\n" "Last-Translator: Zamani Karmana <zamani.karmana(a)gmail.com>\n" "Language-Team: Indonesian (http://www.transifex.com/otf/torproject/language/id/)\n" "MIME-Version: 1.0\n"

1 0

[translation/tails-persistence-setup_completed] Update translations for tails-persistence-setup_completed
by translation＠torproject.org 22 Aug '15

22 Aug '15

commit 05eada753bc56eb82439ec54f9bbd5637d6d1786 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Aug 22 20:15:26 2015 +0000 Update translations for tails-persistence-setup_completed --- gl/gl.po | 65 +++++++++++++++++++++++++++++++++++--------------------------- 1 file changed, 37 insertions(+), 28 deletions(-) diff --git a/gl/gl.po b/gl/gl.po index 9ef79ae..be2e4f4 100644 --- a/gl/gl.po +++ b/gl/gl.po @@ -3,16 +3,17 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# pakoR <gmpakor(a)gmail.com>, 2015 # manuel meixide <m.meixide(a)gmail.com>, 2013 # Xnake, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" -"POT-Creation-Date: 2014-04-16 21:26+0200\n" -"PO-Revision-Date: 2014-05-10 22:20+0000\n" -"Last-Translator: Xnake\n" -"Language-Team: Galician (http://www.transifex.com/projects/p/torproject/language/gl/)\n" +"POT-Creation-Date: 2015-08-05 19:02+0200\n" +"PO-Revision-Date: 2015-08-22 20:07+0000\n" +"Last-Translator: pakoR <gmpakor(a)gmail.com>\n" +"Language-Team: Galician (http://www.transifex.com/otf/torproject/language/gl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -80,8 +81,8 @@ msgid "Browser bookmarks" msgstr "Marcadores do navegador" #: ../lib/Tails/Persistence/Configuration/Presets.pm:120 -msgid "Bookmarks saved in Iceweasel browser" -msgstr "Marcadores gardados no navegador Iceweasel" +msgid "Bookmarks saved in the Tor Browser" +msgstr "Marcadores gardados no Tor Browser" #: ../lib/Tails/Persistence/Configuration/Presets.pm:128 msgid "Printers" @@ -92,26 +93,34 @@ msgid "Printers configuration" msgstr "Configuración de impresoras" #: ../lib/Tails/Persistence/Configuration/Presets.pm:138 +msgid "Bitcoin client" +msgstr "Cliente de Bitcoin" + +#: ../lib/Tails/Persistence/Configuration/Presets.pm:140 +msgid "Electrum's bitcoin wallet and configuration" +msgstr "Carteira de bitcoin Electrum e configuración" + +#: ../lib/Tails/Persistence/Configuration/Presets.pm:148 msgid "APT Packages" msgstr "Paquetes APT" -#: ../lib/Tails/Persistence/Configuration/Presets.pm:140 +#: ../lib/Tails/Persistence/Configuration/Presets.pm:150 msgid "Packages downloaded by APT" msgstr "Paquetes descargados polo APT" -#: ../lib/Tails/Persistence/Configuration/Presets.pm:148 +#: ../lib/Tails/Persistence/Configuration/Presets.pm:158 msgid "APT Lists" msgstr "Listas APT" -#: ../lib/Tails/Persistence/Configuration/Presets.pm:150 +#: ../lib/Tails/Persistence/Configuration/Presets.pm:160 msgid "Lists downloaded by APT" msgstr "Listas descargadas polo APT" -#: ../lib/Tails/Persistence/Configuration/Presets.pm:158 +#: ../lib/Tails/Persistence/Configuration/Presets.pm:168 msgid "Dotfiles" msgstr "Dotfiles (arquivos de configuracións \".arquivo\")" -#: ../lib/Tails/Persistence/Configuration/Presets.pm:160 +#: ../lib/Tails/Persistence/Configuration/Presets.pm:170 msgid "" "Symlink into $HOME every file or directory found in the `dotfiles' directory" msgstr "Crear ligazóns simbólicas (symlinks) en $HOME para todos os arquivos ou cartafois que estean no cartafol 'dotfiles'" @@ -120,67 +129,67 @@ msgstr "Crear ligazóns simbólicas (symlinks) en $HOME para todos os arquivos o msgid "Setup Tails persistent volume" msgstr "Configure o volume persistente de Tails" -#: ../lib/Tails/Persistence/Setup.pm:337 +#: ../lib/Tails/Persistence/Setup.pm:307 ../lib/Tails/Persistence/Setup.pm:451 +msgid "Error" +msgstr "Erro" + +#: ../lib/Tails/Persistence/Setup.pm:338 #, perl-format msgid "Device %s already has a persistent volume." msgstr "O dispositivo %s xa ten un volume persistente." -#: ../lib/Tails/Persistence/Setup.pm:345 +#: ../lib/Tails/Persistence/Setup.pm:346 #, perl-format msgid "Device %s has not enough unallocated space." msgstr "O dispositivo %s non ten espazo suficiente sen asignar." -#: ../lib/Tails/Persistence/Setup.pm:353 ../lib/Tails/Persistence/Setup.pm:367 +#: ../lib/Tails/Persistence/Setup.pm:354 ../lib/Tails/Persistence/Setup.pm:368 #, perl-format msgid "Device %s has no persistent volume." msgstr "O dispositivo %s non ten un volume persistente." -#: ../lib/Tails/Persistence/Setup.pm:359 +#: ../lib/Tails/Persistence/Setup.pm:360 msgid "" "Cannot delete the persistent volume while in use. You should restart Tails " "without persistence." msgstr "Non se pode eliminar o volume persistente estando en uso. Debe reiniciar o Tails sen persistencia." -#: ../lib/Tails/Persistence/Setup.pm:378 +#: ../lib/Tails/Persistence/Setup.pm:379 msgid "Persistence volume is not unlocked." msgstr "O volume de persistencia non está desbloqueado." -#: ../lib/Tails/Persistence/Setup.pm:383 +#: ../lib/Tails/Persistence/Setup.pm:384 msgid "Persistence volume is not mounted." msgstr "O volume de persistencia non está montado." -#: ../lib/Tails/Persistence/Setup.pm:388 +#: ../lib/Tails/Persistence/Setup.pm:389 msgid "Persistence volume is not readable. Permissions or ownership problems?" msgstr "O volume de persistencia non é lexible. Problemas de permisos ou de propiedade?" -#: ../lib/Tails/Persistence/Setup.pm:393 +#: ../lib/Tails/Persistence/Setup.pm:394 msgid "Persistence volume is not writable. Maybe it was mounted read-only?" msgstr "O volume de persistencia non é grabable. Talvez se montou en modo só-lectura?" -#: ../lib/Tails/Persistence/Setup.pm:402 +#: ../lib/Tails/Persistence/Setup.pm:403 #, perl-format msgid "Tails is running from non-USB / non-SDIO device %s." msgstr "Tails está a se executar a partir dun dispositivo %s non-USB / non-SDIO." -#: ../lib/Tails/Persistence/Setup.pm:408 +#: ../lib/Tails/Persistence/Setup.pm:409 #, perl-format msgid "Device %s is optical." msgstr "O dispositivo %s é óptico." -#: ../lib/Tails/Persistence/Setup.pm:415 +#: ../lib/Tails/Persistence/Setup.pm:416 #, perl-format msgid "Device %s was not created using Tails Installer." msgstr "O dispositivo %s non foi creado usando o Instalador de Tails" -#: ../lib/Tails/Persistence/Setup.pm:450 -msgid "Error" -msgstr "Erro" - -#: ../lib/Tails/Persistence/Setup.pm:670 +#: ../lib/Tails/Persistence/Setup.pm:676 msgid "Persistence wizard - Finished" msgstr "Asistente de Persistencia - Rematou" -#: ../lib/Tails/Persistence/Setup.pm:673 +#: ../lib/Tails/Persistence/Setup.pm:679 msgid "" "Any changes you have made will only take effect after restarting Tails.\n" "\n"

1 0

[translation/tails-persistence-setup] Update translations for tails-persistence-setup
by translation＠torproject.org 22 Aug '15

22 Aug '15

commit 78f5cee8eed2ebfe1f976574a8ad06bbc787898b Author: Translation commit bot <translation(a)torproject.org> Date: Sat Aug 22 20:15:21 2015 +0000 Update translations for tails-persistence-setup --- gl/gl.po | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/gl/gl.po b/gl/gl.po index a6afb6d..be2e4f4 100644 --- a/gl/gl.po +++ b/gl/gl.po @@ -3,16 +3,17 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# pakoR <gmpakor(a)gmail.com>, 2015 # manuel meixide <m.meixide(a)gmail.com>, 2013 # Xnake, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" -"POT-Creation-Date: 2015-02-23 13:07+0100\n" -"PO-Revision-Date: 2015-02-24 10:24+0000\n" -"Last-Translator: runasand <runa.sandvik(a)gmail.com>\n" -"Language-Team: Galician (http://www.transifex.com/projects/p/torproject/language/gl/)\n" +"POT-Creation-Date: 2015-08-05 19:02+0200\n" +"PO-Revision-Date: 2015-08-22 20:07+0000\n" +"Last-Translator: pakoR <gmpakor(a)gmail.com>\n" +"Language-Team: Galician (http://www.transifex.com/otf/torproject/language/gl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -81,7 +82,7 @@ msgstr "Marcadores do navegador" #: ../lib/Tails/Persistence/Configuration/Presets.pm:120 msgid "Bookmarks saved in the Tor Browser" -msgstr "" +msgstr "Marcadores gardados no Tor Browser" #: ../lib/Tails/Persistence/Configuration/Presets.pm:128 msgid "Printers" @@ -93,11 +94,11 @@ msgstr "Configuración de impresoras" #: ../lib/Tails/Persistence/Configuration/Presets.pm:138 msgid "Bitcoin client" -msgstr "" +msgstr "Cliente de Bitcoin" #: ../lib/Tails/Persistence/Configuration/Presets.pm:140 msgid "Electrum's bitcoin wallet and configuration" -msgstr "" +msgstr "Carteira de bitcoin Electrum e configuración" #: ../lib/Tails/Persistence/Configuration/Presets.pm:148 msgid "APT Packages"

1 0

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 22 Aug '15

22 Aug '15

commit 2bea8ab085e12f9898feee6c204223cc873d5df0 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Aug 22 19:15:07 2015 +0000 Update translations for bridgedb_completed --- pt_BR/LC_MESSAGES/bridgedb.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pt_BR/LC_MESSAGES/bridgedb.po b/pt_BR/LC_MESSAGES/bridgedb.po index b83f2ae..e41c11c 100644 --- a/pt_BR/LC_MESSAGES/bridgedb.po +++ b/pt_BR/LC_MESSAGES/bridgedb.po @@ -17,7 +17,7 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'POT-Creation-Date: 2015-03-19 22:13+0000\n" -"PO-Revision-Date: 2015-08-22 18:44+0000\n" +"PO-Revision-Date: 2015-08-22 19:04+0000\n" "Last-Translator: Luciana Dark Blue <lucianadarkblue(a)gmail.com>\n" "Language-Team: Portuguese (Brazil) (http://www.transifex.com/otf/torproject/language/pt_BR/)\n" "MIME-Version: 1.0\n" @@ -235,7 +235,7 @@ msgid "" "paste the bridge lines into the text input box. Finally, click 'Connect', and\n" "you should be good to go! If you experience trouble, try clicking the 'Help'\n" "button in the 'Tor Network Settings' wizard for further assistance." -msgstr "Selecione 'Sim' e então clique em 'Proximo'. Para configurar suas novas pontes, copie e \ncole a ponte copiada na caixa de texto. Finalmente, clique em 'Conectar', e\nvocê deve estar pronto! Se você presenciar problemas, tente clicar no botão\n'Ajuda' no assistente 'Configurações da Tor Network' para mais assistencia." +msgstr "Selecione 'Sim' e então clique em 'Próximo'. Para configurar suas novas conexões, copie e cole as coordenadas na caixa de texto. Finalmente, clique em 'Conectar'. Deve ser o suficiente! Se encontrar problemas, tente clicar no botão 'Ajuda' no assistente de 'Configurações da Tor Network' para maiores informações." #: lib/bridgedb/strings.py:142 msgid "Displays this message." @@ -246,7 +246,7 @@ msgstr "Mostrar essa mensagem." #. "plain-ol'-vanilla" bridges. #: lib/bridgedb/strings.py:146 msgid "Request vanilla bridges." -msgstr "Solicitar pontes VANILLA." +msgstr "Solicitar conexões TRADICIONAIS." #: lib/bridgedb/strings.py:147 msgid "Request IPv6 bridges." @@ -308,7 +308,7 @@ msgstr "Parece que houve um erro ao obter seu QRCode" msgid "" "This QRCode contains your bridge lines. Scan it with a QRCode reader to copy" " your bridge lines onto mobile and other devices." -msgstr "Este Código QR contém suas linhas de conexões, escaneie-o com um leitor de Código QR para copiar suas linhas de conexões para um dispositivo móvel e outro dispositivos." +msgstr "Este Código QR contém suas linhas de conexões. Escaneie-o com um leitor de Código QR para copiar as linhas de conexões para um dispositivo móvel e outros dispositivos." #: lib/bridgedb/templates/bridges.html:181 msgid "There currently aren't any bridges available..." @@ -358,7 +358,7 @@ msgstr "Agora, %s inserir as pontes no Navegador Tor %s" #: lib/bridgedb/templates/options.html:38 #, python-format msgid "%sJ%sust give me bridges!" -msgstr "%sS%só me dê pontes!" +msgstr "%sS%só me dê conexões!" #: lib/bridgedb/templates/options.html:52 msgid "Advanced Options" @@ -386,4 +386,4 @@ msgstr "%sS%sim!" #: lib/bridgedb/templates/options.html:151 #, python-format msgid "%sG%set Bridges" -msgstr "%sO%sbtenha Pontes" +msgstr "%sO%sbtenha Conexões"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 22 Aug '15

22 Aug '15

commit 6ef94cdf7beb69984029fbfa108df5355e6ac13f Author: Translation commit bot <translation(a)torproject.org> Date: Sat Aug 22 19:15:03 2015 +0000 Update translations for bridgedb --- pt_BR/LC_MESSAGES/bridgedb.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pt_BR/LC_MESSAGES/bridgedb.po b/pt_BR/LC_MESSAGES/bridgedb.po index b83f2ae..e41c11c 100644 --- a/pt_BR/LC_MESSAGES/bridgedb.po +++ b/pt_BR/LC_MESSAGES/bridgedb.po @@ -17,7 +17,7 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'POT-Creation-Date: 2015-03-19 22:13+0000\n" -"PO-Revision-Date: 2015-08-22 18:44+0000\n" +"PO-Revision-Date: 2015-08-22 19:04+0000\n" "Last-Translator: Luciana Dark Blue <lucianadarkblue(a)gmail.com>\n" "Language-Team: Portuguese (Brazil) (http://www.transifex.com/otf/torproject/language/pt_BR/)\n" "MIME-Version: 1.0\n" @@ -235,7 +235,7 @@ msgid "" "paste the bridge lines into the text input box. Finally, click 'Connect', and\n" "you should be good to go! If you experience trouble, try clicking the 'Help'\n" "button in the 'Tor Network Settings' wizard for further assistance." -msgstr "Selecione 'Sim' e então clique em 'Proximo'. Para configurar suas novas pontes, copie e \ncole a ponte copiada na caixa de texto. Finalmente, clique em 'Conectar', e\nvocê deve estar pronto! Se você presenciar problemas, tente clicar no botão\n'Ajuda' no assistente 'Configurações da Tor Network' para mais assistencia." +msgstr "Selecione 'Sim' e então clique em 'Próximo'. Para configurar suas novas conexões, copie e cole as coordenadas na caixa de texto. Finalmente, clique em 'Conectar'. Deve ser o suficiente! Se encontrar problemas, tente clicar no botão 'Ajuda' no assistente de 'Configurações da Tor Network' para maiores informações." #: lib/bridgedb/strings.py:142 msgid "Displays this message." @@ -246,7 +246,7 @@ msgstr "Mostrar essa mensagem." #. "plain-ol'-vanilla" bridges. #: lib/bridgedb/strings.py:146 msgid "Request vanilla bridges." -msgstr "Solicitar pontes VANILLA." +msgstr "Solicitar conexões TRADICIONAIS." #: lib/bridgedb/strings.py:147 msgid "Request IPv6 bridges." @@ -308,7 +308,7 @@ msgstr "Parece que houve um erro ao obter seu QRCode" msgid "" "This QRCode contains your bridge lines. Scan it with a QRCode reader to copy" " your bridge lines onto mobile and other devices." -msgstr "Este Código QR contém suas linhas de conexões, escaneie-o com um leitor de Código QR para copiar suas linhas de conexões para um dispositivo móvel e outro dispositivos." +msgstr "Este Código QR contém suas linhas de conexões. Escaneie-o com um leitor de Código QR para copiar as linhas de conexões para um dispositivo móvel e outros dispositivos." #: lib/bridgedb/templates/bridges.html:181 msgid "There currently aren't any bridges available..." @@ -358,7 +358,7 @@ msgstr "Agora, %s inserir as pontes no Navegador Tor %s" #: lib/bridgedb/templates/options.html:38 #, python-format msgid "%sJ%sust give me bridges!" -msgstr "%sS%só me dê pontes!" +msgstr "%sS%só me dê conexões!" #: lib/bridgedb/templates/options.html:52 msgid "Advanced Options" @@ -386,4 +386,4 @@ msgstr "%sS%sim!" #: lib/bridgedb/templates/options.html:151 #, python-format msgid "%sG%set Bridges" -msgstr "%sO%sbtenha Pontes" +msgstr "%sO%sbtenha Conexões"

1 0