Project Number Date
test_Tails_ISO_disclose-security-issues-post-release 3 29 May 2026, 19:00

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:20.894 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:9.091
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 12.946
When I start Tails from USB drive "old" with network unplugged 51.851
Then the boot device has safe access rights 2.532
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:335 3.499
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.935
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.662
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 24.213
And I take note of which tps features are available 0.328
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 7.958
After features/support/hooks.rb:335 0.467
After features/support/hooks.rb:104 0.006
Tags: @product
1:20.182
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.750
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.007
When I write some files expected to persist 1.162
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.870
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 2.665
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.765
After features/support/hooks.rb:335 0.112
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.064
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.421
And I log in to a new session 12.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.223
Then the running Tails is installed on USB drive "to_upgrade" 14.702
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:335 2.224
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.326
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.601
Then all tps features from the old Tails version are active 0.960
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.336
And the expected persistent files created with the old Tails version are present in the filesystem 1.255
And all persistent directories from the old Tails version have safe access rights 1.867
After features/support/hooks.rb:335 0.914
After features/support/hooks.rb:104 0.007
3:49.301
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.210
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.017
And Tor is ready 12.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.215
Given I shutdown Tails and wait for the computer to power off 9.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.049
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.014
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.014
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.918
Given I shutdown Tails and wait for the computer to power off 7.924
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.526
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.015
And Tor is ready 19.593
Then the Upgrader considers the system as up-to-date 10.508
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 3.769
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:335 1.099
After features/support/hooks.rb:104 0.010
20.993
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.488
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.598
After features/support/hooks.rb:335 0.744
After features/support/hooks.rb:104 0.000