Your message dated Sat, 07 Mar 2009 09:02:03 +0000
with message-id <[email protected]>
and subject line Bug#516922: fixed in cryptmount 3.1.2-1
has caused the Debian Bug report #516922,
regarding cryptmount: couldn't find libgcrypt cipher "blowfish"
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.)
--
516922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516922
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptmount,libgcrypt11
Severity: important
Last libgcrypt11 seems to have added a problem regarding cryptmount. Since I
do not know which package is to blame I am filing a shared bug report
against both so both maintainers know about this problem. Since libgcrypt11
was updated in the last days, seems that the incompatibility has been
introduced there.
I do not know if other algorithms work, so I am setting this bug report
only as important, although severity is higher for me.
cryptmount: 3.1.1-1
libgcrypt11: 1.4.4-2
$ cryptmount dummy
couldn't find libgcrypt cipher "blowfish"
failed to extract cipher key
Going back to testing libgcrypt11 in my sid box seems to make things work
again,
cryptmount: 3.1.1-1
libgcrypt11: 1.4.1-2
$ cryptmount dummy
Enter password for target "dummy":
Rebuilding cryptmount against last libgcrypt11 seems to not help.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26 (PREEMPT)
Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Source: cryptmount
Source-Version: 3.1.2-1
We believe that the bug you reported is fixed in the latest version of
cryptmount, which is due to be installed in the Debian FTP archive:
cryptmount_3.1.2-1.diff.gz
to pool/main/c/cryptmount/cryptmount_3.1.2-1.diff.gz
cryptmount_3.1.2-1.dsc
to pool/main/c/cryptmount/cryptmount_3.1.2-1.dsc
cryptmount_3.1.2-1_amd64.deb
to pool/main/c/cryptmount/cryptmount_3.1.2-1_amd64.deb
cryptmount_3.1.2.orig.tar.gz
to pool/main/c/cryptmount/cryptmount_3.1.2.orig.tar.gz
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.
RW Penney <[email protected]> (supplier of updated cryptmount
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, 28 Feb 2009 09:00:00 +0000
Source: cryptmount
Binary: cryptmount
Architecture: source amd64
Version: 3.1.2-1
Distribution: unstable
Urgency: low
Maintainer: RW Penney <[email protected]>
Changed-By: RW Penney <[email protected]>
Description:
cryptmount - Management and user-mode mounting of encrypted file systems
Closes: 516922
Changes:
cryptmount (3.1.2-1) unstable; urgency=low
.
* Minor update to version 3.1.2 of upstream package
.
* Closes: bug#516922 (Initialization of libgcrypt library)
.
* Clears lintian warnings about sourceforge-redirector in watch-file,
and redirection of output of updaterc.d
Checksums-Sha1:
0e965f3e8e4319ed47839420e98c6644d4f33405 1050 cryptmount_3.1.2-1.dsc
31dae5c1e010b2033280077365780db14d09269c 303075 cryptmount_3.1.2.orig.tar.gz
cfac56aebf7b1a00ff8ba0291e9d9690aeb09bc0 15900 cryptmount_3.1.2-1.diff.gz
78e917395a7e93068c7c244c60a250149ba48224 117824 cryptmount_3.1.2-1_amd64.deb
Checksums-Sha256:
6ef056babd7d967415a40d856ea4a77ce452db7a91d431fa5823b81b796fffe9 1050
cryptmount_3.1.2-1.dsc
d8c2d3a35319e4e147c6ed555a95d19003c9d73821aaa85c114ded36ef989261 303075
cryptmount_3.1.2.orig.tar.gz
3803dcdd9f7ea44a11f72e39c12d3972ea8e2b86f9132d30b80c48a8af7de812 15900
cryptmount_3.1.2-1.diff.gz
de9b8642a4f188f2a40237d832f14f1906348887389c83a1ee92243ce1646623 117824
cryptmount_3.1.2-1_amd64.deb
Files:
4c1410e89187da19076f27edf82f5e58 1050 admin extra cryptmount_3.1.2-1.dsc
d9167ed4519391bcae5fae9d96e0707b 303075 admin extra
cryptmount_3.1.2.orig.tar.gz
51a2cb4f173aa82cdde6fc2da2de814c 15900 admin extra cryptmount_3.1.2-1.diff.gz
20cfd4cc526c4b039d104e4c5c170794 117824 admin extra
cryptmount_3.1.2-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmyNRkACgkQMDatjqUaT92c0wCfXQoZ7NwQY2kvzibxhm8sZrkR
NycAn1Q7EzDBkwVTwf0EGyFhfze8iz2k
=APTO
-----END PGP SIGNATURE-----
--- End Message ---
