public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] libarchive: Update to version 3.8.2
Date: Sat, 25 Oct 2025 18:07:55 +0200	[thread overview]
Message-ID: <20251025160755.2578911-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20251025160755.2578911-1-adolf.belka@ipfire.org>

- Update from version 3.8.1 to 3.8.2
- Update of rootfile
- Changelog
    3.8.2
	Security fixes:
	    7zip: Fix out of boundary access (#2668)
	    tar reader: fix checking the result of the strftime (#2719, CVE-2025-25724)
	Notable bugfixes:
	    bsdtar: Allow filename to have CRLF endings (#2717)
	    lib: archive_read_data: handle sparse holes at end of file correctly (#2665)
	    lib: improve filter process handling (#2659)
	    lib: fix error checking in writing files (#2672)
	    lib: handle possible errors from system calls (#2679)
	    lib: avoid leaking file descriptors into subprocesses (#2707)
	    lib: parse_date: handle dates in 2038 and beyond if time_t is big enough
		(#2742)
	    RAR5 reader: fix multiple issues in extra field parsing function (#2713)
	    RAR5 reader: early fail when file declares data for a dir entry (#2716)
	    tar writer: fix replacing a regular file with a dir for
		ARCHIVE_EXTRACT_SAFE_WRITES (#2477)
	    tar reader (Windows): check WCS pathname in header_gnutar before
		overwriting (#2740)
	    tar reader: fix an infinite loop when parsing V headers (#2737)
	    zip writer: fix a memory leak if write callback error early (#2664)
	    zip writer: fix writing with ZSTD compression (#2670)
	    zstd write filter: enable Zstandard's checksum feature (#2678)

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/libarchive | 2 +-
 lfs/libarchive                     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/libarchive b/config/rootfiles/common/libarchive
index 4e9951d27..9e35769e5 100644
--- a/config/rootfiles/common/libarchive
+++ b/config/rootfiles/common/libarchive
@@ -7,7 +7,7 @@
 #usr/lib/libarchive.la
 #usr/lib/libarchive.so
 usr/lib/libarchive.so.13
-usr/lib/libarchive.so.13.8.1
+usr/lib/libarchive.so.13.8.2
 #usr/lib/pkgconfig/libarchive.pc
 #usr/share/man/man1/bsdcat.1
 #usr/share/man/man1/bsdcpio.1
diff --git a/lfs/libarchive b/lfs/libarchive
index 9a4a1af5d..b2d2d80b2 100644
--- a/lfs/libarchive
+++ b/lfs/libarchive
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3.8.1
+VER        = 3.8.2
 
 THISAPP    = libarchive-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 92ce11758ea050c7f5b3b2440566b71d29d4fe3ee90ee3455117585ef629eb7cfbe6f3c67bfb309c38d02118ef8f71c1c30ffe14466bfef7929c6d6134b11fc8
+$(DL_FILE)_BLAKE2 = 4f5ed9afbedccf0f754b38743259a62f45d8407ddea8955e301b79b8c9c7653e633b58998a43d7a4bf8cfd35488b20af76ea8f948267230be0557797513b71a6
 
 install : $(TARGET)
 
-- 
2.51.1



      reply	other threads:[~2025-10-25 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 16:07 [PATCH] core199: Ship libarchive Adolf Belka
2025-10-25 16:07 ` Adolf Belka [this message]

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=20251025160755.2578911-2-adolf.belka@ipfire.org \
    --to=adolf.belka@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