Possibly linux@lemmy.zip to Linux@lemmy.mlEnglish · 8 个月前XZ backdoor in a nutshelllemmy.zipimagemessage-square162fedilinkarrow-up11.22K
arrow-up11.22KimageXZ backdoor in a nutshelllemmy.zipPossibly linux@lemmy.zip to Linux@lemmy.mlEnglish · 8 个月前message-square162fedilink
minus-squarenoddy@beehaw.orglinkfedilinkarrow-up31·8 个月前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.
minus-squarePossibly linux@lemmy.zipOPlinkfedilinkEnglisharrow-up19·8 个月前I think we need focus on zero trust when it comes to upstream software
minus-squarePossibly linux@lemmy.zipOPlinkfedilinkEnglisharrow-up1·8 个月前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
minus-squarebillgamesh@lemmy.mllinkfedilinkarrow-up1·8 个月前this was well hidden. not sure anyone would have spotted this by checking commit log
minus-squarebillgamesh@lemmy.mllinkfedilinkarrow-up1·edit-28 个月前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
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