Jonas Meurer wrote:
try 'cryptsetup --version' to verify that the binary really belongs to 1.0.2+1.0.3-rc3-1.
I can't really do that very easily because it's encapsulated in initrd.
do you use plain dm-crypt ('cryptsetup create') or luks
LUKS. So it's cryptsetup luksOpen
cryptsetup luksOpen indeed exits with code 255 if you enter a wrong passphrase. but i tested 1.0.3-1, which is not in debian/unstable yet.
It always used to work. I suspect it's been broken and then fixed but I'm surprised nobody else has noticed.
try # cryptsetup luksOpen /dev/device name; echo "RETURNCODE: $?" to see which returncode cryptsetup gives. if the code is always 0, you should wait for cryptsetup 1.0.3-1 to enter debian/unstable.
And the useful info.... cryptsetup luksOpen /dev/hda xxx ; echo "RETURNCODE: $?" Enter LUKS passphrase: Command failed: No key available with this passphrase. RETURNCODE: 0 cryptsetup --version cryptsetup-luks 1.0.3-rc3 Dick --------------------------------------------------------------------- - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
