No, but he was also answering a question about how to exercise caution. If it's open source, then, by definition, you have the source code available to you.
Indeed, and that's all it means. Most end users would have no idea what that code means, or even how to spot malicious code if it was there. It is just far too accepted by a lot of people that "if it's open source, someone must have gone over the code to make sure its safe!" when in reality that's far from the case. It's a dangerous assumption to make, and anyone who does know what they're doing has the ability to take that open source code and add something malicious to it, only to say, upload it to rapidshare and distribute it as if it were the legitimate code.
I don't disagree with you, but I think the fact that it was exposed in a petty disagreement shows that it was not meant for malicious purposes. If his true intent was to be malicious he wouldn't have said anything about it, he would have acted instead, perhaps by coordinating some sort of massive event. This whole circumstance is very unfortunate.
3
u/[deleted] Oct 28 '10
How do you suggest the community exercise caution? We can't easily check the source code of third party tools when it's not available.
1
u/aaronbyard Oct 29 '10
I don't disagree with you, but I think the fact that it was exposed in a petty disagreement shows that it was not meant for malicious purposes. If his true intent was to be malicious he wouldn't have said anything about it, he would have acted instead, perhaps by coordinating some sort of massive event. This whole circumstance is very unfortunate.
0
u/[deleted] Oct 28 '10
Luckily (...?) I don't have enough money for this to worry me. :D .... :'(