GitHub had connectivity problems • Hacker News Board

Re: GitHub had connectivity problems

#121

Post by atonse » Tue, Aug 25, 2015, 2:09 PM UTC

kzhahou wrote: post #112

It seems a certainty to me that github will be breached one of these days, and all internal data (i.e., private repos) made public. On that day, so many companies will inadvertently become open source! Do we have any info on what steps github takes to prevent this? I ask as a paying customer (with both personal and corporate accounts).

If such a massive scale breach would happen, it would probably have to take weeks because GitHub probably has so much data. (I would guess on the order of hundreds of TB or a few PB).

It would be more likely to just have handful of high visibility repos.

Re: GitHub had connectivity problems

#122

Post by lkaz » Tue, Aug 25, 2015, 2:14 PM UTC

kevinbowman wrote: post #62

Does anyone else find the Github status "messages" page [0] a bit jarring in how it's organised? The way that, when read from top to bottom, time goes forwards within a day but backwards across days? I guess I normally wouldn't notice, but there are currently some messages on there from today and yesterday and I found it hard to read as a story (either forwards or backwards) - I had to jump around a bit to figure it…

I was going to comment the same when I saw yours ahah.

Re: GitHub had connectivity problems

#123

Post by mightybyte » Tue, Aug 25, 2015, 2:21 PM UTC

niuzeta wrote: post #113

xedarius wrote: post #107

I do wonder why GitHub gets hit, and people say it's a high profile target, yes almost definitely. Another thought occurs to me though, I guess one of the problems when writing a DDoS is measuring how well it performs. The GitHub status screen provides a lot of useful metrics for tuning such an attack.

If I may posit... 1. Github is very well known and cater specifically for the tech crowd. So, an attack on Github is more likely to be talked in the tech crowd, which I would assume the people who would try out DDoS attacks be more likely to be part of. Validation is a weird thing. 2. In a convoluted sense, taking down Github doesn't harm as many bystanders. If that makes any sense... 3. As you've mentioned, very cle…

> Validation is a weird thing.

And bragging rights. Imagine the street cred you get amongst that community if you take down something like github...

Re: GitHub had connectivity problems

#124

Post by lai » Tue, Aug 25, 2015, 2:22 PM UTC

Is this because of shadowsocks and China is pissed again?

Re: GitHub had connectivity problems

#125

Post by Rafert » Tue, Aug 25, 2015, 2:27 PM UTC

kzhahou wrote: post #112

It seems a certainty to me that github will be breached one of these days, and all internal data (i.e., private repos) made public. On that day, so many companies will inadvertently become open source! Do we have any info on what steps github takes to prevent this? I ask as a paying customer (with both personal and corporate accounts).

Like http://homakov.blogspot.nl/2013/03/hacking-github-with-webki... or http://homakov.blogspot.nl/2014/02/how-i-hacked-github-again... ? ;)

Re: GitHub had connectivity problems

#126

Post by dubcanada » Tue, Aug 25, 2015, 2:28 PM UTC

kzhahou wrote: post #112

It seems a certainty to me that github will be breached one of these days, and all internal data (i.e., private repos) made public. On that day, so many companies will inadvertently become open source! Do we have any info on what steps github takes to prevent this? I ask as a paying customer (with both personal and corporate accounts).

You would probably get a better answer if you asked Github this question.

Re: GitHub had connectivity problems

#127

Post by mrks_ » Tue, Aug 25, 2015, 2:29 PM UTC

atonse wrote: post #121

kzhahou wrote: post #112

It seems a certainty to me that github will be breached one of these days, and all internal data (i.e., private repos) made public. On that day, so many companies will inadvertently become open source! Do we have any info on what steps github takes to prevent this? I ask as a paying customer (with both personal and corporate accounts).

If such a massive scale breach would happen, it would probably have to take weeks because GitHub probably has so much data. (I would guess on the order of hundreds of TB or a few PB). It would be more likely to just have handful of high visibility repos.

You're probably right. It's unlikely that a hacker would care about my private repos.

That being said, I'm also curious about GitHub's efforts to prevent such a scenario.

Re: GitHub had connectivity problems

#128

Post by JustSomeNobody » Tue, Aug 25, 2015, 2:32 PM UTC

Retr0spectrum wrote: post #14

marinintim wrote: post #6

All these ideas like "let's fetch our deps directly from github" sound good until github is not down.

You have to fetch them from somewhere. If you are fetching deps from multiple sources, there is a much higher chance of at least one source being down.

Not being able to fetch one is just as bad as not being able to fetch all.

Re: GitHub had connectivity problems

#129

Post by JustSomeNobody » Tue, Aug 25, 2015, 2:34 PM UTC

Zirro wrote: post #23

feld wrote: post #17

Earlier quoted context omitted.

If only git were a distributed version control

It would be nice not to have to rely on centralized servers at all. A P2P/torrent client built specifically for sharing code from git repositories, perhaps?

I thought that was the point of git...

Re: GitHub had connectivity problems

#130

Post by JustSomeNobody » Tue, Aug 25, 2015, 2:37 PM UTC

benihana wrote: post #54

feld wrote: post #17

Earlier quoted context omitted.

If only git were a distributed version control

Oh cool, I didn't realize git being distributed solved the communication problems that arise on an engineering team. Back to work everyone, git is distributed version control so we don't need pull requests or gists or any kind of easy-to-read historical record that is also accessible for non-engineers.

I think the bigger point is to have a contingency plan in place so your whole engineering team isn't sitting on their thumbs with stupid grins on their faces.