Package: cryptsetup Version: 20050111-4 Severity: important /usr/share/doc/cryptsetup/CryptoRoot.HowTo recommends the cipher aes-cbc-essiv:sha256 . This leads to a chicken<->egg failure (for me). Attempts to boot into the encrypted root fail due to a missing module/s(?) even though all the steps in CryptoRoot.HowTo have been followed.
I have a simple setup: hda2 - boot (unencrypted) hda3 - root (encrypted) I suspect that `mkinitrd -o /boot/initrd.img.blah` isn't including all of the required files. I'm a bit stuck, let me know what more you'd like to know. Cheers, James. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Versions of packages cryptsetup depends on: ii dmsetup 2:1.01.04-2 The Linux Kernel Device Mapper use ii libc6 2.3.5-8 GNU C Library: Shared libraries an ii libdevmapper1.01 2:1.01.04-2 The Linux Kernel Device Mapper use ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime libr ii libgpg-error0 1.1-4 library for common error values an ii libpopt0 1.7-5 lib for parsing cmdline parameters cryptsetup recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]