Package: loop-aes-utils Version: 2.12a-3 Followup-For: Bug #309977 Thanks for your fast response! I tried the following as you mentioned:
> (It MAY be possible to avoid re-encryption by editing your keyfile and > "converting" it to v2 mode. I haven't tried this, but if you feel like > having an adventure ;-) you could try > > # dd if=/dev/device of=keyfile-v3 bs=8192 count=1 conv=notrunc > (try losetup with 2.12a and this keyfile-v3 to verify it's correct) Worked. > # gpg --decrypt keyfile-v3 | head -n 64 | gpg --symmetric -a > keyfile-v2 > (try losetup again with this keyfile-v2; It should work with 2.12a > and 2.12p; losetup -a from 2.12p should show "multi-key-v2") With "loop-aes-utils -a" from 2.12p I get "multi-key-v3" !!! with keyfile-v2 and the original error message with keyfile-v3. But with keyfile-v2 (using loop-aes-utils 2.12p) it is set up correctly and I can mount it! What is going on here? I noticed that keyfile-v3 has 3915 newlines at the end, is this to worry me for the final step (which I did not yet take)?: > # dd if=keyfile-v2 of=/dev/device bs=8192 count=1 conv=notrunc I'm planning on trying this on a copy tomorrow. I want to give my harddrive a little rest inbetween though.... it's rather large quantities it has to shuffle around. And a comment from you if you think it is safe any more would maybe spare it some heat, particularly if you don't think I should try this... ;-) Thank you for your guidance Anno -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.11-custom Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages loop-aes-utils depends on: ii libblkid1 1.37-2 block device id library ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libuuid1 1.37-2 universally unique id library ii mount 2.12p-4 Tools for mounting and manipulatin -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
