public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] clamav: Update to 1.1.1
Date: Sat, 19 Aug 2023 17:45:28 +0200	[thread overview]
Message-ID: <20230819154528.3930634-1-matthias.fischer@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

For details see:
https://blog.clamav.net/2023/07/2023-08-16-releases.html

Excerpts from changelog:
"ClamAV 1.1.1 is a critical patch release with the following fixes:

    CVE-2023-20197 Fixed a possible denial of service vulnerability
    in the HFS+ file parser. This issue affects versions 1.1.0,
    1.0.1 through 1.0.0, 0.105.2 through 0.105.0, 0.104.4 through
    0.104.0, and 0.103.8 through 0.103.0.

    Fixed a build issue when using the Rust nightly toolchain, which
    was affecting the oss-fuzz build environment used for regression tests.

    Fixed a build issue on Windows when using Rust version 1.70 or newer.

    CMake build system improvement to support compiling with OpenSSL 3.x on
    macOS with the Xcode toolchain. The official ClamAV installers and
    packages are now built with OpenSSL 3.1.1 or newer.

    Removed a warning message showing the HTTP response codes during the
    Freshclam database update process."

Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
 lfs/clamav | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/clamav b/lfs/clamav
index c48c48834..88619afcb 100644
--- a/lfs/clamav
+++ b/lfs/clamav
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = Antivirus Toolkit
 
-VER        = 1.1.0
+VER        = 1.1.1
 
 THISAPP    = clamav-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = clamav
-PAK_VER    = 67
+PAK_VER    = 68
 
 DEPS       =
 
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 6a30558b8e6d2f8d98eb0b990e58ec9a19d7f58b11863ec5dffe97f45c73c1ea8bb0360456193c76d178068ee5eb7f01fc44851eb7bf90d42ca9dd9431413a4f
+$(DL_FILE)_BLAKE2 = 880318a2be3dcc8bc425cd6d7bbc4fb2b6dd28e9f491dcac382e8a9ff7c0229d846512127c6e10a1e1aa7daa5ac53a5284462e341f29725269f8862e73310caa
 
 install : $(TARGET)
 
-- 
2.34.1


                 reply	other threads:[~2023-08-19 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230819154528.3930634-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox