Hello Tails Team and Testers,
Here is our report on Tails 4.11~rc1. Let us know if any clarification is desired.
Thanks to the Tails team for all their hard work, and congratulations on nearing another successful release.
This email is signed with our OpenPGP key, which is also attached in ASCII-armored format.
To learn more about us, or, to confirm the details of said key, please visit our website at:
https://circletop.wordpress.com
Best Regards,
Circletop
Contact: circletop@???
========================================================================================================================
CONTENTS:
+ Introduction
+ Build information
+ Acquisition
+ Verification
+ Installation
+ Boot
+ Persistence
+ Welcome Screen
+ Tor
+ Tor Browser
+ Manual Test Suite
+ References
+ OpenPGP Key Details
========================================================================================================================
INTRODUCTION:
These tests were performed using Tails 4.10 and 4.11~rc1. Both operating systems ran from a USB flash drive on a 64-bit PC computer with password-protected Secure Boot enabled. The computer was plugged into a power source the whole time, and never ran on battery.
All internet connections were established using 2.4 GHz 802.11 ("Wi-Fi") with WPA2 AES-PSK encryption.
In general, 4.11~rc1 performs as well as 4.10. It boots, displays the correct version, runs Tor, the Tor Browser, the Unsafe Browser, and other applications without producing errors.
The new persistent settings on the Welcome Screen function fine, as does persistence of other data.
The main problem we discovered is that the Tor Browser 10.0a6 in Tails 4.11~rc1 is much more likely to produce a Cloudflare captcha request when attempting to access a website than its predecessor, Tor Browser 9.5.4 in Tails 4.10.
========================================================================================================================
BUILD INFORMATION:
This is the build information for the two versions of Tails used in these tests:
Tails 4.10:
4.10 - 20200824
340e0ca863b5f8aca8ac47edab2235d82420dee9
live-build: 3.0.5+really+is+2.0.12-0.tails5
live-boot: 1:20170112
live-config: 5.20190519
Tails 4.11~rc1:
4.11~rc1 - 20200907
f851752ef1b31c0fa5674830ff10df151597fe8f
live-build: 3.0.5+really+is+2.0.12-0.tails5
live-boot: 1:20170112
live-config: 5.20190519
========================================================================================================================
ACQUISITION:
All files relevant to the installation of Tails 4.11~rc1 were downloaded using the Tor Browser 9.5.4 running on Tails 4.10. However, the Tails signing key and signatures were downloaded a second time using the "wget" command in the terminal, then, the checksums of the respective pairs were compared. All were identical.
The following is a list of the five acquired files in addition to relevant information:
1. Tails signing key
Filename: tails-signing.key
Source:
https://tails.boum.org/tails-signing.key
SHA-256 Checksum: 7a4e647d7ead15db1f5b0ba8013c710ace2c91957e75a32110795c3c8be50651
2. Tails 4.11~rc1 USB image
Filename: tails-amd64-4.11~rc1.img
Source:
https://tails.quantum-mirror.hu/alpha/tails-amd64-4.11~rc1/tails-amd64-4.11~rc1.img
SHA-256 Checksum: 3cfc11e112f94f70cde2018c469db65a5653236d05eaa3b4deec449a1ba13c59
3. Tails 4.11~rc1 USB image OpenPGP signature
Filename: tails-amd64-4.11~rc1.img.sig
Source:
https://tails.boum.org/torrents/files/tails-amd64-4.11~rc1.img.sig
SHA-256 Checksum: 05eec118ce725d1b297b7c4d0dfe012907d169866580c210a4e612ea11cb77e3
4. Tails 4.11~rc1 ISO image
Filename: tails-amd64-4.11~rc1.iso
Source:
https://tails.quantum-mirror.hu/alpha/tails-amd64-4.11~rc1/tails-amd64-4.11~rc1.iso
SHA-256 Checksum: c583734586fbc0fdd95289c2e4a51a5dc519349aa5daf16fabeb9b360dd478e0
5. Tails 4.11~rc1 ISO image OpenPGP signature
Filename: tails-amd64-4.11~rc1.iso.sig
Source:
https://tails.boum.org/torrents/files/tails-amd64-4.11~rc1.iso.sig
SHA-256 Checksum: 4e83f68d908696d70f200c92f40eaedb8098110052ce7a14c3f229c75e1955dc
========================================================================================================================
VERIFICATION:
Verification of the Tails 4.11~rc1 installation media using either the terminal or Seahorse-tool integrated into Nautilus ("Files") both succeeded.
The only small problem was a grammatical error in the part of the notification the Seahorse-tool produced which reads "Valid but untrusted signature by on 2020-09-07." The "by" should be removed. This error occurred verifying both the USB and ISO images.
The following is the terminal output displayed when importing the Tails signing key then verifying the respective media using the "gpg" command:
amnesia@amnesia:~$ gpg --import tails-signing.key
gpg: key 0xDBB802B258ACD84F: 2170 signatures not checked due to missing keys
gpg: key 0xDBB802B258ACD84F: "Tails developers (offline long-term identity key) <tails@???>" 8 new signatures
gpg: Total number processed: 1
gpg: new signatures: 8
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
amnesia@amnesia:~$ TZ=UTC gpg --no-options --keyid-format long --verify tails-amd64-4.11~rc1.img.sig tails-amd64-4.11~rc1.img
gpg: Signature made Mon 07 Sep 2020 03:17:42 PM UTC
gpg: using RSA key 05469FB85EAD6589B43D41D3D21DAD38AF281C0B
gpg: Good signature from "Tails developers (offline long-term identity key) <tails@???>" [unknown]
gpg: aka "Tails developers <tails@???>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: A490 D0F4 D311 A415 3E2B B7CA DBB8 02B2 58AC D84F
Subkey fingerprint: 0546 9FB8 5EAD 6589 B43D 41D3 D21D AD38 AF28 1C0B
amnesia@amnesia:~$ TZ=UTC gpg --no-options --keyid-format long --verify tails-amd64-4.11~rc1.iso.sig tails-amd64-4.11~rc1.iso
gpg: Signature made Mon 07 Sep 2020 03:17:30 PM UTC
gpg: using RSA key 05469FB85EAD6589B43D41D3D21DAD38AF281C0B
gpg: Good signature from "Tails developers (offline long-term identity key) <tails@???>" [unknown]
gpg: aka "Tails developers <tails@???>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: A490 D0F4 D311 A415 3E2B B7CA DBB8 02B2 58AC D84F
Subkey fingerprint: 0546 9FB8 5EAD 6589 B43D 41D3 D21D AD38 AF28 1C0B
========================================================================================================================
INSTALLATION:
Tails 4.11~rc1 was installed from Tails 4.10 to a USB drive using its USB image file and the "Restore Disk Image" function of Gnome Disks. This technique is described on the "Install from Linux" page of the Tails documentation. [1]
The installation took about two minutes to complete. After it was done Gnome Disks showed two partitions: "TAILS Partition 1: Tails 1.2 GB FAT" and "Free Space 63 GB."
This is some of the information that was displayed by Gnome Disks when the "TAILS Partition 1: Tails 1.2 GB FAT" partition was selected:
Partitioning: GUID Partition Table
Size: 1.2 GB (1,241,513,984 bytes)
Device: /dev/sdc1
UUID: /dev/sdc1
Partition Type: EFI System (System, Legacy BIOS Bootable, Read-only, Hidden, No Automount)
Contents: FAT (32-bit version) - Not Mounted
This is some of the information that was displayed by Gnome Disks when the "Free Space 63 GB" partition was selected:
Size: FAT (32-bit version) - Not Mounted
Device: /dev/sdc
Contents: Unallocated Space
========================================================================================================================
BOOT:
Tails was booted with Secure Boot enabled. It booted in the same amount of time as Tails 4.10.
To boot Tails 4.11~rc1 we inserted the USB drive containing the operating system, pressed the power button, pressed the function "fn" key related to boot selection, entered our BIOS administrator password, selected the USB drive, and pressed enter.
Then the screen showed:
Welcome to GRUB!
Then the Grub selection screen showed:
GNU Grub 2.04-8
* Tails
Tails (Troubleshooting mode)
Then the following text appeared:
Booting 'Tails'
Loading the Linux kernel...
Loading the initramfs...
Booting...
Then the same three-dot progress bar from earlier versions of Tails appeared, and, as usual, the dots were highlighted left to right.
Then the Welcome Screen appeared, and, after selecting "Start Tails," the operating system began after a few more seconds.
- -----------------------------------------------------------------------------------------------------------------------
The following system and disk space information was generated by the terminal on first boot using the default Welcome Screen options without any persistent volume, administrative password, or other configurations:
amnesia@amnesia:~$ uname -a
Linux amnesia 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 GNU/Linux
amnesia@amnesia:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 787M 9.7M 777M 2% /run
/dev/sdb1 8.0G 1.2G 6.9G 15% /lib/live/mount/medium
/dev/loop0 1.1G 1.1G 0 100% /lib/live/mount/rootfs/filesystem.squashfs
tmpfs 3.9G 16M 3.9G 1% /lib/live/mount/overlay
overlay 3.9G 16M 3.9G 1% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 3.9G 0 3.9G 0% /var/tmp
tmpfs 3.9G 74M 3.8G 2% /run/initramfs
tmpfs 3.9G 0 3.9G 0% /tmp
tmpfs 787M 48K 787M 1% /run/user/1000
========================================================================================================================
PERSISTENCE:
The "Configure Persistent Volume" application was used to create and configure the persistent volume. Every option to save files was selected. 51.62 GB of free space was created out of the 64 GB USB drive, which took about eighteen seconds to complete.
According to the "Configure Persistent Volume" application the persistent volume was located at /dev/sdb2, but the terminal didn't agree. Before restarting, it appeared at /dev/dm-0:
amnesia@amnesia:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 787M 9.7M 777M 2% /run
/dev/sdb1 8.0G 1.2G 6.9G 15% /lib/live/mount/medium
/dev/loop0 1.1G 1.1G 0 100% /lib/live/mount/rootfs/filesystem.squashfs
tmpfs 3.9G 16M 3.9G 1% /lib/live/mount/overlay
overlay 3.9G 16M 3.9G 1% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 3.9G 0 3.9G 0% /var/tmp
tmpfs 3.9G 74M 3.8G 2% /run/initramfs
tmpfs 3.9G 0 3.9G 0% /tmp
tmpfs 787M 52K 787M 1% /run/user/1000
/dev/dm-0 51G 53M 48G 1% /media/tails-persistence-setup/TailsData
After restarting it appeared at /dev/mapper/TailsData_unlocked:
amnesia@amnesia:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 787M 9.7M 777M 2% /run
/dev/sdb1 8.0G 1.2G 6.9G 15% /lib/live/mount/medium
/dev/loop0 1.1G 1.1G 0 100% /lib/live/mount/rootfs/filesystem.squashfs
tmpfs 3.9G 16M 3.9G 1% /lib/live/mount/overlay
overlay 3.9G 16M 3.9G 1% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 3.9G 0 3.9G 0% /var/tmp
tmpfs 3.9G 74M 3.8G 2% /run/initramfs
tmpfs 3.9G 4.0K 3.9G 1% /tmp
/dev/mapper/TailsData_unlocked 51G 55M 48G 1% /live/persistence/TailsData_unlocked
tmpfs 787M 44K 787M 1% /run/user/1000
========================================================================================================================
WELCOME SCREEN:
The persistent volume, Administrative Password, Unsafe Web Browser, and language selection features of the Welcome Screen all worked and persisted through multiple cold boots without problems.
========================================================================================================================
TOR:
This is the tor version in Tails 4.11~rc1:
amnesia@amnesia:~$ apt show tor
Package: tor
Version: 0.4.3.6-1~d10.buster+1
The first line of terminal output for the "tor" command read "Tor 0.4.3.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8."
========================================================================================================================
TOR BROWSER:
This is the Tor Browser version bundled with Tails 4.10:
9.5.4 (based on Mozilla Firefox 68.12.0esr) (64-bit)
This is the Tor Browser version bundled with Tails 4.11~rc1:
10.0a6 (based on Mozilla Firefox 78.2.0esr) (64-bit)
We encountered these four problems testing Tor Browser 10.0a6 running on Tails 4.11~rc1:
1. We visited multiple unrelated websites over the course of several days using both the Tor Browser 10.0a6 and Tor Browser 9.5.4. The same sites which never produced a Cloudflare captcha request on Tor Browser 9.5.4 always did responding to Tor Browser 10.0a6. Using "New Identity" or "New Tor Circuit for this Site" made no difference.
We consider this a serious problem effecting both the functionality and adoption of the Tor Browser and Tails.
2. Some embedded content which loaded automatically using Tor Browser 9.5.4 produced the following notice with Tor Browser 10.0a6:
"Tor Browser Can't Open This Page
To protect your security, [URL] will not allow Tor Browser to display the page if another site has embedded it. To see this page, you need to open it in a new window."
Then clicking "Open Site in New Window" opened a Cloudflare-protected link which rendered content without user intervention in a few seconds.
3. When we visited the internet utility website Arul John [2] the initial Tor Browser 10.0a6 resolution and size displayed was 640x480, but that quickly changed to either 998x499 or 999x500 even though the page hadn't been reloaded. The resolution and size given for Tor Browser 9.5.4 was a static 1000x700. This maybe a bug with the website or the Tor Browser 10.0a6.
4. After loading the JonDonym website using Tor Browser 10.0a6 it showed "Warning: Your IP address is neither anonymized by JonDonym nor by Tor." [3] However, the Tor Project's Tor Check site showed "Congratulations. This browser is configured to use Tor." [4] Finally, visiting the JonDonym website using Tor Browser 9.5.4 showed "You are using Tor," as did the Tor Check site. This maybe a problem with the JonDonym website rather than the Tor Browser.
- -----------------------------------------------------------------------------------------------------------------------
The following is a list of other test results and observations from Tor Browser 10.0a6 running on Tails 4.11~rc1:
1. All websites visited using onion ("hidden") services functioned.
2. An html file of bookmarks exported from Tor Browser 9.5.4 was imported into Tor Browser 10.0a6 without problems.
3. The homepage was changed from "Welcome to Tails!" to "Trying a testing version of Tails." [5]
4. Video-streaming websites worked.
5. Internet speed tests results showed Tor Browser 10.0a6 was roughly 20-40% faster than Tor Browser 9.5.4
6. The uBlock icon was visible. When visiting websites ads weren't displayed and the uBlock icon showed "a strictly positive number of blocked elements."
7. Samy Kamkar's evercookie [6] didn't persist once "New Identity" was used with uBlock disabled.
The created cookie showed:
userData mechanism: undefined
cookieData mechanism: 769
localData mechanism: 769
globalData mechanism: undefined
sessionData mechanism: 769
windowData mechanism: 769
etagData mechanism: 769
cacheData mechanism: 769
lsoData mechanism: undefined
slData mechanism: undefined
Then after "New Identity" was used "Click to rediscover cookies" showed:
pngData mechanism: undefined
etagData mechanism:
cacheData mechanism:
userData mechanism: undefined
cookieData mechanism: undefined
localData mechanism: null
globalData mechanism: undefined
sessionData mechanism: null
windowData mechanism: undefined
lsoData mechanism: undefined
slData mechanism: undefined
8. An extended DNS test showed no leakage. [7]
9. media.peerconnection.enabled was set to "false" in "about:config"
10.
https://net.ipcalf.com displayed:
ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1
11. Using the root terminal "apt" or "apropos" commands didn't show anything about the tor-browser package, which the terminal showed as present with the double-tab or "which" commands:
root@amnesia:~# apropos tor-browser
tor-browser: nothing appropriate.
root@amnesia:~# apt search tor-browser
Sorting... Done
Full Text Search... Done
root@amnesia:~# apt show tor-browser
N: Unable to locate package tor-browser
N: Unable to locate package tor-browser
E: No packages found
root@amnesia:~# tor-
tor-browser tor-instance-create tor-print-ed-signing-cert tor-resolve
tor-gencert tor-launcher tor-prompt
root@amnesia:~# which tor-browser
/usr/local/bin/tor-browser
========================================================================================================================
MANUAL TEST SUITE:
This is a list of tests we ran on Tails 4.11~rc1 largely derived from the "Manual Test Suite." [8]
1. WhisperBack 1.8.4 was used to send a test message and headers with a contact email address and its public OpenPGP key included, then printed "Your message has been sent."
2. APT:
amnesia@amnesia:~$ grep -r jenw7xbd6tf7vfhp.onion /etc/apt/sources.list*
/etc/apt/sources.list.d/tails.list:deb tor+
http://jenw7xbd6tf7vfhp.onion/ 4.11-rc1 main contrib
3. When online the "Tails documentation" desktop launcher opened the Tails Documentation website in the Tor Browser. [9] When offline the same launcher opened a copy of the entire Tails website, whose internal links worked well. [10]
4. The "systemctl --failed --all" command showed "0 loaded units listed" using either the root or standard terminal:
amnesia@amnesia:~$ systemctl --failed --all
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
5. This is the output of the "sudo journalctl -p 0..3" command:
root@amnesia:~# sudo journalctl -p 0..3
amnesia kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
amnesia kernel: radeon 0000:03:00.0: failed VCE resume (-110).
amnesia kernel: usb 2-5: device descriptor read/64, error -71
amnesia kernel: usb 2-5: device descriptor read/64, error -71
amnesia kernel: usb 2-5: device descriptor read/64, error -71
amnesia kernel: usb 2-5: device descriptor read/64, error -71
amnesia kernel: usb 2-5: device not accepting address 6, error -71
amnesia kernel: usb 2-5: device not accepting address 7, error -71
amnesia kernel: usb usb2-port5: unable to enumerate USB device
amnesia kernel: radeon 0000:03:00.0: failed VCE resume (-110).
amnesia spice-vdagent[5227]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
amnesia gdm-password][6502]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared
amnesia gdm-password][6502]: PAM adding faulty module: pam_gnome_keyring.so
amnesia kernel: radeon 0000:03:00.0: failed VCE resume (-110).
amnesia kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
amnesia kernel: firmware_class: See
https://wiki.debian.org/Firmware for information about missing firmware
amnesia spice-vdagent[9586]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
amnesia wpa_supplicant[3895]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlan0/drop_unicast_in_l2_multicast: No suc
amnesia wpa_supplicant[3895]: nl80211: Failed to set IPv4 unicast in multicast filter
amnesia wpa_supplicant[3895]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlan0/drop_unicast_in_l2_multicast: No suc
amnesia wpa_supplicant[3895]: nl80211: Failed to set IPv4 unicast in multicast filter
amnesia wpa_supplicant[3895]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlan0/drop_unicast_in_l2_multicast: No suc
amnesia wpa_supplicant[3895]: nl80211: Failed to set IPv4 unicast in multicast filter
amnesia gdm-session-worker.real[14493]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot o
amnesia gdm-session-worker.real[14493]: PAM adding faulty module: pam_gnome_keyring.so
amnesia kernel: radeon 0000:03:00.0: failed VCE resume (-110).
amnesia kernel: radeon 0000:03:00.0: failed VCE resume (-110).
amnesia kernel: tpm tpm0: tpm_try_transmit: send(): error -5
amnesia gdm-session-worker.real[16334]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot o
amnesia gdm-session-worker.real[16334]: PAM adding faulty module: pam_gnome_keyring.so
lines 1-31
6. The Tails Verification Extension running in the Tor Browser worked to verify both the USB and ISO images of Tails 4.10.
7. The Unsafe Web Browser worked as long as it was enabled in the Welcome Screen and there was an internet connection.
- - Trying to start it without enabling it in the Welcome Screen showed a popup which read:
"Error: The Unsafe Browser was not enabled in the Welcome Screen. To use the Unsafe Browser, restart Tails and enable the Unsafe Browser in the additional settings of the Welcome Screen. To always enable the Unsafe Browser, turn on the Welcome Screen feature of the Persistent Storage."
- - Trying to start it without an internet connection showed a popup which read:
"Error: No DNS server was obtained through DHCP or manually configured in NetworkManager."
- - Starting it with an internet connection showed a popup which read:
"Launch the Unsafe Browser? The Unsafe Browser is not anonymous and the websites that you visit can see your real IP address. Only use the Unsafe Browser to log in to a captive portal or browse trusted web pages on the local network."
8. Root access control worked. Tails was started, the persistent volume was unlocked, the persistent administrative password was subtracted from the welcome screen additional options, then the following tests were performed:
- - Root Terminal was started. The administrative password was entered. No root terminal opened and the screen read "Sorry, that didn't work. Please try again."
- - Terminal was started, then the "sudo su" command was attempted and failed after presenting an option to enter a password:
amnesia@amnesia:~$ sudo su
By default, the administration password is disabled for better security.
In order to perform administration tasks, you need to setup an administration password when starting Tails.
See the corresponding documentation:
https://tails.boum.org/administration_password/
[sudo] password for amnesia:
The administration password is disabled."
- - Terminal was started, then the "su" command was attempted and failed without an option to enter a password:
"amnesia@amnesia:~$ su
By default, the administration password is disabled for better security.
In order to perform administration tasks, you need to setup an administration password when starting Tails.
See the corresponding documentation:
https://tails.boum.org/administration_password/"
9. Tails was started using the "French - France (French-France)," ""Simplified Chinese - China," and Korean language options:
- - The problems listed on the Tails Gitlab persist [11].
- - French is the most localized, followed by Chinese, then, Korean.
- - In all instances DuckDuckGo was the default, pre-selected search plugin.
10. After turning on then off the "Settings > Universal Access > High Contrast" option the Trash icon on the desktop remained in black-and-white high contrast mode. Turning "High Contrast" on and off again failed to get it back to normal, but, did cause Gedit and Nautilus "Files" to freeze for thirty seconds each.
========================================================================================================================
REFERENCES:
[1] "Install from Linux"
https://tails.boum.org/install/linux/usb/index.en.html
[2] "Arul's utilities"
https://aruljohn.com
[3] "JonDonym"
https://ip-check.info
[4] "Tor Check"
https://check.torproject.org
[5] "Welcome to Tails!"
https://tails.boum.org/home/index.en.html
"Trying a testing version of Tails"
https://tails.boum.org/home/testing/index.en.html
[6] "evercookie"
https://samy.pl/evercookie
[7] "DNS Leak Test"
https://www.dnsleaktest.com
[8] "Manual test suite"
https://tails.boum.org/contribute/release_process/test
[9] "Tails Documentation"
https://tails.boum.org/doc/index.en.html
[10] "Tails" (Offline)
file:///usr/share/doc/tails/website/index.en.html
[11] "Automatic language -> keyboard selection is broken when selecting some languages"
https://gitlab.tails.boum.org/tails/tails/-/issues/12638
"Test that the on-screen keyboard works and its layout is correctly set"
https://gitlab.tails.boum.org/tails/tails/-/issues/10263
========================================================================================================================
CIRCLETOP OPENPGP KEY DETAILS:
Type: RSA
Size: 4096
ID: 5500303F
Fingerprint: D75B 048F 4789 A622 A297 E555 B552 E2BA 5500 303F
Format: ASCII-armored PGP key
Name: circletop-public-pgp-key.asc
SHA-256 checksum: e6a5acfb979e67b997e97e8d48d7748b091f8a7d9bfa3e3adbcd1a8bf6fb5fb1
