2,483 karma · joined October 16, 2009
> 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.
Look, if you don't think code review is worthwhile, don't do it. Just give everybody unfettered permission to merge. But don't pretend to do review if you're not trying to maintain some standard of quality.
Next, we can look into reforming those pesky mass and volume units…
Of course, yes, wind and solar are great. But despite the amazing growth in those sources, we're still burning a huge amount of coal and oil.
You can ask the compiler to dump its intermediate representations, so it might not be too hard to answer the question.
Heh.
Do we know that? The website seems silent on the topic, unless I've missed something.
Purely obscene material is also not protected by the 1st, but since the 1970s, the bar for that has been placed very, very high.
The closest I can think of offhand is that for about a year during the pandemic, Twitter suppressed gratuitous COVID misinformation posts, at the request of the government.