Project Number Date
test_Tails_ISO_disclose-security-issues-post-release 2 27 May 2026, 18:38

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.542 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:15.467
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.190
When I start Tails from USB drive "old" with network unplugged 56.150
Then the boot device has safe access rights 3.282
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:335 1.764
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.184
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 55.957
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 25.539
And I take note of which tps features are available 0.397
Then a Tails persistence partition exists on USB drive "old" 0.702
And I shutdown Tails and wait for the computer to power off 8.243
After features/support/hooks.rb:335 0.235
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.422
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.143
Then Tails is running from USB drive "old" 0.216
And all tps features are active 1.323
When I write some files expected to persist 1.567
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 1.960
And I take note of which tps features are available 0.236
And I shutdown Tails and wait for the computer to power off 8.194
# 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.200
After features/support/hooks.rb:335 0.403
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.407
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 without a persistent partition and stopped at Tails Greeter's login screen 8.379
And I log in to a new session 12.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.361
Then the running Tails is installed on USB drive "to_upgrade" 14.751
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:335 2.479
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.906
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.451
Then all tps features from the old Tails version are active 1.243
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.119
And all persistent directories from the old Tails version have safe access rights 2.047
After features/support/hooks.rb:335 0.827
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:48.239
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.022
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.512
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.030
And Tor is ready 12.538
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.930
Given I shutdown Tails and wait for the computer to power off 10.974
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.349
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.204
And the file system changes introduced in version 6.2~testoverlayfs are present 0.483
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.227
# 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.246
When the network is plugged 0.018
And Tor is ready 11.489
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.527
Given I shutdown Tails and wait for the computer to power off 8.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.147
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.012
And Tor is ready 11.474
Then the Upgrader considers the system as up-to-date 10.572
# 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 4.247
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:335 0.944
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
25.913
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.612
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.021
And Tor is ready 15.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.856
After features/support/hooks.rb:335 0.865
After features/support/hooks.rb:104 0.000