June 2016 - tor-commits - lists.torproject.org

[translation/mat-gui_completed] Update translations for mat-gui_completed
by translation＠torproject.org 24 Jun '16

24 Jun '16

commit 1ccfc497782129516977b520e55bee8b556d4dfa Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 24 14:46:03 2016 +0000 Update translations for mat-gui_completed --- ro.po | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ro.po b/ro.po index 75e3b10..53fad07 100644 --- a/ro.po +++ b/ro.po @@ -4,7 +4,7 @@ # # Translators: # Andrei Draga, 2013 -# Jobava <jobaval10n(a)gmail.com>, 2016 +# Baadur Jobava <jobaval10n(a)gmail.com>, 2016 # kyx <mihaidiaconu(a)gmail.com>, 2016 # clopotel <yo_sergiu05(a)yahoo.com>, 2014 msgid "" @@ -12,8 +12,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-02-10 23:06+0100\n" -"PO-Revision-Date: 2016-03-21 16:34+0000\n" -"Last-Translator: Jobava <jobaval10n(a)gmail.com>\n" +"PO-Revision-Date: 2016-06-24 14:42+0000\n" +"Last-Translator: Baadur Jobava <jobaval10n(a)gmail.com>\n" "Language-Team: Romanian (http://www.transifex.com/otf/torproject/language/ro/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/mat-gui] Update translations for mat-gui
by translation＠torproject.org 24 Jun '16

24 Jun '16

commit 6657b0453f171e6118073fcca65e9ca72aee742a Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 24 14:45:55 2016 +0000 Update translations for mat-gui --- ro.po | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ro.po b/ro.po index 75e3b10..53fad07 100644 --- a/ro.po +++ b/ro.po @@ -4,7 +4,7 @@ # # Translators: # Andrei Draga, 2013 -# Jobava <jobaval10n(a)gmail.com>, 2016 +# Baadur Jobava <jobaval10n(a)gmail.com>, 2016 # kyx <mihaidiaconu(a)gmail.com>, 2016 # clopotel <yo_sergiu05(a)yahoo.com>, 2014 msgid "" @@ -12,8 +12,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-02-10 23:06+0100\n" -"PO-Revision-Date: 2016-03-21 16:34+0000\n" -"Last-Translator: Jobava <jobaval10n(a)gmail.com>\n" +"PO-Revision-Date: 2016-06-24 14:42+0000\n" +"Last-Translator: Baadur Jobava <jobaval10n(a)gmail.com>\n" "Language-Team: Romanian (http://www.transifex.com/otf/torproject/language/ro/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[torspec/master] prop224: Remove redundant 'ed25519' header from 'auth-key'.
by asn＠torproject.org 24 Jun '16

24 Jun '16

commit 40ece65c499c116e4d332a99c91131693478653b Author: George Kadianakis <desnacked(a)riseup.net> Date: Fri Jun 24 15:21:23 2016 +0300 prop224: Remove redundant 'ed25519' header from 'auth-key'. The certificate already denotes the type of key. --- proposals/224-rend-spec-ng.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index f9e61e6..e14c2be 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -1004,7 +1004,7 @@ Table of contents: The link-specifiers is a base64 encoding of a link specifier block in the format described in BUILDING-BLOCKS. - "auth-key" SP "ed25519" NL certificate NL + "auth-key" NL certificate NL [Exactly once per introduction point]

1 0

[torspec/master] prop224: Specify overlap descriptor upload logic.
by asn＠torproject.org 24 Jun '16

24 Jun '16

