Commit b42b94fa authored by anonym's avatar anonym
Browse files

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

parents 2d053cdf 3bddb516
......@@ -222,10 +222,11 @@ po_master_language: en|English
# slave languages (translated via PO files) format: ll|Langname
po_slave_languages:
- de|Deutsch
- fa|Farsi
- fr|Français
- pt|Português
# PageSpec controlling which pages are translatable
po_translatable_pages: '!security/audits and !security/audits/* and (about or bugs or chat or contribute or contribute/how/donate or doc or doc/* or download or download.inline or getting_started or inc/release_notes/* or inc/stable_i386_date or inc/stable_i386_release_notes or index or news or news/* or press or press/* or security or security/* or sidebar or support or support/* or todo or torrents or wishlist or misc or misc/* or install or install/* or upgrade or upgrade/*)'
po_translatable_pages: '!security/audits and !security/audits/* and (about or bugs or chat or contribute or contribute/how/donate or doc or doc/* or download or download.inline or getting_started or inc/release_notes/* or inc/stable_i386_release_notes or index or news or news/* or press or press/* or security or security/* or sidebar or support or support/* or todo or torrents or wishlist or misc or misc/* or install or install/* or upgrade or upgrade/*)'
# internal linking behavior (default/current/negotiated)
po_link_to: current
......
......@@ -199,10 +199,11 @@ po_master_language: en|English
# slave languages (translated via PO files) format: ll|Langname
po_slave_languages:
- de|Deutsch
- fa|Farsi
- fr|Français
- pt|Português
# PageSpec controlling which pages are translatable
po_translatable_pages: '!security/audits and !security/audits/* and (about or bugs or chat or contribute or contribute/how/donate or doc or doc/* or download or download.inline or getting_started or inc/release_notes/* or inc/stable_i386_date or inc/stable_i386_release_notes or index or news or news/* or press or press/* or security or security/* or sidebar or support or support/* or todo or torrents or wishlist or misc or misc/* or install or install/* or upgrade or upgrade/*)'
po_translatable_pages: '!security/audits and !security/audits/* and (about or bugs or chat or contribute or contribute/how/donate or doc or doc/* or download or download.inline or getting_started or inc/release_notes/* or inc/stable_i386_release_notes or index or news or news/* or press or press/* or security or security/* or sidebar or support or support/* or todo or torrents or wishlist or misc or misc/* or install or install/* or upgrade or upgrade/*)'
# internal linking behavior (default/current/negotiated)
po_link_to: current
......
This diff is collapsed.
......@@ -11,29 +11,236 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in December 2015.
Everything in this report can be made public.
# A. Replace Claws Mail with Icedove
## A.n. description of subsection
XXX: explain the new timeline / postponed stuff
## A.1.2 Make our improvements maintainable for future versions of Icedove
We've been following up on upstreaming patches from
[tagnaq's paper](https://trac.torproject.org/projects/tor/raw-attachment/wiki/doc/TorifyHOWTO/EMail/Thunderbird/Thunderbird%2BTor.pdf)
and are happy to see that two of them were included upstream.
([[!tails_ticket 6150]])
- `Date` headers are sanitized with a [JS patch in
TorBirdy](https://trac.torproject.org/6314).
- `Message-ID` headers are fixed with a [C++ patch in Thunderbird
45](https://hg.mozilla.org/comm-central/rev/a8573d4c67292962f9dd9b8f51496e9f62bbedb7).
- A.n.m. description of deliverable: ticket numbers
In order to make our improvements maintainable we've got
in touch with the Debian Icedove packaging team and written manual tests for
testing Icedove in Tails. ([[!tails_ticket 9493]])
status summary:
These still have to be converted to automated tests in our test suite.
([[!tails_ticket 6304]])
* what was done
* what is the outcome (how it makes Tails better)
* what was not done, and why
## A.1.3 Integrate Icedove into Tails
Since 1.8 we advertise Icedove to our users as the default email client in
Tails. Claws Mail will be removed in the next release of Tails, version 2.0.
Users can now use the Icedove persistence feature.
# B. Improve our quality assurance process
## B.1. Automatically build ISO images for all the branches of our source code that are under active development
In December, **809 ISOs** were automatically built by our Jenkins
instance.
## B.2. Continuously run our entire test suite on all those ISO images once they are built
In December, **788 ISOs** were tested by our Jenkins instance.
- B.2.4. Implement and deploy the best solution from this research
We went on with the effort we started in October, to identify test
cases that prove to be fragile in our CI environment, that were
blocking us from notifying contributors when tests fail there.
And finally, we reached the point when we felt comfortable with the
subset of our automated test suite we deem to be robust, and
unleashed these notifications to the greater Tails community
([announce](https://mailman.boum.org/pipermail/tails-dev/2015-December/009931.html)).
We will now go on working on making as much of our test suite robust enough
to be suitable for running in this context (B.3.11, see below).
([[!tails_ticket 10296]] and [[!tails_ticket 10382]])
Other than that, our testing setup has seen quite some polishing all
over the place, that we are going to sum up now.
As a way to optimize resource usage and to shorten the feedback
loop, we have limited the amount of tests we run on ISO images built from
documentation branches: we now run only the test cases that depends
on the documentation shipped in Tails, instead of the entire test
suite. ([[!tails_ticket 10492]], [[!tails_ticket 10706]] and
[[!tails_ticket 10707]])
We also excluded early, work-in-progress draft branches from being automatically
tested in Jenkins. We want to encourage developers to share work
even if it is very rough, not ready to be merged, and fails to pass
the test suite. In such cases, we should not discourage developers
with lots of notifications about test failures.
([[!tails_ticket 10389]])
We also had a look to check after a whole release cycle if the saving
of video artifacts for failing scenarios wasn't using too much disk
space, and concluded it was fine. ([[!tails_ticket 10354]])
We also fixed a usability issue where the branches that were not merged yet were
removed from the list of branches to be automatically built and tested
after each release, resulting in losing their automatic build and
test history. ([[!tails_ticket 10123]])
We identified a concerning amount of test suite runs aborted on
Jenkins due to timeouts, investigated the root causes
([[!tails_ticket 10720]]), and mitigated the problem for the time
being. [[!tails_ticket 10717]]
Finally, we automated the way we compute statistics about our ISO
builds and test suite runs in Jenkins tracking progress.
([[!tails_ticket 10507]])
## B.3. Extend the coverage of our test suite
* B.3.11. Fix newly identified issues to make our test suite more robust and faster
During December,
- We fixed several fragile scenarios:
Seahorse ([[!tails_ticket 10501]] and ([[!tails_ticket 9095]]),
whois ([[!tails_ticket 10523]]),
Tails Installer ([[!tails_ticket 10718]])
- Some fragile scenarios have been worked on and have a proposed fix:
Tails OpenPGP keys, by updating the soon to be expired one
([[!tails_ticket 10378]]), and Git ([[!tails_ticket 10444]]))
- We also identified other scenarios that were fragile in Jenkins:
MAC address spoofing ([[!tails_ticket 10774]]),
Evince ([[!tails_ticket 10775]]),
Memory wipe ([[!tails_ticket 10776]]),
Race condition with boot splash ([[!tails_ticket 10777]]), and
Opening Tails roadmap URL from pidgin ([[!tails_ticket 10783]]).
Due to the `wait_until_tor_is_working` helper being buggy
([[!tails_ticket 10497]]), we marked most network related scenarios
as fragile.
## B.4. Freezable APT repository
- B.4.5. Implement processes and tools for importing and freezing
those packages ([[!tails_ticket 10749]], [[!tails_ticket 10748]],
[[!tails_ticket 6299]]),
B.4.2. Implement a mechanism to save the list of packages used at
ISO build time ([[!tails_ticket 6297]])
Some more code was written and reviewed. A few potential issues were
identified and are being discussed within the team.
- B.4.6. Adjust the rest of our ecosystem to the freezable APT
repository
We started an evaluation of the hardware resources required by our
draft design ([[!tails_ticket 6295]]).
# C. Scale our infrastructure
## C.2. Be able to detect within hours failures and malfunction on our services
We had to reschedule our plans on this front, as the Jenkins deliverable
took some more of our time, as well as the Tails 1.8.1 emergency
release.
We already started to deploy locally on a developer machine a prototype
setup using Puppet to get an idea of how the chosen solution can be
deployed, and how compatible it is with our setup.
We plan to go on deploying this prototype by the end of January, as
well as finishing the installation of the VM that will host this
service, which means deciding how we'll handle its Puppet
configuration ([[!tails_ticket 10760]]).
We are now aiming to have this all deployed in production by the end
of March.
## C.4. Maintain our already existing services
We kept on answering the requests from the community as well as taking
care of security updates as covered by "C.4.4. Administer our services
up to milestone IV" until the end of December.
We also had a sysadmin sprint in the middle of December, but sadly, most of it
had to be spent working on the Tails 1.8.1 emergency release.
To save a bit of disk space that we need for later work (e.g freezable
APT repo), we reduced the temporary partitions used by our ISO testing
virtual machines, after evaluating what they really use.
([[!tails_ticket 10396]])
# D. Migration to Debian Jessie
## D.2. Take advantage of systemd to improve the internals of Tails
We polished code that was previously ported to systemd:
* Fixed `tor-has-bootstrapped` semantics on network reconnect
([[!tails_ticket 10732]]).
## D.3. Update our test suite for Tails Jessie
We have updated most of the test suite for Jessie ([[!tails_ticket 7563]]).
Some new test suite robustness problems are left to be addressed, but
the current state was good enough to make us feel comfortable
releasing Tails 2.0~beta1. Besides, we are happy to point out that
this automated test suite made us discover quite a few bugs in
Jessie-based Tails development versions, that we would probably not
have noticed before the first beta release otherwise.
Here is the list of relevant tickets that were resolved during the
reporting period (most of the test suite porting work was done
directly in Git, without filing tickets for each bit that needed to be
adjusted, though):
* Dropped an obsolete test case ([[!tails_ticket 10336]]).
* Disabled screen blanking during the test suite, it breaks some tests ([[!tails_ticket 10403]]).
* Updated the tests for communication with OpenPGP keyservers ([[!tails_ticket 9791]]).
* Replaced our previous iptables status regexp-based parser with a new
XML-based status analyzer: the previous implementation could not be
adjusted to the new ip6tables' output ([[!tails_ticket 9704]]).
* Updated the "all notifications have disappeared" test suite step for
Jessie ([[!tails_ticket 8782]]).
## D.4. Document the changes implied by the move to Jessie on our website
XXX
## D.5. Release an official version of Tails based on Jessie
On December 22 we published a first beta for the upcoming Tails 2.0,
based on Debian Jessie: <https://tails.boum.org/news/test_2.0-beta1/>.
It was very useful so far: we received a lot of feedback, including
a few bug reports. Most of these bugs were fixed since then, but that
will be for next report round :)
The first release of Tails based on Debian Jessie is still scheduled
for January 26.
## Various porting to Jessie
A lot of other porting to Jessie work was done, that does not really
fit into any of the above categories:
* Install Electrum 0.2.5.x in Tails/Jessie ([[!tails_ticket 10754]]).
* Fixed obfs4proxy support ([[!tails_ticket 10724]]).
* Fixed time synchronization in bridge mode when the clock is way off
([[!tails_ticket 10696]]).
# E. Release management
XXX: write this section
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in January 2016.
Everything in this report can be made public.
......@@ -27,6 +30,24 @@ Everything in this report can be made public.
* what is the outcome (how it makes Tails better)
* what was not done, and why
## A.1.1 Secure the Icedove autoconfig wizard
We've been evaluating our own patches for Icedove against those
reported to Mozilla's bugtracker and are happy to announce that our
patches would provide an option to accept only secure protocols, as
a user opt-in. These patches will be submitted to Mozilla's bugtracker
and hopefully integrated upstream.
([[!tails_ticket 7064]])
## A.1.2 Make our improvements maintainable for future versions of Icedove
Unfortunately we also discovered that the autoconfig wizard of Icedove does
not always use the configured proxy. This means, that some traffic can leak.
This is not a security problem in Tails since we drop non-Tor
traffic by default, but for this very reason in breaks the
functionality of the autoconfig wizard in the context of Tails.
We started to write a proof-of-concept patch to fix this bug.
# B. Improve our quality assurance process
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in February 2016.
Everything in this report can be made public.
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in March 2016.
Everything in this report can be made public.
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in April 2016.
Everything in this report can be made public.
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in May 2016.
Everything in this report can be made public.
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in June 2016.
Everything in this report can be made public.
......
......@@ -11,6 +11,9 @@ Deliverable identifiers and descriptions are not free-form: they must
be copy'n'pasted as-is from the proposal sent to the sponsor.
</div>
[Last month's activity on Redmine](https://labs.riseup.net/code/projects/tails/issues?query_id=208)
can be helpful.
This reports covers the activity of Tails in July 2016.
Everything in this report can be made public.
......
Ticket [[!tails_ticket 8578]],
This page summarizes resources we provide to help you make Tails research more effective.
Based on Debian GNU/Linux, working on Tails is mostly glue work, based on research and existing software.
We'd like to work with the academic research community in order to solve some open research questions that exist for live distributions like Tails. This page consists of various open ended research problems we'd like to see resolved.
When you are working on a research question that is interesting for us as a project or solving a related problem to Tails **please** talk to us. The *earlier* the **better** so we can help you make the *right* assumptions.
When you worked on a problem and published a paper about it, please let us know and we'll list your paper on a page on our website and link it from here.
The best way to reach us is through the [tails-dev](https://mailman.boum.org/listinfo/tails-dev/) mailinglist, or at our (possibly) encrypted address tails[AT]boum.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.
* 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)
## Research ideas
* [Randomness seeding](https://tails.boum.org/blueprint/randomness_seeding/)
* [Persistent Tor state](https://tails.boum.org/blueprint/persistent_Tor_state/)
* [Time syncing](https://tails.boum.org/blueprint/robust_time_syncing/)
[[!meta title="About possible derivatives"]]
What for:
- Include additional features that we are not ready to add to Tails (for example
to include GNUnet or Namecoin).
- Have custom branding or configuration.
- Provide ISO images with less or different features (for example to
have VPN instead of Tor).
Why is it complicated:
- Release every 6 weeks, plus the occasional unscheduled emergency
security release
- Heavy quality assurance process (automated builds and tests)
- Complex infrastructure (upgrades)
- User trust (authenticated downloads, OpenPGP Web-of-Trust)
- Fingerprinting & partitioning users into a anonymity subset
- For features that are not in Tails because there has been no time or
solution for doing them correctly, the temptation to just shove them
in hastily and call it done
Good ways of doing it:
- Don't build your own ISO images.
- Package your specific applications in Debian to make them easier to
use in Tails.
- Document how to use your specific applications in Tails.
- Rely on the mechanisms already available in Tails to adapt it to your
needs (additional software packages, persistent storage).
- Help us build in Tails other mechanisms that you might need to adapt
it to your needs (for example to have persistent DConf settings or APT
sources).
- Talk with us to see how we can adapt our ISO images and source code to make them
easier for your to reuse.
- If you want to include a piece of software into Tails, talk to us as
early as possible so we can provide feedback on how to integrate it.
Open questions:
- Trademark aspects. Will derivatives appear as being "Tails" to their
users while having different security features than Tails? Shall we
review ourselves the work of derivatives and "endorse" them? How could
crappy derivatives impact negatively the name and reputation of Tails?
This is about [[!tails_ticket 10040]].
This is about [[!tails_ticket 7642]], [[!tails_ticket 7675]],
[[!tails_ticket 6116]], and friends.
[[!meta title="SecureDrop"]]
This is about [[!tails_ticket 10853]].
[[!meta title="WhisperBack for frontdesk"]]
[[!toc levels=2]]
At the 2015 summit, we identified a few improvements to WhisperBack that
would make the life of our support team easier. Namely:
......
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: tails-l10n@boum.org\n"
"POT-Creation-Date: 2015-07-28 09:53+0200\n"
"PO-Revision-Date: 2015-09-29 14:14+0000\n"
"Last-Translator: Sprint 1 <translation1@451f.org>\n"
"Language-Team: Persian <http://weblate.451f.org:8889/projects/tails/bugs/fa/>"
"\n"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Weblate 2.4-dev\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Bugs\"]]\n"
msgstr "[[!meta title=\"ایراد\"]]\n"
#. type: Plain text
msgid ""
"If you've found a bug in Tails, please read "
"[[doc/first_steps/bug_reporting]]."
msgstr ""
"اگر ایرادی در تیلز پیدا کرده‌اید، این صفحه را بخوانید "
"[[doc/first_steps/bug_reporting]]."
#. type: Plain text
msgid ""
"We don't use this section anymore, see "
"[[contribute/working_together/Redmine]] instead."
msgstr ""
"ما دیگر از این صفحه استفاده می‌کنیم, به جای آن به صفحه‌ی "
"[[contribute/working_together/Redmine]] بروید."
......@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-12-10 15:30+0100\n"
"POT-Creation-Date: 2015-12-26 01:20+0100\n"
"PO-Revision-Date: 2014-04-18 23:25+0100\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -454,8 +454,9 @@ msgid "<a id=\"upstream\"></a>\n"
msgstr "<a id=\"upstream\"></a>\n"
#. type: Title =
#, no-wrap
msgid "Relationship with upstream\n"
#, fuzzy, no-wrap
#| msgid "Relationship with upstream\n"
msgid "Relationship with upstream and derivatives\n"
msgstr "Verhältnis zum Upstream\n"
#. type: Bullet: ' - '
......@@ -467,6 +468,10 @@ msgid "[[Improve Tails by working on Debian|contribute/how/debian]]"
msgstr ""
"[[Tails verbessern, indem Sie an Debian mitarbeiten|contribute/how/help]]"
#. type: Bullet: ' - '
msgid "[[About creating Tails derivatives|contribute/derivatives]]"
msgstr ""
#. type: Plain text
#, no-wrap
msgid "<a id=\"collective-process\"></a>\n"
......
This diff is collapsed.
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