Project Number Date
test_Tails_ISO_security-issues 1 24 Aug 2026, 13:11

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:51.453 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.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.813
When I start Tails from USB drive "old" with network unplugged 51.076
Then the boot device has safe access rights 2.607
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:339 1.814
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.181
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 51.547
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 23.350
And I take note of which tps features are available 6.599
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 2.831
After features/support/hooks.rb:339 0.221
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.600
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.390
Then Tails is running from USB drive "old" 0.250
And all tps features are active 7.660
When I write some files expected to persist 1.251
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 6.726
And I shutdown Tails and wait for the computer to power off 5.105
# 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" 12.628
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.007
Tags: @product
2:17.449
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.882
And I log in to a new session 14.071
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.191
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.750
Then the running Tails is installed on USB drive "to_upgrade" 19.644
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.890
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.159
Then all tps features from the old Tails version are active 1.220
And Tails is running from USB drive "to_upgrade" 0.176
And the boot device has safe access rights 2.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.120
And all persistent directories from the old Tails version have safe access rights 2.301
After features/support/hooks.rb:339 0.648
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:45.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.883
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.284
When the network is plugged 0.027
And Tor is ready 13.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.833
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.028
Given I shutdown Tails and wait for the computer to power off 5.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.163
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.181
When the network is plugged 0.025
And Tor is ready 10.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.956
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.185
Given I shutdown Tails and wait for the computer to power off 5.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.680
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.636
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.022
And Tor is ready 10.824
Then the Upgrader considers the system as up-to-date 0.115
# 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.993
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.800
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.006
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.000