Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

[Tino Keitel <tino.keitel@gmx.de>]

On Sun, Jan 16, 2005 at 17:38:50 +0100, Wesley W. Terpstra wrote:
> On Sun, Jan 16, 2005 at 03:42:50PM +0000, Martin Michlmayr wrote:
> > > Maybe the information in /etc/crypttab should be used the same way as in
> > > the initscript to contruct the command line for cryptsetup.
> > 
> > Wesley, can you take a look at this bug report?
> 
> I can confirm that this is indeed a bug.
> 
> I will look into it soon; I am in the middle of discussing a change to
> upstream cryptsetup which will also affect /etc/crypttab, and I'd like to
> kill the two birds with one stone.
> 
> My current plan is to move /etc/crypttab parsing into another script
> 'parse-crypttab' and call this from both /etc/init.d/cryptdisks and
> /usr/sbin/mkinitrd. 
> 
> This means I will need to upload a new cryptsetup and provide you a
> mkinitrd patch. Then initrd-tools will have to conflict with old versions 
> of cryptsetup.

Hi Wesley,

what's the status here? Will we have fixed initrd-tools and cryptsetup
packages in Sarge?

Regards,
Tino