Live data from Hacker News

Trusting-Trust Attack against an Entire Linux Distribution

arxiv.org

1–10 of 65 posts

Re: Trusting-Trust Attack against an Entire Linux Distribution

#5
This paper can be boiled down to:

If you have malware on your CI machine it can infect the artifacts it creates.

In this paper the malware was a strip trojan, but it could have been just as well a normal piece of malware which starts a service and then waits for the final artifact to be generated after which it infects it.

Re: Trusting-Trust Attack against an Entire Linux Distribution

#6
From TFA:

> Ken Thompson's trusting-trust attack [...] is widely regarded as a threat specific to compilers. We show that it is not

And yet, from Reflections On Trusting Trust:

> In demonstrating the possibility of this kind of attack, I picked on the C compiler. I could have picked on any program-handling program such as an assembler, a loader, or even hardware microcode.

The paper is certainly a nice worked-out example of the attack, which is worthwhile, but it's not novel.

Re: Trusting-Trust Attack against an Entire Linux Distribution

#7

Earlier quoted context omitted.

Nothing about this uses AI in any way. I'm so tired of people injecting it into every conversation.

AI could enable script kiddies to pull this off.

Script kiddies have always been a problem you have to defend against. This is nothing new.

Re: Trusting-Trust Attack against an Entire Linux Distribution

#8
I'm glad they mention Wheeler's work briefly in section 7.2, since it provides a general counter to the trusting-trust attack that a lot of people seem to not know about. They dismiss it as not applying in this case, but I'm not really convinced by their argument. It's true if you only replace the compiler and run in the same environment then it won't help, but IIRC Wheeler's approach treats the environment itself as a parameter to diversify on. So not just the compiler, but also the host/OS, and even the hardware. Thus it's trivial to extend it to strip. Build binutils from source with your bad distro toolchain, fixup with your distro strip, call this build A. Then build binutils from source in a diverse environment, which includes fixup with a diverse stripper, call this B. Then do a rebuild (same diverse environment) but with B's toolchain and stripper, call this C, and compare C with A. Mismatch busts the attack.

Re: Trusting-Trust Attack against an Entire Linux Distribution

#10
post #6

From TFA: > Ken Thompson's trusting-trust attack [...] is widely regarded as a threat specific to compilers. We show that it is not And yet, from Reflections On Trusting Trust : > In demonstrating the possibility of this kind of attack, I picked on the C compiler. I could have picked on any program-handling program such as an assembler, a loader, or even hardware microcode. The paper is certainly a nice worked-out ex…

“Widely regarded” still applies, I think.
Post reply on HN