• recapitated@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    3 months ago

    The xz infiltration is a proof of concept.

    Anyone who is comforted by the fact they’re not affected by a particular release is misguided. We just don’t yet know the ways in which we are thoroughly screwed.

    • BURN@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      3 months ago

      This is a huge wake up call to OSS maintainers that they need to review code a lot more thoroughly. This is far from the last time we’re going to see this, and it probably wouldn’t have been caught if the attacker hadn’t been sloppy

      • ulterno@lemmy.kde.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        3 months ago

        https://upvote.au/comment/818245

        Nah, I’d say the chap was pretty unsloppy.
        Just that we were lucky that someone found it.

        It’s a good thing that xz is a type of program that people may want to profile.

        But this is an eye opener for people saying that Linux is “secure” (not more secure, but just secure .) because the code has many eyes on it. --> jump to digression.

        This confirms my suspicion that we may be affected by the bystander effect, so we actually have less eyes than required for this.


        digression:

        • of course I don’t mean that this makes Linux less secure than Windows. The point that it makes it more secure than Windows/MacOS or other closed source systems is already apparent.
          • Just that, we can’t consider Linux to be secure (without comparing it to something less secure) as many ppl would, when evangelising Linux.

        My point being, tell the whole truth. The newbie that’s taking your advice will thank you for that later on.

        • BURN@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          3 months ago

          The reason I consider this sloppy is because he altered default behavior. Done properly, an injection like this probably could have been done with no change to default behavior, and we’d be even less likely to have gotten lucky.

          Looking back we can see all the signs pointing to it, but it still took a lot of getting lucky to find it.

          I’ve always considered the “source is open so people can check for vulnerabilities” saying a bit ironic, because I’d bet 99% of us never look, nor could find it if we were looking. The bystander effect is definitely here as we all just assume someone else has audited it.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      I’m just waiting for the backdoor to be found in Firefox and Chromium or some library shared by most applications.

      • Gabu@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        The thing about browsers is that there are so many accidental exploits already, it makes little sense to introduce your own on top of it.

    • GreatDong3000@lemm.ee
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      3 months ago

      I always just assumed all the distros I use have backdoors as a fact of life. I take comfort in not being a person of interest to anyone and just blend in with the crowd. I also don’t use windows because for every backdoor my Debian may have, windows will have 100 more. Servers don’t get hacked all the time because it is not linux->internet, it is linux->bunch of stuff->internet, but I am sure backdoors are there.