Changelog: https://download.samba.org/pub/rsync/NEWS#3.5.0
Security: CVE-2026-29518
Security: CVE-2026-43617
Security: CVE-2026-43618
Security: CVE-2026-43619
Security: CVE-2026-43620
Security: CVE-2026-45232
Details
Details
Diff Detail
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 75550 Build 72433: arc lint + arc unit
Event Timeline
Comment Actions
The rsync project has released a security release this month, featuring major internal changes to address multiple CVE issues.
As expected, this update breaks the file flag patch ported to version 3.4.4.
I have successfully ported most of the code to the new version and having some doubts,
I use Claude LLM to review my changes and to add regression tests for the file flags feature.
The synthesis of the changes made by the LLM are available here: https://people.freebsd.org/~rodrigo/rsync_ff_changes_claude_report.md
Currently, the rsync v3.5.0 port builds successfully and passes the existing rsync non-regression tests, including the new file-flag test.
Comment Actions
Can you please submit the patch upstream?
| net/rsync/Makefile | ||
|---|---|---|
| 98 | You should use shebangfix instead. | |
| net/rsync/Makefile | ||
|---|---|---|
| 98 | This line does not only fix the shebang, it cover a few other cases testsuite/fleettest.py has multiple directs calls to python3 testsuite/<another_script>.py testsuite/rrsync-symlink_test.py and testsuite/daemon-namecvt-newline-token_test.py generate a python script wit its own shebang fake_rsync.write_text(
"#!/usr/bin/env python3\n"
"import sys\n"
"try:\n"testsuite/file-flags_test.py use env, which is not corrected by the sebangfix #!/usr/bin/env python3 | |
Comment Actions
Revert changes done by claude to the manpage source to match the original version.
And since 780d5edd16d3542e9946905cec8d8028772e5724 the manpage is not generated
during the build anymore, create a patch to fix the pre-generated one.