Your message dated Tue, 12 Dec 2006 21:36:40 +0100
with message-id <[EMAIL PROTECTED]>
and subject line partman-crypto allows invalid crypto/essiv combinations
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.3-3
Hi cryptsetup maintainers,
I noticed this problem while testing dm-crypt support in
partman-crypto. I'm not completely sure if the parameters have
supported values (keysize, etc.).
Since this is a combination currently offered for users in
partman-crypto, I would much appreciate if you could let us
know and reassign this if there is some problem with the
setup and it should not be offered.
###
# dd if=/dev/zero of=img bs=1M count=10
# losetup /dev/loop0 img
# dd if=/dev/urandom count=512 of=keyfile
# cryptsetup -c blowfish-cbc-essiv:sha256 -s 448 luksFormat /dev/loop0 keyfile
WARNING!
========
This will overwrite data on /dev/loop0 irrevocably.
Are you sure? (Type uppercase yes): YES
Command successful.
# cryptsetup -d keyfile luksOpen /dev/loop0 crypt0; echo $?
key slot 0 unlocked.
Segmentation fault (core dumped)
139
# gdb --args cryptsetup -d keyfile luksOpen /dev/loop0 crypt0
(gdb) r
Starting program: /sbin/cryptsetup -d keyfile luksOpen /dev/loop0 crypt0
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
key slot 0 unlocked.
Program received signal SIGSEGV, Segmentation fault.
0x0804d881 in write_blockwise ()
(gdb) bt
#0 0x0804d881 in write_blockwise ()
#1 0x0804ca5e in ?? ()
#2 0xad5369ba in ?? ()
#3 0xafea54f0 in ?? ()
#4 0xafea5464 in ?? ()
#5 0xafea51d8 in ?? ()
#6 0xafea5460 in ?? ()
#7 0x0809e4a8 in ?? ()
#8 0x00000000 in ?? ()
(gdb) x/i $eip
0x804d881 <write_blockwise+977>: mov 0xfffffffc(%edi),%eax
(gdb) i r edi eax
edi 0xad5369ba -1387042374
eax 0xad5369ba -1387042374
Let me know if there is something I can do to help you debug
this problem.
cheers,
Max
--- End Message ---
--- Begin Message ---
Actually, there are no invalid crypto/essiv combinations. It was a bug
in how LUKS handled keys > 256 bits which has been fixed since then.
So I'm closing this bug.
--
David Härdeman
--- End Message ---
