Commit 315dc374 authored by amnesia's avatar amnesia

updated PO files

parent 4d97e630
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-23 00:01+0300\n"
"POT-Creation-Date: 2014-07-23 00:06+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -37,8 +37,7 @@ msgstr ""
#, no-wrap
msgid ""
"> \"We're happy to see that TAILS 1.1 is being released tomorrow.\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails "
"#tor\"\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails #tor\"\n"
msgstr ""
#. type: Plain text
......@@ -54,8 +53,8 @@ msgid ""
"people report such vulnerabilities, and then they get fixed: This is the "
"power of free and open source software. Others don't disclose them, but run "
"lucrative businesses by weaponizing and selling them instead. This is not "
"new and [comes as no "
"surprise](https://www.eff.org/deeplinks/2012/03/zero-day-exploit-sales-should-be-key-point-cybersecurity-debate)."
"new and [comes as no surprise](https://www.eff.org/deeplinks/2012/03/zero-"
"day-exploit-sales-should-be-key-point-cybersecurity-debate)."
msgstr ""
#. type: Plain text
......@@ -65,7 +64,7 @@ msgid ""
"from them. They informed us that they would provide us with a report within "
"a week. We're told they won't disclose these vulnerabilities publicly before "
"we have corrected it, and Tails users have had a chance to upgrade. We think "
"that this is the right process to responsively disclose vulnerabilities, and "
"that this is the right process to responsibly disclose vulnerabilities, and "
"we're really looking forward to read this report."
msgstr ""
......@@ -73,11 +72,10 @@ msgstr ""
msgid ""
"Being fully aware of this kind of threat, we're continously working on "
"improving Tails' security in depth. Among other tasks, we're working on a "
"[tight "
"integration](https://labs.riseup.net/code/projects/tails/search?q=apparmor) "
"of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] and "
"[[!tails_ticket desc=\"web browser hardening\" 5802]] as well as "
"[[!tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
"[tight integration](https://labs.riseup.net/code/projects/tails/search?"
"q=apparmor) of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] "
"and [[!tails_ticket desc=\"web browser hardening\" 5802]] as well as [[!"
"tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
msgstr ""
#. type: Plain text
......
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-23 00:01+0300\n"
"POT-Creation-Date: 2014-07-23 00:06+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -37,8 +37,7 @@ msgstr ""
#, no-wrap
msgid ""
"> \"We're happy to see that TAILS 1.1 is being released tomorrow.\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails "
"#tor\"\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails #tor\"\n"
msgstr ""
#. type: Plain text
......@@ -54,8 +53,8 @@ msgid ""
"people report such vulnerabilities, and then they get fixed: This is the "
"power of free and open source software. Others don't disclose them, but run "
"lucrative businesses by weaponizing and selling them instead. This is not "
"new and [comes as no "
"surprise](https://www.eff.org/deeplinks/2012/03/zero-day-exploit-sales-should-be-key-point-cybersecurity-debate)."
"new and [comes as no surprise](https://www.eff.org/deeplinks/2012/03/zero-"
"day-exploit-sales-should-be-key-point-cybersecurity-debate)."
msgstr ""
#. type: Plain text
......@@ -65,7 +64,7 @@ msgid ""
"from them. They informed us that they would provide us with a report within "
"a week. We're told they won't disclose these vulnerabilities publicly before "
"we have corrected it, and Tails users have had a chance to upgrade. We think "
"that this is the right process to responsively disclose vulnerabilities, and "
"that this is the right process to responsibly disclose vulnerabilities, and "
"we're really looking forward to read this report."
msgstr ""
......@@ -73,11 +72,10 @@ msgstr ""
msgid ""
"Being fully aware of this kind of threat, we're continously working on "
"improving Tails' security in depth. Among other tasks, we're working on a "
"[tight "
"integration](https://labs.riseup.net/code/projects/tails/search?q=apparmor) "
"of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] and "
"[[!tails_ticket desc=\"web browser hardening\" 5802]] as well as "
"[[!tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
"[tight integration](https://labs.riseup.net/code/projects/tails/search?"
"q=apparmor) of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] "
"and [[!tails_ticket desc=\"web browser hardening\" 5802]] as well as [[!"
"tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
msgstr ""
#. type: Plain text
......
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-23 00:01+0300\n"
"POT-Creation-Date: 2014-07-23 00:06+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -37,8 +37,7 @@ msgstr ""
#, no-wrap
msgid ""
"> \"We're happy to see that TAILS 1.1 is being released tomorrow.\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails "
"#tor\"\n"
"> Our multiple RCE/de-anonymization zero-days are still effective. #tails #tor\"\n"
msgstr ""
#. type: Plain text
......@@ -54,8 +53,8 @@ msgid ""
"people report such vulnerabilities, and then they get fixed: This is the "
"power of free and open source software. Others don't disclose them, but run "
"lucrative businesses by weaponizing and selling them instead. This is not "
"new and [comes as no "
"surprise](https://www.eff.org/deeplinks/2012/03/zero-day-exploit-sales-should-be-key-point-cybersecurity-debate)."
"new and [comes as no surprise](https://www.eff.org/deeplinks/2012/03/zero-"
"day-exploit-sales-should-be-key-point-cybersecurity-debate)."
msgstr ""
#. type: Plain text
......@@ -65,7 +64,7 @@ msgid ""
"from them. They informed us that they would provide us with a report within "
"a week. We're told they won't disclose these vulnerabilities publicly before "
"we have corrected it, and Tails users have had a chance to upgrade. We think "
"that this is the right process to responsively disclose vulnerabilities, and "
"that this is the right process to responsibly disclose vulnerabilities, and "
"we're really looking forward to read this report."
msgstr ""
......@@ -73,11 +72,10 @@ msgstr ""
msgid ""
"Being fully aware of this kind of threat, we're continously working on "
"improving Tails' security in depth. Among other tasks, we're working on a "
"[tight "
"integration](https://labs.riseup.net/code/projects/tails/search?q=apparmor) "
"of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] and "
"[[!tails_ticket desc=\"web browser hardening\" 5802]] as well as "
"[[!tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
"[tight integration](https://labs.riseup.net/code/projects/tails/search?"
"q=apparmor) of AppArmor in Tails, [[!tails_ticket desc=\"kernel\" 7639]] "
"and [[!tails_ticket desc=\"web browser hardening\" 5802]] as well as [[!"
"tails_ticket desc=\"sandboxing\" 6081]], just to name a few examples."
msgstr ""
#. type: Plain text
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment