Can we please use some of that 100 million investment to buy an infrastructure that is more resilient to these kinds of DDoS attacks? Pretty please? This is a service I pay for and my business relies on. Having it down three times in three days impacts our work.
Did it really impact your work, other than slightly inconveniencing you? "UGH GitHub down again, I guess I have to go work on something equally as important for upwards of an hour" I call shenanigans on you, good sir.
GitHub hit by DDoS attack second day in a row
41–50 of 72 posts
Re: GitHub hit by DDoS attack second day in a row
#42Earlier quoted context omitted.
Thank is exactly what I was thinking. Who in their right mind would want to do that?
Someone who wants to test the limits of their botnet and technique. Can you think of a more tech savvy target?
Re: GitHub hit by DDoS attack second day in a row
#43Earlier quoted context omitted.
Thank is exactly what I was thinking. Who in their right mind would want to do that?
Someone who wants to test the limits of their botnet and technique. Can you think of a more tech savvy target?
Re: GitHub hit by DDoS attack second day in a row
#44Perhaps I'm misunderstanding: I thought one goal of DVCS was to remove central points of failure? In that sense, isn't a central "hub" regressive? I wonder if there's a way to host Git repositories with static files, say, on Amazon S3... That would be neat.
http://ozmm.org/posts/when_github_goes_down.html has a good summary of quick ways to keep using git without github.
Re: GitHub hit by DDoS attack second day in a row
#45Earlier quoted context omitted.
Since when is it OK for the services I rely on and pay for to even slightly inconvenience me ... for three days in a row? Since never. At least for businesses that want to remain an ongoing concern.
If high availability git is so critical then why not run your own git servers instead of or in addition to github? I find it slightly ironic that the entire point of git is that it is distributed version control but 90% of git use seems to be focused around a product from a single company.
Re: GitHub hit by DDoS attack second day in a row
#46Earlier quoted context omitted.
Care to elaborate why GitHub would be a target for a state sponsored DDOS attack? Seems a little far-fetched, for a website that is virtually unknown outside of the developer community
In the broadest sense, github is a site where anyone can upload and publicize any file of reasonable size. Depending on who is uploading what, that could easily make them a target.
Why would they go for github of all things?
Re: GitHub hit by DDoS attack second day in a row
#47It's pretty crazy how just a couple thousand LOICs can incapacitate a site as prominent as GitHub. I wonder how many machines are involved this time.
Re: GitHub hit by DDoS attack second day in a row
#48Earlier quoted context omitted.
Since when is it OK for the services I rely on and pay for to even slightly inconvenience me ... for three days in a row? Since never. At least for businesses that want to remain an ongoing concern.
Devil's avocado here: let's say you pay $100/mo for a gym membership and they shut down three days in a row because somebody called in a threat. How upset would you be at the gym? A malicious attack by a third party is different from, say, the gym allowing black mold to grow in the locker room. I'd quit a gym if they had black mold. That's mismanagement. I wouldn't quit a gym if malicious third party intervention inc…
Re: GitHub hit by DDoS attack second day in a row
#49Earlier quoted context omitted.
If high availability git is so critical then why not run your own git servers instead of or in addition to github? I find it slightly ironic that the entire point of git is that it is distributed version control but 90% of git use seems to be focused around a product from a single company.
Github isn't solely a git server. They also have issues, wikis, etc, that are harder to keep in multiple locations.
Issues are normally mirrored to e-mails (caveat: you don't get mail for your own comments), so you can mostly pick up existing threads if your e-mail address book can find the github users involved. If they didn't obscure recipients (at least within an organisation — because I don't think address-book lock-in is worth inconveniencing paying clients), and made an auto self-bcc of your activity, issues would be entirely disaster resistant.
Re: GitHub hit by DDoS attack second day in a row
#50Perhaps I'm misunderstanding: I thought one goal of DVCS was to remove central points of failure? In that sense, isn't a central "hub" regressive? I wonder if there's a way to host Git repositories with static files, say, on Amazon S3... That would be neat.
http://blog.spearce.org/2008/07/using-jgit-to-publish-on-ama...