robert wrote: > Jari Ruusu wrote: > > Plan A: Try using 64 line key file > > > > # gpg --decrypt </home/keyfile.gpg | head -n 64 | \ > > ( sleep 60 ; gpg -a --symmetric >/home/keyfile64.gpg ) > > > > And then try it with /home/keyfile64.gpg key file > > Plan A:" Was FULL SUCCESS ! [snip] > So what just happened ? You used loop-AES-v2 mount and losetup binaries with version 3 key file. Number of lines in key file determine on-disk format: 1 line == v1 format, 64 lines == v2 format, 65 lines == v3 format. Mount from loop-AES-v2 did not userstand v3 on-disk format and set ip up in v2 format anyway. Mount from loop-AES-v3 detected v3 format key file and used v3 on-disk format. It was not compatible as you noticed. This is explained in README section 7. Type "losetup /dev/loop0" and it says multi-key-v2 > I have to use keyfile64.gpg now and in the future ? Yes. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
