https://bugzilla.novell.com/show_bug.cgi?id=332095#c8
Dale Peters II
Well, you are free to not believe me and make your own experience. The problem is not the decryption itself but the IV generation method. Choosing the wrong one results in subtle changes.
Old images really do work, this one is from 8.1: # losetup /dev/loop0 oldimg # cryptsetup --hash ripemd160:20 --cipher twofish-cbc-null --key-size 192 create fff /dev/loop0 Enter passphrase: # mount /dev/mapper/fff /mnt/ # cat /mnt/motd Have a lot of fun...
Doing this would only address part of the problem: mounting an image that has already been created. However, doing these steps doesn't exactly address my issue (and the reason why I initially reported--and reopened--this bug). I was trying to initialize an encrypted, loopback filesytem via the following steps: dd if=~/linux-2.6.22.5-31.tbz of=~/rb bs=1k skip=321 count=2k losetup -e aes -k 2048 `losetup -f` ~/rb losetup -a mkfs -t ext3 `losetup -a | cut -d ":" -f 1` My issue is the second command fails (which the fourth one demonstrates), and this prevents me from being able to format the encrypted, loopback filesystem. So, we know that something isn't functioning correctly with losetup. Yet, until a few minutes ago, I hadn't tested to see if loopback filesystem support worked for non-encrypted filesystems. Here are the steps for my second test: sshfs root@172.16.0.6:/mnt/sdc1 /mnt/tmp mount -o loop,ro /mnt/tmp/stage2.img /mnt/jaz ls /mnt/jaz This worked just fine. Now let's see what happens if I try to create a non-encrypted, loopback filesystem via the following steps: dd if=/dev/zero of=~/rb bs=1k count=2k losetup `losetup -f` ~/rb losetup -a mkfs -t ext3 `losetup -a | cut -d ":" -f 1` mount `losetup -a | cut -d ":" -f 1` /mnt/tmp ls /mnt/tmp This worked just fine too. So, it's definitely an issue with the crypto-code portion of the losetup codebase. If losetup is considered legacy, then what else should we use for creating (and mounting [which I believe invokes the losetup code]) loopback filesystems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.