Dirk Heinrichs wrote:
> You don't need to, cryptsetup-luks is cryptsetup + LUKS features. Just
> unmerge cryptsetup and emerge cryptsetup-luks.
The problem is that cryptsetup and cryptsetup-luks are indeed
*incompatible*. I'm also having problems with pam_mount. ("you must specify
the filesystem type")
Since pam_mount doesn't work I tried calling cryptsetup manually. With the
old cryptsetup-0.1-r3 I can mount my home partition without problems:
# echo $KEY | cryptsetup -c aes-cbc-plain -h ripemd160 -s 256 \
test /dev/loop5
# mount /dev/mapper/test /home/gilles
# ls -l
[...]
# umount /home/gilles
# cryptsetup remove test
But after upgrading to cryptsetup-luks-1.0.3-r2 the _exact same commands_
result in a broken mapping:
# echo $KEY | cryptsetup -c aes-cbc-plain -h ripemd160 -s 256 \
test /dev/loop5
# mount /dev/mapper/test /home/gilles
mount: you must specify the filesystem type
When I revert to plain cryptsetup everything is normal again.
I hope this incompatibility can be worked around someway.
Regards,
Gilles
---------------------------------------------------------------------
- http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
