Live data from Hacker News

GitHub was experiencing a DDoS

status.github.com

41–50 of 74 posts

Re: GitHub was experiencing a DDoS

#43
post #31

Earlier quoted context omitted.

There is a reason there are controls to allow you to upvote, or downvote stories. If you don't like a story, and have nothing to contribute to the story, downvote it. If the story is in the top few, it's because people (that aren't you) are interested in knowing that github is getting attacked. EVERYTHING is inconsequential in the grand scheme of things. Edit: Heh, there are no downvotes on HN for stories. My bad.

OT: How much karma do I need to have to see the downvote button?

It is, or was, 500 points.

Re: GitHub was experiencing a DDoS

#46

Earlier quoted context omitted.

There is no downvote button on submissions only upvote and flag.

Should there be downvote buttons for submissions?

Maybe? I could go both ways. I think downvoting is important but it's also very easily abused. I like stackexchange's downvoting system where it comes at a cost.

Re: GitHub was experiencing a DDoS

#49
post #21

Why would someone DDoS GitHub? Is there some movement against GitHub? Or is it just for fun?

I manage newgrounds.com which gets quite a bit of traffic. We'll get what I think are DDoS attacks at least once a month. I can see our connection tracking stats go up to the millions and traffic spikes way up of course.

I don't know WHY they do this, but last time it happened we got an abuse report saying that we were reported for port scanning from our main firewall / proxy box. Somehow they had reflected traffic off our firewall / proxy to make it try to connect to a bunch of IPs on a known trojan port.

I have no idea how they did this, but it appears that this time around we were being used to scan ports. This is just a stock Debian box with a firewall and port 80 open. Scary.

Re: GitHub was experiencing a DDoS

#50
post #10

Coincidentally, I just finished setting up Gitlab and Gitlab CI on a private server. If I could set up repo mirroring between it and Github, it would add a layer of protection for getting critical work done (security by distribution?).

Just have both gitlab and github as upstreams and push to both every time. aka in your .git/config:

    [remote "origin"]
      url = https://github.com/somerepo.git
      url = https://gitlab.yourdomain.tld/somerepo.git
      fetch = +refs/heads/*:refs/remotes/origin/*
And nothing to worry about when github is down.
Post reply on HN