Emerald (she/her)Debian security amirite?
u/lukmly013 đź’ľ (lemmy.sdf.org)Your Debian stable system is so ancient you got bigger vulnerabilities to worry about: Panik!
Also the problem was that Debian’s sshd linked to liblzma for some systemd feature to work. This mod was done by Debian team.
DasnapLiblzma balls
UckyBonBut do it in private, don’t let my xz.
The linked version in stable was not impacted.
Delilah (She/Her)Even if you’re using debian 12 bookworm and are fully up to date, you’re still running [5.4.1].
The only debian version actually shipping the vulnerable version of the package was sid, and being a canary for this kind of thing is what sid is for, which it’s users know perfectly well.
There was a comment on Mastodon or Lemmy saying that the bad actor had been working with the project for two years so earlier versions may have malicious code as well already.
danThey did but the malware wasn’t fully implemented yet. They spent quite a while implementing it, I guess to try and make it less obvious.
Distros like gentoo reverted to 5.4.2 for that reason. If debian stable is on 5.4.1 that should be ok.
jabjoeNeedless to say all his work ever will already be being reviewed.
PlexSheepWhat do you mean bigger vulnerabilitirs to worry about in Debian stable?
Mostly a joke about him calling it “ancient”, but there may be some unpatched vulnerabilities in older software. Though there could also be some new ones in newest versions.
Still, unless it’s Alpha/Beta/RC, it’s probably better to keep it up-to-date.
Still, unless it’s Alpha/Beta/RC, it’s probably better to keep it up-to-date.
Scroll ResponsiblyDebian patches security vulnerabilities in stable. They don’t change the version numbers or anything but they do fix security holes.
Possibly linuxDebian responds to security issues in stable within a fairly short window. They have a dedicated security team.