Project Number Date
test_Tails_ISO_security-issues 3 25 Aug 2026, 13:56

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:31.887 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:10.113
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.703
When I start Tails from USB drive "old" with network unplugged 52.172
Then the boot device has safe access rights 2.498
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.160
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.496
After features/support/hooks.rb:108 0.055
Tags: @product
1:26.213
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 50.141
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 24.160
And I take note of which tps features are available 6.962
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 4.147
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.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:2.006
Then Tails is running from USB drive "old" 0.261
And all tps features are active 8.834
When I write some files expected to persist 1.054
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.654
And I take note of which tps features are available 6.554
And I shutdown Tails and wait for the computer to power off 4.185
# 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.551
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.730
And I log in to a new session 11.953
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.981
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.548
Then the running Tails is installed on USB drive "to_upgrade" 18.707
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 3.660
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.189
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.027
Then all tps features from the old Tails version are active 1.324
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.156
And all persistent directories from the old Tails version have safe access rights 2.084
After features/support/hooks.rb:339 0.476
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:34.486
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 8.539
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.031
And Tor is ready 13.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.324
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.514
Given I shutdown Tails and wait for the computer to power off 5.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.025
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.190
When the network is plugged 0.036
And Tor is ready 10.677
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.076
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.920
Given I shutdown Tails and wait for the computer to power off 4.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.526
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.611
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.028
And Tor is ready 10.262
Then the Upgrader considers the system as up-to-date 0.088
# 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.508
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.878
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.591
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.977
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.000