Possibly linux to [email protected]English • 2 years agoXZ backdoor in a nutshelllemmy.zipimagemessage-square158fedilinkarrow-up11.23K
arrow-up11.23KimageXZ backdoor in a nutshelllemmy.zipPossibly linux to [email protected]English • 2 years agomessage-square158fedilink
minus-square@[email protected]linkfedilink31•2 years agoThe scary thing about this is thinking about potential undetected backdoors similar to this existing in the wild. Hopefully the lessons learned from the xz backdoor will help us to prevent similar backdoors in the future.
minus-squarePossibly linuxOPlinkfedilinkEnglish19•2 years agoI think we need focus on zero trust when it comes to upstream software
minus-squarePossibly linuxOPlinkfedilinkEnglish1•2 years agoIt is fine to use them just know how they work and check the commit log. That of course requires you to pull from got instead of a tarball
minus-square@[email protected]linkfedilink1•2 years agothis was well hidden. not sure anyone would have spotted this by checking commit log
minus-square@[email protected]linkfedilink1•edit-22 years agoi’m not an expert, but my reading was that it was hidden in a binary used for testing EDIT: oh yeah, i see what you mean
The scary thing about this is thinking about potential undetected backdoors similar to this existing in the wild. Hopefully the lessons learned from the xz backdoor will help us to prevent similar backdoors in the future.
I think we need focus on zero trust when it comes to upstream software
exactly, stop depending on esoteric libraries
It is fine to use them just know how they work and check the commit log.
That of course requires you to pull from got instead of a tarball
this was well hidden. not sure anyone would have spotted this by checking commit log
It was hidden in the Tarball
i’m not an expert, but my reading was that it was hidden in a binary used for testing EDIT: oh yeah, i see what you mean