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

GitHub experiencing a large DDoS attack

status.github.com

Post reply on HN
Print view View original

91–100 of 105 posts

Re: GitHub experiencing a large DDoS attack

#91

Post by nilved »

camus wrote: post #33
twerquie wrote: post #21

Earlier quoted context omitted.

This happens to our team too. Does anyone else find it ironic that Git is a distributed version control system, yet we rushed to centralize it and base our entire workflow around GitHub?

Github is just a node. IF Github dies , people still have the full repos on their computers.That's not always the case with SVN... And most people are too lazy/dont have resources to set up a git server anyway.

What's a "git server?" Set up any machine that can be SSHed into, maybe apt-get install git and you're done. Git is just files.

Re: GitHub experiencing a large DDoS attack

#92

Post by WestCoastJustin »

cmer wrote: post #7

This is getting really problematic. It stops our whole team every time. Anybody has experience with Gitlab and Gitlab CI? How's the flow compared to Github, especially for pull requests, commenting and collaboration?

Although, I don't have experience with Gitlab, I did create a screencast about git/gitolite, which can do 90% of what you want @ http://sysadmincasts.com/episodes/11-internal-git-server-wit...

Then look at something like Gitweb [1], cgit [2], or Gerrit [3] to front the repo. I personally use git, gitolite, and gitweb.

[1] https://git.wiki.kernel.org/index.php/Gitweb

[2] http://git.zx2c4.com/cgit/

[3] http://code.google.com/p/gerrit/

Re: GitHub experiencing a large DDoS attack

#93

Post by sytse »

y0ghur7_xxx wrote: post #50
cmer wrote: post #7

This is getting really problematic. It stops our whole team every time. Anybody has experience with Gitlab and Gitlab CI? How's the flow compared to Github, especially for pull requests, commenting and collaboration?

We are using Gitlab for about half a year with Jenkins, and we could not be happier. We are about 50 devs working with it every day. It has some quirks (for example AD integration) but it has served us well, and we would not want anything else.

GitLab co-founder here, thanks for the comment y0ghur7_xxx. Please let me know if you have any idea's to improve Active Directory Lightweight Directory Service support.

Re: GitHub experiencing a large DDoS attack

#94

Post by sytse »

druiid wrote: post #18
cmer wrote: post #7

This is getting really problematic. It stops our whole team every time. Anybody has experience with Gitlab and Gitlab CI? How's the flow compared to Github, especially for pull requests, commenting and collaboration?

I've been very happy with Gitlab. The CI server seems a bit simplistic at this point and I haven't tried it, but I'm slowly moving all of the stuff I need to have more consistent access to, from Github.

GitLab co-founder here. Thanks for commenting druiid. GitLab CI 3.1 will have very nice integration with GitLab 6.0. It will still be simple, but should cover most cases.

Re: GitHub experiencing a large DDoS attack

#95

Post by andyroid »

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?

My guess would be attention and publicity. Targeting a technical, developer centered site is likely to require more "skill" as one would expect such a site to have their defenses ready for this. All the greater challenge. Secondly, every time this happens it causes quite a discussion on developer forums and sites such as HN. If you're seeking attention and "recognition" amongst technical people, what better site to attack?

Re: GitHub experiencing a large DDoS attack

#97

Post by anemator »

vhost- wrote: post #90
swede wrote: post #84

Earlier quoted context omitted.

Public Service Announcement You can have multiple remotes for your Git repositories, one of them (Github) being down should not affect your work since you can coordinate a new one with your team in the manner described above.

Yep! I usually setup a mirror at bitbucket and set my local to push to both github and bitbucket and only pull from github. It worked well when github was down and I needed a branch from a remote developer.

Nice. I didn't know you could push to multiple remotes (in the same command). Could you give me an example? Thanks!

Re: GitHub experiencing a large DDoS attack

#98

Post by JimmaDaRustla »

camus wrote: post #23
gavingmiller wrote: post #5

I ask because I have no plausible answer: What does someone stand to gain by DDoSing github?

blackmailing ? "if you dont pay we'll DDOS you" or whatever. Given all these infected Windows computers all over the world ,it's not going to stop soon. That's the Microsoft legacy.

It's Microsoft's legacy to have their customers' computers infected with a virus to operate as a giant botnet?

Sheesh.

Re: GitHub experiencing a large DDoS attack

#99

Post by holyjaw »

vhost- wrote: post #90
swede wrote: post #84

Earlier quoted context omitted.

Public Service Announcement You can have multiple remotes for your Git repositories, one of them (Github) being down should not affect your work since you can coordinate a new one with your team in the manner described above.

Yep! I usually setup a mirror at bitbucket and set my local to push to both github and bitbucket and only pull from github. It worked well when github was down and I needed a branch from a remote developer.

Can't reply to the child to this comment, so I'll add this as a new child:

Here's how to set multiple remotes. (See answer 2). http://stackoverflow.com/questions/849308/pull-push-from-mul...

Re: GitHub experiencing a large DDoS attack

#100

Post by 300bps »

cheeseprocedure wrote: post #12

Can someone with experience mitigating an attack like this describe how it's done? A known set of hosts/address spaces is fine, but it's the "distributed" part I don't understand how to deal with.

Can someone with experience mitigating an attack like this describe how it's done?

I believe Step 1 is to submit the fact that GitHub is being DDoS'd to Hacker News, reddit, Slashdot and other social networking sites with a direct link to GitHub's web site. This will cause a flood of real people to load the web site, thereby crowding out the DDoS.

The site will still be down, but at least it will be due to real people and not the DDoS.

Post reply on HN