News for hackers. Stuff that matters.
Re:China's Man-On-the-Side Attack on GitHub by nailer on Tuesday March 31, 2015 @08:14AM (#9295644)
> Another is that you should never ever have any webpage configured to load any resources from a server hosted within China IP address space as it is vulnerable to this sort of attack by the Chinese government.

Yep. Baidu are a NASDAQ listed company, while they may not be the malicious actor here, they still have a responsibility to ensure their networks are not used to attack others - which they don't seem to be taking seriously.

Until Baidu take steps to ensure their networks are not used to attack others, we should drop their packets: https://news.ycombinator.com/item?id=9295617

Re:China's Man-On-the-Side Attack on GitHub by paraboul on Tuesday March 31, 2015 @08:22AM (#9295677)
Baidu network is not used. The response is altered as the trafic goes out of China. The only thing they can do is hosting http://hm.baidu.com in another country.
Re:China's Man-On-the-Side Attack on GitHub by nailer on Tuesday March 31, 2015 @08:44AM (#9295749)
> The response is altered as the trafic goes out of China.

By locating their network inside China, Baidu is allowing a malicious actor to leverage their network traffic - which indeed is a 'use' of Baidu's network.

> The only thing they can do is hosting http://hm.baidu.com in another country.

Most likely, yes. And until they do so, or come to another solution, their traffic should be blocked.

Re:China's Man-On-the-Side Attack on GitHub by ithkuil on Tuesday March 31, 2015 @09:40AM (#9296041)
If their traffic gets blocked by other countries they could mitigate the revenue loss by having some capacity outside China and make sure that most accesses to their property coming from outside China goes to the servers hosted outside China (geo dns or anycast routing).

This would restore their analytics infrastructure functionality and avoid being exploited by their own government for such kinds of attack, while being justified as an infrastructure scalability concern (to avoid backslashes by the Chinese government).

Re:China's Man-On-the-Side Attack on GitHub by teamhappy on Tuesday March 31, 2015 @08:52AM (#9295789)
So what's the rule then? Block all packets coming out of countries with governments that do MITM attacks? Blame the companies for not locating their servers in other countries? Companies like GitHub? This is so hypocritical.
Re:China's Man-On-the-Side Attack on GitHub by nailer on Tuesday March 31, 2015 @09:26AM (#9295955)
> So what's the rule then? Block all packets coming out of countries with governments that do MITM attacks?

Block packets from any company that does not take reasonable steps to stop its network from being used to attack others.

This has been networking rule for a long time.

- We block open mail relays

- we block hacked Windows XP machines

- we should block a company who's in a hacked data center where their upstream adds malicious JavaScript.

Edit: 'we' = network administrators.

Re:China's Man-On-the-Side Attack on GitHub by teamhappy on Tuesday March 31, 2015 @09:43AM (#9296053)
I assumed you were talking about our governments when you said we. Who's stopping you from blocking whatever you want? Or from creating a public block list for that matter. You have to convince me to install it on my machines though. :P
Re:China's Man-On-the-Side Attack on GitHub by woah on Tuesday March 31, 2015 @01:07PM (#9297980)
I think they are addressing their fellow network admins with that comment
Re:China's Man-On-the-Side Attack on GitHub by acveilleux on Tuesday March 31, 2015 @02:00PM (#9298518)
They probably should use a global, non-chinese CDN to avoid this. That and HSTS and HTTPS to pin certs.
Re:China's Man-On-the-Side Attack on GitHub by throwaway7767 on Tuesday March 31, 2015 @08:44AM (#9295750)
Does that mean we should drop everything coming from US prefixes also because the NSA uses them for man-on-the-side attacks?
Re:China's Man-On-the-Side Attack on GitHub by throwaway7767 on Tuesday March 31, 2015 @08:52AM (#9295797)
Replying to myself as HN won't let me reply to the post by 'nailer

> If there is a specific network being leveraged by the US government to attack someone else, and the owner of the network is not taking steps to prevents its misuse, then yes, of course.

We have documented evidence of GCHQ doing man-on-the-side attacks against visitors of LinkedIn and slashdot.org. So are you currently blocking the prefixes of LinkedIn and SourceForge, Inc. on your networks? Or are you aware of any specific acts of these companies to prevent this from being possible in the future?

I worry about mass surveillance and national firewalls no matter where they come from, but I don't think balkanising the internet is a good response.

Re:China's Man-On-the-Side Attack on GitHub by nailer on Tuesday March 31, 2015 @08:47AM (#9295769)
If there is a specific infrastructure being leveraged by the someone to attack someone else, and the owner of the infrastructure is not taking steps to prevent its misuse, then yes, of course.

Edit: yes, throwaway7767, this means any company. However LinkedIn, in this case, was being spoofed, and LInkedIn's infrastructure was not used: http://www.spiegel.de/international/world/ghcq-targets-engin...

Edit 2: no, throwaway7767, Baidu's infrastructure - their bandwidth, their customers, and location within the Chinese Firewall are being used to attack GitHub. Baidu has control over where they locate their servers. Baidu are not exercising that control.

Re:China's Man-On-the-Side Attack on GitHub by throwaway7767 on Tuesday March 31, 2015 @09:44AM (#9296062)
Apparently I can now reply further into the thread, must be a timed thing.

> Edit: yes, throwaway7767, this means any company. However LinkedIn, in this case, was being spoofed, and LInkedIn's infrastructure was not used: http://www.spiegel.de/international/world/ghcq-targets-engin....

LinkedIn was indeed being spoofed, which is exactly what was being done to baidu in this case we are discussing. So it seems to be we now agree that blocking baidu would not be appropriate?

> Edit 2: no, throwaway7767, Baidu's infrastructure - their bandwidth, their customers, and location within the Chinese Firewall are being used to attack GitHub. Baidu has control over where they locate their servers. Baidu are not exercising that control.

And in what way is this different than the attack on LinkedIn we were discussing? Please be specific.

I've already said I disapprove of these methods regardless of who applies them, but you have not seen fit to specifically state that companies like linkedin should move all their servers outside the US/UK/FVEY countries, reserving that course of action only for chinese companies.

Re:China's Man-On-the-Side Attack on GitHub by nailer on Tuesday March 31, 2015 @11:21AM (#9296868)
>> If there is a specific infrastructure being leveraged by the someone to attack someone else, and the owner of the infrastructure is not taking steps to prevent its misuse, then yes, of course.

> you have not seen fit to specifically state that companies like linkedin should move all their servers outside the US/UK/FVEY countries, reserving that course of action only for chinese companies.

Yes, I have. See quote above.