Live data from Hacker News

GitHub under ongoing DDoS attack

status.github.com

111–120 of 352 posts

Re: GitHub under ongoing DDoS attack

#111
post #20

Earlier quoted context omitted.

Which raises the question: when will the rest of the world kick China of the internet? First it was redirecting Chinese internet users to random IPs, if the government didn't like their DNS queries and now they're doing ddos attack on a site that host a large percentage of open source code, used for a whole host of service and products. At some point it's going to make more economical sense to kick China of the inter…

> > Which raises the question: when will the rest of the world kick China of the internet? Well, that's exactly what the DDoS wanted, so the government could just happily control all access to Internet in mainland China The DDoS targets github.com/greatfire and github.com/cn-nytimes by their so called "collateral freedom" [1] Suppose github could just ban Chinese IP all together, but @greatfire could easily jump to a…

Hopefully never. IMO access to the internet is a basic human right, like clean water and immunization. I wouldn't choose to deny these things to citizens of any country.

Re: GitHub under ongoing DDoS attack

#112
post #94

Earlier quoted context omitted.

Its due to these two repost most likely. https://github.com/greatfire/ https://github.com/cn-nytimes/ Access to them is currently no possible though.

It is: https://github.com/cn-nytimes https://github.com/greatfire

Had that wrong. thanks.

Re: GitHub under ongoing DDoS attack

#113
post #50
post #39

The PRC's DDoS of GitHub seems a little risky.[1] If GitHub is inventive (or desperate) enough, they could call on their users for aid. The perpetrators would immediately draw the ire of vast numbers of talented programmers. And GitHub is positioned to direct this ire toward useful ends. They could encourage users to contribute to GreatFire, or even start other initiatives and projects to stymie censorship. The outco…

Looks to me like it's time for a DDoS X-Prize. 1. SSDP Flood 21% 2. SYN Flood 19% 3. UDP Flood 13% 4. UDP Fragment 12% 5. NTP Flood 8% 6. GET Flood 7% 7. CharGEN Attack 5% 8. DNS Flood 5% 9. ICMP Flood 2% 10. SNMP Flood 2% Eliminating these 10 attack vectors would account for 94% of DDoS attacks according to this visualization[1], as witnessed by Akamai over the last 30 days. Just the top 3 is more than 50%. Seems li…

Most of these attack vectors just mean a great amount of a specific traffic of some sort. Traffic volume is not something that you can, or would want to, eliminate.

You have to somehow identify and separate the unwanted requests from you regular traffic. That's why these cases are unique and needs to be handled manually, in cooperation with your uplink(s).

Re: GitHub under ongoing DDoS attack

#114
post #111
post #20

Earlier quoted context omitted.

> > Which raises the question: when will the rest of the world kick China of the internet? Well, that's exactly what the DDoS wanted, so the government could just happily control all access to Internet in mainland China The DDoS targets github.com/greatfire and github.com/cn-nytimes by their so called "collateral freedom" [1] Suppose github could just ban Chinese IP all together, but @greatfire could easily jump to a…

Hopefully never. IMO access to the internet is a basic human right, like clean water and immunization. I wouldn't choose to deny these things to citizens of any country.

What happens when providing those things to another country means denying them to your own country?

Re: GitHub under ongoing DDoS attack

#115

I'm looking forward for a post from GitHub describing what exactly was thrown at them and how they were able to mitigate it.

For what it's worth there's an article[1] from Craig Hockenberry. His servers were hit by massive amounts of traffic from China earlier this year, targeted (randomly?) at Iconfactory's website. The charts are quite impressive. [1] http://furbo.org/2015/01/22/fear-china/

That doesn't look anything like the attack on GitHub. His server buckled from a couple of thousand requests because his webserver was misconfigured. GitHub probably handles an order of magnitude more requests on any normal day.

Re: GitHub under ongoing DDoS attack

#116

Earlier quoted context omitted.

>when will the rest of the world kick China of the internet? One day we're advocating net neutrality and the next day we want to ban entire countries from the internet? I still prefer net neutrality, thank you.

I don't think banning countries from the Internet is the answer, but net neutrality seems like a completely separate issue.

Net neutrality is about carriers treating all traffic equally. Banning a country from the internet is discriminating traffic by origin. That sounds like a net neutrality issue if there ever was one. Whether the discrimination happens in the hardware or in the software stack is a mere implementation detail.

Re: GitHub under ongoing DDoS attack

#117
post #88
post #80

Earlier quoted context omitted.

I agree in general, but in this specific case, Beijing can just demand access to Baidu's private keys and MITM all traffic passing through the GFWoC.

That would be the death of Baidu among the Chinese diaspora.

Buh? Encryption is de-facto illegal in China. To the extent SSL is used, you can be sure that the government already has a copy of the master key. I've worked on Chinese deployed train systems, and we were banned from encrypting train control signals (signing was allowed, though), just in case someone might try to sneak in a political message in an ATO control telegram...

Re: GitHub under ongoing DDoS attack

#118
post #50

Earlier quoted context omitted.

Looks to me like it's time for a DDoS X-Prize. 1. SSDP Flood 21% 2. SYN Flood 19% 3. UDP Flood 13% 4. UDP Fragment 12% 5. NTP Flood 8% 6. GET Flood 7% 7. CharGEN Attack 5% 8. DNS Flood 5% 9. ICMP Flood 2% 10. SNMP Flood 2% Eliminating these 10 attack vectors would account for 94% of DDoS attacks according to this visualization[1], as witnessed by Akamai over the last 30 days. Just the top 3 is more than 50%. Seems li…

SYN Flood is already mitigated a long time ago with SYN cookies. The rest ..... well, it's basically just packets. I see this latest development as good news. The Javascript MITM trick was very clever because forcing github to render and serve a page is a lot more resource consuming than just firing packets at servers that ignore them (like a UDP or SYN flood). The latter can saturate network links until the sources…

> well, it's basically just packets

Is "DNS flood" a DNS reflection attack though?

Re: GitHub under ongoing DDoS attack

#120
Time to DDOS the entire Chinese IP space. Once the citizens experience network outages, they'll be able to direct their anger at the PRC who started this bullshit.

PRC wins if Github null-routes the Chinese IP space, Github must stay up no matter what.

Post reply on HN