I’m not saying incomprehensible build scripts are good here, my mistake for making it seem that way. I’m not confident that hiding it elsewhere would have been strictly more obvious but it absolutely could have been.
I’ve done some pretty complex C projects and haven’t had build scripts nearly that large. This one seems particularly unwieldy and certainly helped the attacker.
I’m going to be honest, I’m getting a little tired of hearing everyone’s thoughts on the xz backdoor. It’s discouraging and sucks when every detail of the project which, keep in mind, was maintained by one person who fell victim to a social engineering attack, is scrutinized. It makes me concerned about anyone depending on any of my projects.
Especially the comments on things such as the build scripts, which this kind of article seems to gravitate towards. If the build scripts were tiny and checked then the attack vector would have just been different, I’m not even too sure the language mattered. The attack was social engineering, after that it was pretty much project agnostic. xz was targeted cause the maintainer was done working on it and it was heavily depended on.
Impressive! Try getting in touch with the ABC crew or pannenkoek2012! Seeing as many of the levels require: numerous frame-perfect inputs, making tons of object clones, and absurd analog stick precision. I’m sure they’d love to learn how you did it RTA!