Your message dated Mon, 08 Apr 2024 20:34:58 +0000
with message-id <e1rtvhi-00eifm...@fasolo.debian.org>
and subject line Bug#1064724: fixed in yapet 2.6-2
has caused the Debian Bug report #1064724,
regarding libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
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 ow...@bugs.debian.org
immediately.)
--
1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl3
Version: 3.0.13-1~deb12u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@security.debian.org
Control: affects -1 + yapet
Dear maintainer,
This version of libssl3 from bookworm-proposed-updates breaks YAPET.
When I try to open my passwords database, it claims the master password I type
is incorrect. But downgrading libssl3 fixes the problem.
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libssl3 depends on:
ii libc6 2.36-9+deb12u5
libssl3 recommends no packages.
libssl3 suggests no packages.
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: yapet
Source-Version: 2.6-2
Done: Salvatore Bonaccorso <car...@debian.org>
We believe that the bug you reported is fixed in the latest version of
yapet, which is due to be installed in the Debian FTP archive.
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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso <car...@debian.org> (supplier of updated yapet 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 08 Apr 2024 21:32:50 +0200
Source: yapet
Architecture: source
Version: 2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso <car...@debian.org>
Changed-By: Salvatore Bonaccorso <car...@debian.org>
Closes: 1064724
Changes:
yapet (2.6-2) unstable; urgency=medium
.
* crypt/blowfish: Remove EVP_CIPHER_CTX_set_key_length() (Closes: #1064724)
* crypt/aes: Remove EVP_CIPHER_CTX_set_key_length()
Checksums-Sha1:
77a9dbb34c6c2046ffe5b63a38017ef71e4c3002 2032 yapet_2.6-2.dsc
fe1fbdf8a638b496a141b2d35069be4e20ec3645 7996 yapet_2.6-2.debian.tar.xz
Checksums-Sha256:
6c9b34160d20ce23c0b0c9d230268c0d4cfe9c62751cdd233bda74fd62a1c3c8 2032
yapet_2.6-2.dsc
d730ba75509e872bb65261172cd71325aa24b7e4daa007a41d1c33c1a02b0995 7996
yapet_2.6-2.debian.tar.xz
Files:
80259088fe14003a53ce2c90aea62b26 2032 utils optional yapet_2.6-2.dsc
bfbb7689511ec6fb58b5601b605f0405 7996 utils optional yapet_2.6-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYURxZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EH24QAJmmjht7mDwrJXoZnInXsJV6oDbcMQ5C
5QyfHZW8X15MQCzkYyFhu+xFTpvsHLaYzDeUm3ikZP1c18vphvCzIDgDnTlaBoeq
Xato2YDoOl1hpwAZ/rFL7C0rb/XhEqrGpe0NjYANfglQKwug6KuEb2ll0+cDIQI0
se/Ovvkbe3sH40UjFv+e0gu0S79f0uz9eMQj3+DM1XG9Rtl6BNiG6A+dGxsEJr01
E8TpOQ5CwiOQl5S16Uax2NqZcEGXTbdY5ngfWmpI1MyL0PfXKBM0W9xi7sGCQc+O
GwH1YIjyIgD6lKumI9kGzQx0jG3ev8ivDrY2czVWDeTTolKUwXbSKeKkrmHMPZbi
0Yz8Eazv5c96wPfdxAYB0DMjNEVT4OYgYt6ukjQrxtcf96YUKSp0e9gIxRh8tiUH
8BOTE7uJO3t8xZYnxdLuJtxSF1dpiDgL1DDZwpFYgAhdNcSU4yUkARDXeU5XItid
SMus9NjXszlG0m9FQ8Rle8Q1JgoCiESE1Udro1tLES5LmQKat1UkfDzzSkpNfpFS
kGsL57PM6hDrfQFclxmGjWlxDbi6WwZX102Jfsob/P0k96b2aZ5zRqmPEsF/NIis
Jukm3YxzrV4YKewbyRaD52AACItKJIg527XbY9p0gPBc992q+CHF0zp3pYaO5z1b
/SxKnB/9dp6m
=pbZe
-----END PGP SIGNATURE-----
pgpDiwrWXKjR9.pgp
Description: PGP signature
--- End Message ---
