On Sun, Jan 07, 2007 at 01:53:08PM +0100, Marcus Better wrote:
David Härdeman wrote:
That would mean that the fstype binary from klibc-utils doesn't
recognize the decrypted device as a suspend image. Could you please
follow the steps in bugs.debian.org/398302
Ok, I played a little with it and think I have found the bug. The crypto
script invokes cryptsetup with "-h sha256". If I remove that option (but
leave -c and -s as they are), I get a correct fstype (suspend).
On the other hand, it seems that /lib/cryptsetup/cryptdisks.functions creates
the mapping without the -h option, and the default hash algorithm is
ripemd160 according to the man page.
Cool, could you provide me with the following two files:
/etc/crypttab
/conf/conf.d/cryptroot from the initramfs image, you can get it from a
running system by doing:
([EMAIL PROTECTED]:~)$ mkdir test
([EMAIL PROTECTED]:~)$ cd test
([EMAIL PROTECTED]:~/test)$ cp /boot/initrd.img-2.6.19+1 ./image.gz
([EMAIL PROTECTED]:~/test)$ gunzip image.gz
([EMAIL PROTECTED]:~/test)$ cpio -i < image
20301 blocks
([EMAIL PROTECTED]:~/test)$ cat conf/conf.d/cryptroot
Also, as a workaround, try specifying hash=ripemd160 in the relevant
entry in the /etc/crypttab file and regenerate the initramfs image.
--
David Härdeman
