Commit 7e026323 authored by intrigeri's avatar intrigeri
Browse files

Merge remote-tracking branch 'origin/master' into testing

parents efa6c024 55b750b6
......@@ -311,7 +311,11 @@ The IUK size is involved in at least four concerns:
`config/chroot_local-includes/usr/local/bin/tails-upgrade-frontend-wrapper`)
so the upgrade would fail. This is a regression for users with 2 GB
memory: for all of 2.x and 3.x, all IUKs have been under 400 MB,
which would work fine with 2 GB of memory.
which would work fine with 2 GB of memory. If that's a blocker, then
we have to solve it by changing the format of the IUKs
([[!tails_ticket 6876]]); we should coordinate this with other changes
that will break automated upgrades from Tails N to N+1, such as
Tails 4.0 and the migration to overlayfs ([[!tails_ticket 9373]]) .
* Bandwidth needs of the RM. Uploading 10 GB of IUKs can be a pain for
some of us, but that can easily be solved by making it possible to
generate IUKs on lizard (and then compare them with the ones you
......
......@@ -138,3 +138,4 @@ Other resources
* [Linux Container Security](http://mjg59.dreamwidth.org/33170.html),
by Matthew Garrett
* Whitepaper by NCC Group on [Linux containers](https://www.nccgroup.trust/globalassets/our-research/us/whitepapers/2016/june/container_whitepaperpdf/) and their weaknesses/strengths
* Google's design for [Linux containers](https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md) within ChromeOS
......@@ -22,22 +22,16 @@ If you have an idea yourself and would like to propose it, please write to us th
## User interface
If you're an user interface designer you might be delighted to hear that we have a [mailing list](https://tails.boum.org/contribute/how/user_experience/) targeted at you!
If you're an user interface designer you might be delighted to hear that we have a full [mailing list](https://mailman.boum.org/listinfo/tails-ux) about UX!
Our page on [improving](https://tails.boum.org/contribute/how/user_experience/) the Tails user interface might also interest you.
Our page on [improving](https://tails.boum.org/contribute/how/user_experience/) the Tails user interface might also be of interest to you.
## User experience
In the context of Tails, there are some interesting problems that touch upon user experience and usable security. The following points might be an interesting point to start from.
- [Tails Installer](https://tails.boum.org/install/)
- XXX find more projects
We have a mailing list dedicated to UX/UI that's called the [Tails-UX](https://mailman.boum.org/listinfo/tails-ux) mailing list.
This is the place where you would want to subscribe, if you're interested in the process of reviewing and/or proposing changes in this area.
- XXX anything else we'd like to list or swap?
## How to get involved
......@@ -58,13 +52,11 @@ The Tor Project has a page dedicated to open open research questions that they f
[Tor project Research](https://research.torproject.org/)
## Academic communities
The questions posed by Tails might me of interest for researchers from various fields. A list of potentially interested communities that we are aware of can be seen below.
The questions posed by Tails might me of interest for researchers from various fields. A list of potentially interested communities that we are aware of.
* Anonymity researchers - [PETS](http://petsymposium.org/)
* Usable Privacy and Security - [SOUPS](https://cups.cs.cmu.edu/soups/index.html)
* Computer science in various fields - [USENIX](https://www.usenix.org/conferences)
## Other reasonably secure operating systems
Often, the reasonably secure operating systems faces similar challenges. Maybe solutions that we can come up with and implement, are interesting for these other projects. We could share time and resources if they're willing.
An interesting platform to discuss this would be the [Secure OS](https://secure-os.org/) desktops mailing list.
There are certain common shared problems in the reasonably secure operating systems space. Maybe solutions that we can come up with and implement, are interesting for these other projects. We could share time and resources if they're willing.
......@@ -82,6 +82,14 @@ interface.
first-time users?
- How should it sound?
### References
- <https://styleguide.mailchimp.com/>
- <http://voiceandtone.com/>
- <https://uxdesign.cc/ux-writing-content-strategy-lessons-from-facebook-286e8ac76307>
- <https://medium.com/level-up-web/technical-writing-as-a-part-of-user-experience-2cfd97554d09>
- <http://uxpajournal.org/overlap-influence-intertwining-the-interplay-of-ux-and-technical-communication/>
### Deliverable
- Suggestions in copy and documentation for clarity and tone.
......
......@@ -3,7 +3,9 @@ Also tracked by ticket: [[!tails_ticket 10181]]
What's the problem
------------------
some ideas/suggestions:
We want the Tails community to be diverse. In order to achieve this, our documentation should be the most welcoming possible, to all spectra of gender and provide the same openness in all translations. Also see [Debian's diversity statement](https://www.debian.org/intro/diversity).
Some ideas/suggestions:
* Can we measure how severe the problem is?
......
......@@ -491,6 +491,14 @@ developed by SecondMuse:
### References
- [The Citizen Lab: Reckless Exploit Mexican Journalists, Lawyers, and a Child Targeted with NSO Spyware](https://citizenlab.ca/2017/06/reckless-exploit-mexico-nso/)
- [Wikipedia: List of journalists and media workers killed in Mexico](https://en.wikipedia.org/wiki/List_of_journalists_and_media_workers_killed_in_Mexico)
- Interviews
- [[Claudia & Felix|interviews#Claudia]]
- [[Joana & Orlando|interviews#Joana]]
- [Digital Rights Foundation: Digital (In)security of Journalists in Pakistan](https://digitalrightsfoundation.pk/wp-content/uploads/2018/01/Report-Digi-Insecurity-of-Journos.pdf)
- [Javier Garza Ramos, Journalist Security in the Digital World](http://www.cima.ned.org/wp-content/uploads/2016/03/CIMA-Journalist-Digital-Tools-03-01-15.pdf)
......
# /dev/random and /dev/urandom radomness seeding in Tails
# /dev/random and /dev/urandom randomness seeding in Tails
/dev/random and /dev/urandom are special Linux devices that provide
access from user land to the Linux kernel Cryptographically Secure
Pseudo Random Number Generator (CSPRNG). This generator is used for
almost every security protocol, like TLS/SSL key generation, choosing
TCP sequences, ASLR offsets, and GPG key generation
[https://eprint.iacr.org/2006/086.pdf]. In order for this CSPRNG to
indeed be cryptographically secure, it's recommended to seed it with a
'good' entropy source, even though The Linux kernel collects entropy
from several sources, for example keyboard typing, mouse movement, among
others.
TCP sequences, ASLR offsets, and
[https://eprint.iacr.org/2006/086.pdf](GPG key generation) . In order
for this CSPRNG to indeed be cryptographically secure, it's recommended
to seed it with a 'good' entropy source, even though The Linux kernel
collects entropy from several sources, for example keyboard typing,
mouse movement, among others.
Because of Tails' feature of being amnesic, and run from different types
of live devices (from DVDs to USB sticks), special care must be taken to
......@@ -25,10 +25,10 @@ done to tackle the problem. We looked at notes and research from LiveCD
OS's and supply them here for completeness' sake. Whonix has a [wiki
page](https://www.whonix.org/wiki/Dev/Entropy) with some notes, and
Qubes has tickets about this
([http://wiki.qubes-os.org/trac/ticket/673],
[https://github.com/QubesOS/qubes-issues/issues/1311],
[https://groups.google.com/forum/#!msg/qubes-devel/Q65boPAbqbE/9ZOZUInQCgAJ],
[https://groups.google.com/forum/#!topic/qubes-devel/5wI8ygbaohk]).
[http://wiki.qubes-os.org/trac/ticket/673](Qubes 673),
[https://github.com/QubesOS/qubes-issues/issues/1311](Qubes 1311),
[https://groups.google.com/forum/#!msg/qubes-devel/Q65boPAbqbE/9ZOZUInQCgAJ](Qubes devel),
[https://groups.google.com/forum/#!topic/qubes-devel/5wI8ygbaohk](Qubes devel).
## Current situation
......@@ -36,7 +36,7 @@ See the related [[design document|contribute/design/random]]
Tails does not ship /var/lib/urandom/random-seed in the ISO, since it
means shipping a fixed known value for every Tails installation, which
in turn means that entropy contribution would zero. Furthermore, this
in turn means that entropy contribution would be zero. Furthermore, this
breaks reproducibility of the ISO image.
Without this random seed, systemd-random-seed won't write anything to
......@@ -198,7 +198,7 @@ very well be that this case does not happen anymore. And if it does, we need to
on average how much time that blocking would last. [[!tails_ticket
11758]]
### Regulary check available entropy and notify if low
### Regularly check available entropy and notify if low
An idea that has been mentioned several times is to have a service that
checks if the available entropy is high enough, and notifies the user if
......@@ -206,6 +206,13 @@ it's not the case. One downside is, that observing the entropy pool costs
randomness, so this may have to be implemented with care or is worth
discussing/researching the costs/benefits.
## Also see
* [Schleuder thread about haveged](https://0xacab.org/schleuder/schleuder/issues/194)
* The
[federal office for IT security in Germany analysed the rng in linux kernel 4.9 and all changes made up to 4.17](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/LinuxRNG/LinuxRNG_EN.pdf?__blob=publicationFile&v=10).
* [checking for available entropy](https://salsa.debian.org/tookmund-guest/pgpcr/issues/16)
## Related tickets
This is about [[!tails_ticket 7642]], [[!tails_ticket 7675]],
......
......@@ -4,12 +4,13 @@ It would be nice to replace Pidgin with another secure IM client. Unfortunately
The document can also list candidate clients together with some indication where they are lacking (and where they shine).
TODO: Would a pair of two separate client (XMPP and IRC) also be okay, or are we only looking for a single client that can do both? In fact, it is not even clear if Tails needs to contain an IRC client at all, after #tails and #tails-dev have been moved to XMPP.
[[!toc levels=3]]
# Requirements
**Note**: this is a work in progress. See [[!tails_ticket 11686]]
and its blockers for the next steps.
**Note**: the key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
......@@ -44,8 +45,6 @@ The client must have a easy to use GUI that makes it hard for users to use the c
The client must support connections using TLS.
TODO: Is STARTTLS needed?
### Support for Tor
The client must support Tor and must not leak any private data (hostname, username, local IP, ...) at the application level.
......@@ -62,6 +61,15 @@ TODO: Pidgin already has an apparmor profile; should we require that a replaceme
The client MUST NOT save logs of conversations.
### Candidates
Suggested by sajolida on <https://mailman.boum.org/pipermail/tails-dev/2016-January/010123.html>:
* private group chat
* search and archive past public communications
* offline-friendliness
* <https://dymaxion.org/essays/pleasestop.html>
## XMPP (Jabber)
*( Here is a [list](https://developer.pidgin.im/wiki/SupportedXEPs) of XMPP extensions supported by Pidgin )*
......@@ -75,16 +83,22 @@ The client must support SASL authentication.
# Candidate alternatives
## CoyIM (based on xmpp-client) ([[!tails_ticket 8574]])
## CoyIM
* [Homepage](https://coy.im/)
* [Github](https://github.com/twstrike/coyim/)
* [Github](https://github.com/coyim/coyim/)
* CoyIM only supports XMPP.
* CoyIM [is in Debian](https://tracker.debian.org/pkg/coyim)
* Support for multi-user chatrooms (MUC) is [in
progress](https://github.com/coyim/coyim/projects/2) and lacks some
important features such as having a persistent list of rooms
persistently saved in the configuration
* Supports Tor, TLS, OTR
* Supports creation of random accounts.
* Supports importing accounts from Pidgin.
* No logging, no clickable links.
* Not audited.
* Test results in Tails: [[!tails_ticket 8574]]
## dino
......@@ -92,7 +106,7 @@ The client must support SASL authentication.
* implemented in GTK+/Vala
* supports XMPP and OMEMO; OTR support is
[not high on the todo list](https://github.com/dino/dino/issues/97)
* is be [[!debpts dino-im desc="in Debian"]] experimental
* is [[!debpts dino-im desc="in Debian"]] Buster
* the Debian maintainer wants to add an AppArmor profile and got in
touch with intrigeri about it
......
......@@ -76,7 +76,7 @@ released:
--force-bad-version \
--distribution "${DISTRIBUTION:?}" \
--force-distribution \
"Rebuild Thunderbird with Tails' secure autoconfiguration patches." && \
"Rebuild with Tails' secure autoconfiguration patches." && \
git commit debian/changelog \
-m "document changes and release ${TAILS_VERSION:?}"
......@@ -91,7 +91,10 @@ released:
gbp buildpackage --git-debian-branch=tails/stretch \
--git-sign-tags --git-tag-only
1. Include all sources in the `.changes` file:
1. If you've built a package based on an _upstream_ release (as in:
what's before the first `-` in the package version number)
whose `.orig.tar.xz` tarball was never uploaded to our custom
APT repository, include all sources in the `.changes` file:
cd path/to/build/artifacts/directory && \
cp path/to/build-area/*${UPSTREAM_VERSION:?}*.orig*.tar.xz . && \
......@@ -103,18 +106,17 @@ released:
named tag:
GBP_TAG="debian/$(echo ${TAILS_VERSION:?} | tr '~:' '_%')"
GBP_TAG_COMMIT="$(git rev-list -n 1 "${GBP_TAG}")"
NEW_GBP_TAG="$(echo ${GBP_TAG:?} | sed 's@/1%@/@')" && \
git tag -s "${NEW_GBP_TAG:?}" \
-m "thunderbird Debian release 1:${TAILS_VERSION:?}" \
"${GBP_TAG_COMMIT:?}"
"${GBP_TAG:?}"
1. Git push and upload packages:
git push --follow-tags origin \
${NEW_GBP_TAG:?} \
tails/stretch \
upstream-52.x \
upstream-60.x \
pristine-tar && \
(cd /path/to/build/artifacts && \
debsign "${CHANGES_FILE:?}" && \
......
......@@ -40,7 +40,7 @@ Priorities for the next years
- **Create outreach material** ([[!tails_ticket 14523]])
- **Outreach to under-represented communities** ([[!tails_ticket 14560]])
- **Recruit new core workers**: sysadmin, technical writer, and accountant
- **Recruit new core workers**: <strike>sysadmin</strike>, <strike>technical writer</strike>, and accountant
- **Lower technical requirements** for new contributors ([[!tails_ticket 14516]])
### Applications and features
......
......@@ -12,11 +12,8 @@ as a fallback if no other contributor volunteers to do it.
- Redacting release notes based on the
Changelog excerpts provided by RM.
- Redacting exceptional publications on our
blog (security advisory, call for donations, etc.) or reviewing
blog (security advisory, etc.) or reviewing
them against GDSG and the rest of our documentation.
- Reviewing contributions of paid workers to our end-user
documentation (/doc and /support) against GDSG and consistency
with the rest of our documentation.
- Maintaining a style guide of Tails-related terms and usage to
summarizes the terminology decision taken elsewhere.
- Documenting new features, including [[doc/about/features]].
......@@ -26,6 +23,8 @@ as a fallback if no other contributor volunteers to do it.
[[FAQ|support/faq]] or in the list
[[known issues|support/known_issues]]), based on information
provided by our Help Desk and triaged by the Foundations Team.
- Keeping our documentation and support pages efficient for the people
reading them (relevant and easy to navigate).
As technical writers have a limited amount of time to dedicate to these
tasks, Tails as a project should redefine priorities on a regular basis.
......
......@@ -7,14 +7,14 @@ msgid ""
msgstr ""
"Project-Id-Version: Tails\n"
"POT-Creation-Date: 2016-09-19 17:28+0300\n"
"PO-Revision-Date: 2018-04-03 13:47+0200\n"
"PO-Revision-Date: 2018-05-26 20:17+0200\n"
"Last-Translator: Tails translators\n"
"Language-Team: Tails translators <tails@boum.org>\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.8.11\n"
"X-Generator: Poedit 2.0.7\n"
#. type: Plain text
#, no-wrap
......@@ -32,7 +32,7 @@ msgstr ""
#. type: Title =
#, no-wrap
msgid "Unlock the persistent volume\n"
msgstr ""
msgstr "Entsperren Sie den beständigen Speicherbereich\n"
#. type: Bullet: '1. '
msgid ""
......@@ -44,15 +44,7 @@ msgstr ""
"administration_password]]."
#. type: Plain text
#, fuzzy, no-wrap
#| msgid ""
#| "1. Choose\n"
#| " <span class=\"menuchoice\">\n"
#| " <span class=\"guimenu\">Applications</span>&nbsp;▸\n"
#| " <span class=\"guisubmenu\">Accessories</span>&nbsp;▸\n"
#| " <span class=\"guimenuitem\">Disk Utility</span>\n"
#| " </span>\n"
#| " to open the <span class=\"application\">GNOME Disk Utility</span>.\n"
#, no-wrap
msgid ""
"1. Choose\n"
" <span class=\"menuchoice\">\n"
......@@ -65,51 +57,38 @@ msgstr ""
"1. Wählen Sie\n"
" <span class=\"menuchoice\">\n"
" <span class=\"guimenu\">Anwendungen</span>&nbsp;▸\n"
" <span class=\"guisubmenu\">Zubehör</span>&nbsp;▸\n"
" <span class=\"guimenuitem\">Laufwerksverwaltung</span>\n"
" <span class=\"guisubmenu\">Hilfsprogramme</span>&nbsp;▸\n"
" <span class=\"guimenuitem\">Laufwerke</span>\n"
" </span>\n"
" um die <span class=\"application\">GNOME Laufwerksverwaltung</span> zu starten.\n"
" um <span class=\"application\">GNOME Laufwerke</span> zu starten.\n"
#. type: Bullet: '1. '
#, fuzzy
#| msgid ""
#| "In the left pane, click on the device corresponding to your Tails device."
msgid ""
"In the left pane, click on the device corresponding to your Tails USB stick."
msgstr ""
"Wählen Sie im linken Fensterbereich das Speichergerät aus, welches Ihrem "
"Tails Medium entspricht."
"Wählen Sie im linken Fensterbereich das Speichermedium aus, welches Ihrem "
"USB-Stick mit Tails entspricht."
#. type: Bullet: '1. '
#, fuzzy
#| msgid ""
#| "In the right pane, click on the partition labeled as <span class="
#| "\"guilabel\">Encrypted</span>. The <span class=\"guilabel\">Partition "
#| "Label</span> must be <span class=\"label\">TailsData</span>."
msgid ""
"In the right pane, click on the partition labeled as <span class=\"guilabel"
"\">TailsData LUKS</span>."
msgstr ""
"Wählen Sie im rechten Fensterbereich die Partition mit dem Namen <span class="
"\"guilabel\">Verschlüsselt</span> aus. Der <span class=\"guilabel"
"\">Partitionsname</span> muss <span class=\"label\">TailsData</span> lauten."
"Klicken Sie im rechten Fensterbereich auf die Partition mit dem Namen <span "
"class=\"guilabel\">TailsData LUKS</span>."
#. type: Bullet: '1. '
#, fuzzy
#| msgid ""
#| "Click on <span class=\"guilabel\">Unlock Volume</span> to unlock the old "
#| "persistent volume. Enter the passphrase of the old persistent volume and "
#| "click <span class=\"guilabel\">Unlock</span>."
msgid ""
"Click on the <span class=\"guimenu\">[[!img lib/unlock.png alt=\"Unlock\" "
"class=\"symbolic\" link=\"no\"]]</span> button to unlock the persistent "
"volume. Enter the passphrase of the persistent volume and click <span class="
"\"guilabel\">Unlock</span>."
msgstr ""
"Wählen Sie <span class=\"guilabel\">Datenträger entsperren</span> aus, um "
"den alten, beständigen Speicherbereich freizuschalten. Geben Sie die "
"Passphrase des alten, beständigen Speicherbereichs ein und wählen Sie <span "
"class=\"guilabel\">Entsperren</span> aus."
"Klicken Sie auf die Schaltfläche <span class=\"guimenu\">[[!img lib/unlock."
"png alt=\"Entsperren\" class=\"symbolic\" link=\"no\"]]</span>, um den "
"beständigen Speicherbereich freizuschalten. Geben Sie die Passphrase des "
"beständigen Speicherbereichs ein und klicken Sie auf <span class=\"guilabel"
"\">Entsperren</span>."
#. type: Bullet: '1. '
msgid ""
......@@ -120,17 +99,12 @@ msgstr ""
"klicken Sie auf <span class=\"guilabel\">Anmelden</span>."
#. type: Bullet: '1. '
#, fuzzy
#| msgid ""
#| "Click on the <span class=\"guilabel\">TailsData</span> partition that "
#| "appears below the <span class=\"guilabel\">Encrypted Volume</span> "
#| "partition."
msgid ""
"Click on the <span class=\"guilabel\">TailsData Ext4</span> partition that "
"appears below the <span class=\"guilabel\">TailsData LUKS</span> partition."
msgstr ""
"Wählen Sie die Partition <span class=\"guilabel\">TailsData</span> aus, die "
"unter der Partition <span class=\"guilabel\">Verschlüsselter Datenträger</"
"Klicken Sie auf die Partition <span class=\"guilabel\">TailsData Ext4</"
"span>, die unter der Partition <span class=\"guilabel\">TailsData LUKS</"
"span> erscheint."
#. type: Bullet: '1. '
......@@ -140,15 +114,20 @@ msgid ""
"dev/mapper/luks-xxxxxxxx</code>. Triple-click to select it and press <span "
"class=\"keycap\">Ctrl+C</span> to copy it to the clipboard."
msgstr ""
"Ermitteln Sie den <span class=\"guilabel\">Gerätenamen</span> Ihres "
"beständigen Speicherbereichs, welcher unter der Liste der Medien erscheint. "
"Er sollte etwa <code>/dev/mapper/luks-xxxxxxxx</code> lauten. Klicken Sie "
"drei Male auf ihn und drücken Sie <span class=\"keycap\">Strg+C</span>, um "
"ihn in die Zwischenablage zu kopieren"
#. type: Title =
#, fuzzy, no-wrap
#, no-wrap
#| msgid "[[!meta title=\"Check the file system of the persistent volume\"]]\n"
msgid "Check the file system using the terminal\n"
msgstr "[[!meta title=\"Das Dateisystem des beständigen Speicherbereichs überprüfen\"]]\n"
msgstr "Das Dateisystem im Terminal überprüfen\n"
#. type: Plain text
#, fuzzy, no-wrap
#, no-wrap
#| msgid ""
#| "1. Choose\n"
#| " <span class=\"menuchoice\">\n"
......@@ -166,23 +145,24 @@ msgid ""
" and enter your administration password to open a root terminal.\n"
msgstr ""
"1. Wählen Sie\n"
" <span class=\"menuchoice\">\n"
" <span class=\"guimenu\">Anwendungen</span>&nbsp;▸\n"
" <span class=\"guisubmenu\">Zubehör</span>&nbsp;▸\n"
" <span class=\"guimenuitem\">Laufwerksverwaltung</span>\n"
" </span>\n"
" um die <span class=\"application\">GNOME Laufwerksverwaltung</span> zu starten.\n"
" <span class=\"menuchoice\">\n"
" <span class=\"guimenu\">Anwendungen</span>&nbsp;▸\n"
" <span class=\"guisubmenu\">Systemwerkzeuge</span>&nbsp;▸\n"
" <span class=\"guimenuitem\">Root Terminal</span></span>\n"
" und geben Sie ihr Administrationspasswort ein, um ein Terminal mit Administrationsrechten zu starten.\n"
#. type: Bullet: '1. '
msgid ""
"In the terminal, execute the following command, replacing `[device]` with "
"the device name found in step 8:"
msgstr ""
"Führen Sie im Terminal folgenden Befehl aus und ersetzen Sie `[Gerät]` mit "
"dem Gerätenamen, den Sie in Schritt 8 herausgefunden haben:"
#. type: Plain text
#, no-wrap
msgid " fsck -y [device]\n"
msgstr ""
msgstr " fsck -y [Gerät]\n"
#. type: Plain text
#, no-wrap
......@@ -191,6 +171,9 @@ msgid ""
" <span class=\"keycap\">Shift+Ctrl+V</span> to paste the device name from the\n"
" clipboard.\n"
msgstr ""
" Um dies zu tun, können Sie <span class=\"command\">fsck -y&nbsp;</span> eingeben und \n"
" <span class=\"keycap\">Shift+Strg+V</span> drücken, um den Gerätenamen aus der Zwischenablage\n"
" einzufügen.\n"
#. type: Bullet: '1. '
msgid ""
......@@ -198,6 +181,9 @@ msgid ""
"class=\"command\">fsck</span> starts with <span class=\"command\">TailsData: "
"clean</span>."
msgstr ""
"Wenn das Dateisystem fehlerfrei ist, beginnt die letzte Zeile der Ausgabe "
"von <span class=\"command\">fsck</span> mit <span class=\"command"
"\">TailsData: clean</span>."
#. type: Plain text
#, no-wrap
......@@ -206,6 +192,9 @@ msgid ""
" fix them automatically. After it finishes, you can try executing the same\n"
" command again to check if all errors are solved.\n"
msgstr ""
" Falls das Dateisystem fehlerhaft ist, versucht <span class=\"command\">fsck</span> diese automatisch\n"
" zu beheben. Nachdem es fertig ist, können Sie den Befehl erneut ausführen, um zu überprüfen ob alle\n"
" Fehler gelöst sind.\n"
#~ msgid "Click on <span class=\"guilabel\">Check Filesystem</span>."
#~ msgstr ""
......
......@@ -7,14 +7,14 @@ msgid ""
msgstr ""
"Project-Id-Version: Tails\n"
"POT-Creation-Date: 2017-07-31 21:51+0000\n"
"PO-Revision-Date: 2015-10-18 17:00+0100\n"
"Last-Translator: Tails translators <tails@boum.org>\n"
"PO-Revision-Date: 2018-05-30 08:41+0200\n"
"Last-Translator: Tails translators\n"
"Language-Team: Tals translators <tails@boum.org>\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.6.10\n"
"X-Generator: Poedit 2.0.7\n"
#. type: Plain text
#, no-wrap
......@@ -26,14 +26,15 @@ msgid ""
"Start Tails from the USB stick on which you want to delete the persistent "
"volume."
msgstr ""
"Starten Sie Tails von dem USB-Stick, von dem Sie den beständigen "
"Speicherbereich löschen möchten."
#. type: Plain text
#, no-wrap
msgid " Do not enable the persistent volume in <span class=\"application\">Tails Greeter</span>.\n"
msgstr ""
msgstr " Aktivieren Sie den beständigen Speicherbereich im <span class=\"application\">Tails Greeter</span> nicht.\n"
#. type: Bullet: ' 1. '
#, fuzzy
#| msgid ""
#| "To delete the persistent volume of a Tails device, choose\n"
#| "<span class=\"menuchoice\">\n"
......@@ -47,25 +48,15 @@ msgid ""
"span>&nbsp;▸ <span class=\"guisubmenu\">Tails</span>&nbsp;▸ <span class="
"\"guimenuitem\">Delete persistent volume</span></span>."
msgstr ""
"Um den beständigen Speicherbereich eines Tails Mediums zu löschen, wählen "
"Sie\n"
"<span class=\"menuchoice\">\n"
" <span class=\"guimenu\">Anwendungen</span>&nbsp;▸\n"
" <span class=\"guisubmenu\">Tails</span>&nbsp;▸\n"
" <span class=\"guimenuitem\">Delete persistent volume</span></span> und "
"wählen Sie die\n"
" <span class=\"guilabel\">Löschen</span>-Schaltfläche aus.\n"
"Wählen Sie <span class=\"menuchoice\"> <span class=\"guimenu\">Anwendungen</"
"span>&nbsp;▸ <span class=\"guisubmenu\">Tails</span>&nbsp;▸ <span class="
"\"guimenuitem\">Delete persistent volume</span></span>."
#. type: Bullet: ' 1. '
msgid "Click <span class=\"guilabel\">Delete</span>."
msgstr ""
msgstr "Klicken Sie auf <span class=\"guilabel\">Löschen</span>."
#. type: Plain text
#, fuzzy
#| msgid ""
#| "This can be useful in order to delete all the files saved to the "
#| "persistent volume in a single operation. You can later create a new "
#| "persistent volume on the same device without having to reinstall Tails."
msgid ""
"This can be useful in order to delete all the files saved to the persistent "
"volume in a single operation. You can later create a new persistent volume "
......@@ -73,8 +64,8 @@ msgid ""
msgstr ""
"Dies kann nützlich sein, um alle Dateien, die im beständigen Speicherbereich "
"gesichert sind, in einem einzelnen Vorgang zu löschen. Sie können "
"anschließend einen neuen beständigen Speicherbereich auf dem gleichen Medium "
"erstellen, ohne dass es notwendig ist, Tails neu zu installieren."
"anschließend einen neuen beständigen Speicherbereich auf dem gleichen USB-"
"Stick erstellen, ohne dass es notwendig ist, Tails neu zu installieren."
#. type: Title -
#, no-wrap
......@@ -87,13 +78,7 @@ msgid "<div class=\"caution\">\n"
msgstr "<div class=\"caution\">\n"
#. type: Plain text
#, fuzzy, no-wrap
#| msgid ""
#| "<strong>The previous technique might not prevent an attacker from recovering the files in the\n"
#| "old persistent volume using [[data\n"
#| "recovery techniques|encryption_and_privacy/secure_deletion#why]].</strong>\n"
#| "To securely delete the persistent volume, start Tails from another media, and do the following\n"
#| "operations on the device that you want to delete securely:\n"
#, no-wrap
msgid ""
"<strong>The previous technique might not prevent an attacker from recovering the files in the\n"
"old persistent volume using [[data\n"
......@@ -101,24 +86,13 @@ msgid ""
"To securely delete the persistent volume, start Tails from another USB stick or DVD, and do the following\n"
"operations on the USB stick that you want to delete securely:\n"
msgstr ""
"<strong>Die vorherige Methode könnte Angreifende nicht davon abhalten, die Dateien\n"
"im alten beständigen Speicherbereich mit [[Verfahren für Datenwiederherstellung|encryption_and_privacy/secure_deletion#why]] zurückzugewinnen.</strong>\n"
"Um den beständigen Speicherbereich sicher zu löschen, starten Sie Tails von einem anderen Medium,\n"
"<strong>Die vorherige Methode kann Angreifende möglicherweise nicht davon abhalten, die Dateien\n"
"im alten beständigen Speicherbereich mit [[Verfahren für Datenwiederherstellung|encryption_and_privacy/secure_deletion#why]] wiederherzustellen.</strong>\n"
"Um den beständigen Speicherbereich sicher zu löschen, starten Sie Tails von einem anderen USB-Stick oder von einer DVD,\n"
"und erledigen Sie die folgenden Arbeitsschritte mit dem Medium, das Sie sicher löschen möchten:\n"
#. type: Plain text
#, fuzzy, no-wrap
#| msgid ""