Reinhard Tartler wrote: > Peter Klotz <peter.klotz@xxxxxx> 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. Hi, loading of dm_crypt is not cryptsetup job. Device-mapper has already autoloading of necessary target modules built in. You just need device-mapper core initialized (dm_mod kernel module loaded). It just "simply works" on default configuration: # lsmod Module Size Used by dm_mod 48656 0 # cryptsetup luksOpen /dev/sdb crypt Enter LUKS passphrase: key slot 0 unlocked. Command successful. # lsmod |grep dm_crypt dm_crypt 12836 1 crypto_blkcipher 15652 3 cbc,dm_crypt dm_mod 48656 2 dm_crypt > > I'm CC'ing the upstream mailing list. Do you guys have any idea how this > could be solved? This bug was originaly filed at > https://launchpad.net/bugs/267192 Is it reproducible in other system? If not, it is some bug in Ubuntu Live CD. Milan -- mbroz@xxxxxxxxxx --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
