[pkg-cryptsetup-devel] Bug#524485: cryptsetup: cryptdisks_start incorrectly reports failure
Celejar
celejar at gmail.com
Fri Apr 17 13:34:19 UTC 2009
Package: cryptsetup
Version: 2:1.0.6+20090405.svn49-1
Severity: normal
My /etc/crypttab contains the line:
cdisk1 /dev/wd/disk1 none luks,noauto
~# cryptdisks_start cdisk1
Starting crypto disk...cdisk1 (starting).
Enter passphrase to unlock the disk /dev/wd/disk1 (cdisk1):
key slot 0 unlocked.
Command successful.
cdisk1 (started)...cdisk1 (failed, not found in crypttab)...done.
This output is not sane; both success and failure are reported, and 'not found
in crypttab' is simply incorrect.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-rc2-wl-lizzie
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.30-3 The Linux Kernel Device Mapper use
ii libc6 2.9-7 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.30-3 The Linux Kernel Device Mapper use
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libuuid1 1.41.3-1 universally unique id library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
ii dosfstools 3.0.2-1 utilities for making and checking
ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs
ii udev 0.140-2 /dev/ and hotplug management daemo
-- no debconf information
More information about the pkg-cryptsetup-devel
mailing list