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

[Jonas Meurer]

hello,

On 16/08/2009 Celejar wrote:
> This is not really a bug, but it's at least a request for better documentation.
> 
> I have a standard LUKS volume (created by the Debian installer), using
> aes-cbc-essiv:sha_256.  While stock Debian kernels as well as ones that I build
> based on the stock config handle it fine, my 'lean' kernel configurations
> choke as follows:
> 
> table:254:0:	error allocating crypto tfm
> ioctl:		error adding target to table
> ioctl:		device doesn't appear to be in the dev hash table
> Command failed: failed to setup dm-crypt key mapping for device /dev/hda4
> Check that kernel supports aes-cbc-essiv:sha_256 cipher
> 
> I have googled extensively, and this message apparently usually indicates that
> kernel support for the appropriate cipher / hash is not available, but I've
> checked, double-checked, and racked my brains to figure out what I could
> possibly be missing, to no avail.  aes_generic.ko, cbc.ko, crypto_blkcipher.ko,
> sha256_generic.ko, dm-crypt.ko, dm-mod.ko are all there.
> 
> I've obviously disabled something that cryptsetup needs, but what?  Google
> turns up nothing current and useful.

please paste the output of the following commands:
# cryptsetup luksDump /dev/hda4
# dmsetup targets
# lsmod
# cat /proc/crypto

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/8755cff2/attachment.pgp>