• ZephrC@lemm.ee
    1192·
    8 months ago

    OpenSUSE Tumbleweed has it. The Fedora 40 beta has it. Its just a result of being bleeding edge. Arch doesn’t have exclusive rights to that.

  • fl42v@lemmy.ml
    1151·
    8 months ago

    Incorrect: the backdoored version was originally discovered by a Debian sid user on their system, and it presumably worked. On arch it’s questionable since they don’t link sshd with liblzma (although some say some kind of a cross-contamination may be possible via a patch used to support some systemd thingy, and systemd uses liblzma). Also, probably the rolling opensuse, and mb Ubuntu. Also nixos-unstalbe, but it doesn’t pass the argv[0] requirements and also doesn’t link liblzma. Also, fedora.

    Btw, https://security.archlinux.org/ASA-202403-1

    • SpaceCowboy@lemmy.ca
      192·
      8 months ago

      Sid was that dickhead in Toystory that broke the toys.

      If you’re running debian sid and not expecting it to be a buggy insecure mess, then you’re doing debian wrong.

      • fl42v@lemmy.ml
        51·
        8 months ago

        Unlike arch that has no “stable”. Yap, sure; idk what it was supposed to mean, tho.

      • milicent_bystandr@lemm.ee
        2·
        8 months ago

        Yes, but Arch, though it had the compromised package, it appears the package didn’t actually compromise Arch because of how both Arch and the attack were set up.

  • lemmyvore@feddit.nlEnglish
    882·
    8 months ago

    I thought Arch was the only rolling distro that doesn’t have the backdoor. Its sshd is not linked with liblzma, and even if it were, they compile xz directly from git so they wouldn’t have gotten the backdoor anyway.

    • angel@iusearchlinux.fyi
      312·
      8 months ago

      TBF they only switched to building from git after they were notified of the backdoor yesterday. Prior to that, the source tarball was used.

    • qwioeue@lemmy.worldOP
      254·
      8 months ago

      liblzma is the problem. sshd is just the first thing they found that it is attacking. liblzma is used by firefox and many other critical packages.

      • Rustmilian@lemmy.worldEnglish
        32·
        8 months ago

        Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command:

        ldd "$(command -v sshd)"
        • qwioeue@lemmy.worldOP
          1710·
          8 months ago

          Yes, this sshd attack vector isn’t possible. However, they haven’t decomposed the exploit and we don’t know the extent of the attack. The reporter of the issue just scratched the surface. If you are using Arch, you should run pacman right now to downgrade.

          • Fubarberry@sopuli.xyzEnglish
            35·
            8 months ago

            They actually have an upgrade fix for it, at least for the known parts of it. Doing a standard system upgrade will replace the xz package with one with the known backdoor removed.

          • HopFlop@discuss.tchncs.de
            15·
            8 months ago

            If you are using Arch, you should run pacman right now to downgrade.

            No, just update. It’s already fixed. Thats the point of rolling release.

        • bitwolf@lemmy.one
          11·
          8 months ago

          Do not use ldd on untrusted binaries.

          I executed the backdoor the other day when assessing the damage.

          objdump is the better tool to use in this case.

    • Possibly linux@lemmy.zipEnglish
      3·
      8 months ago

      The extent of the exploit is still being analyzed so I would update and keep your eye on the news. If you don’t need your computer you could always power down.

    • Possibly linux@lemmy.zipEnglish
      5·
      8 months ago

      It is not entirely clear either this exploit can affect other parts of the system. This is one those things you need to take extremely seriously

    • chrash0@lemmy.world
      132·
      8 months ago

      i think it’s a matter of perspective. if i’m deploying some containers or servers on a system that has well defined dependencies then i think Debian wins in a stability argument.

      for me, i’m installing a bunch of experimental or bleeding edge stuff that is hard to manage in even a non LTS Debian system. i don’t need my CUDA drivers to be battle tested, and i don’t want to add a bunch of sketchy links to APT because i want to install a nightly version of neovim with my package manager. Arch makes that stuff simple, reliable, and stable, at least in comparison.

      • laurelraven@lemmy.blahaj.zone
        112·
        8 months ago

        “Stable” doesn’t mean “doesn’t crash”, it means “low frequency of changes”. Debian only makes changing updates every few years, and you can wait a few more years before even taking those changes without losing security support while Arch makes changing updates pretty much every time a package you have installed does.

        In no way is Arch more stable than Debian (other than maybe Debian Unstable/Sid, but even then it’s likely a bit of a wash)

      • Possibly linux@lemmy.zipEnglish
        15·
        8 months ago

        If you are adding sources to Debian you are doing it wrong. Use flatpak or Distrobox although distrobox is still affected

      • ZephrC@lemm.ee
        152·
        8 months ago

        It literally does though. Stable doesn’t mean bug free. It means unchanging. That’s what the term “stable distro” actually means. That the software isn’t being updated except for security patches. When people say stable distro, that is what they are trying to communicate. That means the software will be old. That’s what stable actually means.

    • MyNamesNotRobert@lemmynsfw.com
      717·
      8 months ago

      In my experience they’re the same from a reliability standpoint. Stuff on Arch will break for no reason after an update. Stuff on Debian will break for no reason after an update. It’s just as difficult to solve reliability problems on both.

      Because Debian isn’t a rolling release you will often run into issues where a bug got fixed in a future version of whatever program it is but not the one that’s available in the repository. Try using yt-dlp on any stable Debian installation and it won’t work for example.

      Arch isn’t without its issues. Half of the good stuff is on the AUR, and fuck the AUR. Stuff only installs without issues half the time. Good luck installing stuff that needs like 13+ other AUR packages as dependencies because non of that shit can be installed automatically. On other distros,all that stuff can be installed automatically and easily with a single command.

      I use Arch btw.

      • AHemlocksLie@lemmy.zip
        4·
        8 months ago

        You can get yay for an AUR package manager, but it’s generally not recommended because it means blindly trusting the build scripts for community packages that have no real oversight. You’re typically advised to check the build script for every AUR package you install.

        • scoobford@lemmy.zip
          1·
          8 months ago

          I’ve had the exact opposite experience. I switched to Arch when proton came out, and I haven’t had a system breakage since that wasn’t directly caused by my actions.

          Debian upgrades would basically fail to boot about 20% of the time before that.

      • dan@upvote.au
        3·
        8 months ago

        Stuff on Debian will break for no reason after an update

        I have never had this happen on Debian servers and I’ve been using it for around 20 years. The only time I broke a Debian system was my fault - I tried to upgrade an old server from Debian 10 to 12. It’s only supported to upgrade one version at a time. Had to restore from backup and upgrade to Debian 11 first, then to 12.

        • pathief@lemmy.world
          8·
          8 months ago

          I heard this so many times that I really believed arch was so brittle that my system would become unbootable if I went on vacation. Turns out updating it after 6 months went perfectly fine.

          • bruhduh@lemmy.world
            1·
            8 months ago

            I updated arch after two months and it broke completely, i guess it’s because i had unfathomable amount of packages and dependencies, so it varies from person to person, if you keep your system light then it may work like it worked for you, if you install giant amount of packages and dependencies then it would work like it worked for me

          • Possibly linux@lemmy.zipEnglish
            1·
            8 months ago

            But didn’t it take a while? Not that it wouldn’t take a while on Debian but Debian doesn’t push so many updates

            • pathief@lemmy.world
              2·
              8 months ago

              It took a bit more than usual but nothing unreasonable. 3 to 5 minutes at most, in an old MacBook pro.

  • Allero@lemmy.today
    642·
    8 months ago

    Arch is not vulnerable to this attack vector. Fedora Rawhide, OpenSUSE Tumbleweed and Debian Testing are.

  • carl://@upload.chat
    50·
    8 months ago

    Arch has already updated XZ by relying on the source code repository itself instead of the tarballs that did have the manipulations in them.

    It’s not ideal since we still rely on a potentially *otherwise* compromised piece of code still but it’s a quick and effective workaround without massive technical trouble for the issue at hand.

    • A_Very_Big_Fan@lemmy.worldEnglish
      4·
      8 months ago

      instead of the tarballs that did have the manipulations in them

      My only exposure to Linux is SteamOS so I might be misunderstanding something, but if not:

      How in the world did it get infected in the first place? Do we know?

      • khannie@lemmy.worldEnglish
        8·
        8 months ago

        From what I read it was one of the contributors. Looks like they have been contributing for some time too before trying to scooch in this back door. Long con.

      • HopFlop@discuss.tchncs.de
        4·
        8 months ago

        Basically, one of the contributors that had been contributing for quite some time (and was therefore partly trusted), commited a somewhat hidden backdoor. I doubt it had any effect (as it was discovered now before being pushed to any stable distro and the exploit itself didnt work on Arch) bjt we’ll have to wait for the effect to be analyzed.

  • yuki!@lemmy.worldEnglish
    471·
    8 months ago

    Bro WTF. How about you actually read up on the backdoor before slandering Arch. The backdoor DOES NOT affect Arch.

  • RegalPotoo@lemmy.worldEnglish
    483·
    8 months ago

    https://arstechnica.com/security/2024/03/backdoor-found-in-widely-used-linux-utility-breaks-encrypted-ssh-connections/

    There are no known reports of those versions being incorporated into any production releases for major Linux distributions, but both Red Hat and Debian reported that recently published beta releases used at least one of the backdoored versions […] A stable release of Arch Linux is also affected. That distribution, however, isn’t used in production systems.

    Ouch

      • Kata1yst@kbin.social
        12·
        8 months ago

        I think the confusion comes from the meaning of stable. In software there are two relevant meanings:

        1. Unchanging, or changing the least possible amount.

        2. Not crashing / requiring intervention to keep running.

        Debian, for example, focuses on #1, with the assumption that #2 will follow. And it generally does, until you have to update and the changes are truly massive and the upgrade is brittle, or you have to run software with newer requirements and your hacks to get it working are brittle.

        Arch, for example, instead focuses on the second definition, by attempting to ensure that every change, while frequent, is small, with a handful of notable exceptions.

        Honestly, both strategies work well. I’ve had debian systems running for 15 years and Arch systems running for 12+ years (and that limitation is really only due to the system I run Arch on, rather than their update strategy.

        It really depends on the user’s needs and maintenance frequency.

    • mlg@lemmy.worldEnglish
      25·
      8 months ago

      Very common compression utility for LZMA (.xz file)

      Similar to .gzip, .zip, etc.

      • dan@upvote.au
        4·
        8 months ago

        It’s definitely common, but zstd is gaining on it since in a lot of cases it can produce similarly-sized compressed files but it’s quicker to decompress them. There’s still some cases where xz is better than zstd, but not very many.

    • teegus@sh.itjust.works
      192·
      8 months ago

      People doesn’t even know what a rootkit XZ is, why should they care? -Sony CEO probably

  • JATth@lemmy.world
    51·
    8 months ago

    I just did: “rm -rf xz”

    pacman -Syu
find / -name "*xz*"  | sort | grep -e '\.xz$' | xargs -o -n1 rm -i 
pacman -Qqn | pacman -S -

    (and please, absolutely don’t run above as root. Just don’t.) I carefully answered to retain any root owned files and my backups, despite knowing the backdoor wasn’t included in the culprit package. This system has now “un-trusted” status, meaning I’ll clean re-install the OS, once the full analysis of the backdoor payload is available.

    Edit: I also booted the “untrusted” system without physical access to the web, no gui, and installed the fixed package transferred to it locally. (that system is also going to be dd if=/dev/zero'd)