There was a request to test this in 8.10. I ran into it and then found this thread. (BTW, am I supposed to clone this on some other thread that concernts 8.10/2.6.27.11?)
Here is my info: // Various places recomends loading modules manually hence, just to ensure r...@nowhere:~# modprobe dm-mod r...@nowhere:~# modprobe dm-crypt //This is the problem section, I intend to encrypt the entire partition sda3 (intended for /home) r...@nowhere:~# cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/sda3 WARNING! ======== This will overwrite data on /dev/sda3 irrevocably. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: Command failed: Failed to setup dm-crypt key mapping. Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/sda3 contains at least 258 sectors //The device /dev/sda3 is a partition that is roughly 100Gb so the sectors should be sufficient, remains the kernel support, but that seems to be in order: r...@nowhere:~# lsmod | egrep 'aes|dm' aes_x86_64 16384 2 aes_generic 36392 1 aes_x86_64 dm_crypt 22792 1 crypto_blkcipher 27780 3 cbc,dm_crypt dm_mod 72944 3 dm_crypt r...@nowhere:~# cat /proc/crypto | grep name name : cbc(blowfish) name : cbc(blowfish) name : blowfish name : sha256 name : sha224 name : cbc(aes) name : cbc(aes) name : aes name : aes name : md5 //Whats really annoying is that I've been able to set up and map a partition for swap on the very same machine: r...@nowhere:~# cat /proc/swaps Filename Type Size Used Priority /dev/mapper/cryptoswap partition 5855652 0 -1 r...@nowhere:~# cryptsetup status cryptoswap /dev/mapper/cryptoswap is active: cipher: aes-cbc-essiv:sha256 keysize: 256 bits device: /dev/sda5 offset: 0 sectors size: 11711322 sectors mode: read/write r...@nowhere:~# ls /dev/mapper/ control cryptoswap //Just some version info r...@nowhere:~# cryptsetup --version cryptsetup 1.0.6 r...@nowhere:~# uname -a Linux nowhere 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux What is really embarrasing is that this is a fresh install that I made at work after failing to upgrade a Fedora installation. Incidently I made some rather discrediting statments about Fedora in general and yum in particular to my colleagues before making the transition.... -I need to get this working, is not an understatement. Thanks in advance -- cryptsetup / LUKS won't work https://bugs.launchpad.net/bugs/58102 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
