You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When doing the LUKS container re-encryption, either by itself or as part of OEM factory reset, the new password(s) are displayed as plain text on screen and will stay there until the process is complete, which can take some time with a large drive that needs to be fully re-encrypted; this is fine when there is no chance of anyone seeing the screen in this time, but many people live together with others in the same space and in those cases it's inconvenient to have the secrets displayed for so long and have to cover the screen with a towel or similar.
After doing the re-encryption the user must sign all checksums again, but I didn't see this being communicated (maybe I missed it?). This should be part of the information given to the user or the user should be prompted to do it after the process completes (this is regarding LUKS re-encryption by itself, as I think OEM factory reset already does that).
Describe the solution you'd like
I would suggest clearing the screen at once (perhaps a warning about this and ask user confirmation; there is still the summary window anyway, though currently there's a bug about it).
Prompt the user to sign all files and checksums after doing a LUKS-container re-encryption.
Describe alternatives you've considered
Perhaps having the re-encryption process "push" the text up (i.e. insert newlines) periodically, e.g. once every 10 seconds so that the secrets will all disappear from screen in 2 or 3 minutes.
Put some info on screen telling user to sign checksums after LUKS container re-encryption.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: