Your message dated Wed, 14 Aug 2019 20:21:15 +0200 with message-id <cea047f77e8848c9110db78ae65dc48672bac144.ca...@g-e-u-e-r.de> and subject line This bug has been fixed has caused the Debian Bug report #924043, regarding tomb: tomb-kdb-pbkdf2 program not included 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.) -- 924043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: tomb Version: 2.5+dfsg1-2 The tomb(1) man page tells me the following: For additional protection against dictionary attacks on keys, the --kdf option can be used when forging a key, making sure that the tomb-kdb-pbkdf2 binaries in extras/kdf were compiled and installed on the system. So far there seems no Debian package containing the command tomb-kdb-pbkdf2, not even tomb. And there is no "extra/kdf" in the source package of tomb, just "extras/kdf-keys". But the Makefile in there clearly shows that it will compile a bunch of "tomb-kdb-something" including "tomb-kdb-pbkdf2". So please include at least those binaries from extras/kdf-keys so that "tomb forge --kdf" can be used. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages tomb depends on: ii cryptsetup-bin 2:2.1.0-2 ii e2fsprogs 1.44.6-1 ii gnupg 2.2.13-1 ii pinentry-curses [pinentry] 1.1.0-1+b1 ii pinentry-fltk [pinentry] 1.1.0-1+b1 ii pinentry-gnome3 [pinentry] 1.1.0-1+b1 ii pinentry-gtk2 [pinentry] 1.1.0-1+b1 ii pinentry-qt [pinentry] 1.1.0-1+b1 ii pinentry-tty [pinentry] 1.1.0-1+b1 ii sudo 1.8.27-1 ii zsh 5.7.1-1 tomb recommends no packages. tomb suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: tomb Version: 2.6+dfsg1-1 We believe that the bug you reported is fixed in the latest version of tomb, which is due to be installed in the Debian FTP archive. Regards, Sven
--- End Message ---
