Project Number Date
test_Tails_ISO_security-issues 2 24 Aug 2026, 14:05

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 12:16.174 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:24.294
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.172
When I start Tails from USB drive "old" with network unplugged 1:5.520
Then the boot device has safe access rights 2.744
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.764
After features/support/hooks.rb:108 0.062
Tags: @product
1:28.176
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login 50.005
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 25.396
And I take note of which tps features are available 7.622
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 4.196
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.266
Then Tails is running from USB drive "old" 0.238
And all tps features are active 8.220
When I write some files expected to persist 1.103
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.711
And I take note of which tps features are available 6.235
And I shutdown Tails and wait for the computer to power off 3.948
# 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.028
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.151
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.716
And I log in to a new session 13.032
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.577
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.085
Then the running Tails is installed on USB drive "to_upgrade" 19.274
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.109
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.688
Then all tps features from the old Tails version are active 1.220
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.528
And the expected persistent files created with the old Tails version are present in the filesystem 1.055
And all persistent directories from the old Tails version have safe access rights 1.805
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:56.330
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 22.557
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.029
And Tor is ready 12.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.783
Given I shutdown Tails and wait for the computer to power off 5.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.342
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.275
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.251
When the network is plugged 0.027
And Tor is ready 10.571
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.986
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.071
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.834
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.295
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.028
And Tor is ready 10.468
Then the Upgrader considers the system as up-to-date 0.098
# 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.517
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.328
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.212
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.617
After features/support/hooks.rb:339 1.043
After features/support/hooks.rb:108 0.000