commit ff797a6d623259e1d3cd066af45aaf3314b60d3d Author: George Kadianakis <desnacked(a)riseup.net> Date: Wed May 11 18:05:57 2016 -0400 prop224: Specify overlap descriptor upload logic. Conflicts: proposals/224-rend-spec-ng.txt --- proposals/224-rend-spec-ng.txt | 107 ++++++++++++++++++++--------------------- 1 file changed, 51 insertions(+), 56 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index 0a673a7..b0949c8 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -27,8 +27,8 @@ Table of contents: 2.1. Deriving blinded keys and subcredentials [SUBCRED] 2.2. Locating, uploading, and downloading hidden service descriptors 2.2.1. Dividing time into periods [TIME-PERIODS] - 2.2.2. Overlapping time periods to avoid thundering herds [TIME-OVERLAP] - 2.2.3. Where to publish a service descriptor + 2.2.2. When to publish a hidden service descriptor [WHEN-HSDESC] + 2.2.3. Where to publish a hidden service descriptor [WHERE-HSDESC] 2.2.4. Using time periods and SRVs to fetch/upload HS descriptors 2.2.5. URLs for anonymous uploading and downloading 2.3. Publishing shared random values [PUB-SHAREDRANDOM] @@ -688,44 +688,50 @@ Table of contents: after the epoch at 2016-04-12 12:00 UTC, and ended at (16904+1)*1500*60 + (12*60*60) seconds after the epoch at 2016-04-13 12:00 UTC. -2.2.2. Overlapping time periods to avoid thundering herds [TIME-OVERLAP] +2.2.2. When to publish a hidden service descriptor [WHEN-HSDESC] - If every hidden service host were to generate a new set of keys and - upload a new descriptor at exactly the start of each time period, the - directories would be overwhelmed by every host uploading at the same - time. Instead, each public key becomes valid at its new location at a - deterministic time somewhat _before_ the period begins, depending on - the public key and the period. + Hidden services periodically publish their descriptor to the responsible HSDirs. + The set of responsible HSDirs is determined as specified in [WHERE-HSDESC]. - 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 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. + Specifically, everytime a hidden service publishes its descriptor, it also + sets up a timer for a random time between 60 minutes and 120 minutes in the + future. When the timer triggers, the hidden service needs to publish its + descriptor again to the responsible HSDirs for that time period. + [TODO: Control republish period using a consensus parameter?] - The time at which a key from the next interval becomes valid is - determined by taking the first two bytes of +2.2.2.1. Overlapping descriptors - OFFSET = H("interval-offset" | KEY | INT_8(NEXT_PERIOD_NUM)) + Hidden services need to upload their descriptors to the HSDirs _before_ the + beginning of each time period, so that they are readily available for + clients to fetch them. However, if every hidden service were to upload a new + descriptor at exactly the start of each time period, directories would get + overwhelmed by every host uploading at the same time. - as a big-endian integer, dividing by 65536, and treating that as a - fraction of the overlap interval. + To avoid this thundering herd problem, hidden services upload descriptors + for the upcoming time period at a random time _before_ the time period starts. - 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. + For the above "descriptor overlap" system to work, fresh shared random + values must be available multiple hours *before* the time period changes, so + that hidden services have enough time to publish their overlap descriptors + to the future set of responsible HSDirs. In the current system, fresh shared + random values get published at 00:00UTC every day, whereas the time period + changes at 12:00UTC, giving 12 hours for hidden services to fetch new + consensuses and upload overlap descriptors. - 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. + Specifically, when a hidden service fetches a consensus with "valid-after" + between 00:00UTC and 12:00UTC, it goes into "descriptor overlap" + mode. During "descriptor overlap" mode, the hidden service uploads its + descriptor to the HSDirs of the current time period (using the previous SRV + from the consensus) _and_ it also uploads its descriptors for the upcoming + time period (using the current SRV from the consensus). -2.2.3. Where to publish a service descriptor + The above mechanism ensures that when the time period starts at 12:00UTC, + the hidden service will already have uploaded its descriptors to the + responsible HSDirs for that time period. + + [TODO: What to do when we run multiple hidden services in a single host?] + +2.2.3. Where to publish a hidden service descriptor [WHERE-HSDESC] The following consensus parameters control where a hidden service descriptor is stored; @@ -784,11 +790,6 @@ Table of contents: 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 @@ -816,35 +817,29 @@ Table of contents: | 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. + Legend: [TP#1 = Time Period #1] + [SRV#1 = Shared Random Value #1] + ["=" denotes descriptor overlap period] 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. + Hence, when clients and hidden services 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 until 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. + Hidden services in "descriptor overlap" mode _always_ use the current SRV + for publishing overlap descriptors. Clients on the other hand ignore the + overlap period and always fetch the descriptor of the current time period. - For more examples and discussion on this technique, please see [SRV-TP-REFS]. + For examples and discussion on this technique, please see [SRV-TP-REFS]. 2.2.5. URLs for anonymous uploading and downloading

1 0

[torspec/master] prop224: Specify lifetime of HS descriptors.
by asn＠torproject.org 24 Jun '16

24 Jun '16

commit dacf568f5e28c9c48a674a45b14af9db6b4e2bde Author: George Kadianakis <desnacked(a)riseup.net> Date: Wed May 11 19:07:51 2016 -0400 prop224: Specify lifetime of HS descriptors. Conflicts: proposals/224-rend-spec-ng.txt --- proposals/224-rend-spec-ng.txt | 34 +++++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index b0949c8..e8225e5 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -30,7 +30,8 @@ Table of contents: 2.2.2. When to publish a hidden service descriptor [WHEN-HSDESC] 2.2.3. Where to publish a hidden service descriptor [WHERE-HSDESC] 2.2.4. Using time periods and SRVs to fetch/upload HS descriptors - 2.2.5. URLs for anonymous uploading and downloading + 2.2.5. Expiring hidden service descriptors [EXPIRE-DESC] + 2.2.6. URLs for anonymous uploading and downloading 2.3. Publishing shared random values [PUB-SHAREDRANDOM] 2.3.1. Client behavior in the absense of shared random values 2.3.2. Hidden services and changing shared random values @@ -790,15 +791,6 @@ Table of contents: Again, nodes from lower-numbered replicas are disregarded when choosing the spread for a replica. - 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. - - 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. Using time periods and SRVs to fetch/upload HS descriptors Hidden services and clients need to make correct use of time periods and @@ -841,7 +833,18 @@ Table of contents: For examples and discussion on this technique, please see [SRV-TP-REFS]. -2.2.5. URLs for anonymous uploading and downloading +2.2.5. Expiring hidden service descriptors [EXPIRE-DESC] + + Hidden services set their descriptor's "descriptor-lifetime" field to 180 + minutes (3 hours). Hidden services ensure that their descriptor will remain + valid in the HSDir caches, by republishing their descriptors periodically as + specified in [WHEN-HSDESC]. + + Hidden services MUST also keep their introduction circuits alive for as long + as descriptors including those intro points are valid (even if that's after + the time period has changed). + +2.2.6. URLs for anonymous uploading and downloading Hidden service descriptors conforming to this specification are uploaded with an HTTP POST request to the URL @@ -904,6 +907,15 @@ Table of contents: The version-number contains a positive integer indicating the version of the descriptor. Current version is "3". + "descriptor-lifetime" SP LifetimeMinutes NL + + [Exactly once] + + The lifetime of a descriptor in minutes. An HSDir SHOULD expire the + hidden service descriptor at least LifetimeMinutes after it was uploaded. + + The LifetimeMinutes field can take values between 30 and 3000 (50 hours). + "descriptor-signing-key-cert" NL certificate NL [Exactly once.]

