121
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Mar 2024
121 points (96.2% liked)
Sysadmin
7694 readers
326 users here now
A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world
founded 1 year ago
MODERATORS
Wow, thank you for sharing this! Grumblegrumble have to reinstall my system...
This straight on the back of a thread about flatpak verification and security - a reminder that a lot of the incredible work of a distribution, especially Debian, is a community of people curating packages with care, and not just for how quick they can be made to work together.
Also a highlight for the work toward fully replicatable systems - if I understand right, the exploit here was snuck in in the binary, not in the source code.
Well you only have to reinstall if you had affected versions installed.
For e.g. Debian stable, thats not the case. Or e.g. Arch sshd doesnt link to xz, so thats not a concern there.
Most systems wont be affected because their sshd doesnt link xz, didnt update to that version yet or simply isnt accessible from the outside.
Though it does show how vulnerable critical packages can be and how much better we need to protect them.
No, it was snuck into the website download of the source code. If you got it from GitHub it was fine, if you got it from their website you got pwnd
That's not correct as far as I can tell. The backdoored code ended up in release tarballs (but not source tarballs because of
autoconffuckery), see eg. this mailing list discussion.Ah, you’re right. I wasn’t aware they had release tars on GitHub as well