GitHub experiencing a large DDoS attack • Hacker News Board

Re: GitHub experiencing a large DDoS attack

#71

Post by bdcravens » Thu, Aug 15, 2013, 4:31 PM UTC

rblstr wrote: post #47

briandear wrote: post #29

Earlier quoted context omitted.

The so what is that the majority of people on HN are developers and the majority of them use Github either personally or with their teams. So a major outage is costing potentially millions of dollars in potentially lost developer time. If you calculate an average hourly of just $50 and a developer loses 20 minutes. Then that outage costs $17 x the number of affected developers. That's a pretty big loss. I'm reading H…

You can't pull code from another node, i.e another developer? Git is distributed, if you want centralised source control use Perforce or SVN or something.

You may want to reread the comment. It's more than being able to commit and pull via the command line.

Re: GitHub experiencing a large DDoS attack

#72

Post by Cakez0r » Thu, Aug 15, 2013, 4:34 PM UTC

manojlds wrote: post #45

AnSavvides wrote: post #35

I do not understand why GitHub get attacked so often - honestly it's not like they are doing anything wrong, they are a fabulous service and the go-to place for most (if not all) developers for all sorts of projects, be it open source or in an enterprise/corporate context.

Didn't you just answer your question? It is the "go-to" place for most developers.

That doesn't really answer his question. Why would somebody want to inconvenience developers?

Re: GitHub experiencing a large DDoS attack

#73

Post by jbrooksuk » Thu, Aug 15, 2013, 4:34 PM UTC

acjohnson55 wrote: post #61

kenster07 wrote: post #55

Earlier quoted context omitted.

With due respect, God probably had little to do with make.

Who made the make maker?

Science.

Re: GitHub experiencing a large DDoS attack

#74

Post by joemaller1 » Thu, Aug 15, 2013, 4:35 PM UTC

Snarky comments about distributed version control aside, the bigger problem is the ecosystems which revolve around GitHub. Two which are immediately screwing my day up are Composer and Homebrew. Currently, both are totally dependent on GitHub.

Re: GitHub experiencing a large DDoS attack

#75

Post by abeger » Thu, Aug 15, 2013, 4:36 PM UTC

Cakez0r wrote: post #72

manojlds wrote: post #45

Earlier quoted context omitted.

Didn't you just answer your question? It is the "go-to" place for most developers.

That doesn't really answer his question. Why would somebody want to inconvenience developers?

Maybe a developer killed their parents?

Re: GitHub experiencing a large DDoS attack

#76

Post by jofo25 » Thu, Aug 15, 2013, 4:38 PM UTC

Cakez0r wrote: post #72

manojlds wrote: post #45

Earlier quoted context omitted.

Didn't you just answer your question? It is the "go-to" place for most developers.

That doesn't really answer his question. Why would somebody want to inconvenience developers?

Maybe they want to disrupt developers working for a big bad company.

Re: GitHub experiencing a large DDoS attack

#77

Post by daemon13 » Thu, Aug 15, 2013, 4:39 PM UTC

danielsju6 wrote: post #68

Just a PSA Git is distributed, fire up a quick instance with git daemon. git daemon --verbose --export-all --base-path=.git --reuseaddr --strict-paths .git/

>> Just a PSA Git is distributed

Can you please elaborate?

Re: GitHub experiencing a large DDoS attack

#78

Post by KurtMueller » Thu, Aug 15, 2013, 4:40 PM UTC

jbrooksuk wrote: post #65

ripter wrote: post #54

Earlier quoted context omitted.

Everyday? The last attack was August 4th. https://status.github.com/messages

I said "almost".

You said 'almost every day'. Seems more like 'almost every week'. I'm just nitpicking though.

Re: GitHub experiencing a large DDoS attack

#79

Post by [deleted] » Thu, Aug 15, 2013, 4:40 PM UTC

[deleted]

Re: GitHub experiencing a large DDoS attack

#80

Post by thenonsequitur » Thu, Aug 15, 2013, 4:40 PM UTC

Cakez0r wrote: post #72

manojlds wrote: post #45

Earlier quoted context omitted.

Didn't you just answer your question? It is the "go-to" place for most developers.

That doesn't really answer his question. Why would somebody want to inconvenience developers?

The goal may be to potentially open up a new attack vector to steal code, some of which may contain secrets. This is pure speculation, but a definite possibility.