Your message dated Fri, 06 Jun 2008 20:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#478268: fixed in cryptsetup 2:1.0.6-2
has caused the Debian Bug report #478268,
regarding cryptsetup: LUKS device no more recognized at boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
478268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478268
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.6-1
Severity: critical

Hi there!

With the (not so new) cryptsetup version [1], whichever LUKS passhprase
I enter at boot I get the same error with 3 different kernels
(2.6.24-1-amd64, 2.6.25-rc8-amd64 and 2.6.25-trunk-amd64):

=====
device-mapper: table: 254:0: crypt: unknown target type
device-mapper: ioctl: error adding target to table
device-mapper: ioctl: device doesn't appear to be in the dev hash table.

Command failed: No key available with this passhprase.
=====

This is a bug in cryptsetup_2:1.0.6-1: simply downgrading to the
previous version (2:1.0.6~pre1+svn45-1) is enough to solve it.

Since I thought this could be caused by the default hash being changed
to ripemd160, I (re)read the cryptsetup NEWS.Debian and then guessed I
was OK (I use LUKS and the entire disk encryption has been set up by the
Debian Installer).  However, this doesn't seem the case, hence the
severity set to critical.

As in /usr/share/doc/cryptsetup/README.initramfs.gz, since I use LUKS my
/etc/crypttab contains a very simple line:

  sda2_crypt  /dev/sda2  none  luks

Thx, bye,
Gismo / Luca

Footnotes: 
[1] I vaguely remember having experienced this bug with a 2.6.25-rcX
    version when I upgraded cryptsetup, but then I thought it was
    related to #466573 [2] and since I hadn't a lot of free time I
    switched to a released kernel until the bug appeared on
    2.6.24-1-amd64, too.  Sorry for not having investigated more before
[2] http://bugs.debian.org/466573

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cryptsetup depends on:
ii  dmsetup                      2:1.02.24-4 The Linux Kernel Device Mapper use
ii  libc6                        2.7-10      GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.24-4 The Linux Kernel Device Mapper use
ii  libpopt0                     1.10-3      lib for parsing cmdline parameters
ii  libuuid1                     1.40.8-2    universally unique id library

cryptsetup recommends no packages.

-- no debconf information

Attachment: pgpPGnr0mQ6wY.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.0.6-2

We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive:

cryptsetup-udeb_1.0.6-2_amd64.udeb
  to pool/main/c/cryptsetup/cryptsetup-udeb_1.0.6-2_amd64.udeb
cryptsetup_1.0.6-2.diff.gz
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-2.diff.gz
cryptsetup_1.0.6-2.dsc
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-2.dsc
cryptsetup_1.0.6-2_amd64.deb
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Härdeman <[EMAIL PROTECTED]> (supplier of updated cryptsetup package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 26 May 2008 08:12:32 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb
Architecture: source amd64
Version: 2:1.0.6-2
Distribution: unstable
Urgency: low
Maintainer: Jonas Meurer <[EMAIL PROTECTED]>
Changed-By: David Härdeman <[EMAIL PROTECTED]>
Description: 
 cryptsetup - configures encrypted block devices
 cryptsetup-udeb - configures encrypted block devices (udeb)
Closes: 477658 478268
Changes: 
 cryptsetup (2:1.0.6-2) unstable; urgency=low
 .
   [ Jonas Meurer ]
   * Taken from ubuntu:
     - debian/scripts/luksformat: Use 256 bit key size by default. (LP: #78508)
     - debian/patches/02_manpage.patch: Clarify default key sizes (128 for
       luksFormat and 256 for create) in cryptsetup.8. (side-note in LP #78508)
   * Use 'shred -uz' instead of 'rm -r' to remove a tempfile that contains a
     key in gen-ssl-key example script.
 .
   [ David Härdeman ]
   * Misc bugfixes to askpass, make sure it is installed to the correct
     location and is built using pedantic mode.
   * Change the initramfs script to use askpass to prompt for
     passphrases, this should hopefully fix #382375 and #465902 once it
     is enabled in the init scripts as well.
   * Add a keyscript called passdev which allows a keyfile to be
     retrieved from a device which is first mounted, mainly useful to get
     keyfiles off USB devices etc.
   * Unbreak MODULES=dep booting (closes: #478268)
   * Relax checks for suspend devices a bit (closes: #477658)
   * Convert man pages to docbook.
Checksums-Sha1: 
 a7c94c55cc45210375ef0895a25aa45b391d308f 1434 cryptsetup_1.0.6-2.dsc
 c3e3ad343b8ea77ba2901f1f3dbc2c1c4f8cf42b 55494 cryptsetup_1.0.6-2.diff.gz
 5e23255dde5229378fb62fc7b7194f1ae5c66270 307752 cryptsetup_1.0.6-2_amd64.deb
 2f89ad866868de44ea40128d11334ca1457f235c 247136 
cryptsetup-udeb_1.0.6-2_amd64.udeb
Checksums-Sha256: 
 61a62587051e9b10f0c84ed28fbbdd86658ffcdac32821c8bc9bc00b5d96b4f9 1434 
cryptsetup_1.0.6-2.dsc
 20b936daabd472bef7587958d65832bc36fa7aa3be9bd4ebf2fb4e6c7f8d699b 55494 
cryptsetup_1.0.6-2.diff.gz
 5c9e7c0ac88f4eec530b7a476bb04ec9776151567a9e2e44d470ebeb3ea7b978 307752 
cryptsetup_1.0.6-2_amd64.deb
 e0c28025a1118a62c4c87892dc09aa3041078062d9307ce8f7ec91ec2416071f 247136 
cryptsetup-udeb_1.0.6-2_amd64.udeb
Files: 
 99a6be9e62f66c6389fdc846ba3e1280 1434 admin optional cryptsetup_1.0.6-2.dsc
 1a421d54c13ae38569a7688a5a1b6411 55494 admin optional 
cryptsetup_1.0.6-2.diff.gz
 9798a21c931db267cb1aa7fbf85ee6ac 307752 admin optional 
cryptsetup_1.0.6-2_amd64.deb
 5149d96b74e0582c1e1da297441441c1 247136 debian-installer optional 
cryptsetup-udeb_1.0.6-2_amd64.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhJGRoACgkQd6lUs+JfIQIjeQCeNLAuoZ4fam0r1jXwv1shOaDF
lk4An2WN/ryIcqSn88XkVDEl4GH3/fXG
=MbZd
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to