It really is unlock, as one can use, if configured: * remote unlocking via ssh * keyfile / hardware tokens to unlock (a secret stored in a file on a drive) * execute arbitrary script to unlock (e.g. to use TPM, smartcards, U2F, OTP, multi-factor, etc...)
In previous releases we also listed the full UUID of the partition to unlock, which has been dropped some time back as being essentially unrecognizable to the user. I'm not sure new wording is that much better. Maybe adding a training colon would help: with possibly showing the cursor too? (not sure, but cursor maybe especially disabled). I do appreciate testing LUKS encrypted volumes on s390x, however it is only a protection for physically insecure devices. I am struggling to identify a usecase in which mainframe and mainframe storage has zero physical security to access it. On desktops, we use plymouth, and thus no boot messages are shown and the full screen is taken with a prompt for password. There is no video / splash available for s390x over serial console during boot. ** Changed in: cryptsetup (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546144 Title: LUKS Unlock prompt should be reworded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1546144/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
