ihatelinux@sh.itjust.works to Linux@lemmy.ml · 4 months agoDoes any distro read through 100% of the source-code of a package before adding it to its repo?message-squaremessage-square57fedilinkarrow-up1121arrow-down19
arrow-up1112arrow-down1message-squareDoes any distro read through 100% of the source-code of a package before adding it to its repo?ihatelinux@sh.itjust.works to Linux@lemmy.ml · 4 months agomessage-square57fedilink
minus-squarelily33@lemm.eelinkfedilinkarrow-up25·4 months agoFinally, presumably if anyone added some malicious code in a their program, it would be sneaky and not obvious from quickly reading the code.
minus-squareNorgur@kbin.sociallinkfedilinkarrow-up38·4 months agoI’d expect them to properly comment it with “#-------Begin malicious shit--------”. COMMENT YOUR CODE, PEOPLE!
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up21·4 months agoThe exploit should be written in a way that it is obvious and doesn’t need commenting!
minus-squarelily33@lemm.eelinkfedilinkarrow-up14·edit-24 months agoOh, in that case we don’t need to read either - just run a simple grep!
minus-squareNorgur@kbin.sociallinkfedilinkarrow-up11·4 months agoThose malicious coders are too sly for that. Some write “Sh1t” to throw grep off, others even do a “B3g1n”… They are always one step ahead!
minus-squarelily33@lemm.eelinkfedilinkarrow-up5·4 months agoGood point. I’d try to grep for something like [Bb3][Ee3]g[Ii1][nη]\w+<and so on> but I just know I’ll miss something
minus-squarebanazir@lemmy.mllinkfedilinkarrow-up12·4 months agoWell yeah, the recent xz vulnerability was not present in the source code at all. Any amount of code reading would not have caught that one.
minus-squareSuccessful_Try543@feddit.delinkfedilinkarrow-up3·edit-24 months agoWasn’t the problem that it the backdoor was not present in the source code on GitHub, but was in the source tarball? So as long as one reads the code that one actually builds from should be fine.
minus-squareSuperIce@lemmy.worldlinkfedilinkEnglisharrow-up6·4 months agoA line of code that enables the backdoor was out present in the tarball. The actual code was obfuscated within an archive used for the unit testing.
minus-squareSuccessful_Try543@feddit.delinkfedilinkarrow-up4·4 months agoOK. So simply reading what was readable wouldn’t have helped. Thanks.
Finally, presumably if anyone added some malicious code in a their program, it would be sneaky and not obvious from quickly reading the code.
I’d expect them to properly comment it with “#-------Begin malicious shit--------”.
COMMENT YOUR CODE, PEOPLE!
The exploit should be written in a way that it is obvious and doesn’t need commenting!
Oh, in that case we don’t need to read either - just run a simple grep!
Those malicious coders are too sly for that. Some write “Sh1t” to throw grep off, others even do a “B3g1n”… They are always one step ahead!
Good point. I’d try to grep for something like
[Bb3][Ee3]g[Ii1][nη]\w+<and so on>but I just know I’ll miss somethingWell yeah, the recent xz vulnerability was not present in the source code at all. Any amount of code reading would not have caught that one.
Wasn’t the problem that
itthe backdoor was not present in the source code on GitHub, but was in the source tarball? So as long as one reads the code that one actually builds from should be fine.A line of code that enables the backdoor was out present in the tarball. The actual code was obfuscated within an archive used for the unit testing.
OK. So simply reading what was readable wouldn’t have helped. Thanks.