Milan Broz writes:
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
On Wed, Sep 10, 2008 at 04:27:41PM +0200, Reinhard Tartler wrote:
Milan Broz writes:
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
LVM2 tackles this by doing the library equivalent of 'dmsetup targets'
and if the target is not listed it tries modprobe then checks again.
Alasdair
--
[EMAIL PROTECTED]
--
Misleading cryptsetup error message
https://bugs.launchpad.net/bugs/267192
You received this bug notification because you
Public bug reported:
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:
[EMAIL PROTECTED]:~# cryptsetup
Peter Klotz [EMAIL PROTECTED] writes:
[EMAIL PROTECTED]:~# 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
