Hi Jonas,
please provide more information about your dm-crypt setup. which command
do you use in order to unlock the dm-crypt device? is it a LUKS
encrypted device, or do you use plain dm-crypt?
Yes, I am using plain dm-crypt:
cryptsetup -d ${KEYFILE} create container1 /dev/loop1
i guess that you use plain dm-crypt and didn't set cipher, hash and hash
size in the crypttab, thus running into issues with the changed defaults.
Thanks for the advice. I am now able to mount the container using the
latest packages using:
cryptsetup -c aes-cbc-plain -h ripemd160 -s 256 -d ${KEYFILE}
create container1 /dev/loop1
Just the cipher seemed to do the trick but I expect the other options
will protect me from future changes. I should probably start using
crypttab - I didn't know what it was before.
Thanks again
David
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
