On Thu, Dec 14, 2006 at 11:08:26PM +0000, Rob Walker wrote:
The correct syntax would be something like:
/sbin/cryptsetup luksOpen /dev/something tmpfoo
I know the syntax to the cryptsetup command I gave is incorrect, but
crypt setup should catch such errors and print a useful warning
message rather than lock up the system
Furthermore, I can't reproduce this (using the version currently in
unstable):
<snip>
...
Yes, these commands work OK. I only discovered the bug when I made a
mistake in experimenting with cryptsetup
Problem is I can't reproduce the bug with your commands either
(executing them as a regular user):
([EMAIL PROTECTED]:~)$ dd if=/dev/zero of=/tmp/foo bs=1k count=1024
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.0060463 seconds, 173 MB/s
([EMAIL PROTECTED]:~)$ /sbin/cryptsetup luksOpen /tmp/foo /dev/mapper/_tmp_foo
Enter LUKS passphrase:
/tmp/foo is not a LUKS partition
Enter LUKS passphrase:
/tmp/foo is not a LUKS partition
Enter LUKS passphrase:
/tmp/foo is not a LUKS partition
Command failed: No key available with this passphrase.
([EMAIL PROTECTED]:~)$
Are you able to reproduce the error with the version of cryptsetup that
is currently in unstable?
--
David Härdeman
