# rsync updates — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/c49f65bf988af613

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-09-29 15:47 ingested 2026-09-30 02:40

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1wtdoaj/rsync_updates/)

## retained text



```
FYI, rsync has just had an update (pushed to Debian, and most likely to other distros) that addresses CVEs, but also may change its behavior.

The announcement text follows:

> In order to fix 33 CVEs, I have decided to bump the package to 3.5.0 rather
> than backporting all patches individually. After analysing the extra changes
> from the bump, not included in the CVE fixes, I have concluded this approach
> carries the lower amount of risk compared to the alternative.

> This update contains behavior changes, all of which stems from the CVE fixes
> themselves, not exclusive to the version bump. The ones most likely to break
> an existing setup are listed here; /usr/share/doc/rsync/NEWS.md.gz has the
> full list.

> Operator-supplied paths are no longer followed through untrusted symlinks.
> The destination directory and the arguments to --backup-dir, --temp-dir,
> --partial-dir, --link-dest, --compare-dest, --copy-dest, --log-file,
> --password-file, --files-from, --include-from, --exclude-from,
> --write-batch, --read-batch and --filter merge files are now resolved one
> component at a time, following a symlink only when it is owned by root or
> by the user running rsync; one owned by anyone else is refused with
> "refusing to follow a symlink owned by an untrusted user".
> --insecure-links restores the old behaviour, but it is local only and a
> daemon never honours it. For a single trusted module, set
> "insecure links = yes" in that module instead.

> rrsync now refuses --debug on every invocation. When restricted to a
> subdirectory it additionally denies --copy-unsafe-links, passes the new
> --confine-root so the server will not resolve a client-named filter merge
> file outside that directory, and passes --drop-D when receiving, so an
> upload can no longer create devices or special files there ("skipping
> non-regular file"). A plain "rsync -a" otherwise still works.

> --chmod=a+s now sets both the setuid and setgid bits, matching chmod(1);
> it previously set setuid alone.

> rsyncd changes that can change who gets in:
>  * "proxy protocol = true" without "proxy protocol hosts" now rejects
>    every connection and warns at startup, instead of trusting a
>    client-supplied PROXY header.
>  * "hosts deny" now fails closed when a configured hostname cannot be
>    resolved (with "forward lookup", the default), so a host previously
>    admitted by an unresolvable deny entry is now blocked.
>  * "auth users" values that start with a comma now split on commas alone,
>    as documented, so a deny or :ro rule naming a group whose name contains
>    a space now takes effect where it was silently ignored.
>  * "hosts allow" / "hosts deny" patterns now fold case inside a [...]
>    bracket expression as well, so a rule such as [A-Z]* matches hosts it
>    used to miss.
>  * A client-requested --compress-threads is capped at 8.

> rsync-ssl now verifies the server certificate. The default openssl
> backend additionally binds it to the requested hostname, so a certificate
> valid for some other name is now rejected. The stunnel and gnutls
> backends refuse to run unless RSYNC_SSL_CA_CERT is set, or
> RSYNC_SSL_ALLOW_INSECURE_STUNNEL=1 / RSYNC_SSL_ALLOW_INSECURE_GNUTLS=1 is
> set to opt out.

>-- Samuel Henrique <samueloph@debian.org>  Tue, 15 Sep 2026 18:46:30 -0700
```



document fetched 2026-09-30 00:32 · canonical https://reddit.com/r/selfhosted/comments/1wtdoaj/rsync_updates
