Your message dated Mon, 12 May 2014 15:40:18 +0000 with message-id <[email protected]> and subject line Bug#725141: fixed in libpam-abl 0.6.0-3 has caused the Debian Bug report #725141, regarding libpam-abl: Whitelisting host corrupted database 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.) -- 725141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725141 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libpam-abl Version: 0.4.3-1 Severity: normal Today I tried to whitelist one of my hosts with the following results. The second pam_abl listing hung and had to be interrupted with C-c. $ sudo pam_abl <expected listing> $ sudo pam_abl --whitelist -H <host> No such file or directory (2) while reading config file Invalid argument (22) while reading config file: No db_home dir specified $ sudo pam_abl pam-abl: unable to join the environment pam-abl: unable to join the environment ^C $ I removed all of the files in my pam-abl database directory (db_home=/var/lib/abl/) and this cleared up the problem. In addition to having a corrupted database, the error message above is incorrect; as you can see, db_home *is* specified. Note that I just upgraded to wheezy, so I'm suspecting a database upgrade had a role to play. If this is true, please retitle this issue to "Upgrading database version corrupts database." Dependencies should be put in place so that the pam-abl database is automatically rebuilt upon a database upgrade. At the very least, documentation should be added to /usr/share/doc/libpam-abl/README.Debian. For example, please see Section 2.6, Updating Berkeley DB version underneath bogofilter, in /usr/share/doc/bogofilter-bdb/README.db. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-abl depends on: ii libc6 2.13-38 ii libdb5.1 5.1.29-5 libpam-abl recommends no packages. libpam-abl suggests no packages. -- Configuration Files: /etc/security/pam_abl.conf changed: db_home=/var/lib/abl/ host_db=/var/lib/abl/hosts.db host_purge=2d host_rule=*:3/1h,30/1d user_db=/var/lib/abl/users.db user_purge=2d user_rule=nobody:3/1h,30/1d -- no debconf information -- Bill Wohler <[email protected]> aka <[email protected]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
--- End Message ---
--- Begin Message ---Source: libpam-abl Source-Version: 0.6.0-3 We believe that the bug you reported is fixed in the latest version of libpam-abl, 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Mestiashvili <[email protected]> (supplier of updated libpam-abl 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: SHA256 Format: 1.8 Date: Mon, 12 May 2014 13:38:18 +0200 Source: libpam-abl Binary: libpam-abl Architecture: source amd64 Version: 0.6.0-3 Distribution: unstable Urgency: medium Maintainer: Alexandre Mestiashvili <[email protected]> Changed-By: Alexandre Mestiashvili <[email protected]> Description: libpam-abl - blocks hosts attempting a brute force attack Closes: 725141 742024 Changes: libpam-abl (0.6.0-3) unstable; urgency=medium . * d/control: fixed with help of cme! Closes: #725141,#742024, upload to unstable * d/NEWS: describe the new way of configuration Checksums-Sha1: 3fbd8ec57cf42d599656aba634e2e1102d21a586 1924 libpam-abl_0.6.0-3.dsc 5e8d1b133de70f6ce3a5dbcc5dda4c92658b4557 5336 libpam-abl_0.6.0-3.debian.tar.xz 770eb4543e04c232842709d94bbee9702c1a67d6 42622 libpam-abl_0.6.0-3_amd64.deb Checksums-Sha256: 67807a13be8ed58e1172c669f47475d38277c5003e3dd33222ce00b840c52dd2 1924 libpam-abl_0.6.0-3.dsc e250d203ee20fc4833ff27dcb2d01adaae74c90b551f08f6994b46d6b7bd757e 5336 libpam-abl_0.6.0-3.debian.tar.xz b82f7a574aadc7841296911363d22edaa43924877a75befa590c9e041f21e67b 42622 libpam-abl_0.6.0-3_amd64.deb Files: d5c997b8c4af9a30af1d63ff1cedd46f 42622 admin extra libpam-abl_0.6.0-3_amd64.deb 862d552cef7bf78c58a98928ab238ea3 1924 admin extra libpam-abl_0.6.0-3.dsc 4d1c90cb5258b9d27754cb1bd9e7d559 5336 admin extra libpam-abl_0.6.0-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJTcNDRAAoJEBz3khEbUiiwUrkP/1qyRrMNzRn8j6+cOypopiPM K+oY9x8uEwTWFpQyNduhZhlhlNMyJvKkhXbogvziZ2xCVIUKX5g23W8WIVgENn0w TH0yAwQBOmeEkVeTxCfgloHJqhVi7wOjyILTh+ltHwNUAvjJlgwkMpdbzEu8Hm5t T2YhiBH13aOTquFKPwHVmpKwLOUIrk6duy5McPuiVwlmUIBAtXf8GSlxX2TtmGT/ p4noveTgqD8EPXruWMqgU0tpNgm8K661Dk64s29X5KoQ9qJIjaE5+kDoUPgytx1f qNFz7ECGFEDRYkCVkX75HFE4RJmi5nYEBWHkQKU6RnkPKmJHyUn63qAV8/9BE73S XPw5h5BSTPMkLEDNyZ0VKwe70nTnqcrea0RZv+VlWqbARA3amVOvzjd6eWv2yukU 0VaMCCC5YoO9o3TEz9CKKpySEjmnY9wUtWb/cV2y85wVCBhqW1pqvjYX3D9sD7ht x5nGszB73e+E9HnRv2t+f0zw4Py+uptU4pPZWkswNdAbqObZbR7hgcmMxHUU2/5f EMUhPJMZvT4vgfzsCbQ7cih/TqLcPgDMDOxQ0tWWbgpnUJZBMXkjmERMnXVBQxO4 bt76Gg9tQLWLtNJ3Ho0RbOYKed55Wilu3C13s/IzhskbnYXGRHph6YAUC/FzTkYX GNs2udT65gBpso7GW7bj =C7Ke -----END PGP SIGNATURE-----
--- End Message ---
