You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
rrsync refuses "absolute" source path (starting with /) #922
d4c4f67 added a single line to rrsync to "remove multiple leading slashes". By removing all leading slashes, this line ensures that the test for a leading slash four lines further down never succeeds and "absolute" paths below the rrsync base directory are not appended to that base directory anymore. This breaks rsync calls with, e.g., source path /.
I'm not sure #890 is a good fix for this. The fix requires the client to be aware of the restricted path on the server's side, as well specifying an additional argument for rrsync. To me, it seems like a completely different feature that just happens to work as an escape hatch for this issue (alternative to the one provided in the issue description).
I'd like to second @h7x4's comment. This is a breaking change. An rrsync configuration that previously worked will not work without changes after this update.
To make the „fix“ work, I would need to change the configuration of both the server and the client, which in production environments is not always simple to do.
Activity
Revert "gnu: rsync: Update to 3.4.3 [security-fixes]."
tridge commentedon Jun 5, 2026
thanks for the report! fixed in #890 in master
h7x4 commentedon Jun 29, 2026
I'm not sure #890 is a good fix for this. The fix requires the client to be aware of the restricted path on the server's side, as well specifying an additional argument for rrsync. To me, it seems like a completely different feature that just happens to work as an escape hatch for this issue (alternative to the one provided in the issue description).
Instead of doing:
Server:
ForceCommand rrsync -absolute /path/to/restrictedClient:
rsync -r user@host:/path/to/restricted .I'd like the following usecase to work again:
Server:
ForceCommand rrsync /path/to/restrictedClient:
rsync -r user@host:/ .which should sync all the contents of
/path/to/restrictedto.due to the path restriction.flyx commentedon Jul 1, 2026
I'd like to second @h7x4's comment. This is a breaking change. An
rrsyncconfiguration that previously worked will not work without changes after this update.To make the „fix“ work, I would need to change the configuration of both the server and the client, which in production environments is not always simple to do.
Update docs to reflect changed rrsync logic
stapelberg commentedon Aug 1, 2026
I also think the fix does not work. I filed #1037 as a separate issue (because it’s lengthy) with a standalone reproducer and more details.
Update docs to reflect changed rrsync logic (#2026)