GitHub down due to DoS attack [Update]

Software development isn't an easy job. It takes plenty of time to get clean code and stamp out any nasty bugs with work as well. And, as sites go, GitHub is one of the best when it comes to helping streamline the final aspect; sharing a completed product with the world.

At the time of writing, GitHub is down pending a Denial of Service attack, as its status page reports. The status page doesn't provide anything on who is responsible, but using that slick new Twitter search it's possible to see other reactions. So far, nobody has taken the credit for it.

As far as attacks go, GitHub is a fairly prominent target. For the particular market it targets, the service is also very popular. It's hard to see why the site has been attacked, but interesting all the same. So far there's nothing to suggest security has been compromised, so passwords may remain secure.

As they point out on their status page, it will remain 'yellow' until they discover the issue. Getting to the front page remains possible, so may be less of an obvious issue to non-users.

UPDATE: The site is back up and we will update the article with details as they become available.

Source: GitHub Status

Report a problem with article
Previous Story

Obama Administration overrules ITC import ban of older Apple iOS devices

Next Story

Two videos claim to show shells of iPad 5 and plastic iPhone 5C

10 Comments

Commenting is disabled on this article.

Mr. Dee said,
I guess that means Linus was a bit unproductive today.

Compared to TFS, if you're using Git you can actually do some work while offline .

Mr. Dee said,
I guess that means Linus was a bit unproductive today.

Actually not true. you can work offline and even still commit. then sync branch when back online and resolve any conflict. But nobody is forced to don't work because Git is down if you have the code on your local computer from the Git repo.

Mr. Dee said,
I guess that means Linus was a bit unproductive today.

The Linux Kernel is only mirrored on Github, the primary repository is hosted at git.kernel.org, so it won't have had any effect on Linus.

There is no such thing as PRIMARY REPOSITORY in Git. The whole concept of distributed version control is that there is NO CENTER, there is NO PRIMARY, that every clone of the repository is an independent point, that each and every repository is under FULL CONTROL of it's owner and he can pull changes he need/want from any of the other repositories in existence or ignore them if he wish.

The git.kernel.org repository are - so to speak - the mirror of the repository of Linus Torvalds, the so called vanilla kernel... but there are many other kernel repositories (Red Hat, IBM, Oracle, Google, Ubuntu, SONY, Samsung, Joe, Jack, You, Me...) and they are all different but they are all Linux Kernel repositories.

Linus Torvalds tried a few times to explain this, but unfortunately the CVS/SVN centralistic mindset are so deeply imprinted in developers mind that most of them simply can't really understand what Git is about, what distributed version control is about. IT IS ABOUT HAVING NO CENTER!!!

So why GitHub then, or git.kernel.org? The answer is: it is helpful to have a repository where the "main developer's" version of the code (usually the one who holds most of the copyrights for that project) are easily available for the world. But you can get the code from any other repository in the world if you know about their existence. You can get the Linux kernel (with my changes) from my repository, and Linus may never want to include those changes to his Kernel (the so called vanilla kernel) but all the people who need those changes are free to get them from me or from any other repository which already get them. Even if Linus rejects them or ignore them.

There is no dictator in Linux Kernel, not even a benevolent one... at least not since the birth of Git.

aludanyi said,
...

I'm fully aware how Git works, "primary" repository was just a bad choice of words. The original post referenced Linus specifically (i.e. the remote where he is most likely to push to first), not the Linux Kernel in general.

Pretty sure anyone who's ever used git before understands this, aludanyi. It was pretty clear what ZakO meant, even before he clarified it. Calm down - you're starting to sound like Linus himself freaking out like that...

Max Norris said,
It's back up again.. but that's a weird target for an attack. Curious as to motivation, or just a bored idiot.

More like a bored git....