You can help Tails! The first release candidate for the upcoming version 3.0 is out. We are very excited and cannot wait to hear what you think about it :)

What's new in 3.0~rc1?

Tails 3.0 will be the first version of Tails based on Debian 9 (Stretch). As such, it upgrades essentially all included software.

Changes since Tails 3.0~beta4 include:

  • Important security fixes!

  • Upgrade to current Debian 9 (Stretch).

  • Upgrade tor to 0.3.0.7-1.

  • Upgrade Tor Browser to 7.0a4.

  • Migrate from Icedove to Thunderbird (only cosmetic).

Technical details of all the changes are listed in the Changelog.

How to test Tails 3.0~rc1?

We will provide security updates for Tails 3.0~rc1, just like we do for stable versions of Tails.

But keep in mind that this is a test image. We tested that it is not broken in obvious ways, but it might still contain undiscovered issues.

But test wildly!

If you find anything that is not working as it should, please report to us on tails-testers@boum.org.

Bonus points if you first check if it is a known issue of this release or a longstanding known issue.

Get Tails 3.0~rc1

To upgrade, an automatic upgrade is available from 3.0~beta4 to 3.0~rc1.

If you cannot do an automatic upgrade, you can install 3.0~rc1 by following our usual installation instructions, skipping the Download and verify step.

Tails 3.0~rc1 ISO image OpenPGP signature
Tails 3.0~rc1 torrent

Known issues in 3.0~rc1

  • The documentation has only been partially updated so far.

  • The graphical interface fails to start on some Intel graphics adapters. If this happens to you:

    1. Add the xorg-driver=intel option in the boot menu.
    2. If this fixes the problem, report to to tails-testers@boum.org the output of the following commands:

      lspci -v
      lspci -mn
      

      … so we get the identifier of your graphics adapter and can have this fix applied automatically in the next Tails 3.0 pre-release.

    3. If this does not fix the problem, try Troubleshooting Mode and report the problem to tails-testers@boum.org. Include the exact model of your Intel graphics adapter.
  • There is no Read-Only feature for the persistent volume anymore; it is not clear yet whether it will be re-introduced in time for Tails 3.0 final (#12093).

  • The persistent Tor Browser bookmarks feature is broken if you enable it for the first time in Tails 3.0~rc1; any persistent bookmarks from before will still work.

    You can workaround this as follows, after you start Tails the first time with Browser bookmarks persistence enabled:

    1. Start Tor Browser and let it load
    2. Close Tor Browser
    3. Run this in a Terminal:

      cp /home/amnesia/.tor-browser/profile.default/places.sqlite \
         /home/amnesia/.mozilla/firefox/bookmarks/places.sqlite
      rm /home/amnesia/.tor-browser/profile.default/places.sqlite*
      ln -s /home/amnesia/.mozilla/firefox/bookmarks/places.sqlite \
            /home/amnesia/.tor-browser/profile.default/places.sqlite
      
  • Open tickets for Tails 3.0~rc1

  • Open tickets for Tails 3.0

  • Longstanding known issues

What's coming up?

We will likely publish the first release candidate for Tails 3.0 around May 19.

Tails 3.0 is scheduled for June 13.

Have a look at our roadmap to see where we are heading to.

We need your help and there are many ways to contribute to Tails (donating is only one of them). Come talk to us!

Tags:

We had written and adopted a Code of Conduct since our first public hackfest in Paris in 2014. This code was and is meant as a guide to make our public spaces welcoming and friendly to every sentient being.

We have since then worked on a Social Contract which we proudly present today!

The Tails Social Contract is a set of commitments that we as contributors to the Tails project stand by. This work is derived from the Debian Social Contract and the Tor Social Contract. If you have any questions or comments, feel free to email: tails-project@boum.org.

This is a promise from our contributors community to the rest of the world, affirming a commitment to our beliefs.

1. By creating Tails we try to provide usable tools for anonymity and privacy

We believe that privacy, the free exchange of ideas, and equal access to information are essential to free and open societies. Through our community standards and the tools we create, we provide means that empower all people to protect and advance these ideals.

2. Tails is and will remain free software

Equal access to information includes the free availability of our code and documentation as well as the transparency of our decision making processes.

All the components of Tails that we create ourselves are, and will be, licensed in a manner consistent with the Debian Free Software Guidelines.

Tails will always be free to use, remix, adapt and distribute. As the only exceptions to this rule, Tails includes:

  • a minor part of non-free firmware in order to work on as much hardware as possible;
  • a few pieces of software whose source code is public but not compatible with the Debian Free Software Guidelines; they are needed to support important use cases.

3. We will give back to the Free Software community

Tails is a privacy-oriented Debian Derivative.

We want usable security and privacy-oriented tools to become a standard for the Free Software community as a whole.

Bug fixes, code improvements, Debian packaging, as well as work on usability issues will be sent upstream whenever possible. This way, our modifications will benefit others and can be improved upon further by a wider audience of people.

4. We encourage participation and transparency

We want to produce Tails in a way that encourages participation, which requires publicly documenting what can be improved. As Tails is created in such a transparent manner, anyone is encouraged to participate, review it and point out problems.

To make our community a welcoming place for everybody we agreed on a Code of Conduct.

5. We will never harm our users intentionally

We will always do our best to create secure and usable tools. We will never willingly include backdoors or malicious software nor will we cooperate with any entity wanting us to harm our users.

Mistakes sometimes happen. We will be honest about them and fix those that affect the safety of Tails users when they are reported to us.

Whenever severe security issues are reported to us in private, we will test them and ensure we promptly fix these issues. We will notify our users whenever such an issue has been reported to us. However, for the security of our users, we might not disclose such a severe issue before releasing a fix.

6. We give users the means to decide how much they can rely on Tails

We encourage users to inform themselves and decide if Tails is suitable for their use case and how much they can trust it. We work diligently to keep our community up-to-date through our various communication channels about the current state of our software and its limitations. We encourage users to read our documentation as well as third-party documentation in order to make an informed decision and engage in a learning process about the tools we ship.

We provide and explain methods of verification so that anyone can ensure that they downloaded a genuine copy of Tails.

Tags:

You can help Tails! The fourth beta for the upcoming version 3.0 is out. We are very excited and cannot wait to hear what you think about it :)

