crypt setup requires slow typing

Bug #442141 reported by Patrik Nilsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cryptsetup

When a password is entered for crypt setup to decrypt the hard disks at start up you need to type the password slower than needed.

If you press two different keys after each other rather fast, less than a second between them, crypt setup begins to repeat the second key as it were pressed for a longer time.

patrik@ubuntu:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

patrik@ubuntu:~$ apt-cache policy cryptsetup
cryptsetup:
  Installed: 2:1.0.6-7ubuntu7
  Candidate: 2:1.0.6-7ubuntu7
  Version table:
 *** 2:1.0.6-7ubuntu7 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Reinhard Tartler (siretart) wrote :

please attach your /etc/crypttab and /etc/fstab files.

do you enter the passphrase in text mode or graphically via usplash?

Changed in cryptsetup (Ubuntu):
status: New → Incomplete
Revision history for this message
Patrik Nilsson (nipatriknilsson) wrote :

I enter in text mode.

/etc/crypttab:
sda1_crypt /dev/disk/by-uuid/f264b4b2-4ce5-4a69-9bd5-8d4c13c999a1 none luks

/etc/fstab:
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/mapper/ubuntu-root during installation
UUID=b981ed74-c989-4cdf-be7a-e1605ccbdf4a / ext3 relatime,errors=remount-ro 0 1
# /boot was on /dev/sda5 during installation
UUID=6d9a2b5e-3a8e-4166-be2e-144704bbd3dd /boot ext2 relatime 0 2
# swap was on /dev/mapper/ubuntu-swap_1 during installation
UUID=2224bcb5-aa78-481b-8ed9-5c3182d4afd3 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/scd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

Luke Faraone (lfaraone)
Changed in cryptsetup (Ubuntu):
status: Incomplete → New
Revision history for this message
mejo (jonas-freesources) wrote :

i strongly believe that this is an invalid bugreport. several people i know, me included,
do type their password a lot faster than one letter per second. we never discovered
such behaviour.
how do you know that the key is repeated? i shouln't see your input on the prompt.
or did you debug it properly?

maybe your keyboard is broken or you misstyped the password or something else.

Changed in cryptsetup (Ubuntu):
status: New → Invalid
Revision history for this message
Patrik Nilsson (nipatriknilsson) wrote :

mejo,

Most probably you are right, that it is an invalid bug report. After I reinstalled Ubuntu just a few days ago many issues which I've reported as bugs actually has appeared to be upgrade issues or issues of unknown heritage.

(I formatted the hard disks and installed Ubuntu Alternate 9.10.)

Revision history for this message
Patrik Nilsson (nipatriknilsson) wrote :

I open this bug again since it is still there.

Too give an even clearer description of the bug:

If I have a password like "abcdefghijkklmnoppqrstuvwxyz", and I type the password fast, I need to slow down the typing of "kk" and "pp", otherwise "kk" becomes "kkkk", and "pp" "pppp". In the Ubuntu system I have enabled "bounce keys", "slow keys", and changed "repeat keys", so it suits my typing behavior.

Is this possible to do here too?

Changed in cryptsetup (Ubuntu):
status: Invalid → New
Changed in cryptsetup (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

"incomplete" means the developers are waiting for more information from the bug submitter. Setting back to 'new'.

Changed in cryptsetup (Ubuntu):
status: Incomplete → New
Changed in cryptsetup (Ubuntu):
status: New → Invalid
Revision history for this message
Patrik Nilsson (nipatriknilsson) wrote :

Sorry, I meant it was a bug not to care of. At the moment I don't know how this "bug" can be programmed so it disappears. Until then it is a not-care-of-bug.

btw. Maybe instead of dots, writing how many chars you have typed. You will quickly learn what character i.e. 5 is and you'll quickly notice if anything is typed in the wrong way.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.