hello, can you give me more information about the bug?
which kernel do you run under woody when you create the encrypted device? can you submit the output of 'uname -a'? the same for sarge when it fails to setup/mount. you said, that even in a woody chroot, started from a sarge system, you're not able to access the encrypted device. this leads to the fact that the running kernel is responsible for the failture. my assumption is, that the 'serpent' cipher from 2.4 kernels is incompatible to the one from 2.6 kernels. in this case, the bug would be related to the linux kernel, not to the cryptsetup package. in any case, you used losetup all the time, so crypto loop from the kernel was used. cryptsetup uses dm-crypt. it is compatible with crypto loop as long as the same cipher is used, but so far i don't see where cryptsetup is used to produce the bug. the best would be, if you could give exact information about - the woody system you used to create the crypto loop device - the sarge system you used when mouunting the crypto loop device failed - the exact commands you used. i cannot even create the encrypted device in the way you did it: # losetup -e serpent -k 128 /dev/loop0 /dev/vg00/test Password: *password* ioctl: LOOP_SET_STATUS: Invalid argument ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
