*** This bug is a duplicate of bug 62751 *** I think it is a problem with cryptsetup. I have a setup where a partition on my harddrive is encrypted with a key. This key is saved in a file, and encrypted with openssl.
I have this on two laptops, so when the first laptop was reinstalled with Edgy, I found the problem, and made a new encrypted partition, which works just fine. When I came to installing edgy on the other laptop, I wrote this info down: 1. The unencrypted key 2. The first ten lines from a hexdump of the encrypted partition 3. The first ten lines from a hexdump of the unencrypted partition “mounted” on /dev/mapper/_dev_hda3 through cryptsetup After installation of Edgy and cryptsetup, I did the same as above: 1. The unencrypted key was the same, which must indicate that openssl works like in Dapper 2. The first ten hexdump lines of the encrypted partition was the same, so the partition might not have changed (I should have made a MD5SUM of the entire partition, but I am quite sure it is unchanged.) 3. Then I made a hexdump of /dev/mapper/_dev_hda3 after mounting it with cryptsetup, which wasn’t like the one from the Dapper installation. Cryptsetup didn’t complain about anything, but my guess is that the version of cryptsetup in Edgy don’t work the same way as in Dapper. I might be wrong, but I can’t see what else should cause this? Regards Christoffer -- Doesn't detect cryptdisks https://launchpad.net/bugs/62406 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
