Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-01 Thread David Härdeman
On Mon, October 1, 2007 21:16, Dick Middleton wrote: > I have a curious effect; sometimes I get an error with luksOpen such as > this: > > Failed to setup dm-crypt key mapping. > Check kernel for support for the aes-cbc-plain cipher spec and verify that > /dev/mapper/vg02-devil contains at least 26

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-02 Thread David Härdeman
On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote: David Härdeman wrote: On Mon, October 1, 2007 21:16, Dick Middleton wrote: I have a curious effect; sometimes I get an error with luksOpen such as this: Failed to setup dm-crypt key mapping. The first message is usually reporte

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-02 Thread Dick Middleton
David Härdeman wrote: On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote: David Härdeman wrote: On Mon, October 1, 2007 21:16, Dick Middleton wrote: I have a curious effect; sometimes I get an error with luksOpen such as this: Failed to setup dm-crypt key mapping. The first mes

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-02 Thread Jérémy Bobbio
On Tue, Oct 02, 2007 at 11:04:13PM +0100, Dick Middleton wrote: > Is this helpful? Could have been, but you got the wrong trace. :) > strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil devil Please try the following: echo -n x | strace cryptsetup luksOpen /dev/mapper/vg02-de

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-02 Thread David Härdeman
On Wed, October 3, 2007 00:04, Dick Middleton wrote: > David Härdeman wrote: >> On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote: >>> David Härdeman wrote: On Mon, October 1, 2007 21:16, Dick Middleton wrote: > I have a curious effect; sometimes I get an error with luksOpen s

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-03 Thread Dick Middleton
David Härdeman wrote: strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil devil Sorry, but you need to have the strace call on the right hand side of the pipe ("echo -n xxx | strace ..."). Could you please try again? And it didn't seem to reproduce the same error (probably be

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-03 Thread Dick Middleton
David Härdeman wrote: Thanks, could you now do one more thing for me? A strace from a successful invocation would be nice for comparison (I assume you've setup a test partition for this considering the "testpwd" password that you use). No, it's real; I just added a new password. Don't worry, I

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-03 Thread David Härdeman
On Wed, October 3, 2007 10:39, Dick Middleton wrote: > David Härdeman wrote: >>> strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil >>> devil >> >> Sorry, but you need to have the strace call on the right hand side of >> the >> pipe ("echo -n xxx | strace ..."). Could you please try

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-05 Thread David Härdeman
On Mon, October 1, 2007 21:16, Dick Middleton wrote: > Package: cryptsetup > Version: 2:1.0.5-2 > Severity: important > > > I have a curious effect; sometimes I get an error with luksOpen such as > this: > > Failed to setup dm-crypt key mapping. > Check kernel for support for the aes-cbc-plain ciph

Bug#444914: [Pkg-cryptsetup-devel] Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

2007-10-05 Thread Marco d'Itri
On Oct 05, David Härdeman <[EMAIL PROTECTED]> wrote: > The problem seems to be documented here (and the ubuntu patch to > libdevmapper seems to contain some relevant code): > https://wiki.ubuntu.com/UdevDeviceMapper All of this needs to be fixed in the lvm packages, udev does not ship any rules wh