Improve user experience when wiping memory at shutdown
Presumably, displaying a nice splash screen instead of low-level details while wiping memory would improve user experience.
#6 Updated by Anonymous over 5 years ago
These are remarks by the UX experts, as collected after the 1st Tails UX session:
Tails Shutdown: the user shuts down Tails by removing the USB key. A
black screen appears with some messages regarding sensitive data
exposure and many lines of hard-to-read status messages. When asked what
this screen means the user says that it's basically telling you that
it's cleaning up the sensitive data and that she doesn't really read or
understand what the rest of the status message means.
Observations: the function of this screen probably wouldn't be clear
to a first-time user and even to an expert user it doesn't mean much in
its current state. At first glance it looks like a system crash screen,
more alarming than reassuring.
Recommendations: it seems that the objective of this screen would be
to a) inform the user that her data is being wiped from memory and b) to
conceal the user's activity in case of an abrupt shutdown prompted by a
physical confidentiality threat (someone entering the room for example).
You could for example mask this shutdown screen as a common Windows or
OSX shutdown process, with a progress bar / wheel that informs the user
that the "cache is being cleared", "the system is shutting down" or
whatever other message is more appropriate.
#7 Updated by intrigeri over 5 years ago
- we currently disable running plymouth at shutdown time (
- it's probably possible to run plymouth at shutdown time, and have some (existing or new) initscript send a message to plymouth to have it display graphically the message we want
- emergency shutdown handles things a bit differently:
chvt 1; not sure if that one can easily be converted to using plymouth as well. But improving things for regular (non-emergency) shutdown first would be a first great step.
#13 Updated by sajolida over 3 years ago
People think that "this is the fundamental functionality of Tails":
We have a serious mental model issue here :)
#15 Updated by intrigeri almost 3 years ago
- Status changed from Confirmed to In Progress
- Assignee set to sajolida
- QA Check set to Ready for QA
- Feature Branch set to bugfix/12354-drop-kexec-memory-wipe
Once our fix for #12354 is merged (likely in 3.0~rc1), IMO there's nothing to improve here as the machine shuts down in very few seconds:
- with emergency shutdown (unplugging the boot medium), I have barely time to notice the debugging messages that are displayed on the screen; we could hide them once we are confident the new implementation is reliable
- with normal shutdown (shutdown button in the GNOME top-right menu) I see no message at all, just a black screen for a couple seconds
But I'd like sajolida's opinion on this one, so please test either with 3.0~rc1 once it's out, or with a nightly build from the feature branch (until it's merged), or with a nightly build from feature/stretch (between the time my branch is merged and the release of 3.0~rc1). Alternatively, if you have no time, let me know and I'll test on a couple more machines before closing this ticket as resolved.