[pkg-cryptsetup-devel] Bug#493622: cryptsetup: cryptdisks_starts Command failed parse errors and keyboard locks
Joaquín Martínez
jmbouzas at gmail.com
Sun Aug 3 16:18:23 UTC 2008
Package: cryptsetup
Version: 2:1.0.6-4
Severity: normal
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26.1c0
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.27-3 The Linux Kernel Device Mapper use
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.27-3 The Linux Kernel Device Mapper use
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libuuid1 1.41.0-3 universally unique id library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
ii dosfstools 2.11-6 utilities for making and checking
ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs
ii udev 0.114-2 /dev/ and hotplug management daemo
ii yaird [linux-initramfs-tool] 0.0.13-2 Yet Another mkInitRD
-- no debconf information
<above the emacs debian-bug command output>
The exact and complete text of any error messages printed or logged:
# cryptdisks_start sdb2_crypt
sdb2_crypt (starting).
Command failed: No key available with this passphrase
A description of the incorrect behaviour: exactly what behaviour
you were expecting, and what you observed.
attached /etc/crypttab file where you can see the "none" => interactive
passphrase.
After the "Command failed: No key..." message" the keyboard
locks (X-Windows system) and a reboot is needed (mouse does not lock).
The direct command "cryptsetup luksOpen /dev/sdb2 sdb2_crypt"
works perfectly, only the crypdisks_start script fails.
cryptdisks_stop sdb2_crypt script is successfull if runs after
"cryptsetup luksOpen /dev/sdb2 sdb2_crypt"
Suggested fix:
I do not know. Please let me know if you need some testing for your fixes.
Additional information:
After some reading of the documentation I have found the following
extrange things:
File:
/usr/share/doc/cryptsetup/README.Debian.gz
"If you are using udev, it might be a good idea to use the /dev/disk/by-label
links instead of /dev/sdg2 as the link will work no matter in which order the
media is inserted and detected."
/dev/disk/by-label ... on kernel 2.6.26.1 also are /dev/disk/by-id
but in "/lib/cryptsetup/cryptdisks.functions"
# parse UUID= symlinks
if [ "${src#UUID=}" != "$src" ]; then
src="/dev/disk/by-uuid/${src#UUID=}"
elif [ "${src#LABEL=}" != "$src" ]; then
src="/dev/disk/by-label/${src#LABEL=}"
UUID= and LABEL= sintaxes are not documented on man crypttab
There is also ID= ( /dev/disk/by-id on GNU/Linux kernel 2.6.26.1)
Maybe remove this sintax and use the full /dev path on all cases.
Thank you for your work and time.
Best regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crypttab
Type: application/octet-stream
Size: 454 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080803/36feb638/attachment.obj
More information about the pkg-cryptsetup-devel
mailing list