[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#411743: marked as done (cryptsetup luksOpen Command failed on arm (NSLU2))

Your message dated Sun, 30 Sep 2007 10:07:10 +0200
with message-id <20070930080710.GR14630@deprecation.cyrius.com>
and subject line Bug#406552: arm: LUKS fails under load
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: important



-- System Information:
Debian Release: 4.0
Architecture: arm (armv5tel)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages cryptsetup depends on:
ii  dmsetup  2:1.02.08-1                     The Linux Kernel Device Mapper use
ii  libc6    2.3.6.ds1-11                    GNU C Library: Shared libraries
ii  libdevma 2:1.02.08-1                     The Linux Kernel Device Mapper use
ii  libgcryp 1.2.3-2                         LGPL Crypto library - runtime libr
ii  libgpg-e 1.4-1                           library for common error values an
ii  libpopt0 1.10-3                          lib for parsing cmdline parameters
ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library

cryptsetup recommends no packages.

-- no debconf information

I've setup a crypted file with the loop device:

nslu2:~# dd if=/dev/urandom of=fwcrypt.loop bs=5000000 count=1
1+0 records in
1+0 records out
5000000 bytes (5.0 MB) copied, 13.0638 seconds, 383 kB/s

nslu2:~# losetup /dev/loop0 fwcrypt.loop
nslu2:~# cryptsetup -v -y -c aes-cbc-essiv:sha256 -s 256 luksFormat
/dev/loop0

WARNING!
========
This will overwrite data on /dev/loop0 irrevocably.

Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
Command successful.

After this i've tried to open and got "Command failed":

nslu2:~# cryptsetup luksOpen /dev/loop0 fwcrypt
Enter LUKS passphrase:
Command failed.

nslu2:~# cryptsetup luksDump /dev/loop0
LUKS header information for /dev/loop0

Version:       	1
Cipher name:   	aes
Cipher mode:   	cbc-essiv:sha256
Hash spec:     	sha1
Payload offset:	2056
MK bits:       	256
MK digest:     	c1 39 f0 6e 03 cd b0 90 dd 0e 70 1f dd d1 84 0d 2f 8c 07 5f 
MK salt:       	18 9a 1f 21 db ea bd c8 ea 6a 25 3e 8a fd c5 b2 
               	e2 43 3c ba 71 26 e8 9c 35 1b d7 bd 36 92 f1 bf 
MK iterations: 	10
UUID:          	e6b7516b-fedd-41fd-919e-84ab9ecc7887

Key Slot 0: ENABLED
	Iterations:         	13019
	Salt:               	44 d9 3d 07 66 ed a0 0c e9 22 21 b6 17 52 bb fc 
	                      	dd 71 58 ca be 4d 66 5a d3 f0 3b b9 15 03 c4 0b 
	Key material offset:	8
	AF stripes:            	4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

--- End Message ---
--- Begin Message --- 
* Gordon Farquharson <gordonfarquharson@gmail.com> [2007-09-30 00:16]:
> I made a mistake when I told you that I had checked for the presence
> of this bug in 2.6.22. I was actually working with 2.6.21 at the time.
> The good news is that I have now checked with 2.6.22 (Debian SVN 9552)
> and 2.6.23-rc8, and I am unable to trigger this bug anymore. However,
> I'm not sure what fixed the problem.
> 
> Martin, is it worth trying to isolate the patch between 2.6.21 and
> 2.6.22 that fixed this problem?

I don't think it's worth the effort.

As long as it's fixed... that's good news.  Let's close the bug.
Thanks a lot, Gordon!
-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---
Reply to: