[pkg-cryptsetup-devel] Bug#541835: Bug#541835: cryptsetup: unclear kernel requirements

[Jonas Meurer]

hey,

On 16/08/2009 Celejar wrote:
> ~# cryptsetup luksDump /dev/hda4
> 
> LUKS header information for /dev/hda4
> 
> Version:       	1
> Cipher name:   	aes
> Cipher mode:   	cbc-essiv:sha256

so you at least need aes, cbc and sha256 kernel modules.

> > # dmsetup targets
> > # lsmod
> > # cat /proc/crypto

the output of these commands would only be interesting when running the
kernel that causes cryptsetup to fail.

> Note: these are from a kernel that handles the LUKS volume successfully
> (2.6.31-rc6 from mainline git repo).  Getting the output from one of my
> non-working kernels would be more difficult, since the entire system
> (except /boot) is on LVM on top of the LUKS volume, and my kernels'
> fail during the initrds' (made by initramfs-tools) attempts to unlock
> the LUKS volume.  I have tried to explore the problem using the
> 'break=mount' kernel parameter, but even after manually modprobing the
> aes, cbc, blkcipher, dm-crypt modules, the kernel can't unlock the
> volume.

all of the above programs (cryptsetup, dmsetup, lsmod and cat) should be
available within the initramfs, so executing them from the emergency
shell shouldn't be a problem. you could pipe them into some file on
/boot after mounting it.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090816/7d50a9de/attachment.pgp>