{"id":181894,"date":"2026-06-04T02:49:02","date_gmt":"2026-06-04T00:49:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/regressii-v-rsync-3-4-3-i-prinyatie-izmenenij-podgotovlennyh-s-ispolzovaniem-ai"},"modified":"2026-06-04T02:49:02","modified_gmt":"2026-06-04T00:49:02","slug":"regressii-v-rsync-3-4-3-i-prinyatie-izmenenij-podgotovlennyh-s-ispolzovaniem-ai","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/regressii-v-rsync-3-4-3-i-prinyatie-izmenenij-podgotovlennyh-s-ispolzovaniem-ai","title":{"rendered":"Regressions in rsync 3.4.3 and acceptance of changes prepared using AI","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After the release of the rsync 3.4.3 update, which fixed 6 vulnerabilities, regressions that disrupt previously used configurations have been noted. Additionally, the addition of approximately 50 changes prepared using the AI model Claude over the last two weeks has caused misunderstanding and dissatisfaction among users. Some users have linked the emergence of these regressions to the generation of low-quality vulnerability fixes using AI.<\/p>\n
Some of the regressions in rsync 3.4.3:<\/p>\n
\n
The command for incremental backups that specified multiple options \u2014compare-dest\u2014 has started to fail.\n
Became \nit's impossible to build rsync on systems with Linux kernels older than version 5.6 due to the invocation of the openat2 system call (commit 1, commit 2);<\/p>\n
The format 'host::module\/path' has stopped working (commit).\n
Commands using the option \n\u2014delete-missing-args\u2014 together with \u2014files-from\u2014 (commit).<\/p>\n
During synchronization, errors about finding modtime_nsec values outside the permitted range began to appear.\n
Builds on older versions of macOS were disrupted.\n
The behavior of the \u2014link-dest\u2014 option has changed (commit).\n
Crashes occurred when starting in the terminal multiplexer tmux.\n<\/ul>\n
Andrew Tridgell, founder of the Samba and rsync projects, who returned to maintain rsync two years ago and added the problematic commits, published a note explaining the current situation. According to Andrew, the rsync project faced a flood of vulnerability reports, many of which were generated by AI. In the release of rsync 3.4.3, the emergence of regressions became the price of eliminating vulnerabilities. Andrew consciously chose to fix the vulnerabilities, despite the fact that the fixes might disrupt some rare but valid use cases of rsync. Such scenarios were not covered by the old test suite and manual checks, so the regressions went unnoticed and will be addressed in the next release, 3.4.4.<\/p>\n
The situation prompted Andrew to upgrade the test suite, implement code coverage checks, and establish testing within the continuous integration system across various platforms, along with conducting potential vulnerability analyses. As Andrew is nearly 60 years old and would prefer to sail on a yacht rather than spend his time patching vulnerabilities in rsync, he decided to bring in AI assistants for routine tasks amidst an avalanche of vulnerability reports. Andrew devised the architecture, testing plan, and structure for the new test suite, after which he used AI to generate it in Python, replacing the previously used test shell script. The development employed the Claude model with manual result checks and cross-verification in Codex and Gemini. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"