[Pkg-cryptsetup-devel] Bug#388087: cryptsetup: old entries with 2 options crypttab, results in grave problems at reboot

[Michael Steinfurth]

Package: cryptsetup
Version: 2:1.0.4~rc2-1
Severity: normal

In prev. version of cryptsetup, crypttab option 3 and option 4 were not mandatory, now they are. New initscript 
response errors and does not start devmapper device(s) with only 2 mandatory options of previous version given in 
crypttab. Grave Problems during next boot can be a result of that.
In manpage SYNOPSIS block 3rd and 4th option are also defined as optional, although it is mandatory.
Possible Solution: check on update for existing entries in crypttab.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

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-4 GNU C Library: Shared libraries
ii  libdevmapper1.02             2:1.02.08-1 The Linux Kernel Device Mapper use
ii  libgcrypt11                  1.2.3-2     LGPL Crypto library - runtime libr
ii  libgpg-error0                1.2-1       library for common error values an
ii  libpopt0                     1.10-3      lib for parsing cmdline parameters
ii  libuuid1                     1.39-1      universally unique id library

cryptsetup recommends no packages.

-- no debconf information