Bug#315693: [Pkg-cryptsetup-devel] Bug#315693: need more information regarding [Cryptoloop filesystem incompatible between woody and sarge]

[Jonas Meurer]

On 20/08/2006 To 315693 at bugs.debian.org wrote:
> 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

ok, this was due to a stupid fault on my side. i missed to load the
'cryptoloop' module before running 'losetup -e serpent'.

but according to the commands you used, you didn't setup the loopback
device before mounting the encrypted device.

if you set up /dev/sda1 as /dev/loop0 once, you need to redo that before
mounting /dev/sda1.

/dev/sda1 will be the plain encrypted device - and only the loopback
device, set up exactly like the first time - is able to be mounted.

i.e.:

in woody:
# losetup -e serpent -k 128 /dev/loop0 /dev/sda1
# mkfs.ext2 /dev/loop0
[ fill /dev/loop0 with data ]

in sarge:
# losetup -e serpent -k 128 /dev/loop0 /dev/sda1
# mount -t ext2 /dev/loop0 /mnt/

this one for sure doesn't work:
# mount -t ext2 /dev/sda1 /mnt/

Dominik, please give us more information about how to reproduce the bug.

...
 jonas