• MotoAsh@lemmy.world
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    edit-2
    10 months ago

    IIRC, that was more about auditing the “supply chain” of apps and Linux. Some college kids were purposefully trying to get malware on the mainline Linux repo and obviously got themselves banned from touching Linux.

    Otherwise it’s just been normal security vulnerability type stuff? There was also a long-existing bug found in a very common library recently, but that’s very solidly in the normal flow of security research, the bug just happened to be sitting there a while.

    Linux of course is a target and has malware. It’d be completely stupid of attackers to ignore Linux because the vast majority of servers run it. It’s a readily available target with lots of goodies on those servers.

    • thefartographer@lemm.ee
      link
      fedilink
      arrow-up
      9
      ·
      10 months ago

      I don’t think it was just some college kids, I could have sworn their professor was specifically getting his students to perform as bad actors to support some super-biased research papers he was trying to publish.

      • Pika@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        8
        ·
        10 months ago

        Yeah but this wasn’t recent, this one was like 4 or 5 years ago unless it happened again. If I remember correctly it got the entire University’s email address banned from contributing to the kernel

        • thefartographer@lemm.ee
          link
          fedilink
          arrow-up
          5
          ·
          10 months ago

          Oh yeah, I get what you’re saying. Yeah, two completely separate instances. Although, from the sound of it, there are a surprising number of people who seem to think that sabotaging Linux and hacking Linux are the same thing. I mean, I guess a pirate can sail on any ship, right?