Live data from Hacker News

Keybase launches encrypted Git

keybase.io

211–220 of 277 posts

Re: Keybase launches encrypted Git

#211
post #87
post #6

I'm really happy about this. I have private repos for personal information (e.g., tax spreadsheets going back a decade) that I keep synchronized across machines, and have to jump through hoops to get an encrypted authoritative remote source. Right now I do that with an encrypted partition on a private VM. And, it really sucks that GitHub does not encrypt data at rest: --- SNIP from https://help.github.com/articles/gi…

Out of curiosity: why do you keep such documents in repositories instead of simply in a filesystem (on an encrypted volume, backed up and possibly synced across devices)? Tax spreadsheets usually don't change, so there's no need for version history (if anything, new rows for new years are added, but without changing past data). I ask this because I'm trying to figure out a solution for myself for keeping sensitive pe…

For me one big benefit is that it's distributed. I like to keep my important documents backed up on all the computers i have, on a USB drive stored in a safe location and also store the data with a cloud provider.

Now, if i update one document on computer A, and another document using computer B, i have to sync it to all other devices which is a PITA without git. You get into the situation where you don't know if the version on the USB drive was newer or older than the one on computer B etc, whereas with git all this is available in the version tree and there are nice merge tools available.

I've been planning to do this even for photos, for all the reasons above, but haven't taken the full step yet.

Re: Keybase launches encrypted Git

#212
post #208

Wait, what exactly _is_ keybase? The home page says: > Keybase is a new and free security app for mobile phones and computers. ok, so, what does it do? > For the geeks among us: it's open source and powered by public-key cryptography. Still have no idea what it does .. > Keybase is for anyone. Imagine a Slack for the whole world, except end-to-end encrypted across all your devices. Or a Team Dropbox where the server…

It's a lot, isn't your third quote a pretty good description?

> Keybase is for anyone. Imagine a Slack for the whole world, except end-to-end encrypted across all your devices. Or a Team Dropbox where the server can't leak your files or be hacked.

It's not much of a reach to assume familiarity with Slack and Dropbox; the message is clearly that Keybase is those (via Keybase Chat & FS) but encrypted.

For what it's worth, it's also a keyserver, and (now) git remote.

Re: Keybase launches encrypted Git

#213

Earlier quoted context omitted.

I've had nothing but good experiences using 1Password.

No official/stable support for linux

the beta cli is available now, though it's more of an API than CLI. [1]

I've written a simple wrapper [2] to make it easy to use.

[1] https://support.1password.com/command-line-getting-started/

[2] https://github.com/dcreemer/1pass

Re: Keybase launches encrypted Git

#214
post #208

Wait, what exactly _is_ keybase? The home page says: > Keybase is a new and free security app for mobile phones and computers. ok, so, what does it do? > For the geeks among us: it's open source and powered by public-key cryptography. Still have no idea what it does .. > Keybase is for anyone. Imagine a Slack for the whole world, except end-to-end encrypted across all your devices. Or a Team Dropbox where the server…

I'm fairly new to Keybase, but essentially, at it's core, Keybase is a software/service for managing trust of identity/public keys, and easily sharing public keys with "trusted" parties, based on Keybase's trust model.

All of the other features you've mentioned are built on top of that key exchange, and use it to offer encrypted services.

Re: Keybase launches encrypted Git

#215
post #208

Wait, what exactly _is_ keybase? The home page says: > Keybase is a new and free security app for mobile phones and computers. ok, so, what does it do? > For the geeks among us: it's open source and powered by public-key cryptography. Still have no idea what it does .. > Keybase is for anyone. Imagine a Slack for the whole world, except end-to-end encrypted across all your devices. Or a Team Dropbox where the server…

The first I ran into it, it was basically a key server where you could associate your public key with social media "proof" -- someone who had access to the private key proved it by posting from this Twitter account, this Github user, this Reddit user, etc.

It seems like the last year or two they've really been ramping up ways to actually _use_ those keys though. They do have a chat app, which I've used with coworkers, but only to share stuff we don't want to send over Slack. It seems like at least part of the issue they've got with the homepage is that their "core" product -- hosting a public key for someone -- isn't really very interesting compared to the satellite offerings.

Re: Keybase launches encrypted Git

#216
I have a long running vm on Google cloud with only tiny configuration. I communicate to it with strong crypt way to access my 'pass' s git repo. So far so good, but I'm good to see what keybase's good work on how to improve the personal data safety, that's a good choice.

Re: Keybase launches encrypted Git

#218
post #209

Earlier quoted context omitted.

To expand on this, you need to add the fork as an alternate remote (as opposed to origin), and then replace "origin" in the command posted prior.

I thought it was in the PR destination repository (since they are under that repository's /pull namespace). You'd need to add the alternate remote if it's a PR into a fork (as opposed to from it), no?

You are absolutely correct. My apologies, as I understood the problem as "I have a fork and want to receive pull requests".

This can be a pretty common setup for some git workflows. Everybody makes a fork and takes / pushes pull requests or branches from their fork to others. The main advantage would be that if you have a lot of branches they don't all have to be on upstream and you don't need to have upstream permissions for everyone to push branches or changes to.

Nonetheless, I can see why my comment raised some confusion.

Re: Keybase launches encrypted Git

#219
Nice, this is perfect timing for me to see this actually. I've been slowly building out a little cli tool that I use to track .env files (and other files that you don't want to check into source) in a git repository that is parallel to your project's git repository.

The way it works is you identify a file that you don't want to check into source. The cli moves it to a parallel repo, commits the file to the parallel repo, and symlinks the file back to the original location.

From then on, you get all of the normal source control features like local changes, revision history, etc... that you get with every other file in your project. I basically got fed up with "crap what was that value I was using before? Let me dig through my credentials store" or resorting to commenting out old lines just in case I needed to revert.

So far, I've just been keeping those parallel repositories local for lack of an encrypted remote to push to. Definitely checking this out.

Re: Keybase launches encrypted Git

#220

Earlier quoted context omitted.

Everything you just said makes perfect sense. That being said, I think Keybase is one of the most important companies around right now. I would gladly pay $10/month, even if literally all it did was put a "Supporter" badge on my profile. I'm sure hundreds of other people agree. Crypto is far too important for it to remain locked away behind GPG.

The outpouring of positive energy (on HN!) is really inspiring. Everyone on the Keybase team is feeling good about our work right now, so thanks!

Get off HN and take my money already. Seriously. I'd gladly pay you money for nothing, a "supporter" badge would only be a nice bonus
Post reply on HN