Seems like he’s been pushed into using LLMs as a way to cope with the deluge of LLM-generated security reports.

  • ExLisper@lemmy.curiana.net
    link
    fedilink
    arrow-up
    0
    ·
    12 hours ago

    The whole story started because rsync stopped working for some users. That’s “not properly maintained” in my books.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      11 hours ago

      I don’t know the degree to that, but bugs do happen occasionally either way as long as there are changes. In the article, they explain why the changes are necessary. Prioritizing security over no-change-stability seems reasonable and warranted.

      • ExLisper@lemmy.curiana.net
        link
        fedilink
        arrow-up
        0
        ·
        11 hours ago

        The author said:

        yes, there were regressions in some use cases of rsync in the 3.4.3 release. I quite deliberately tried to err on the side of fixing security issues for that release, and there were some valid (but unusual) use cases that got caught up in the changes.

        So as I said, I don’t think it’s fair to scream at him to work harder. I do think it’s fair to worn people that rsync is having issues with stability. The author claims he knows what he’s doing and it’s all on purpose. You are free to trust him and ignore the whole affair. Other people may prefer to look for alternatives.