News for hackers. Stuff that matters.
Re:What we know about the xz Utils backdoor that almost infe... by simiones on Monday April 01, 2024 @09:20AM (#39893887)
I think the point is that all of the code which will get compiled to produce the final binary should be in the repo, and so any generated code that affects the final binary should be in the repo.

The use of autotools or other similar tools, ones that are supposed to generate code on the fly on the final user's machine, make this requirement essentially impossible.

Re:What we know about the xz Utils backdoor that almost infe... by Nullabillity on Monday April 01, 2024 @10:14AM (#39894383)
Your compiler also falls under that bucket, though.
Re:What we know about the xz Utils backdoor that almost infe... by sokoloff on Monday April 01, 2024 @10:36AM (#39894589)
Reference the old Ken Thompson compiler hack to provide a backdoor for Unix logins: https://wiki.c2.com/?TheKenThompsonHack
Re:What we know about the xz Utils backdoor that almost infe... by simiones on Tuesday April 02, 2024 @02:16AM (#39902863)
In this case, we're talking about someone distributing source code for others to compile, so that is out of scope.