> This is something that could easily occur with scripting languages, backend systems, open source, closed source, etc. Basically any black-box system that takes in some input could pre-manipulate the input yielding an unknown/unexpected output.
IMO thats why it's a scary attack. It's a really simple idea and there are so many ways to apply it
Re:How to Build an Evil Compiler
by josephcsible on Monday April 18, 2022 @05:49PM
(#31077052)
The key point is that if your system has an evil compiler, building your own compiler from known-good source code will just give you another evil compiler, no matter how many times you do it. It creates a bootstrapping problem for the victim that doesn't have easy solutions.
Perhaps another way to say it-using an evil compiler could bootstrap any kind of malicious code in the compiled artifact whether it’s a compiler or not.
Re:How to Build an Evil Compiler
by josephcsible on Tuesday April 19, 2022 @02:04AM
(#31080103)
No, because if that's all it did, just rebuilding your compiler twice would free you from it.
This is something that could easily occur with scripting languages, backend systems, open source, closed source, etc.
Basically any black-box system that takes in some input could pre-manipulate the input yielding an unknown/unexpected output.