Trusting-Trust Attack against an Entire Linux Distribution
1–10 of 65 posts
Re: Trusting-Trust Attack against an Entire Linux Distribution
#2Re: Trusting-Trust Attack against an Entire Linux Distribution
#3In other words: AI can not be trusted.
Re: Trusting-Trust Attack against an Entire Linux Distribution
#4Re: Trusting-Trust Attack against an Entire Linux Distribution
#5If 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> 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
#7Re: Trusting-Trust Attack against an Entire Linux Distribution
#8Re: Trusting-Trust Attack against an Entire Linux Distribution
#9Re: Trusting-Trust Attack against an Entire Linux Distribution
#10From 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…