Misleading cryptsetup error message
Bug #267192 reported by
Peter Klotz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: cryptsetup
Ubuntu 8.10 Alpha 5, i386:
The following steps result in a misleading cryptsetup error message:
* Boot from LiveCD
* Become root: sudo su -
* Install cryptsetup: apt-get cryptsetup
* Open a LUKS device:
root@ubuntu:~# cryptsetup luksOpen /dev/sdb1 crypt_rally2
Enter LUKS passphrase:
Command failed: No key available with this passphrase.
Actually the supplied password was correct but kernel module dm_crypt is not loaded in this scenario.
* modprobe dm_crypt
root@ubuntu:~# cryptsetup luksOpen /dev/sdb1 crypt_rally2
Enter LUKS passphrase:
key slot 1 unlocked.
Command successful.
Maybe there is a chance to give the user a hint what is really going wrong.
Changed in cryptsetup: | |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
Peter Klotz <email address hidden> writes:
> root@ubuntu:~# cryptsetup luksOpen /dev/sdb1 crypt_rally2
> Enter LUKS passphrase:
> Command failed: No key available with this passphrase.
>
> Actually the supplied password was correct but kernel module dm_crypt
> is not loaded in this scenario.
After looking into the code (luks/keymanage.c) this is not something
easy to add. Checking for the module is not an option either, because
the kernel might have support for dm-crypt compiled in.
I'm CC'ing the upstream mailing list. Do you guys have any idea how this /launchpad. net/bugs/ 267192
could be solved? This bug was originaly filed at
https:/
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4