Poisoned Fruit


The classic paper on compilers called “Trusting Trust” sheds light on the most devastating type of attacks
in a computing environment. An attacker altering a compiler binary can make it produce malicious versions of every program it compiles, including itself. Once this is done, the attack remains undetectable in perpetuity:


Apple sunk millions of dollars
into creating LLVM just to undermine GCC and to close off their development chain from developers. The problem with their closed proprietary model is that there can never be a way for users to
verify that their binary copy of the compiler is derived from clean
source code. Apple want to prevent users from seeing the source for
the compiler and spies are taking advantage of this.

Apple also bans GPL software from their Appstore.

This ladies and gentlemen is why the world without GCC would be a very dark place. Revelations like these vindicate Richard Stallman and his philosophy.

To no amazement, the tree of secret proprietary development can only bear the fruits of sabotage. By backdooring the compiler, as they do with Apple’s Xcode, the Intelligence Community is poisoning entire software ecosystems. For them its OK as long as they can get at a few bad apples. See what I did there? 😛

Screw you Apple for viciously attacking Free Software, you reap what you sow.

My favorite part:
“I want to be absolutely clear that we have never worked with any government agency from any country to create a backdoor in any of our products or services. We have also never allowed access to our servers. And we never will,” Cook said last September in announcing Apple’s new privacy policy.

LOL ever heard of PRISM Mr. Cook? What do you mean you “never” allowed access to your servers? Last time I checked all surveillance programs foreign and domestic are still in place and being beefed up as we speak. Before you make privacy Apple’s next marketing gimmick you’d do well to keep up with the headlines.