Your message dated Sun, 06 Oct 2024 00:08:57 +0000 with message-id <e1sxepv-007frm...@fasolo.debian.org> and subject line Bug#1083112: fixed in samhain 4.1.4-3 has caused the Debian Bug report #1083112, regarding O: samhain -- Data integrity and host intrusion alert system 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.) -- 1083112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: wnpp Severity: normal X-Debbugs-Cc: samh...@packages.debian.org Control: affects -1 + src:samhain The current maintainer of the samhain package is apparently not active anymore or has no time to maintain this specific package. Thus, filing this bug. Also see #1082808. The package description is: Samhain is an integrity checker and host intrusion detection system that can be used on single hosts as well as large, UNIX-based networks. It supports central monitoring as well as powerful (and new) stealth features to run undetected on memory using steganography. . Main features * Complete integrity check + uses cryptographic checksums of files to detect modifications, + can find rogue SUID executables anywhere on disk, and * Centralized monitoring + native support for logging to a central server via encrypted and authenticated connections * Tamper resistance + database and configuration files can be signed + logfile entries and e-mail reports are signed + support for stealth operation
--- End Message ---
--- Begin Message ---Source: samhain Source-Version: 4.1.4-3 Done: Javier Fernández-Sanguino Peña <j...@debian.org> We believe that the bug you reported is fixed in the latest version of samhain, 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 1083...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña <j...@debian.org> (supplier of updated samhain 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: SHA256 Format: 1.8 Date: Sun, 06 Oct 2024 01:41:16 +0200 Source: samhain Architecture: source Version: 4.1.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools <team+pkg-secur...@tracker.debian.org> Changed-By: Javier Fernández-Sanguino Peña <j...@debian.org> Closes: 843304 865574 866278 900202 999967 1007320 1066529 1082808 1083112 10337089 Changes: samhain (4.1.4-3) unstable; urgency=medium . * Acknowledge NMUs (Closes: #1066529, #999967, #1007320, #843304) * Update the package and fix open bugs, to ensure it is properly supported now the package is team maintained (Closes:#1082808, #1083112) * debian/rules: - Remove libprelude from the configuration as libprelude does not support Python 3.13 (see #1081473) - Fix the call to dh_install to properly install the configuration file * debian/samhain.logrotate: Rename the file so it is installed by dh_installlogrotate and remove it from dh_install * debian/samhain.install: adjust the contents of the file * debian/control: - Update debhelper version and Standards version - Change the Maintainer field to make this a package managed by the pkg-security team - Remove libprelude dependency - Add location of VCS in Salsa * debian/samhain.service: Have samhain start through the PIDfile so integrity database gets created if it does not exist. Otherwise it will never start properly on a fresh install * Remove debian/compat as we set the debhelper level in debian/control * debian/po: Convert all files in ISO-8859 encoding to UTF-8 * debian/README.Debian: Convert to UTF-8 * debian/config, debian/preinst: Do not ignore errors in maintainer scripts (lintian fix) (Closes: #866278) * debian/rules: Fix FTCBFS: Pass --build and --host to ./configure with patch provided by Helmut Grohne (Closes: #900202) * debian/po/ro.po: Add Romanian translation (Closes: #10337089) * debian/samhain.init: Add short description to the init.d file so that the service name is properly logged into console (previously it would say 'null' (Closes: #865574) * Add new patches: - debian/patches/configure_fixes.patch: Fix the autoconfiguration of the sources to work with the latest autoconf version in unstable - debian/patches/realclean: Clean properly the sources and autogenerated files - debian/patches/improve_errors: Improve the errors shown when samhain cannot start due to the database not existing (which needs to be initialise) as this is shown to the users when the service is attempted to be started but no database yet exists. Also improve the error shown when the configuration file does not exist. Checksums-Sha1: 7c57fd8d076a2b97f10476b548917344fb7f9c8b 2029 samhain_4.1.4-3.dsc d25b117e21d97b14a3790022d72917bfddbe30a9 96900 samhain_4.1.4-3.debian.tar.xz 77444bd7847f139e2913e0a3477614e61a46050e 7516 samhain_4.1.4-3_i386.buildinfo Checksums-Sha256: 0f11adf2db1bd485d6e1bb22aabf70c693c31a913a4f20ab2129d85345859ad3 2029 samhain_4.1.4-3.dsc 4cd41e3adf3c742969386e66e48579364f85f9664e5e9db4d31e779bdb8c2350 96900 samhain_4.1.4-3.debian.tar.xz ef7b23704cdb993ad13395088cfe864de4582845a49bdedef3fea5f2d4ece847 7516 samhain_4.1.4-3_i386.buildinfo Files: 8c5047dfea8b690c77c11f4ecbcf5174 2029 admin optional samhain_4.1.4-3.dsc ebe12402e543741f31a2b4e21468fda9 96900 admin optional samhain_4.1.4-3.debian.tar.xz 93f2f81effa5819ce149fbf132cddfa4 7516 admin optional samhain_4.1.4-3_i386.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAmcBzw8ACgkQix9vSKsl f5ii7xAAjetT9+Fs1L6HwgPjUu4tmmI9eEReTPn4ZeXiZeaNRa7MDLtJhkU8c4PE OjYJUJEqxiLtlteBKR2YQMxn9mRIhpcVNPZ2QcCzQhCRojajOEcWh5nPzVdgtHUx bi73AU5qXSWj0qFJEIfgqR7hEBMHCaGh4q+33vYHBx2SAVyX4jAnre4OGKBCW2Qc 5rdhdOvJOFrJQZLhy44lUGe/e9p9/XYHIptjaOKQEzHyF/wQ4hn9nPc59z9SMpxs k/pa/+oWmp37fmoy++nWScT+3vg4OpY08U9VFe5GcVufakudmglWzwuBYeYZTYtK CzaIiPsl9Ay9aPi3h/RVrIdk+8mKspA8A6DCh4WErixb1UhV4uaLuFjjC8hY3acW C1xC3HEQNxO4eGO16rid9Qwy41VCi6b0265FBo4rGv53NN0rgXvgmR37XDLgO7Wr /CACnGD/vzWNb9l5dgsyZe8bwLaDwYfe2zFOyBTPMsRD1G4ayC3knEeBUnra32tU eSuro+aVCfbkQaoEGgyxDaTkd5cduyCVIodB7cyn4iBfhb8rJWxv31kC8xFWFCtb AyW2lZVsagoXHDJsEp/CyHH2qtLt4juj3lznCvt2zDG/WyYrtynAgQUme9jHVwQC VFokbl5vM6cilCOUmcTob9C5dyz4F0otTClVvBwRIHJThFqsQMU= =9iRf -----END PGP SIGNATURE-----
pgpkfIUyuei_o.pgp
Description: PGP signature
--- End Message ---
