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?).
Twitter I don't think so but I feel like the majority of people visiting Hack News use Github in some way. Remote Repo, Deploying, Open Source tools that are hosted on Github.
the might assume that its a problem on their end / on their ISP end.. Clearly enough people think its relevant for it to make its way onto the Homepage via upvotes ;)
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.
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.
> If you don't like a story, and have nothing to contribute to the story, downvote it.
You should try doing this because I don't think it actually exists.
I do understand why the hackernews crowd is interested in the status of github. What I don't understand is why those same people don't know about status.github.com and @githubstatus already.
If github is a critical piece of your infrastructure, add a couple of bookmarks and never be in the dark again.
Good point on the existence of the down vote functionality, I've amended my comment above.
To your other points though, Github being DDoSed is something I would like to know about, but does not happen so frequently that I should bookmark the status page and check it every hour to see if someone is DDoSing them. That's rather absurd.
Maybe it's a sign someone should look into an expanded notification system. I imagine someone could cook up an interesting IF case for IFTTT.
A good way for a company like GitHub to do it might be an RSS feed. That won't necessarily allow to define a status message type indicating the occurrence of the problem vs. the resolution - and the severity of the status problem.
I think the problem with BitBucket and GitHub is that i never need to go to the website for most things. All the interfacing I do is thought the Git or mercurial Interface.
We've had some minor issues with Bitbucket being down, or at least inaccessible. Never anything really disconcerting, but it's always a pain when you can't get to your code, even if it's only for a few hours.
Mostly Bitbucket has moments where it seems a little slugish and a pull or push takes what seems like forever.
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.
They wouldn't necessarily have received useful data from it. Consider what happens if you spoof the sender IP and port in the first packet of a TCP handshake: the recipient will send a response to the spoofed IP, making it look like they are the bad guys.
Someone isn't filtering Martians properly, or those spoofed packets would have been filtered before they reached you.
> 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.
Not sure it's solved, but I added some additional firewall rules to block certain types of ICMP packets that they were sending and added some additional logging for when it happens again.
If you are looking to host an internal git server, then you should watch my screencast, where I talk about how to configure a central git server and manage user access with gitolite.
73 comments
[ 2.4 ms ] story [ 154 ms ] threadAlso the red banner looks a bit off to me, the "More Status History" just seems plonked in the middle of it.
Hopefully didn't type too soon
That's a lot of techies services attacked for such a short time.
EDIT: typo
What happens if the repos aren't in sync and you pull?
Edit: curiosity got the better of me https://gist.github.com/mitchty/0c2089445c1400d46cb9
Basically exactly what you'd think.
Maybe just me...
EVERYTHING is inconsequential in the grand scheme of things.
Edit: Heh, there are no downvotes on HN for stories. My bad.
You should try doing this because I don't think it actually exists.
I do understand why the hackernews crowd is interested in the status of github. What I don't understand is why those same people don't know about status.github.com and @githubstatus already.
If github is a critical piece of your infrastructure, add a couple of bookmarks and never be in the dark again.
To your other points though, Github being DDoSed is something I would like to know about, but does not happen so frequently that I should bookmark the status page and check it every hour to see if someone is DDoSing them. That's rather absurd.
A good way for a company like GitHub to do it might be an RSS feed. That won't necessarily allow to define a status message type indicating the occurrence of the problem vs. the resolution - and the severity of the status problem.
(note that I'm not agreeing we should post to HN for every blip)
https://status.github.com/api/messages.json
see: https://status.github.com/api
[1] http://blog.bitbucket.org/2013/07/02/scheduled-downtime-bitb...
Mostly Bitbucket has moments where it seems a little slugish and a pull or push takes what seems like forever.
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.
Someone isn't filtering Martians properly, or those spoofed packets would have been filtered before they reached you.
I'm filtering martians/bogons, which I see getting blocked constantly.
How did you solve it?
This is literally going to ruin someones picnic.
http://sysadmincasts.com/episodes/11-internal-git-server-wit...