Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Keybase launches encrypted Git

keybase.io

Post reply on HN
Print view View original

31–40 of 277 posts

Re: Keybase launches encrypted Git

#31

Post by r0ze-at-hn »

eropple wrote: post #10
malgorithms wrote: post #2

Keybase team member here. Interesting fact: git doesn't check the validity of sha-1 hashes in your commit history. Meaning if someone compromises your hosted origin, they can quietly compromise your history. So even the fears about data leaks aside, this is a big win for safety. From an entrepreneurial perspective, this is my favorite thing we've done at Keybase. It pushes all the buttons: (1) it's relatively simple,…

So I love Keybase unconditionally and if you guys weren't rolling in physical offices (and not one in Boston) I'd have been beating down your door to come work there--I think what Keybase is doing is important and it's something I'd love to work on. But I have a serious question that maybe you can answer, and it's something everybody who I've showed this to has asked me: How is Keybase gonna make money? How am I assu…

100% agreed. Hosting sensitive git repositories is problem that companies and people are willing to pay $$$ for and stuff that is free has a tendency to go away after a few years. Heck don't bother putting any technical work into it or anything (aka work) and continue being free, but allow me to have a "paying account" or whatever. Pretty much if you are providing value let me prove it by giving you some cash.

Re: Keybase launches encrypted Git

#32

Post by NikolaeVarius »

tehno wrote: post #19
NikolaeVarius wrote: post #13

My first initial gut thought is, could this be as a good ol cross platform method of password management? I've never been able to properly manage keepass due to syncing between different platforms being a pain.

Maybe combine Keybase git with gopass, that one stores data in a git repo: https://www.justwatch.com/gopass/#features

That sounds promising. I can't be the only one with this problem. (aka secure cross platform synchronized password management without requiring personal/managing cloud infrastructure.

Re: Keybase launches encrypted Git

#33

Post by quadrangle »

ericfrederich wrote: post #17

This removes the ability for collaborating, browsing online, basically any feature of GitLab/GitHub/BitBucket. ... I think I'm in favor of this. I think of the things that those services provide on top of Git should actually be ported or mapped to Git itself. Branches, pull requests, comments, etc... should all be Git objects of some sort.

Branches are Git objects. Incidentally, here's a distributed VCS that includes bug tracking: https://fossil-scm.org

Re: Keybase launches encrypted Git

#34

Post by eropple »

mikeash wrote: post #27
eropple wrote: post #20

Earlier quoted context omitted.

OK, so maybe we're using "local" for different things. Are you developing in your local copy of Dropbox , or are you cloning to a local directory using the Dropbox directory as a source (probably bare)? I assumed the former, which is what I meant by "local"; you can end up syncing multiple different instances of the repo and horking the contents of your .git directory (as well as cross-edited files, etc, that bleed c…

That explains the confusion, I'm talking about keeping a bare repository in Dropbox and cloning it to a non-Dropbox location on each computer where I work. It never occurred to me to keep the working copy itself on DB, that would be silly! I expect that this could break the bare repository on DB if I ever pushed from two places simultaneously (where "simultaneously" could potentially encompass a period of hours or da…

For sure--I'm going to go poke at the Keybase one this afternoon! (Also, to be clear, the Keybase method is essentially the same as git-remote-dropbox. Both set up git remote helpers.)

Re: Keybase launches encrypted Git

#35

Post by stevenleeg »

NikolaeVarius wrote: post #13

My first initial gut thought is, could this be as a good ol cross platform method of password management? I've never been able to properly manage keepass due to syncing between different platforms being a pain.

https://www.passwordstore.org/

This might be exactly what you're looking for :)

Re: Keybase launches encrypted Git

#37

Post by r0ze-at-hn »

malgorithms wrote: post #24
eropple wrote: post #10

Earlier quoted context omitted.

So I love Keybase unconditionally and if you guys weren't rolling in physical offices (and not one in Boston) I'd have been beating down your door to come work there--I think what Keybase is doing is important and it's something I'd love to work on. But I have a serious question that maybe you can answer, and it's something everybody who I've showed this to has asked me: How is Keybase gonna make money? How am I assu…

We believe the right long-term answer for Keybase is finding a way to charge large corporations and offer pretty much everything else for free. Obviously there would have to be some paid tier if you really wanted 10TB of storage or something, but very few people want that right now. We're still just getting started. Of course to achieve our goal, we'll also have to find a way to distinguish communities - which we'll…

> Many of us on the team have come from ad-supported businesses and we really, really never want to do that again. I personally guarantee I will never be a "publisher" again.

So prove it. Provide a way that customers can try to give you money for solving their problems. Even if it is just a dummy static page with a form to contact your "sales" department, really show that you will be here for the longer term.

Re: Keybase launches encrypted Git

#38

Post by falsedan »

malgorithms wrote: post #2

Keybase team member here. Interesting fact: git doesn't check the validity of sha-1 hashes in your commit history. Meaning if someone compromises your hosted origin, they can quietly compromise your history. So even the fears about data leaks aside, this is a big win for safety. From an entrepreneurial perspective, this is my favorite thing we've done at Keybase. It pushes all the buttons: (1) it's relatively simple,…

> Interesting fact: git doesn't check the validity of sha-1 hashes in your commit history.

You mean, you have to run git fsck after pulling, since git only checks that you got what you asked for?

Re: Keybase launches encrypted Git

#39

Post by mateuszf »

ericfrederich wrote: post #17

This removes the ability for collaborating, browsing online, basically any feature of GitLab/GitHub/BitBucket. ... I think I'm in favor of this. I think of the things that those services provide on top of Git should actually be ported or mapped to Git itself. Branches, pull requests, comments, etc... should all be Git objects of some sort.

It could be used for storing/fetching secrets and managing access for teams of real/application users.

Re: Keybase launches encrypted Git

#40

Post by falsedan »

quadrangle wrote: post #33
ericfrederich wrote: post #17

This removes the ability for collaborating, browsing online, basically any feature of GitLab/GitHub/BitBucket. ... I think I'm in favor of this. I think of the things that those services provide on top of Git should actually be ported or mapped to Git itself. Branches, pull requests, comments, etc... should all be Git objects of some sort.

Branches are Git objects. Incidentally, here's a distributed VCS that includes bug tracking: https://fossil-scm.org

> Branches are Git objects

That's not how I understand refs, they don't even live in the .git/objects hierarchy.

Post reply on HN