[Pkg-cryptsetup-devel] Bug#432150: /sbin/cryptsetup: repair tools needed

[gambarimasu+reportbug at gmail.com]

Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: wishlist
File: /sbin/cryptsetup


dm-crypt has data corruption issues, and this includes the luks
header.  a tool to repair the luks header so that you can run fsck on
the fs would be useful.  it might be that most of the data are ok.

this could take the form of an fsck-like repair, or a similar
partition's header to repair the header, or a luksRestore from a
backed up luksDump.  i'm sure there are issues with each of these, but
it seems likely that *something* can be done.  there was brief
discussion on the dm-crypt mailing list about how to repair luks
headers and that might be a place to start.

data corruption reports can be found via google, and on the dm-crypt
mailing list.  many, including mine, are hard to reproduce.  fwiw,
here is mine: message 2007-07-01 02:59:28 GMT on
http://news.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt .

there is a well-known and probably fixed issue with 2.6.18 and raid 5,
and there are issues that do not involve that kernel and do not
involve raid 5.  i suspect that even 2.6.22rc7 is vulnerable.

thanks.

-- System Information:
Debian Release: 4.0
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18myver-2007-06-q
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-13                    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-2 universally unique id library

cryptsetup recommends no packages.

-- no debconf information