Bug#403075: [Pkg-cryptsetup-devel] Bug#403075: cryptsetup luksOpen can kill unrelated processes (out of memory killer)

David Härdeman david at hardeman.nu
Fri Dec 15 00:29:53 UTC 2006


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):

(david at austin:~)$ 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
(david at austin:~)$ /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.

(david at austin:~)$

Are you able to reproduce the error with the version of cryptsetup that 
is currently in unstable?

-- 
David Härdeman




More information about the pkg-cryptsetup-devel mailing list