[Bug 1047384] Re: System Encryption Password set before setting keyboard locale

Lars J. Nielsen lars.j.nielsen at gmail.com
Thu Nov 28 23:06:13 UTC 2013


James Bennet (#10):
"By the way, this can be triaged by doing the following on the next boot (if you could get access, but it was just not the key you expected i.e. in my case)

cryptsetup -y luksAddKey /dev/sda[x]
sudo cryptsetup luksRemoveKey /dev/sda[x] 0

Check with:

sudo cryptsetup luksDump /dev/sda5"

How is this supposed to be read?
Do I replace [x] with a number and if so, which one? My fstab doesn't list drives like that.

I'll echo the others in asking how this is only medium importance when
it is this annoying to fix for users and has been in several releases
(I'm on 13.10 desktop). And the arguments about it being faster to
install when you can do some of the work in the background while the
user fills in things is not a good one when for many of the security
conscious users it means another reinstallation or more to make it work,
maybe even resulting in some giving up enabling the feature or finding
another distribution instead. Ubuntu is supposed to be one of the easy
distributions, user confusing errors like this one are not acceptable
for more than one release, if even that.

I'm tired of reinstalling because I forget about this (twice now), and
because of silly things like enabling encryption of the home directory
and then wanting to change user name (not just the displayed name but
all the uses of the username) and it being easier to reinstall because
the GUI tool doesn't do all that and there is no good documentation on
how to do it manually for encrypted home directories.

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

Title:
  System Encryption Password set before setting keyboard locale

Status in “ubiquity” package in Ubuntu:
  Triaged
Status in “ubiquity” source package in Trusty:
  Triaged

Bug description:
  Ubuntu 12.10

  When installing my system, I selected to encrypt access to my system.
  This prompted me to enter a password. I entered a password with a #
  symbol in it, however due to using an english keyboard, this would not
  have been correctly recorded as a #, but as a ' instead - leading it
  to refuse my password when booting.

  I tested this both connected to and not connected to the internet.

  It seems that at the point of entering the password during the
  installer, the keyboard layout was set to en_US. Therefore, when
  booting and having the locale as en_GB - it didn't correctly work.

  I tried this with the @ symbol, which when entered was accepted on
  boot by hitting shift+2 (american combination)

  I also tried this by entering a password with a £ sign (shift 3 on UK
  keyboard - which would be a # on a US keyboard)

  When entering password on boot, entering the password with the # key
  rather than the £ key worked.

  In summary - when entering password for encrypting system, keyboard is
  set as a US keyboard layout, which differs from that when booting to
  enter the password if it is changed in a later step.

  Proposed solution: Move the keyboard selection / Locale Setup before
  any input boxes. (espescially those where you can't see the contents
  of them!)

  <http://goo.gl/YwIcT>: "The “Keyboard layout” screen should appear
  immediately before whichever is the first keyboard-requiring step."

  <http://goo.gl/PSaUz>: "Whenever “Encrypt the new Ubuntu installation
  for security” is checked, the caption 'You’ll choose a security key in
  just a moment.' should be sensitive. 'Choose a security key' is a
  keyboard-requiring step, so that typing the security key works as
  expected."

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



More information about the foundations-bugs mailing list