Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Github: Major Service Outage

status.github.com

Post reply on HN
Print view View original

71–80 of 80 posts

Re: Github: Major Service Outage

#71

Post by wfarr »

kijin wrote: post #64
mst wrote: post #59

Earlier quoted context omitted.

> "disabling port 80 is a great way to handle this" It's been a disaster for a bunch of people I know. git is distributed by nature so they all had extra remotes they could use. github's issues and other project metadata wasn't distributed, since that's github's alone. So all of the friends of mine who are corporate github users who were using git in a distributed style (a minority of their overall customer base, I w…

The web app is also available on port 443, which every "corporate github user" should have been using anyway.

In fact, all HTTP access redirects to HTTPS for just about everything. And most modern browsers (recent versions of Chrome and Safari) that have accessed a website over HTTPS once happen to _prefer_ HTTPS by default for that site.

Re: Github: Major Service Outage

#73

Post by huhtenberg »

riffraff wrote: post #69
fusiongyro wrote: post #43

Earlier quoted context omitted.

I heard once about a tire shop that drummed up business by strewing nails along the highway around it. Somewhere outside America; India or Thailand or somewhere else. Anyway, that kind of business practice wouldn't get you far in the Western world, so it seems unlikely. OTOH, if I had a botnet and I wanted to see how powerfully it could DDOS without drawing a lot of mainstream media attention, github might be good fo…

OT: the urban legend about tire shops putting nails in the neighborhoods' is very widespread. I have heard about it in at least three countries, and I recall my school teacher telling me about it in '91. I sort of expect it wouldn't be an effective practice anywhere.

It's an urban legend until you actually catch a nail and there is a tire shop conveniently located not 100 yards away. True story, Indian reservation in BC, Canada. Who cares if it's a tacky business model or an urban legend. It works.

Re: Github: Major Service Outage

#74

Post by huhtenberg »

zheng wrote: post #34

First off, as others have said, disabling port 80 is a great way to handle this, I don't really care that much if I can see/use github the website for a few hours, but I'd be much more upset if I couldn't pull my code. Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.

> disabling port 80 is a great way to handle this

They got lucky. What would be a great way to handle it if next time it's port 21 or 443?

Re: Github: Major Service Outage

#75

Post by zheng »

huhtenberg wrote: post #74
zheng wrote: post #34

First off, as others have said, disabling port 80 is a great way to handle this, I don't really care that much if I can see/use github the website for a few hours, but I'd be much more upset if I couldn't pull my code. Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.

> disabling port 80 is a great way to handle this They got lucky. What would be a great way to handle it if next time it's port 21 or 443?

Like I said, disabling port 80 is a great way to handle this kind of attack. Those would obviously be trickier. I'm no network security expert, but I would assume that they are much more resilient to other attacks, as most protocols aren't as network intensive as TCP.

Re: Github: Major Service Outage

#76

Post by acdha »

wamatt wrote: post #51

/enqueue jokes about decentralized DVCS systems being hosted centrally... Srsly tho, the relationship between Git and GitHub, might be somewhat analogous to that of BitTorrent and TPB

It's both a joke and educational: I didn't know they were down until I caught up on my RSS feeds last night

Re: Github: Major Service Outage

#79

Post by longdivision »

veeti wrote: post #47
longdivision wrote: post #37

https://twitter.com/AnonymousOwn3r is taking credit for attacks against YouTube and GitHub amongst others.

Stop giving some idiot script kiddie the attention he wants. It's probably not him anyway.

It's Likely, but this is someone with a history of claims to this sort of attack and a large following. I was interested in who was running the large attacks and what their motivations might be and no sources had been suggested in the discussion at that point.

Re: Github: Major Service Outage

#80

Post by dasil003 »

goldfeld wrote: post #57
dasil003 wrote: post #49

Earlier quoted context omitted.

If it's one service though there is still always a single point of failure outside of your control. If you want true redundancy you need to use multiple versions with no interconnections and develop your own solution to mitigate partial failure, of course your own solution is also a single point of failure, but at least it's under your control. That said, Github has never been down long enough for me to justify a fal…

There will be no crossing if the bridge is down, though.

Of course there will be. We are talking about git. Everyone has a full copy of the repository. Github's data center gets hit by a meteor tomorrow and it's a minor setback, nothing more.
Post reply on HN