News for hackers. Stuff that matters.
Re:Mise: Dev tools, env vars, task runner by jdxcode on Sunday December 08, 2024 @06:35PM (#42361713)
> And where are those mystery meat binaries supposed to come from?

the vendor

Re:Mise: Dev tools, env vars, task runner by Nullabillity on Sunday December 08, 2024 @06:39PM (#42361725)
Right, because that never goes wrong.[0,1]

[0]: https://news.ycombinator.com/item?id=42351722

[1]: https://tukaani.org/xz-backdoor/

Re:Mise: Dev tools, env vars, task runner by goku12 on Sunday December 08, 2024 @10:06PM (#42362739)
The xz example does not support your case. Not only was every downstream build infected until it was discovered, it also needed a distro-specific modification (to openssh in Debian and Fedora, IIRC) to work at all.
Re:Mise: Dev tools, env vars, task runner by Nullabillity on Sunday December 08, 2024 @11:41PM (#42363122)
The xz backdoor relied on a discrepancy between the development repository and the released (source) artifact.

While skipping the released tarballs wouldn't have prevented the problem entirely, it would have made it much harder to hide.