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] rsync: Update to version 3.5.2
Date: Wed,  4 Nov 2026 11:55:29 +0100	[thread overview]
Message-ID: <20261104105529.3116687-1-adolf.belka@ipfire.org> (raw)

- Update from version 3.5.1 to 3.5.2
- No change in rootfile
- 1 CVE fix
- Changelog
3.5.2
BUG FIXES:
	- Fixed interrupted `--append` and `--inplace` transfers writing the final
	  256 KiB buffer twice. An interrupted destination now remains a clean prefix
	  which the next transfer can resume or repair.
	- Fixed uploads through `rrsync` when the destination file already exists.
	  Existing files are now reached beneath a pinned parent directory instead of
	  being passed as an unwritable `/proc/self/fd/N` destination.
	- Fixed poor matching performance on large sparse and repeated-block files
	  when duplicate checksum chains exhausted the search limit. Valid basis
	  blocks are no longer hidden behind duplicate entries.
	- Bounded strong-checksum work when a malicious receiver supplies weak
	  checksums that collide with consecutive rolling windows
	  (CVE-2026-119741).
	- Prevented the `--inplace` matcher from advancing its aligned basis index
	  beyond the available checksum entries. This avoids signed overflow on large
	  source files when the peer supplies a small block count.
	- Recovered from failed hard-link creation without aborting or hanging the
	  generator. Remaining members fall back to a fresh hard-link group when the
	  original destination inode cannot accept another link.
	- Prevented an out-of-bounds write while invalidating a sender checksum after
	  a file read error when the negotiated checksum length is zero.
	- Fixed a daemon receiver stack overflow when queued deletion output reached
	  `--max-alloc`. Quiet daemon transfers no longer queue deletion messages
	  unless the client requested them.
	- Fixed a `--files-from` pull from a subdirectory of a daemon module, which
	  read each listed file from the module root instead.  It could send, and with
	  `--remove-source-files` delete, a same-named file the module's filter
	  excludes.
	- Fixed password files whose first line is empty. The parser no longer skips
	  the empty line and uses a later password.
	- Escaped terminal control characters in filenames and diagnostics written to
	  standard output, standard error and log files while preserving printable
	  text in the active locale.
	- Preserved Cygwin and MSYS2 UNC roots during ownership-checked path walks.
	- Restored daemon startup from accepted named Unix sockets on standard input,
	  including filesystem and Linux abstract sockets used for socket activation.
	  Unnamed local socket pairs remain non-daemon channels.
	- Fixed forward-DNS hostname entries in daemon `hosts allow` and `hosts deny`
	  lists for IPv6 peers. Address comparison is now binary and family-aware.
	- Preserved Unix symlink permissions on systems which require `fchmodat()` to
	  change the mode of a symlink rather than its target.
	- Restored builds on systems without `O_CLOEXEC` or `O_DIRECTORY`, including
	  Solaris 10.
ENHANCEMENTS:
	- Added `--nice` to adjust CPU and I/O scheduling priorities for local and
	  remote rsync processes. Daemon clients and rrsync cannot raise server-side
	  priorities.
	- Human-readable output now uses dynamic precision to show three significant
	  digits and appends `i` to binary unit suffixes. `--progress` uses the same
	  formatter for transfer rates and labels byte counts and rates with `B` and
	  `B/s`. Example output includes `46.7M`, `48.8Mi`, `782,448B` and
	  `113,295B/s`. File-list, created-directory and skipped-deletion counts also
	  use thousands separators.
	- Added `--delay-symlinks` to defer creating new and changed symlinks until
	  other transferred files are in place. It implies `--no-inc-recursive` and
	  requires protocol 29 or newer with support on the receiving side. It cannot
	  be combined with `--remove-source-files`, `--hard-links`, `--compare-dest`,
	  `--copy-dest` or `--link-dest`.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/rsync | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/rsync b/lfs/rsync
index 775eae04a..fed91c8e0 100644
--- a/lfs/rsync
+++ b/lfs/rsync
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = Versatile tool for fast incremental file transfer
 
-VER        = 3.5.1
+VER        = 3.5.2
 
 THISAPP    = rsync-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = rsync
-PAK_VER    = 26
+PAK_VER    = 27
 
 DEPS       = libxxhash
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 513d03ddadf484424c90755f8d3a947993fdbac3fd7e7b2cdc675e25096f376d7086318be904efd32071d4ba27a06bdaf2875a2086e94f7bd5a7cc9fbdf065ef
+$(DL_FILE)_BLAKE2 = f869e19d12d2960e670e07558e3e7126728729b3765ba66f645f4434df03af2fca832fb8061055dfc6f5e6d8113fe3296610f218eef620b7a6ac924ff8ba8c4d
 
 install : $(TARGET)
 
-- 
2.56.0



                 reply	other threads:[~2026-11-04 10:55 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=20261104105529.3116687-1-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