Why the 30‑Year Guardian of Global Backups Became a Target After Using AI to Patch rsync

1. The 1996 Algorithm Hidden in All Backups

In 1996, Australian National University PhD student Andrew Tridgell and Paul Mackerras designed the rsync algorithm, which transfers only changed file blocks by exchanging lightweight fingerprints, enabling a 4 GB file with a single line change to sync in seconds.

2. A Accidental Git Creator

Tridgell later co‑authored the first version of Samba and, in 2005, helped develop a free alternative to the proprietary BitKeeper used by the Linux kernel. By simply typing help to a BitKeeper server, he exposed its command set, violating the license and prompting BitMover to revoke free access, which forced Linus Torvalds to write Git.

3. Keeping a Promise While a Hidden Threat Lurks

After Wayne Davison, the long‑time rsync maintainer, stepped down in 2024, he called Tridgell for help. Unaware of existing flaws, Tridgell soon faced six newly disclosed security bugs—two from Google Cloud researchers that could be chained for remote code execution with a CVSS score of 9.8—and a seventh from a third‑party.

4. AI‑Generated Reports Flood the Inbox

Tridgell reports that many of the incoming security notices are AI‑generated; they look professional and reference real code but most describe non‑existent issues. Each report must be manually inspected, costing hours that could otherwise be spent fixing genuine bugs.

5. Reinforcing rsync with AI‑Assisted Development

To address the vulnerabilities, Tridgell released rsync 3.4.0 on 2025‑01‑14, quickly followed by 3.4.1 to fix a regression. He rewrote the test suite in Python, added code‑coverage analysis, and set up continuous integration across multiple platforms, using Claude as the primary AI assistant and Codex and Gemini for cross‑checking. All changes were manually reviewed and CI‑tested.

6. The 2026‑05‑20 rsync 3.4.3 Release

Version 3.4.3 fixed six security flaws but introduced compatibility problems for edge‑case configurations that had worked for years. Users reported obscure errors when legacy backup scripts invoked rsync with rarely used parameter combinations.

7. Openrsync Performs Poorly in the New Test Suite

Tridgell evaluated the open‑source replacement openrsync with his AI‑enhanced test suite: out of 98 tests, 85 failed, confirming that openrsync lacks much of rsync’s functionality.

8. Community Backlash and Future Choices

Community members opened issues on GitHub demanding stability, while some accused Tridgell of “wrecking” the software. He now faces a decision: ship 3.4.4 to resolve compatibility glitches or jump to 3.5.0 with broader architectural changes.

9. Reflections on a Single‑Maintainer Model

The piece concludes that after three decades the world’s backup reliability still hinges on one retired developer, highlighting the fragility of relying on a lone maintainer for critical infrastructure.