Atemu@lemmy.ml to Linux@lemmy.ml · 7 months agobackdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.comexternal-linkmessage-square99fedilinkarrow-up1525arrow-down15cross-posted to: selfhosted@lemmy.worldprogramming@programming.dev
arrow-up1520arrow-down1external-linkbackdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.comAtemu@lemmy.ml to Linux@lemmy.ml · 7 months agomessage-square99fedilinkcross-posted to: selfhosted@lemmy.worldprogramming@programming.dev
minus-squareSavvyBeardedFish@reddthat.comlinkfedilinkEnglisharrow-up22arrow-down5·7 months agoArchlinux’s XZ was compromised as well. News post Git change for not using tarballs from source
minus-squareflying_sheep@lemmy.mllinkfedilinkarrow-up13·7 months agoNo, read the link you posted: 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)" However, out of an abundance of caution, we advise users to remove the malicious code from their system by upgrading either way.
minus-squareprogandy@feddit.delinkfedilinkarrow-up5arrow-down2·edit-27 months agoI think that was a precaution. The malicious build script ran during the build, but the backdoor itself was most likely not included in the resuling package as it checked for specific packaging systems. https://www.openwall.com/lists/oss-security/2024/03/29/22
Archlinux’s XZ was compromised as well.
News post
Git change for not using tarballs from source
No, read the link you posted:
I think that was a precaution. The malicious build script ran during the build, but the backdoor itself was most likely not included in the resuling package as it checked for specific packaging systems.
https://www.openwall.com/lists/oss-security/2024/03/29/22