What's new in 3.0~beta4?

Tails 3.0 will be the first version of Tails based on Debian 9 (Stretch). As such, it upgrades essentially all included software.

Other changes since Tails 3.0~beta3 include:

  • Important security fixes!

  • All changes brought by Tails 2.12.

  • Upgrade to current Debian 9 (Stretch).

  • Many bug fixes in Tails Greeter.

  • Fix the ORCA screen reader.

  • Replace Pidgin's "systray" icon with the guifications plugin.

Technical details of all the changes are listed in the Changelog.

How to test Tails 3.0~beta4?

We will provide security updates for Tails 3.0~beta4, just like we do for stable versions of Tails.

But keep in mind that this is a test image. We tested that it is not broken in obvious ways, but it might still contain undiscovered issues.

But test wildly!

If you find anything that is not working as it should, please report to us on tails-testers@boum.org.

Bonus points if you first check if it is a known issue of this release or a longstanding known issue.

Get Tails 3.0~beta4

To upgrade, an automatic upgrade is available from 3.0~beta2 and 3.0~beta3 to 3.0~beta4.

If you cannot do an automatic upgrade, you can install 3.0~beta4 by following our usual installation instructions, skipping the Download and verify step.

Tails 3.0~beta4 ISO image OpenPGP signature

Known issues in 3.0~beta4

  • The documentation has only been partially updated so far.

  • The graphical interface fails to start on some Intel graphics adapters. If this happens to you:

    1. Add the xorg-driver=intel option in the boot menu.
    2. If this fixes the problem, report to to tails-testers@boum.org the output of the following commands:

      lspci -v
      lspci -mn
      

      … so we get the identifier of your graphics adapter and can have this fix applied automatically in the next Tails 3.0 pre-release.

    3. If this does not fix the problem, try Troubleshooting Mode and report the problem to tails-testers@boum.org. Include the exact model of your Intel graphics adapter.
  • There is no Read-Only feature for the persistent volume anymore; it is not clear yet whether it will be re-introduced in time for Tails 3.0 final (#12093).

  • Open tickets for Tails 3.0~rc1

  • Open tickets for Tails 3.0

  • Longstanding known issues

What's coming up?

We will likely publish the first release candidate for Tails 3.0 around May 19.

Tails 3.0 is scheduled for June 13.

Have a look at our roadmap to see where we are heading to.

We need your help and there are many ways to contribute to Tails (donating is only one of them). Come talk to us!

Tags:

This release fixes many security issues and users should upgrade as soon as possible.

Changes

New features

  • We installed again GNOME Sound Recorder to provide a very simple application for recording sound in addition to the more complex Audacity. Sound clips recorded using GNOME Sound Recorder are saved to the Recordings folder.

Upgrades and changes

  • We removed I2P, an alternative anonymity network, because we unfortunately have failed to find a developer to maintain I2P in Tails. Maintaining software like I2P well-integrated in Tails takes time and effort and our team is too busy with other priorities.

  • Upgrade Linux to 4.9.13. This should improve the support for newer hardware (graphics, Wi-Fi, etc.).

For more details, read our changelog.

Known issues

  • The video application Totem may crash Tails. You can work around this problem by installing VLC.

See the list of long-standing issues.

Get Tails 2.12

What's coming up?

Tails 3.0 is scheduled for June 13th.

Have a look at our roadmap to see where we are heading to.

We need your help and there are many ways to contribute to Tails (donating is only one of them). Come talk to us!

Tags:

Releases

Tails 2.11 was released on March 7 (minor release).

Tails 2.12 is scheduled for April 18.

The following changes were introduced in Tails 2.11:

  • If running on a 32-bit processor, notify the user that it won't be able to start Tails 3.0 anymore. (#12193)

  • Notify I2P users that I2P will be removed in Tails 2.12. (#12271)

  • Fix CVE-2017-6074 (local root privilege escalation) by disabling the dccp module. (#12280) Also disable kernel modules for some other uncommon network protocols. (Part of #6457)

  • Tor Browser: Don't show offline warning when opening the local documentation of Tails. (#12269)

  • Fix rare issue causing automatic upgrades to not apply properly (#8449 and #11839)

  • Install Linux 4.8.15 to prevent GNOME from freezing with Intel GM965/GL960 Integrated Graphics. (#12217)

Code

I2P to be removed

We are very sad to announce that Tails 2.11 will be the last version to include I2P, an alternative anonymizing network. But we will be happy to reintroduce I2P if we find a volunteer to take care of maintaining it in Tails. If you are a developer and care about I2P in Tails, that person could be you! Come talk to us!

Reproducible builds

We had a very productive 3-days sprint. After many iterations we have finally seen an ISO image build reproducibly on several machines! This implied fixing a number of things, and submitting a number of patches upstream.

The build environment variations we've tested include: build system clock (last month, next month; could not test next year yet), number of CPU cores, CPU brand and model, building in Vagrant or not.

For details, see the full report that was written after the sprint.

Porting Tails to Debian 9 (Stretch)

A bunch of Tails developers and technical writers had a very productive sprint. The remaining work now feels tractable: aside of the documentation update, only a few major regressions and adjustments remain to be dealt with.

So, we are increasingly confident that we can make Tails 3.0 a solid release, published according to schedule on June 13… but possibly a little bit earlier or later, if it allows us to release at the same time as Debian 9 (Stretch).

Two beta releases for Tails 3.0 were published (?3.0~beta2 on March 8, ?3.0~beta3 on March 19). They introduce the following changes:

  • Upgrade Linux to 4.9.0-2 (version 4.9.13-1).

  • Make it possible to start graphical applications in the Root Terminal.

  • Improve styling of the GNOME Shell window list.

  • Tails Greeter:

    • Make the "Formats" settings in Tails Greeter take effect (it was introduced in Tails 3.0~alpha1 but has been broken since then).
    • Add keyboard shortcuts:
      • Alt key for accelerators in the main window
      • Ctrl+Shift+A for setting an administrator password
      • Ctrl+Shift+M for MAC spoofing settings
      • Ctrl+Shift+N for Tor network settings
  • Remove I2P.

  • Reintroduce the X11 guest utilities for VirtualBox (clipboard sharing and shared folders should work again).

  • Upgrade X.Org server and the modesetting driver in hope it will fix crashes when using some Intel graphics cards.

  • Automate the migration from KeePassX databases generated on Tails 2.x to the format required by KeePassX 2.0.x.

Infrastructure

We upgraded some of our systems to Debian 9 (Stretch), in order to help identify remaining issues before it becomes the new Debian stable release.

All major browsers will now refuse to connect to our website, and to any web service we host in the tails.boum.org namespace, unless HTTPS is used with a valid certificate: they are now on the Google Chrome 57 HSTS preload list, and all other major browsers build their own list from this one.

We started researching our options for upgrading our server hardware.

We made some progress on deploying a web platform for translations and an internal XMPP server.

We started a process to hire a new system administrator.

Funding

We've sent a proposal to OTF, that covers:

  • adding TrueCrypt support in GNOME;
  • adding a graphical interface for the Additional Packages persistent feature;
  • a small fraction of our day-to-day operations budget.

Our budget until the end of March, 2018 was approved by the Tails core contributors.

Outreach

Past events

  • On March 1st, Austin English presented Tails at the Austin (Texas) Linux Meetup.
  • Four of us attended the Tor developers meeting in Amsterdam. It was great! See the first report about it.
  • Two of us gave a training about Tails and digital security at Mediapart. Apparently, everything went fine: attendees where mostly interested and happy with it, and asked a lot of questions, ranging from "How can I manage my passwords" to "How much does it cost to compromise my laptop?".

Upcoming events

  • intrigeri will be giving a keynote at CryptoRave (São Paulo, May 5-6).

On-going discussions

We had a contributors meeting on March 3 (minutes).

Translation

All the website

  • de: 56% (3189) strings translated, 5% strings fuzzy, 50% words translated
  • fa: 40% (2265) strings translated, 8% strings fuzzy, 44% words translated
  • fr: 82% (4670) strings translated, 1% strings fuzzy, 81% words translated
  • it: 28% (1598) strings translated, 3% strings fuzzy, 25% words translated
  • pt: 27% (1549) strings translated, 8% strings fuzzy, 25% words translated

Total original words: 58396

Core pages of the website

  • de: 82% (1538) strings translated, 10% strings fuzzy, 83% words translated
  • fa: 38% (708) strings translated, 10% strings fuzzy, 39% words translated
  • fr: 99% (1845) strings translated, 0% strings fuzzy, 99% words translated
  • it: 79% (1486) strings translated, 10% strings fuzzy, 79% words translated
  • pt: 49% (922) strings translated, 13% strings fuzzy, 50% words translated

Total original words: 17057

You can help Tails! The first release candidate for the upcoming version 2.12 is out. Please test it and report any issue. We are particularly interested in feedback relating to whether Tor's startup works better or worse.

How to test Tails 2.12~rc1?

Keep in mind that this is a test image. We tested that it is not broken in obvious ways, but it might still contain undiscovered issues.

But test wildly!

If you find anything that is not working as it should, please report to us! Bonus points if you first check if it is a known issue of this release or a longstanding known issue.

Download and install

Tails 2.12~rc1 ISO image ?OpenPGP signature

To install 2.12~rc1, follow our usual installation instructions, skipping the Download and verify step.

Upgrade from 2.10 or 2.11

  1. Start Tails 2.10 or 2.11 on a USB stick installed using Tails Installer and set an administration password.

  2. Run this command in a Root Terminal to select the "alpha" upgrade channel and start the upgrade:

    echo TAILS_CHANNEL=\"alpha\" >> /etc/os-release && \
         tails-upgrade-frontend-wrapper
    
  3. After the upgrade is installed, restart Tails and choose Applications ▸ Tails ▸ About Tails to verify that you are running Tails 2.12~rc1.

What's new since 2.11?

Changes since Tails 2.11 are:

  • Major changes

    • Completely remove I2P. :( We have decided to remove I2P (see #11276) due to our failure of finding someone interested in maintaining it in Tails (Closes: #12263).
    • Upgrade the Linux kernel to 4.9.0-0.bpo.2 (Closes: #12122).
  • Security fixes

    • Mount a dedicated filesystem on /var/tmp, to mitigate the hardlinks permissions open by the user-tmp abstraction. See https://labs.riseup.net/code/issues/9949#note-23 for details (Closes: #12125).
    • Protect against CVE-2017-2636 by disabling the n-hdlc kernel module (Closes: #12315).
    • Ensure /etc/resolv.conf is owned by root:root in the SquashFS. lb_chroot_resolv will "cp -a" it from the source tree, so it inherits its ownership from the whoever cloned the Git repository. This has two problems. First, this results in unsafe permissions on this file (e.g. a Vagrant build results in the 'amnesia' user having write access to it).
  • Minor improvements

    • Don't add the live user to the "audio" group. This should not be needed on a modern Linux desktop system anymore (Closes: #12209).
    • Install virtualbox-* 5.1.14-dfsg-3~bpo8+1 from our custom APT repository (Closes: #12307).
    • Install virtualbox-guest-* from sid. The version currently in jessie-backports is not compatible with Linux 4.9, and there's basically no chance that it gets updated (the maintainer asked for them to be removed from jessie-backports) (Closes: #12298).
    • Pull ttdnsd from our custom APT repository. It's gone from the TorProject one. We removed ttdnsd on feature/stretch already, so we'll need to pull it from our custom APT repository only for the next 3 months.
    • Clean up libdvd-pkg build files, again. This cleanup operation was mistakenly removed in commit c4e8744 (Closes: #11273).
    • Install gnome-sound-recorder (Closes #10950). Thanks to Austin English austinenglish@gmail.com for the patch!
    • Stop restarting tor if bootstrapping stalls. It seems tor might have fixed the issues we used (see: #10238, #9516) to experience with the bootstrap process stalling and requiring a restart to kickstart it (Closes: #12411).
    • tor.sh: communicate via the UNIX socket instead of TCP port. This makes the library usable when run inside systemd units that have PrivateNetwork=yes set.
    • Get tor's bootstrap progress via GETINFO instead of log grep:ing.
  • Bugfixes

    • mirror-pool-dispatcher: bump maximum expected mirrors.json size to 32 KiB. This fixes an error where Tails Upgrader would complain with "cannot choose a download server" (Closes: #11735).

For more details, see also our changelog.

Known issues in 2.12~rc1

  • In Tails Greeter, selecting the This computer's Internet connection is censored, filtered, or proxied is broken. Using it will start Tor Launcher but it will fail to connect to tor, so it's unusable, and tor itself will not be able to bootstrap. If you need this option, skip this release candidate; this issue will be fixed in the final 2.12 release.

  • Longstanding known issues

Tags:

You can help Tails! The third beta for the upcoming version 3.0 is out. We are very excited and cannot wait to hear what you think about it :)

What's new in 3.0~beta3?

Tails 3.0 will be the first version of Tails based on Debian 9 (Stretch). As such, it upgrades essentially all included software.

Other changes since Tails 3.0~beta2 include:

  • Important security fixes!

  • Upgrade to current Debian 9 (Stretch).

  • Tails Greeter:

    • Make the "Formats" settings in Tails Greeter take effect (it was introduced in Tails 3.0~alpha1 but has been broken since then).
    • Add keyboard shortcuts:
      • Alt key for accelerators in the main window
      • Ctrl+Shift+A for setting an administrator password
      • Ctrl+Shift+M for MAC spoofing settings
      • Ctrl+Shift+N for Tor network settings
  • Remove I2P. (This will happen in Tails 2.12 as well.)

  • Reintroduce the X11 guest utilities for VirtualBox (clipboard sharing and shared folders should work again).

  • Upgrade X.Org server and the modesetting driver in hope it will fix crashes when using some Intel graphics cards.

  • Automate the migration from KeePassX databases generated on Tails 2.x to the format required by KeePassX 2.0.x.

Technical details of all the changes are listed in the Changelog.

How to test Tails 3.0~beta3?

We will provide security updates for Tails 3.0~beta3, just like we do for stable versions of Tails.

But keep in mind that this is a test image. We tested that it is not broken in obvious ways, but it might still contain undiscovered issues.

But test wildly!

If you find anything that is not working as it should, please report to us on tails-testers@boum.org.

Bonus points if you first check if it is a known issue of this release or a longstanding known issue.

Get Tails 3.0~beta3

To upgrade, an automatic upgrade is available from 3.0~beta2 to 3.0~beta3.

If you cannot do an automatic upgrade, you can install 3.0~beta3 by following our usual installation instructions, skipping the Download and verify step.

Tails 3.0~beta3 ISO image OpenPGP signature

Known issues in 3.0~beta3

Tags:

You can help Tails! The second beta for the upcoming version 3.0 is out. We are very excited and cannot wait to hear what you think about it :)

What's new in 3.0~beta2?

Tails 3.0 will be the first version of Tails based on Debian 9 (Stretch). As such, it upgrades essentially all included software.

Other changes since Tails 3.0~beta1 include:

  • All changes brought by Tails 2.11.

  • Upgrade to current Debian 9 (Stretch).

  • Upgrade Linux to 4.9.0-2 (version 4.9.13-1).

  • Make it possible to start graphical applications in the Root Terminal.

  • Improve styling of the GNOME Shell window list.

Technical details of all the changes are listed in the Changelog.

How to test Tails 3.0~beta2?

We will provide security updates for Tails 3.0~beta2, just like we do for stable versions of Tails.

But keep in mind that this is a test image. We tested that it is not broken in obvious ways, but it might still contain undiscovered issues.

But test wildly!

If you find anything that is not working as it should, please report to us on tails-testers@boum.org.

Bonus points if you first check if it is a known issue of this release or a longstanding known issue.

Download and install

Tails 3.0~beta2 ISO image OpenPGP signature

To install 3.0~beta2, follow our usual installation instructions, skipping the Download and verify step.

Known issues in 3.0~beta2

  • The documentation was not adjusted yet.

  • The Formats settings chosen in Tails Greeter have no effect (#12079).

  • There is no Read-Only feature for the persistent volume anymore; it is not clear yet whether it will be re-introduced in time for Tails 3.0 final (#12093).

  • If you use the KeePassX persistence feature, you need to manually import your passwords database (#10956).

  • Some command-line programs (at least Monkeysign, Git, and wget) display confusing error messages in the Terminal, although they work fine: #11736, #12091, #12205.

  • I2P fails to start (#12108). Note that I2P will be removed in Tails 2.12 and 3.0.

  • Open tickets for Tails 3.0

  • Longstanding known issues

Tags:

This release fixes many security issues and users should upgrade as soon as possible.

Changes

We are very sad to announce that Tails 2.11 will be the last version to include I2P, an alternative anonymizing network.

Maintaining software like I2P well-integrated in Tails takes time and effort and our team is too busy with other priorities. Unfortunately, we failed to find a developer outside of our team to maintain I2P in Tails. As a consequence, the last version of I2P being shipped in Tails is 0.9.25, which is nearly one year old now at this moment.

But we will be happy to reintroduce I2P if we find a volunteer to take care of maintaining it in Tails. If you are a developer and care about I2P in Tails, that person could be you! Come talk to us!

New features

  • If running on a 32-bit processor, notify the user that it won't be able to start Tails 3.0 anymore. (#12193)

  • Notify I2P users that I2P will be removed in Tails 2.12. (#12271)

Upgrades and changes

  • Upgrade Tor Browser to 6.5.1.

  • Fix CVE-2017-6074 (local root privilege escalation) by disabling the dccp module. (#12280) Also disable kernel modules for some other uncommon network protocols. (Part of #6457)

Fixed problems

  • Tor Browser: Don't show offline warning when opening the local documentation of Tails. (#12269)

  • Fix rare issue causing automatic upgrades to not apply properly (#8449 and #11839)

  • Install Linux 4.8.15 to prevent GNOME from freezing with Intel GM965/GL960 Integrated Graphics. (#12217)

For more details, read our changelog.

Known issues

None specific to this release.

See the list of long-standing issues.

Get Tails 2.11

What's coming up?

Tails 2.12 is scheduled for April 18th.

Have a look at our roadmap to see where we are heading to.

We need your help and there are many ways to contribute to Tails (donating is only one of them). Come talk to us!

Tags:

Releases

The following changes were introduced in Tails 2.10:

  • We installed OnionShare, a tool for anonymous file sharing.

  • We enabled the circuit view in Tor Browser.

  • Replace AdBlock Plus with uBlock Origin.

  • Configure the APT package manage to use Debian's Onion services.

  • Install the AMDGPU display driver. This should improve the support for newer AMD graphics adapters.

  • Renamed the Boot Loader Menu entries from "Live" to "Tails", and replaced the confusing "failsafe" wording with "Troubleshooting Mode".

  • Add support for exFAT.

  • Remove Nyx (previously called arm).

  • Rewrite Tor control port filter entirely. Now Tails can safely support OnionShare, the circuit view of Tor Browser, and similar. This also enabled Whonix to replace their own similar piece of software with this one.

Code

  • We (almost) finished updating the AppArmor policy in Debian Stretch so that it supports merged-/usr systems.
  • We started evaluating USBGuard, and posted suggestions to improve its user experience, that upstream warmly welcomes.

Documentation and website

  • We documented how to use OnionShare, a tool for anonymous file sharing.

  • We documented the circuit view in Tor Browser.

User experience

Infrastructure

  • We started to set up a XMPP server to satisfy the need for private communication tools expressed by one of our teams.
  • We enabled an Onion service for our APT repository (#11556).
  • We improved our systems so that they send less useless email to our system administrators.
  • We started updating our Puppet modules to better support Debian Stretch.

Funding

Outreach

Upcoming events

  • We have a booth at FOSDEM in Brussels.
  • Tails will be presented at a cryptoparty on March 4th 2017 in Rennes, France.
  • We started organizing a Debian event that will take place in Paris on May 13-14. Stay tuned!

On-going discussions

Translation

All the website

  • de: 54% (3050) strings translated, 5% strings fuzzy, 49% words translated
  • fa: 40% (2265) strings translated, 8% strings fuzzy, 45% words translated
  • fr: 81% (4562) strings translated, 1% strings fuzzy, 80% words translated
  • it: 28% (1602) strings translated, 3% strings fuzzy, 26% words translated
  • pt: 27% (1551) strings translated, 8% strings fuzzy, 25% words translated

Total original words: 57564

Core pages of the website

  • de: 82% (1539) strings translated, 10% strings fuzzy, 83% words translated
  • fa: 38% (710) strings translated, 10% strings fuzzy, 40% words translated
  • fr: 98% (1842) strings translated, 1% strings fuzzy, 99% words translated
  • it: 80% (1490) strings translated, 10% strings fuzzy, 79% words translated
  • pt: 49% (924) strings translated, 13% strings fuzzy, 50% words translated

Metrics

  • Tails has been started more than 662 874 times this month. This makes 21 383 boots a day on average.
  • 14 782 downloads of the OpenPGP signature of Tails ISO from our website.
  • 142 bug reports were received through WhisperBack.