1 0

[torspec/master] prop224: Minor cleanup of [WHERE-HSDESC] section.
by asn＠torproject.org 24 Jun '16

24 Jun '16

commit c00e9370c3ceb09006da0bd05a7738e3f2c270df Author: George Kadianakis <desnacked(a)riseup.net> Date: Mon Jun 13 15:15:00 2016 +0300 prop224: Minor cleanup of [WHERE-HSDESC] section. --- proposals/224-rend-spec-ng.txt | 25 +++++++------------------ 1 file changed, 7 insertions(+), 18 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index e8225e5..f9e61e6 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -737,18 +737,13 @@ Table of contents: The following consensus parameters control where a hidden service descriptor is stored; - hsdir_n_replicas = an integer in range [1,16] - with default value 2. - - hsdir_spread_fetch = an integer in range [1,128] - with default value 3. - - hsdir_spread_store = an integer in range [1,128] - with default value 3. + hsdir_n_replicas = an integer in range [1,16] with default value 2. + hsdir_spread_fetch = an integer in range [1,128] with default value 3. + hsdir_spread_store = an integer in range [1,128] with default value 3. To determine where a given hidden service descriptor will be stored in a given period, after the blinded public key for that period is - derived, the uploading or downloading party calculate + derived, the uploading or downloading party calculates: for replicanum in 1...hsdir_n_replicas: hs_index(replicanum) = H("store-at-idx" | @@ -756,8 +751,9 @@ Table of contents: INT_8(replicanum) | INT_8(period_num) ) - where blinded_public_key is specified in section KEYBLIND, and period_num is - defined in section [TIME-PERIODS]. + where blinded_public_key is specified in section [KEYBLIND], and period_num + is calculated using the current consensus "valid-after" as specified in + section [TIME-PERIODS]. Then, for each node listed in the current consensus with the HSDirV3 flag, we compute a directory index for that node as: @@ -777,13 +773,6 @@ Table of contents: service, any nodes already chosen are disregarded (i.e. skipped over) when choosing a replica's hsdir_spread_store nodes. - [ XX/teor - because the positions don't match the key, this might leak - the fact that nodes from other replicas are nearby to a HSDir. - But this is preferable to having fewer HSDirs for a service. - I think the probability of a collision is approximately: - 1 / (n_hsdirs / (hsdir_n_replicas * hsdir_spread_store)) = 6 / n_hsdirs, - where n_hsdirs is the total number of HSDirs in the hash ring. ] - When choosing an HSDir to download from, clients choose randomly from among the first hsdir_spread_fetch nodes after the indices. (Note that, in order to make the system better tolerate disappearing

1 0

[translation/tails-iuk_completed] Update translations for tails-iuk_completed
by translation＠torproject.org 24 Jun '16

24 Jun '16

commit 6f1d3b5a4a2bd615f319f50c77297d6e268c5eac Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 24 04:46:50 2016 +0000 Update translations for tails-iuk_completed --- de.po | 100 +++++++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 56 insertions(+), 44 deletions(-) diff --git a/de.po b/de.po index ab2db3a..4df7193 100644 --- a/de.po +++ b/de.po @@ -3,6 +3,7 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# 2Pacalypse <kingmichele99(a)gmail.com>, 2016 # Andreas Demmelbauer, 2014 # max weber, 2015 # noble <noble(a)posteo.de>, 2013 @@ -17,9 +18,9 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" -"POT-Creation-Date: 2016-03-07 17:51+0100\n" -"PO-Revision-Date: 2016-03-21 16:27+0000\n" -"Last-Translator: max weber\n" +"POT-Creation-Date: 2016-05-25 16:55+0200\n" +"PO-Revision-Date: 2016-06-24 04:29+0000\n" +"Last-Translator: 2Pacalypse <kingmichele99(a)gmail.com>\n" "Language-Team: German (http://www.transifex.com/otf/torproject/language/de/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -27,18 +28,18 @@ msgstr "" "Language: de\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" -#: ../lib/Tails/IUK/Frontend.pm:146 ../lib/Tails/IUK/Frontend.pm:522 -#: ../lib/Tails/IUK/Frontend.pm:662 +#: ../lib/Tails/IUK/Frontend.pm:148 ../lib/Tails/IUK/Frontend.pm:524 +#: ../lib/Tails/IUK/Frontend.pm:697 msgid "" "For debugging information, execute the following command: sudo tails-" "debugging-info" msgstr "Führen Sie folgenden Befehl für Informationen zur Fehlerdiagnose aus: sudo tails-debugging-info" -#: ../lib/Tails/IUK/Frontend.pm:215 +#: ../lib/Tails/IUK/Frontend.pm:217 msgid "Error while checking for upgrades" msgstr "Fehler beim Suchen nach Aktualisierungen" -#: ../lib/Tails/IUK/Frontend.pm:218 +#: ../lib/Tails/IUK/Frontend.pm:220 msgid "" "Could not determine whether an upgrade is available from our website.\n" "\n" @@ -47,64 +48,64 @@ msgid "" "If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html" msgstr "Es konnte nicht festgestellt werden, ob auf unserer Website eine Aktualisierung verfügbar ist.\n\nBitte die Netzwerkverbindung überprüfen, und Tails für einen erneuten Versuch einer Aktualisierung neu starten.\\n\\nWenn das Problem weiterhin besteht, lesen Sie bitte 'file:///usr/share/doc/tails/website/doc/upgrade/error/check.de.html'." -#: ../lib/Tails/IUK/Frontend.pm:233 +#: ../lib/Tails/IUK/Frontend.pm:235 msgid "no automatic upgrade is available from our website for this version" msgstr "Für diese Version steht keine automatische Aktualisierung auf unserer Website zur Verfügung." -#: ../lib/Tails/IUK/Frontend.pm:239 +#: ../lib/Tails/IUK/Frontend.pm:241 msgid "your device was not created using Tails Installer" msgstr "Ihr Medium wurde nicht mit dem Tails-Installationsprogramm erstellt" -#: ../lib/Tails/IUK/Frontend.pm:244 +#: ../lib/Tails/IUK/Frontend.pm:246 msgid "Tails was started from a DVD or a read-only device" msgstr "Tails wurde von einer DVD oder einem anderen Medium gestartet, auf das nur lesend zugegriffen werden kann" -#: ../lib/Tails/IUK/Frontend.pm:249 +#: ../lib/Tails/IUK/Frontend.pm:251 msgid "there is not enough free space on the Tails system partition" msgstr "Die Partition, auf der Tails installiert ist, besitzt nicht genug freien Speicher" -#: ../lib/Tails/IUK/Frontend.pm:254 +#: ../lib/Tails/IUK/Frontend.pm:256 msgid "not enough memory is available on this system" msgstr "Auf diesem System steht nicht genug Speicher zur Verfügung" -#: ../lib/Tails/IUK/Frontend.pm:260 +#: ../lib/Tails/IUK/Frontend.pm:262 #, perl-brace-format msgid "No explanation available for reason '%{reason}s'." msgstr "Für Ursache »%{reason}s« ist keine Erklärung vorhanden." -#: ../lib/Tails/IUK/Frontend.pm:280 +#: ../lib/Tails/IUK/Frontend.pm:282 msgid "The system is up-to-date" msgstr "Das System ist auf dem neuesten Stand" -#: ../lib/Tails/IUK/Frontend.pm:285 +#: ../lib/Tails/IUK/Frontend.pm:287 msgid "This version of Tails is outdated, and may have security issues." msgstr "Diese Version von Tails ist veraltet und könnte Sicherheitslücken haben." -#: ../lib/Tails/IUK/Frontend.pm:317 +#: ../lib/Tails/IUK/Frontend.pm:319 #, perl-brace-format msgid "" "The available incremental upgrade requires %{space_needed}s of free space on" " Tails system partition, but only %{free_space}s is available." msgstr "Die inkrementelle Aktualisierung benötigt %{space_needed}s freien Speicherplatz auf der Tails-Systempartition, aber es sind nur %{free_space}s verfügbar." -#: ../lib/Tails/IUK/Frontend.pm:333 +#: ../lib/Tails/IUK/Frontend.pm:335 #, perl-brace-format msgid "" "The available incremental upgrade requires %{memory_needed}s of free memory," " but only %{free_memory}s is available." msgstr "\"Die inkrementelle Aktualisierung benötigt %{memory_needed}s freien Arbeitsspeicher, aber es sind nur %{free_memory}s verfügbar." -#: ../lib/Tails/IUK/Frontend.pm:355 +#: ../lib/Tails/IUK/Frontend.pm:357 msgid "" "An incremental upgrade is available, but no full upgrade is.\n" "This should not happen. Please report a bug." msgstr "Eine inkrementelle Aktualisierung ist verfügbar, jedoch keine vollständige Aktualisierung.\\nDas sollte nicht passieren. Bitte melden Sie diesen Fehler." -#: ../lib/Tails/IUK/Frontend.pm:359 +#: ../lib/Tails/IUK/Frontend.pm:361 msgid "Error while detecting available upgrades" msgstr "Fehler beim Suchen nach Aktualisierungen" -#: ../lib/Tails/IUK/Frontend.pm:369 +#: ../lib/Tails/IUK/Frontend.pm:371 #, perl-brace-format msgid "" "You should upgrade to %{name}s %{version}s.\n" @@ -120,19 +121,19 @@ msgid "" "Do you want to upgrade now?" msgstr "Sie sollten auf %{name}s %{version}s aktualisieren.\n\nFür weitere Informationen über diese neue Version siehe %{details_url}s\n\nEs wird empfohlen, alle offenen Anwendungen während der Aktualisierung zu schließen.\nDas Herunterladen der Aktualisierung kann möglicherweise sehr lange dauern, von einigen Minuten bis zu einigen Stunden\nNach dem Herunterladen und Aktualisieren wird das Netzwerk deaktiviert.\n\nGröße zum Herunterladen: %{size}s\\n\\nWollen Sie jetzt aktualisieren?" -#: ../lib/Tails/IUK/Frontend.pm:384 +#: ../lib/Tails/IUK/Frontend.pm:386 msgid "Upgrade available" msgstr "Aktualisierung verfügbar" -#: ../lib/Tails/IUK/Frontend.pm:385 +#: ../lib/Tails/IUK/Frontend.pm:387 msgid "Upgrade now" msgstr "Jetzt aktualisieren" -#: ../lib/Tails/IUK/Frontend.pm:386 +#: ../lib/Tails/IUK/Frontend.pm:388 msgid "Upgrade later" msgstr "Später aktualisieren" -#: ../lib/Tails/IUK/Frontend.pm:394 +#: ../lib/Tails/IUK/Frontend.pm:396 #, perl-brace-format msgid "" "You should do a manual upgrade to %{name}s %{version}s.\n" @@ -144,20 +145,20 @@ msgid "" "To learn how to do a manual upgrade, go to https://tails.boum.org/doc/first_steps/upgrade/#manual" msgstr "Sie sollten eine manuelle Aktualisierung auf %{name}s %{version}s vornehmen.\n\nFür weitere Informationen zur neuen Version besuchen Sie bitte %{details_url}s.\n\nEs ist nicht möglich, automatisch auf diese neue Version zu aktualisieren: %{explanation}s.\n\nUm zu lernen, wie man eine manuelle Aktualisierung vornimmt, besuchen Sie bitte https://tails.boum.org/doc/first_steps/upgrade/index.de.html#manual" -#: ../lib/Tails/IUK/Frontend.pm:410 +#: ../lib/Tails/IUK/Frontend.pm:412 msgid "New version available" msgstr "Eine neue Version ist verfügbar" -#: ../lib/Tails/IUK/Frontend.pm:467 +#: ../lib/Tails/IUK/Frontend.pm:469 msgid "Downloading upgrade" msgstr "Aktualisierung wird heruntergeladen" -#: ../lib/Tails/IUK/Frontend.pm:470 +#: ../lib/Tails/IUK/Frontend.pm:472 #, perl-brace-format msgid "Downloading the upgrade to %{name}s %{version}s..." msgstr "Aktualisierung auf %{name}s %{version}s wird heruntergeladen …" -#: ../lib/Tails/IUK/Frontend.pm:511 +#: ../lib/Tails/IUK/Frontend.pm:513 msgid "" "The upgrade could not be downloaded.\\n\\nCheck your network " "connection, and restart Tails to try upgrading again.\\n\\nIf the problem " @@ -165,26 +166,37 @@ msgid "" "file:///usr/share/doc/tails/website/doc/upgrade/error/download.en.html" msgstr "Die Aktualisierung konnte nicht heruntergeladen werden.\\n\\nBitte überprüfen Sie Ihre Netzwerkverbindung, und starten Sie Tails für einen erneuten Versuch einer Aktualisierung neu.\\n\\nWenn das Problem weiterhin besteht, lesen Sie bitte file:///usr/share/doc/tails/website/doc/upgrade/error/download.de.html" -#: ../lib/Tails/IUK/Frontend.pm:527 ../lib/Tails/IUK/Frontend.pm:546 +#: ../lib/Tails/IUK/Frontend.pm:529 ../lib/Tails/IUK/Frontend.pm:548 msgid "Error while downloading the upgrade" msgstr "Fehler beim Herunterladen der Aktualisierung" -#: ../lib/Tails/IUK/Frontend.pm:539 +#: ../lib/Tails/IUK/Frontend.pm:541 #, perl-brace-format msgid "" "Output file '%{output_file}s' does not exist, but tails-iuk-get-target-file " "did not complain. Please report a bug." msgstr "Die Ausgabedatei »%{output_file}s« existiert nicht, aber tails-iuk-get-target-file hat nichts beanstandet. Bitte melden Sie diesen Fehler." -#: ../lib/Tails/IUK/Frontend.pm:558 +#: ../lib/Tails/IUK/Frontend.pm:560 msgid "Error while creating temporary downloading directory" msgstr "Fehler beim Erstellen eines temporären Verzeichnisses zum Herunterladen" -#: ../lib/Tails/IUK/Frontend.pm:561 +#: ../lib/Tails/IUK/Frontend.pm:563 msgid "Failed to create temporary download directory" msgstr "Es konnte kein temporäres Verzeichnis zum Herunterladen erstellt werden" -#: ../lib/Tails/IUK/Frontend.pm:573 +#: ../lib/Tails/IUK/Frontend.pm:587 +msgid "" +"Could not choose a download server.\n" +"\n" +"This should not happen. Please report a bug." +msgstr "Wir konnten leider keinen geeigneten Download Server finden/b>\n\nDas sollte eigentlich nicht passieren. Senden sie uns bitte diesen Fehler." + +#: ../lib/Tails/IUK/Frontend.pm:591 +msgid "Error while choosing a download server" +msgstr "Fehler beim auswählen eines Download Servers" + +#: ../lib/Tails/IUK/Frontend.pm:608 msgid "" "Your Tails device was successfully upgraded.\n" "\n" @@ -194,46 +206,46 @@ msgid "" "Do you want to restart now?" msgstr "Ihr Tails-Medium wurde erfolgreich aktualisiert.\n\nEinige Sicherheitsfunktionen wurden vorübergehend abgeschaltet.\nSie sollten Tails mit der neuen Version so bald wie möglich neu starten.\n\nWollen Sie jetzt neu starten?" -#: ../lib/Tails/IUK/Frontend.pm:578 +#: ../lib/Tails/IUK/Frontend.pm:613 msgid "Restart Tails" msgstr "Tails neu starten" -#: ../lib/Tails/IUK/Frontend.pm:579 +#: ../lib/Tails/IUK/Frontend.pm:614 msgid "Restart now" msgstr "Jetzt neu starten" -#: ../lib/Tails/IUK/Frontend.pm:580 +#: ../lib/Tails/IUK/Frontend.pm:615 msgid "Restart later" msgstr "Später neu starten" -#: ../lib/Tails/IUK/Frontend.pm:591 +#: ../lib/Tails/IUK/Frontend.pm:626 msgid "Error while restarting the system" msgstr "Beim Neustart des Systems ist ein Fehler aufgetreten" -#: ../lib/Tails/IUK/Frontend.pm:594 +#: ../lib/Tails/IUK/Frontend.pm:629 msgid "Failed to restart the system" msgstr "Das System konnte nicht neu gestartet werden" -#: ../lib/Tails/IUK/Frontend.pm:609 +#: ../lib/Tails/IUK/Frontend.pm:644 msgid "Error while shutting down the network" msgstr "Fehler beim Herunterfahren des Netzwerks" -#: ../lib/Tails/IUK/Frontend.pm:612 +#: ../lib/Tails/IUK/Frontend.pm:647 msgid "Failed to shutdown network" msgstr "Herunterfahren des Netzwerks ist fehlgeschlagen" -#: ../lib/Tails/IUK/Frontend.pm:622 +#: ../lib/Tails/IUK/Frontend.pm:657 msgid "Upgrading the system" msgstr "System wird aktualisiert" -#: ../lib/Tails/IUK/Frontend.pm:624 +#: ../lib/Tails/IUK/Frontend.pm:659 msgid "" "Your Tails device is being upgraded...\n" "\n" "For security reasons, the networking is now disabled." msgstr "Ihr Tails-Medium wird aktualisiert …\n\nAus Sicherheitsgründen wird das Netzwerk jetzt abgeschaltet." -#: ../lib/Tails/IUK/Frontend.pm:657 +#: ../lib/Tails/IUK/Frontend.pm:692 msgid "" "An error occured while installing the upgrade.\\n\\nYour Tails device" " needs to be repaired and might be unable to restart.\\n\\nPlease follow the" @@ -241,6 +253,6 @@ msgid "" "file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html" msgstr "Ein Fehler ist während der Aktualisierung aufgetreten.\\\\n\\\\nIhr Tails-Medium muss repariert werden und kann eventuell nicht neu gestartet werden.\\\\n\\\\nBitte folgen Sie den Anweisungen in der Datei file:///usr/share/doc/tails/website/doc/upgrade/error/install.de.html" -#: ../lib/Tails/IUK/Frontend.pm:667 +#: ../lib/Tails/IUK/Frontend.pm:702 msgid "Error while installing the upgrade" msgstr "Fehler beim Installieren der Aktualisierungen"

1 0

[translation/tails-iuk] Update translations for tails-iuk
by translation＠torproject.org 24 Jun '16

24 Jun '16

commit 259f19826b92b557003dc89c7720f6fd84f0b8e5 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 24 04:46:44 2016 +0000 Update translations for tails-iuk --- de.po | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/de.po b/de.po index dc52dc9..4df7193 100644 --- a/de.po +++ b/de.po @@ -3,6 +3,7 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# 2Pacalypse <kingmichele99(a)gmail.com>, 2016 # Andreas Demmelbauer, 2014 # max weber, 2015 # noble <noble(a)posteo.de>, 2013 @@ -18,8 +19,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" "POT-Creation-Date: 2016-05-25 16:55+0200\n" -"PO-Revision-Date: 2016-05-26 08:49+0000\n" -"Last-Translator: carolyn <carolyn(a)anhalt.org>\n" +"PO-Revision-Date: 2016-06-24 04:29+0000\n" +"Last-Translator: 2Pacalypse <kingmichele99(a)gmail.com>\n" "Language-Team: German (http://www.transifex.com/otf/torproject/language/de/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -189,11 +190,11 @@ msgid "" "Could not choose a download server.\n" "\n" "This should not happen. Please report a bug." -msgstr "" +msgstr "Wir konnten leider keinen geeigneten Download Server finden/b>\n\nDas sollte eigentlich nicht passieren. Senden sie uns bitte diesen Fehler." #: ../lib/Tails/IUK/Frontend.pm:591 msgid "Error while choosing a download server" -msgstr "" +msgstr "Fehler beim auswählen eines Download Servers" #: ../lib/Tails/IUK/Frontend.pm:608 msgid ""

1 0

[webwml/master] Update Erin's blurb. Cookies much important
by sebastian＠torproject.org 23 Jun '16

23 Jun '16

commit e9f62b1569ab3888c9845cca1a1cc0a2235e0438 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Fri Jun 24 01:29:19 2016 +0200 Update Erin's blurb. Cookies much important --- about/en/corepeople.wml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/about/en/corepeople.wml b/about/en/corepeople.wml index 14a2f8f..e7d2c0b 100644 --- a/about/en/corepeople.wml +++ b/about/en/corepeople.wml @@ -363,7 +363,7 @@ Princeton.</dd> <dt>Erin Wyatt, HR Manager</dt> - <dd>Based in the Seattle office.</dd> + <dd>Employee benefits, policy questions, and baked goods.</dd> <dt>Yawning, Developer</dt> <dd>Lead developer on obfs4proxy and other pluggable transports.

1 0

[webwml/master] Add ewyatt to core people
by sebastian＠torproject.org 23 Jun '16

23 Jun '16

commit 28d5d360b651288c53e7670d20d1a84f4c5ccdae Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Fri Jun 24 01:13:43 2016 +0200 Add ewyatt to core people --- about/en/corepeople.wml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/about/en/corepeople.wml b/about/en/corepeople.wml index 2e13483..14a2f8f 100644 --- a/about/en/corepeople.wml +++ b/about/en/corepeople.wml @@ -362,6 +362,9 @@ and part of the pluggable transports team. Post-doc at Princeton.</dd> + <dt>Erin Wyatt, HR Manager</dt> + <dd>Based in the Seattle office.</dd> + <dt>Yawning, Developer</dt> <dd>Lead developer on obfs4proxy and other pluggable transports. Part of the pluggable transports team.</dd>

1 0