Live data from Hacker News

Rsync 3.4.3 has hundreds of Claude commits

mastodon.gamedev.place

11–20 of 86 posts

Re: Rsync 3.4.3 has hundreds of Claude commits

#13
post #6
post #3

Currently there are 130 Claude-coauthored commits, and the maintainer seems to not be engaging with any of the recent issues and just pushing more of the "security in depth" fixes that are breaking real features for people.

Citation needed :) That's a bold claim. May be true, but it's a bold one, so something backing it up would be nice.

Go look for yourself, quite a few mention CVEs.

Re: Rsync 3.4.3 has hundreds of Claude commits

#15
post #6
post #3

Currently there are 130 Claude-coauthored commits, and the maintainer seems to not be engaging with any of the recent issues and just pushing more of the "security in depth" fixes that are breaking real features for people.

Citation needed :) That's a bold claim. May be true, but it's a bold one, so something backing it up would be nice.

EDIT: posted on top, see https://news.ycombinator.com/item?id=48334270

Re: Rsync 3.4.3 has hundreds of Claude commits

#17

So, has anyone actually checked if it's just an issue with 3.4.3? Going to back to 3.4.1 skips 3.4.2 which features many contributions that aren't either by Andrew or Claude.

Seems like 3.4.2 was already vibe-maintained: https://github.com/RsyncProject/rsync/commits/v3.4.2

Re: Rsync 3.4.3 has hundreds of Claude commits

#18
Looks fine? most of the commits are tests, ci, docs and issues that could cause memory corruption / hidden bugs rather than any new feature development. Of course it's unfortunate that it caused this bug to surface and it would be curious to investigate exactly why this happened, maybe the "safe" c operations have different (unexpected) behavior instead of immediately pointing out that "ai bad". I think patching issues that could cause future CVE's is pretty important especially because rsyncing a file -> client compromise could be pretty devestating as it often runs unsandboxed.

Everyone is still learning how and how much AI should be used and we shouldn't be too harsh on opensource developers. (edit: if someone hears "you are irresponsible if you don't let claude review your code", it would be pretty natural to let AI review your code and fix issues without knowing the full implications of it)

I suspect this commit: https://github.com/RsyncProject/rsync/commit/4fa7156ccdb2ad3..., appears to be changing behavior and changes like these shouldn't be in a patch version (unless it's an active security exploit).

Re: Rsync 3.4.3 has hundreds of Claude commits

#19
Maybe he got notified from the mythos team of a bunch of vulnerabilities and then followed up using claude. Doesn't seem that unlikely.

What would you do if suddenly there were a dozen exploitable CVEs in your highly used open source project staring you down? Maybe you'd use the tool that found them to patch them as quickly as possible.

Re: Rsync 3.4.3 has hundreds of Claude commits

#20
post #10

It's rather ironic that in profit making enterprises using AI are not only encouraged but also part of KPIs. But in open source it's scourge

I don't think using AI as such is the core problem here. It's the type of use. Vibe coding, brain off coding and blind trust are the issue, and an issue everywhere, just enterprises were never really about quality in the first place. But eventually, they too will generate more crap than they can handle.
Post reply on HN