[Pkg-cryptsetup-devel] Bug#388083: cryptsetup update does not check crypttab, grave problems during reboot

Michael Steinfurth michael.steinfurth at fh-stralsund.de
Mon Sep 18 13:47:42 UTC 2006


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

In prev. versions I only used two entries in /etc/crypttab, now four 
entries in crypttab are mandatory, but update does not check the entries 
and just installs new initscript/cryptdisks.functions.
After reboot you could have grave problems if some cryptdisks do not start, 
because the entries only have 2 entries.

Possible solution: check entries of crypttab during update of package 
and display a warning or something else.

crypttab manpage section SYNOPSIS is wrong. Last two arguments are shown
as optional but they are mandatory.

-- 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




More information about the Pkg-cryptsetup-devel mailing list