Your message dated Sat, 09 Aug 2008 12:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#493848: fixed in cryptsetup 2:1.0.6-6
has caused the Debian Bug report #493848,
regarding [EMAIL PROTECTED]: [pkg-cryptsetup-devel] crypttab problem]
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.)


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

forwarding a bug reported by Marco Gatti to the pkg-cryptsetup-devel
mailinglist.

greetings,
 jonas

----- Forwarded message from Marco Gatti <[EMAIL PROTECTED]> -----

Date: Mon, 4 Aug 2008 12:24:41 +0200
From: Marco Gatti <[EMAIL PROTECTED]>
Subject: [pkg-cryptsetup-devel] crypttab problem
To: [EMAIL PROTECTED]

Using Lenny with an encrypted partition on a secondary disk the new
version of cryptsetup doesn't work anymore with this line configured
in /etc/crypttab:

backup          /dev/hdb1               /path/to/file.key   hash=sha512

The device get created but there's no chance to mount it since it
doesn't find any proper filesystem (even forcing it in the mount
options).
If i run cryptsetup manually it works and i see all my data:

cryptsetup create backup /dev/hdb1 --key-file=/path/to/file.key --hash=sha512

I've tried to look at the documentation and the changes but didn't
find if i'm doing something wrong (and i've been using this setup for
years...).


System Information:
Debian Release: lenny
Kernel: Linux 2.6.25.14 #1 SMP PREEMPT Mon Aug 4 10:26:20 CEST 2008
i686 GNU/Linux

Package:
ii  cryptsetup                     2:1.0.6-4
configures encrypted block devices

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


-- 
Linux Registered User #398764 - http://counter.li.org/
[EMAIL PROTECTED] User - http://www.boincstats.com/signature/user_833490.gif

_______________________________________________
pkg-cryptsetup-devel mailing list
[EMAIL PROTECTED]
http://lists.alioth.debian.org/mailman/listinfo/pkg-cryptsetup-devel


----- End forwarded message -----

Attachment: signature.asc
Description: Digital signature


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

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-6_amd64.udeb
  to pool/main/c/cryptsetup/cryptsetup-udeb_1.0.6-6_amd64.udeb
cryptsetup_1.0.6-6.diff.gz
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-6.diff.gz
cryptsetup_1.0.6-6.dsc
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-6.dsc
cryptsetup_1.0.6-6_amd64.deb
  to pool/main/c/cryptsetup/cryptsetup_1.0.6-6_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.
Jonas Meurer <[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: Sat, 09 Aug 2008 13:36:31 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb
Architecture: source amd64
Version: 2:1.0.6-6
Distribution: unstable
Urgency: high
Maintainer: Jonas Meurer <[EMAIL PROTECTED]>
Changed-By: Jonas Meurer <[EMAIL PROTECTED]>
Description: 
 cryptsetup - configures encrypted block devices
 cryptsetup-udeb - configures encrypted block devices (udeb)
Closes: 493848
Changes: 
 cryptsetup (2:1.0.6-6) unstable; urgency=high
 .
   * Don't cat keyfile into pipe for do_noluks(). cryptsetup handles
     --key-file=- different for luks and plain dm-crypt mappings. This time
     really (closes: #493848). Thus again upload with urgency=high.
Checksums-Sha1: 
 c0b6f984e0aef633c5a76114388a9f55878949b3 1445 cryptsetup_1.0.6-6.dsc
 e9f941500b167e65f619dd66e1c548ec5f1093a1 57581 cryptsetup_1.0.6-6.diff.gz
 b2c2dc17f2a3728579c8d1be1c2edea3eedcfd65 307900 cryptsetup_1.0.6-6_amd64.deb
 a3f8a086ccff08dd77225fdefd5bf1b95810813a 248230 
cryptsetup-udeb_1.0.6-6_amd64.udeb
Checksums-Sha256: 
 9c13eb14e158e062190f018aa568f2e297cf3b6b45b7dd17296f45524bb26fbb 1445 
cryptsetup_1.0.6-6.dsc
 a25f8c2b03f9bab6112c5f387dc66e7e58d89eab4236e22acc5677e2a62c7c1d 57581 
cryptsetup_1.0.6-6.diff.gz
 705da52a907b78408e8fac308bd2e94c39fd2e37d27743ad07a8306bcf8d8625 307900 
cryptsetup_1.0.6-6_amd64.deb
 b63df1c7c9ecb0cd18f565c56efb8b5dfca53554ac460f85966fa491e23cef19 248230 
cryptsetup-udeb_1.0.6-6_amd64.udeb
Files: 
 d5cffb79b78b2648cc93c794db92841f 1445 admin optional cryptsetup_1.0.6-6.dsc
 20f48337c3f4ab593973529a01d2a5f6 57581 admin optional 
cryptsetup_1.0.6-6.diff.gz
 55139fdd371dcd36e6bd98e351266ad8 307900 admin optional 
cryptsetup_1.0.6-6_amd64.deb
 dd80d5da125759305ef13795bde61328 248230 debian-installer optional 
cryptsetup-udeb_1.0.6-6_amd64.udeb
Package-Type: udeb

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

iEYEARECAAYFAkidi58ACgkQd6lUs+JfIQLiGgCfVx7cSe7B3tyBjwzjCBvKcAQ/
QBUAoJA6SWNgpyTYFtdSShY7/TlczZr/
=06pu
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to