Thought this was a good read exploring some how the “how and why” including several apparent sock puppet accounts that convinced the original dev (Lasse Collin) to hand over the baton.

  • xionzui@sh.itjust.works
    link
    fedilink
    arrow-up
    6
    ·
    7 months ago

    i can’t see how paying someone would have changed anything in this scenario.

    we need more people actively reviewing code and release artifacts

    I think you’ve answered your own question there

    • Dunstabzugshaubitze@feddit.de
      link
      fedilink
      arrow-up
      2
      arrow-down
      3
      ·
      7 months ago

      no, the solution is not to pay someone to have someone to blame if shit happens.

      there are a bus load of people involved on the way from a git repo to actuall stuff running on a machine and everyone in that chain is responsible to have an eye on what stuff they are building/packaging/installing/running and if something seems off, it’s their responsibility to investigate and communicate with each other.

      attacks like this will not be solved by paying someone to read source code, because the code in the repo might not be what is going to run on a machine or might look absolutely fine in a vacuum or will be altered by some other part in the chain. and even if you have dedicated code readers, you cant be sure that they are not compromised or that their findings will reach the people running/packaging/depending on the software.

      • xionzui@sh.itjust.works
        link
        fedilink
        arrow-up
        3
        ·
        7 months ago

        Of course you can’t be sure anyone involved, paid or not, isn’t compromised. But if you want more human effort put into a project, people need a reason to do so. Complaining that volunteer contributors don’t spend enough of their time and effort with no compensation isn’t going to solve anything. Maybe AI tools will make that work more available in the near future.