News for hackers. Stuff that matters.
Re:Sourceforge Hijacks the Nmap Sourceforge Account by heyalexej on Wednesday June 03, 2015 @05:30AM (#9651448)
Plenty popular names on there. That's shocking.
Re:Sourceforge Hijacks the Nmap Sourceforge Account by ghshephard on Wednesday June 03, 2015 @05:52AM (#9651528)
To be clear - there is a difference between mirroring (which is good netizen behavior, and to be complimented), and trojaning (which is modifying the upstream sources before delivering them to users - which is decidedly not good netizen behavior).

It's important to understand which is which for those accounts.

Re:Sourceforge Hijacks the Nmap Sourceforge Account by dagw on Wednesday June 03, 2015 @06:23AM (#9651620)
As long as one of those accounts is trojaning (or even just suspected of possibly having been trojaning once) it instantly poisons all the mirrors. Even if they are perfect netizens 99% of the time, that 1% makes all their other efforts useless.
Re:Sourceforge Hijacks the Nmap Sourceforge Account by DaFranker on Wednesday June 03, 2015 @08:38AM (#9652059)
Whoa what. Are you suggesting that suspicion of possibly maybe having put a trojan in someone else's files somewhere is grounds to make all one's efforts useless and poisons everything else you do?

Geeze, I guess we should stop using Google. They've been accused and suspected of much worse by a lot of people. I hope that's not what you meant.

Re:Sourceforge Hijacks the Nmap Sourceforge Account by dagw on Wednesday June 03, 2015 @08:46AM (#9652093)
Are you suggesting that suspicion of possibly maybe having put a trojan in someone else's files somewhere is grounds to make all one's efforts useless and poisons everything else you do?

Short answer: Yes. Downloading and running arbitrary binaries from the web inherently a quite dangerous thing do to, and I only feel comfortable taking such a risk with sites I trust. I no longer trust Sourceforge and there is very little they can promise me to make me start wanting to download from them again.

Re:Sourceforge Hijacks the Nmap Sourceforge Account by DaFranker on Wednesday June 03, 2015 @08:57AM (#9652162)
Er, okay.

Well, I don't agree¹ with your method of evaluating trustworthiness (which seems to me rather too quantized and "chastity"-minded), but at least you know exactly what you're doing and who you're trusting.

[1] Read as "I believe it's sub-optimal for a given cost-benefit formula, after some assumptions about certain variables and certain opportunity costs, and other methods would likely be more useful in context."

Re:Sourceforge Hijacks the Nmap Sourceforge Account by dec0dedab0de on Wednesday June 03, 2015 @10:45AM (#9652923)
suspicion of possibly maybe having put a trojan in someone else's files

Isn't it a hard fact at this point?

Re:Sourceforge Hijacks the Nmap Sourceforge Account by DaFranker on Wednesday June 03, 2015 @02:56PM (#9654944)
For Sourceforge specifically? Sure.

In general, the way the comment was worded? No, suspicion does not equal hard fact.

We were talking about the latter.

Re:Sourceforge Hijacks the Nmap Sourceforge Account by beagle3 on Wednesday June 03, 2015 @06:25AM (#9651630)
No, it is not important at all - because today's mirror will silently be replaced with tomorrow's trojan.

It is important to expose this behavior for what it is.

And in the process, remind everyone that abuse of power is a question of WHEN, not IF, whether it's a government entity or a corporate one.

Re:Sourceforge Hijacks the Nmap Sourceforge Account by rythie on Wednesday June 03, 2015 @09:25AM (#9652313)
Sourceforge's mirrors are a complete miss-use of the term mirror. A mirror should be an exact copy of the source and should be approved by the original project, which I doubt any of these 'mirrors' are.
Re:Sourceforge Hijacks the Nmap Sourceforge Account by hodefoting on Wednesday June 03, 2015 @12:50PM (#9653956)
Interesting weaseling of SourceForge is to add a "downloader" which fetches either the actual unmodified installer/sources. The "downloader" installs adware while fetching the real installer for the software. In the case of GIMP the filename of the downloader was made to be the same as the filename expected of the installer for a given version. This dirty approach might be thwarting ways of protecting with cryptographic signatures, or even trademarks/copyleft.