Commit 1c46f792 authored by Ulrike Uhlig's avatar Ulrike Uhlig

Merge branch 'master' of

parents eb42db4f e811bcdd
......@@ -67,6 +67,87 @@ Template email for validating the output
<a id="Daan"></a>
Daan, December 2017
Daan is a 18 years old ICT (information and communications technology)
student and a security researcher. He lives in the Netherlands and
cares a lot about privacy.
He learned about Tails on the Tor website after he started using Tor.
He tried Tails, noticed that everything was routed through Tor by
default and liked it. He also immediately appreciated that
cryptography tools, such as OpenPGP encryption, are readily
accessible. The memory erasure on shutdown feature was another
key point.
Daan is a power-user who themed his Tails and uses additional software
packages. He uses Tails only when he feels it's needed and not daily,
for example when he feels like the government may target him because
he looks up specific information. He uses Tails for penetration
testing, sharing files privately with his friends, and occasionally
for software development.
Things he likes:
1. Memory erasure on shutdown.
2. Access to encryption tools (OpenPGP, KeePassX).
3. No data leaves the computer without going through Tor.
Things he dislikes:
1. He find the applications menu hard to use (but he likes GNOME).
2. He would like to see [tcpcrypt]( integrated
in Tails.
3. He finds the Tails user interface glossy and thinks it should
look fancier.
4. He wants server functionality in Tails.
<a id="Charles"></a>
Charles, December 2017
Charles is 30 years old and lives in North America. He is a political
activist working on law reform at the state level. He cares about free
software and calls himself a "purist". He is part of an organization
that provides computers and cell phones with free software
(_libreboot_, _Replicant_) to people.
Around 2012, Bill Binney's revelations about the amount of spying done
by the US government shocked him and prompted him to re-evaluate his
decisions about how he kept control of his data & communication.
This made him start to use Tor and Tails.
Since three years, Charles uses Tails daily. He submits bug reports
and sends suggestions to the developers. He is a power-user at ease in
a terminal; he installs additional packages to adapt Tails to
his needs. He mainly uses Tails for IRC and XMPP chat, email, web
browsing and SSH.
Things he likes:
1. He has a sense of trust in the people who work on the Tails
project, and particularly about the fact they will make decisions
that will be in his best interest.
2. Something he calls "usability": once the desired settings are in
place, every time he boots Tails it's fresh (but customized as
3. Tor is integrated system-wide by default, which avoids the need to
configure another OS to achieve this goal.
Things he dislike:
1. Tails lacks support for next-generation IM (e.g. OMEMO); he is
aware that this support might be available via Additional Software
Packages already, but he thinks it should be available by default.
2. Charles misses a really free software version of Tails (Linux Libre
kernel, no firmware).
3. Charles misses support for server-related features (XMPP server,
Media Goblin, Mumble).
<a id="Miguel"></a>
Miguel, May 2017
[[!meta title="Tails report for December, 2017"]]
[[!meta date="DATE"]]
[[!toc ]]
* [[Tails VERSION was released on MONTH DAY|news/version_VERSION]] ([major|minor] release).
* Tails VERSION+1 is [[scheduled for MONTH DAY|contribute/calendar]].
The following changes were introduced in Tails VERSION:
XXX: Copy the "Changes" section of the release notes, and compact a bit:
* Remove lines about software upgrade (that's not Tails itself).
* Remove screenshots.
* Remove "New features" and "Upgrades and changes" headlines.
* Remove line about Changelog.
XXX: List important code work that is not covered already by the Release
section (for example, the changes being worked on for the next version).
* XXX: for Additional Software Package & VeraCrypt work, see
[[blueprint/SponsorW/2017_12]] (or if it's been published already,
Documentation and website
XXX: Explore the Git history:
git log --patch --since='1 October' --until='1 November' origin/master -- "*.*m*"
User experience
XXX: Check the archives of tails-ux:
* XXX: for Additional Software Package & VeraCrypt work, see
[[blueprint/SponsorW/2017_12]] (or if it's been published already,
Hot topics on our help desk
1. [[!tails_ticket 15066 desc="Tor Browser cannot print to file"]]
XXX: Count the number of tests in /features at the beginning of next month
git checkout `git rev-list -n 1 --before="June 1" origin/devel`
git grep --extended-regexp '^\s*Scenario:' -- features/*.feature | wc -l
XXX: Report only if more scenarios have been written and add the diff from the previous month, for example:
- Our test suite covers SCENARIOS scenarios, DIFF more that in May.
- We have converted two sources of email sent by cron with Icinga2
monitoring checks that are easier to track and fine-tune
([[!tails_ticket 11598]], [[!tails_ticket 12455]]).
- We have fixed a longstanding bug that made the UX of our CI system
confusing when deleting a branch in Git ([[!tails_ticket 15069]]).
- We have set up a local email server on every Jenkins node that runs
automated ISO tests, as a first step towards making our automatic
_Thunderbird_ tests more robust ([[!tails_ticket 12277]]).
- We have tuned our servers to get a little bit better performance
out of our CI system ([[!tails_ticket 15054]]).
XXX: The fundraising team should look at the fundraising Git.
git log --patch --since='1 December' --until='1 January' origin/master
XXX: The fundraising and accounting teams should look at the archives of <> and <>.
Past events
Upcoming events
XXX: We will have a booth at FOSDEM in Brussels.
On-going discussions
XXX: Link to the thread on <>.
Press and testimonials
XXX: Copy content from press/media_appearances_2017.mdwn
This page is continuously updated by, so if
it's empty there might be nothing special to report.
XXX: Add the output of `contribute/l10n_tricks/`
XXX: Add the output of (adjust month!):
git checkout $(git rev-list -n 1 --before="September 1" origin/master) && \
git submodule update --init && \
* Tails has been started more than BOOTS/MONTH times this month. This makes BOOTS/DAY boots a day on average.
* SIGS downloads of the OpenPGP signature of Tails ISO from our website.
* WHISPERBACK bug reports were received through WhisperBack.
XXX: Ask for these numbers.
......@@ -47,7 +47,7 @@ Hot topics on our help desk
XXX: Ask to list hot topics for the last month.
1. Electrum, Metldown and Spectre vulnerabilities made our users restless.
......@@ -86,6 +86,7 @@ The client must support SASL authentication.
* It has support for "temporary XMPP accounts" that require no
registration (no user input!) which would be useful for our support
channel (see [[!tails_ticket 11307]]).
* Tor Messenger provides Linux packages but is not in Debian :(
* FWIW: Tor Messenger got 30K USD funding in 2017!
* FWIW: anonym has been happy using it exclusively for chatting since
September, 2016.
......@@ -105,6 +106,11 @@ The client must support SASL authentication.
* [Homepage](
* [Github](
* CoyIM only supports XMPP.
* CoyIM [is in Debian](
* Supports Tor, TLS, OTR
* Supports creation of random accounts.
* No logging, no clickable links.
* Not audited.
## dino
......@@ -112,8 +118,7 @@ The client must support SASL authentication.
* implemented in GTK+/Vala
* supports XMPP and OMEMO; OTR support is
[not high on the todo list](
* should be [[!debpts dino-im desc="in Debian"]] when you read this
([[!debbug 860055]])
* is be [[!debpts dino-im desc="in Debian"]] experimental
* the Debian maintainer wants to add an AppArmor profile and got in
touch with intrigeri about it
[[!meta title="Strategic planning"]]
This living document reflects the current state of the thinking
process, within the Tails project, about our mission and goals.
You can
[[prepare and propose|contribute/meetings#preparing-a-discussion]]
a discussion about a strategic planning topic for the
[[contributors meeting|contribute/meetings]].
[[!toc levels=2]]
# How to read this document
Every stated property or goal below is tagged with letters between
square brackets (`[]`) as being part of one or several categories:
- **R** for **relevance & usefulness** goals, expressed in numbers or
facts e.g. "triple userbase in 3 years", "you use Tails in Tibet"
- **I** for **identity**: the way we want Tails to be perceived, for
example "Tails is for everyone and not just for extreme use cases
like Edward Snowden"
- **UX** for **UX goals**: the problem we want to solve for our
users. For example, "non-technical Mac users say it's easy to
install Tails" or "Tails makes me safe when I'm in Saudi Arabia"
- **D** for **differentiators**: what are we offering that noone else
can? e.g. "you can use Tails on someone else's computer"
- **B** for **benefits**, that is why should users care: for example,
answers to "why should I put that much effort int getting started
with Tails?" such as "it feels good to use a computer that behaves
the way I legitimately expect"
The examples above are only meant to be examples, not necessarily
actual goals.
Each stated property or goal below is also tagged with numbers that
reflect how attendees of the Tails summit 2017 ranked it.
Every attendee was given five "+1" dots and five "-1" dots.
For example, "+3-1" on a statement means that that three attendees
put dot in favour of it, while one attendee put a dot against it.
# Current properties
## Seems consensual
- Tails works on ~cheap, 2nd hand or off-the-shelf PC hardware [D+B, +5]
- Tails works on computers that have no baseband [D, +1]
- Trustworthy OS: does what it says on the box, honest about its limitations,
driven by ethical values [B,D,I, +4]
- Tails is self-contained: use it everywhere and keep it in your pocket [B, +1]
- Tails doc is world class [D, +1]
- Tails is reliable and here to stay [I+D, +3]
- Tails contributors can be occasional + part-time + ad-hoc [I, +1]
- A nice help desk & user support [D, +2]
- Tails cares about its international audience [I, +1]
- Tails allows me to act more freely (with sense of security) [B, +1]
## Needs discussion
- I can afford a 2nd computer for Tails only [B, +1-1]
- Can share Tails with other users [B, +1-2]
# Goals
## Seems consensual
- Streamline installation / 1st boot / upgrade [UX, +19]
- Using Tails, I can communicate with smartphone users (e.g. Matrix, Signal, etc.) [UX, +3]
- All journalists know how to use Tails (as part of their studies) [UX, +2]
- Tails doc is fun and sexy [D, +2]
- Use data gathered by help desk to refine documentation [R, +1]
- More heterogeneous & easy to join community [R+I, +11]
- Wi-Fi works [UX, +1]
- Tails works [I, +2]
- You cannot break Tails (just reboot) [D, +2]
- Tails is easy: you don't have to know how it works [I+B, +5]
- Support more diverse users / use cases, e.g. blind users, people using Tails
3 times a year only, Windows & macOS users [I+R, +8]
- I don't have to be a power-user to use Tails conveniently; e.g. no terminal
involved, don't scare users away with complexity [UX+D, +4]
- Sustainable funding: e.g. 100% of core budget comes from unrestricted funding,
more recurrent donations after help desk & from partners, Tails is endorsed
(sponsored?) by major press organizations [R, +5]
- 10% of core budget goes in UX improvement (including whatever software
development it may require) [R, +2]
- Attract + hire new project members specialized in accounting,
management, and grant writing; lighten the plate of the current
accounting team members. This does *not* cover team leads for
development projects, who have to be technical people. [R, consensus]
- Less concentration of responsibility/workload, and Tails survival does not
depend on any individual. [R, +3]
- More contributors [R, +2]
- Persistence should be trivial to use and to backup [UX, +2]
- Keeping a DIY and family sprint for our gatherings which is both
cheaper and more friendly [R, consensus]
- Stick to self-organization, consensus-based decision making, and
welcome people with diverse backgrounds as long as they are fine with
this and abide by our [[contribute/working together/Code of conduct]]
([R, consensus])
- I want to find things on the website without the 90s experience [UX, +2]
## Needs discussion
- Sandboxing (better resist exploitation without degrading UX) [R+B, +9-4]
- Tails runs on mobile/touch/ARM devices [R, +6-3]
- Oppressed people can safely use Tails (e.g. without being detected) [B, +5-3]
- Usability without documentation [UX, +3-1]
- Users can give feedback to help improve UX [UX, +1-1]
- Tails is easily customizable [UX+B, +2-2]
- Don't have to trust your hardware [B, +1-2]
- Tails should be endorsed (sponsored) by (meta-) state institutions (EU?) [R, +1-3]
- Containers/separated identities without rebooting [R, +1-1]
- I can meet Tails people in person [I, +1-1]
- The Tails project can be trusted [I, +2-1]
- Funding from government independent organizations [I, +2-2]
- Public advocacy and increased visibility [I, +2-1]
- I can't go outside without my Tails [I, +1-1]
### To be discussed at Tails Summit 2018
- We can accommodate more diverse financial needs, e.g. long-term
stable full-time workers, various part-time or occasional
contributions [R, +6-1]
- How large should our project, and user base be [R+I, +7-5]
# Unclear
## Current properties
- Free do-it-yourself online safety
## Goals
- Users know how to interact with the developer community [?, +1]
- I don't need to trust Tails' infra/servers [UX, +1]
- Cut through national firewalls to allow free flow of new + knowledge [?, +1]
- Tails is something obvious [I, +1]
- Website nice and easy (personas) [UX, +1]
- Tails is an all-in-one solution to global surveillance [B, +1]
- Tails "employs" >= 1 more Debian developers [R, +1]
- UX/documentation/l10n is as important as technical aspects [R, +1]
- I can easily create a safe communication channel with others [B, +1]
- Help desk budget < RM budget [R, +1]
- Tails itself is a friendly environment of Tails development [UX, +1]
......@@ -63,9 +63,25 @@ What we plan to do is:
[Schematics of the different Git repos, ikiwiki instances, and their relationships.](
Currently the repo is following Tails master repo, but the changes it generates are not fed back onto Tails master.
Currently the repo is following Tails master repo, but the changes it generates are not fed back onto Tails master automatically.
There are several languages enabled, some of them with few or not translations.
You can check out weblate-generated Tails repo with:
git clone
This Tails repository has two main differences with other repos:
- The ikiwiki.setup file has been changed to build more language files
- There are lots of new language files
Staging version
From this repository, a version of the website with more languages will be built [[!tails_ticket 12311]] so users can see how the file they are translating looks.
......@@ -152,3 +152,15 @@ able to reproduce the build of a released ISO) = 3 years.
Depending on the growth rate of our tagged snapshots in practice, we
may or may not need to implement expiration of these snapshots any
time soon. Time will tell.
# Known issues
## Unusable tagged APT snapshots generated for unused APT sources
When an APT source from which we pull no package at ISO build time is
configured in the Tails Git repository, the tagged APT snapshot
generated for that APT source will be unusable, which breaks the
ISO build.
To avoid this problem, ensure we do not enable any useless APT source
at ISO build time.
......@@ -34,10 +34,14 @@ To have fruitful discussions we prepare them to make sure that:
- The required people or skills are present.
- The discussion is lead in a fruitful way.
If you want to propose a discussion:
Discussions with no assignee will be postponed.
## Discussion about a Redmine ticket
If you want to propose a discussion about
a [[Redmine|contribute/working_together/Redmine]] ticket:
- Make sure that it corresponds to a
[[Redmine|contribute/working_together/Redmine]] ticket with:
- Make sure that it corresponds to a ticket with:
- *Discuss* as its *Type of Work*
- You as its *Assignee*
......@@ -45,7 +49,21 @@ If you want to propose a discussion:
- Add it to the [[blueprint of the agenda|blueprint/monthly_meeting]].
Discussions with no assignee will be postponed.
## Discussion about a strategic planning topic
If you want to propose a discussion about a strategic planning topic:
- Make sure it is marked *Needs discussion* on our
[[blueprint/Strategic planning]] living document.
- Prepare yourself for facilitating this discussion:
- Think about how you will structure the discussion.
- The
[Facilitating consensus in Virtual Meetings](
guide is a good resource to get started.
- Add it to the [[blueprint of the agenda|blueprint/monthly_meeting]].
<a id="notes"></a>
......@@ -6,6 +6,8 @@ This report covers the activity of Tails in December 2017.
Everything in this report is public.
<a id="veracrypt"></a>
# A. VeraCrypt support in GNOME
## A.1 Research user needs and implementation costs
......@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Tails\n"
"POT-Creation-Date: 2017-12-27 00:17+0100\n"
"PO-Revision-Date: 2017-08-13 11:25+0000\n"
"PO-Revision-Date: 2018-01-12 18:13+0000\n"
"Last-Translator: AtomiKe <>\n"
"Language-Team: Tails translators <>\n"
"Language: fr\n"
......@@ -55,8 +55,6 @@ msgid " [[!img introduction_to_gnome_and_the_tails_desktop/system.png link=\"no
msgstr " [[!img introduction_to_gnome_and_the_tails_desktop/system.png link=\"no\"]]\n"
#. type: Plain text
#, fuzzy
#| msgid "- By removing physically the USB stick or DVD Tails is running from."
msgid ""
"- By physically removing the USB stick or DVD that Tails is running from."
msgstr ""
......@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Tails\n"
"POT-Creation-Date: 2017-12-26 21:18+0100\n"
"PO-Revision-Date: 2017-06-07 16:39+0000\n"
"PO-Revision-Date: 2018-01-12 17:52+0000\n"
"Last-Translator: amnesia <>\n"
"Language-Team: Tails translators <>\n"
"Language: fr\n"
......@@ -140,21 +140,15 @@ msgid "Using <span class=\"application\">Tails Greeter</span>\n"
msgstr "Utiliser <span class=\"application\">Tails Greeter</span>\n"
#. type: Plain text
#, fuzzy, no-wrap
#| msgid ""
#| "<span class=\"application\">Tails Greeter</span> is the set of dialogs that\n"
#| "appear after the <span class=\"application\">Boot Loader Menu</span>, but before the\n"
#| "<span class=\"application\">GNOME Desktop</span> appears. This is how the first\n"
#| "screen of <span class=\"application\">Tails Greeter</span> looks like:\n"
#, no-wrap
msgid ""
"<span class=\"application\">Tails Greeter</span>\n"
"appears after the <span class=\"application\">Boot Loader Menu</span>, but before the\n"
"<span class=\"application\">GNOME Desktop</span>:\n"
msgstr ""
"<span class=\"application\">Tails Greeter</span> est un ensemble de boîtes de dialogue\n"
"qui apparaît après le <span class=\"application\">menu du chargeur d’amorçage</span>, mais avant que le\n"
"<span class=\"application\">bureau GNOME</span> n'apparaisse. Voici à quoi ressemble\n"
"le premier écran de <span class=\"application\">Tails Greeter</span> :\n"
"<span class=\"application\">Tails Greeter</span>\n"
"apparaît après le <span class=\"application\">menu du chargeur d’amorçage</span>, mais avant le\n"
"<span class=\"application\">bureau GNOME</span> :\n"
#. type: Plain text
#, no-wrap
......@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2017-12-26 20:48+0100\n"
"POT-Creation-Date: 2018-01-11 23:26+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <>\n"
......@@ -126,6 +126,11 @@ msgid ""
"strong adversaries.</a>"
msgstr ""
#. type: Content of: <div><div><div><div><div><p>
msgid ""
"[[How does the extension work?|contribute/design/verification_extension]]"
msgstr ""
#. type: Content of: <div>
msgid "\"\"\"]]"
msgstr ""
......@@ -172,11 +177,16 @@ msgid "<u>Tails Verification</u> extension installed!"
msgstr ""
#. type: Content of: <div><div><div><div><div>
#, fuzzy
#| msgid ""
#| "[[!inline pages=\"inc/stable_amd64_gpg_verify\" raw=\"yes\" sort=\"age\"]]"
msgid ""
"<label id=\"verify-download-wrapper\" class=\"btn btn-primary inline-block"
"\"> Verify download&hellip; <input id=\"verify-download\" type=\"file\"/> </"
"\"> Verify Tails <span class=\"remove-extra-space\">&nbsp;[[!inline pages="
"\"inc/stable_amd64_version\" raw=\"yes\" sort=\"age\"]]</span>&hellip; "
"<input id=\"verify-download\" type=\"file\"/> </label>"
msgstr ""
"[[!inline pages=\"inc/stable_amd64_gpg_verify\" raw=\"yes\" sort=\"age\"]]"
#. type: Content of: <div><div><div><div><div><div><p>
msgid "Verifying <span id=\"filename\">$FILENAME</span>&hellip;"
......@@ -206,6 +216,17 @@ msgid ""
"during the download."
msgstr ""
#. type: Content of: <div><div><div><div><div><div><div><p>
#, fuzzy
#| msgid ""
#| "[[!inline pages=\"inc/stable_amd64_gpg_verify\" raw=\"yes\" sort=\"age\"]]"
msgid ""
"The verification also fails if you try to verify a different download than "
"the latest version (<span class=\"remove-extra-space\">[[!inline pages=\"inc/"
"stable_amd64_version\" raw=\"yes\" sort=\"age\"]]</span>)."
msgstr ""
"[[!inline pages=\"inc/stable_amd64_gpg_verify\" raw=\"yes\" sort=\"age\"]]"
#. type: Content of: <div><div><div><div><div><div><div><p>
msgid ""
"Less likely, the verification might have failed because of a malicious "
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2017-12-26 20:48+0100\n"
"POT-Creation-Date: 2018-01-11 23:26+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"