In debian/watch no matching files for watch line https://www.clamav.net/download.html /downloads/.*/clamav-(1.3.*).tar.gz
There are 2 open security issues in trixie.
There are 2 open security issues in sid.
commit 7dbfb93f01e201093065727940d5c55a7a712df0 Author: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Date: Tue Aug 27 22:56:29 2024 +0200 Prepare 1.3.1+dfsg-5 Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> commit d06bf521e3620eb26e214cfb585bd89aece12e08 Author: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Date: Tue Aug 27 23:02:39 2024 +0200 d: Add the bin bits for "expired certs patch". Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> commit b1c4a78a05b0ec8bc06d0c7dc45363fa6f322a9f Merge: 32a7447 6bfba1e Author: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Date: Tue Aug 27 23:00:39 2024 +0200 merge patched-unstable into unstable commit 6bfba1ec0ccb0e703a2e01279c73e2158fad7e9c Author: Micah Snyder <micasnyd@cisco.com> Date: Wed Jul 10 16:26:00 2024 -0400 Fix unit test caused by expiring signing certificate The clamscan test "assorted_test.py::TC::test_pe_cert_trust" is about to fail because the "test.exe" test file was signed with a cert set to expire after only 2 years, and it has been 23 months. While attempting to generate a new one that will last 73000 days (200 years), I discovered that any signing certificate set to expire after 2038 will fail the trust-check because the `ca.not_after` variable is maxed out `time_t` incapable of expressing a higher number. To fix this, I've upgraded the variables to `uint64_t`. I also had to replace a bunch of generated signatures to match the new "test.exe". Finally, I noticed that "ca.not_before" was being set to the token[8] instead of token[9], which presumably mean the "NotBefore" field for Trusted and Revoked Certificates was non-functional, as it was treating the "CertSign" boolean as the "NotBefore" value. Fixes: https://github.com/Cisco-Talos/clamav/issues/1300 Patch-Name: Fix-unit-test-caused-by-expiring-signing-certificate.patch
There are 2 open security issues in bookworm.
You can find information about how to handle these issues in the security team's documentation.
Among the 5 debian patches available in version 1.3.1+dfsg-5 of the package, we noticed the following issues:
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.