[Bug 1546144] Comment bridged from LTC Bugzilla

bugproxy bugproxy at us.ibm.com
Fri Feb 19 10:19:29 UTC 2016


------- Comment From ROESCH3 at de.ibm.com 2016-02-19 05:14 EDT-------
(In reply to comment #7)
> 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 guess this would be an improvement, yes. It would still be more
obvious if you had "enter passphrase" in there somewhere. But maybe this
is only my opinion :-)

> 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.

OK understood. But should the encryption support (LUKS and ecryptfs)
then not be removed completely or only be a hidden option?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1546144

Title:
  LUKS Unlock prompt should be reworded

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Michael Roesch <ROESCH3 at de.ibm.com> - 2016-02-16 04:08:05 ==
  When using LUKS-encrypted partitions, it should be more obvious that the system wants you to enter a password to unlock the respective partition. The current message is misleading. 

  Current message:

  Begin: Running /scripts/init-premount ... done.   
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   
  Please unlock disk dasda2_crypt

  I suggest the following change:

  Please enter passphrase to unlock disk dasda2_crypt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1546144/+subscriptions



More information about the foundations-bugs mailing list