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.
It’s a double edged sword, fastest patches and fastest exploits.
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.
Fedora and debian was affected in beta/dev branch only, unlike arch
Unlike arch that has no "stable". Yap, sure; idk what it was supposed to mean, tho.
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.
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.
TBF they only switched to building from git after they were notified of the backdoor yesterday. Prior to that, the source tarball was used.
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.
Interestingly, looking at Gentoo's package, they have both the github and tukaani.org URLs listed:
https://github.com/gentoo/gentoo/blob/master/app-arch/xz-utils/xz-utils-5.6.1.ebuild#L28
From what I understand, those wouldn't be the same tarball, and might have thrown an error.
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.
most stable
How the hell is arch more stable than Debian?
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.
"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)
If you are adding sources to Debian you are doing it wrong. Use flatpak or Distrobox although distrobox is still affected
Just Arch users being delusional. Every recent thread that had Arch mentioned in the comments has some variation of "Arch is the most stable distro" or "Stable distros have more issues than Arch".
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
In the case of Arch the backdoor also wasn't inserted into liblzma at all, because at build time there was a check to see if it's being built on a deb or rpm based system, and only inserts it in those two cases.
See https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27 for an analysis of the situation.
So even if Arch built their xz binaries off the backdoored tarball, it was never actually vulnerable.
Arch is not vulnerable to this attack vector. Fedora Rawhide, OpenSUSE Tumbleweed and Debian Testing are.
Notice normal distros aren't affected
tf is a normal distro?
Distros that have some sort of testing before hitting users. Arch also had the issue of killing Intel laptop displays not to long ago as well.
Maybe using the term "normal distro" is a bit of a stretch but my point is that testing is good.
In this context, I'm going to assume they mean "non-rolling-release"
Non betas/testing probably?
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.
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?
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.
It seems like this contributor had malicious intent the entire time they worked on the project. https://boehs.org/node/everything-i-know-about-the-xz-backdoor
Wow. That is some read.
edit:I keep thinking my jaw can't go any closer to the floor but I keep reading and my jaw keeps dropping.
HOLY COW!
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
Also,
Arch is the most stable
Are you high?
I think the confusion comes from the meaning of stable. In software there are two relevant meanings:
Unchanging, or changing the least possible amount.
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.
It has the freshest packages, ahead of all distros
Let me introduce you to Nixpkgs. Its packages are "fresher" than Arch's by a large margin. Even on stable channels.
And the xz package?
As fresh as the CISA will allow it!
Bro WTF. How about you actually read up on the backdoor before slandering Arch. The backdoor DOES NOT affect Arch.
nixos unstable had it too: https://github.com/NixOS/nixpkgs/pull/300028
I would still be cautious as the details of this exploit have not been ironed out
what even is xz?
Very common compression utility for LZMA (.xz file)
Similar to .gzip, .zip, etc.
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.
People doesn't even know what ~~a rootkit~~ XZ is, why should they care? -Sony CEO probably
Arch users are really just cannon fodder against supply chain attacks.
We're the front line dog. Strike me down so Debian Stable's legacy may live on.
void doesnt have it :3
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)
Hint: :q!
Community rules (click to expand)
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.