GitLab

Currently translated at 17.7% (11 of 62 strings)

Translation: Tails/wiki/src/news/version_3.14.1.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_3141po/pt/

Currently translated at 39.0% (16 of 41 strings)

Translation: Tails/wiki/src/news/version_3.11.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_311po/it/

8.5.4-build2 was published as 8.5.4 while the Tor Browser import was
being performed. Acknowledge there were no changes between both
versions.

This avoids the need to build and upload Thunderbird packages every now and
then. Instead, we'll need to refresh our patches when they don't apply
as-is anymore.

Current patchset imported from our icedove.git at
commit a3eab1e85558f2c9cf01d332920ac81fea3cd9fd.

sdhci and subdependencies initrd kernel modules loaded to support Heads kexec'ing Tails kernel from sdcard integrity validated iso, permitting Tails to boot from a Read Only sdcard (fromiso). Heads boot device is referred by device/by-uuid (fromiso) to continue Heads kexec boot process from OS initrd loaded modules, prerequisite to continue kernel booting.

This would permit measured boot (on-boot iso integrity validation from Read Only sdcard) on many tamper evident laptop models( RYF x200, QubesOS to be certified x230, x220 and many other laptops using those modules for memory extension slot support).

Linked to this discussion: https://lists.autistici.org/message/20190612.203305.bcc3b98b.en.html
Linked to this Heads ticket: https://github.com/osresearch/heads/issues/581

Let's hope that bringing the initramfs down under 32MB will repair the boot of
feature/buster on MacBookPro 8,1. In any case, this should improve UX by:

 - making boot faster for every user
 - shortening the duration during which we display a black screen,
   between the bootloader and the Plymouth splash screen

Not using -buildN as I'm importing the tarballs that were *already*
released, so in this case -buildN does not matter and this information
is not readily available anyway.

It brings linux 4.19.37-4.

This is a follow-up on commit:7174efed,
that claimed to test whether we were building a stable release,
but merely checked whether $TAILS_CHANNEL == alpha. Both are equivalent
at the moment but as anonym pointed out, this assumption might become
wrong, e.g. if we ever add a "beta" channel.

Fix-committed: #16780

Some programs expect this, which could lead to hard-to-debug issues
for front desk from users installing such a program.

Refs: #16148

We attempt to completely block it on the netfilter level but we have
seen ICMPv6 "leaks" any way (related to Router Solicitation, refs:
16148) so let's just completely disable.

Most of thunderbird.feature is @fragile so we need the +force-all-tests
suffix so that Jenkins runs these tests.

Set Tor Browser's homepage to https://tails.boum.org/home/testing/ if building anything but a stable release (refs: #12003)

This depends on web/12003-custom-home-for-rc being merged into master,
so that this new specific homepage actually exists.

procmail is listed with packages said to be “Priority: standard” but
it's only “Priority: optional” in stretch. With monkeysphere going away
(in 2cee7949), this package is no longer
pull and no longer visible in tagged snapshots, which leads to this
FTBFS:

    E: Unable to locate package procmail
    E: config/chroot_local-hooks/98-remove_unwanted_packages failed (exit non-zero). You should check for errors.

Hotfix for 3.14: switch to mutt-style removal, and trigger a purge for
procmail only if it's (known and) installed.

Without arguments partprobe will scan all devices, and if it
encounters a device it doesn't support (e.g. fake raid-0 arrays) it
will return non-zero, thus aborting Tails' partitioning script,
resulting in an unbootable install.

Will-fix: #16389

This version requirement is satisfied by Jessie and I doubt Tails would build in
anything older.

And anyway, we now only support building in Vagrant, which guarantees us we have
a recent enough syslinux installed.

To be consistent with other Tails apps (e.g. additional-software).

Enable all available mitigations for the MDS vulnerability and disable SMT on vulnerable CPUs (refs: #16720)