• sp3ctr4l@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    4 days ago

    It does happen occasionally, from time to time, but, because everything is gasp open source, it tends to get caught, identified, blocked/quarantined and then fixed considerably more rapidly, with decent fallback instructions/procedures in that interim period.

    Like apparently it actually just recently happened with some asshole uploading bs malware libs/sources to the AUR… even still, got caught pretty quickly.

    Also, you can basically describe the entire CrowdStrike fiasco as exactly this kind of upstream oopsie doopsie.

    Doesn’t really matter in the big picture if it was intentionally malicious or not, when you Y2K 1/4 of the world’s computer systems.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 hour ago

      Exactly.

      When there’s a high profile bug in an important FOSS project, everyone and their dog is looking for a fix. Usually it’ll be patched within days, if not hours, of being reported.

      When there’s a high profile bug in a closed size source project, the company backing it will deflect and delay until they’re forced to fix it, and they can sometimes get away with it for years or even decades.

      All software has bugs, which remain strategy do you prefer?

      • sp3ctr4l@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        31 minutes ago

        I mean, myself personally, I prefer to simp and fanboy for my favorite exploitative corperate overlord, because I’m sure there are good reasons everyone uses them, despite their well documented history of massive fuckups and fuckovers of all possible kinds!

        /s