Keybase's mission is to make encryption mainstream
1–10 of 84 posts
Re: Keybase's mission is to make encryption mainstream
#2> Two veteran entrepreneurs are running a little startup built around making it easy to build web and mobile applications from day one that make data impossible for a digital trespasser to read. In fact, it encrypts data in such a way that even if you use some company’s service, that company can’t see what you’re doing with it.
Is it? Not that I'm questioning Keybase, I just had no idea they were offering some type of encryption-as-a-service thing. I thought key base offered encrypted identity management, along with some encryption focused tools (kbfs, and now chat). Of course, I don't know/use key base - hence why I'm asking.
Can anyone go into more detail on how key base is offering this service:
> In fact, it encrypts data in such a way that even if you use some company’s service, that company can’t see what you’re doing with it.
(Assuming "some company's service" is a 3rd party service)
Re: Keybase's mission is to make encryption mainstream
#3Nice work team. I've been on Keybase for a while but I've only recently installed and started using Teams on iPhone and Mac and both the apps are very polished and easy to use. Definitely a lot easier than posting up my key and waiting for someone to email me encrypted text ;)!
I think the strategy of decentralising the data is a good one for enterprise apps like this, where there's typically little value from the perspective of the business user, employee user, or service provider from holding the data. Lots of data is great for driving personalisation and other features in a million+ person network but not really in cases like this one.
Hopefully this is a pattern that will keep working its way into enterprise apps.
Re: Keybase's mission is to make encryption mainstream
#4A good article that covers what Keybase is, where they came from, what they try to do, and where they're trying to go -- although you couldn't tell from the headline. As in the article body, Slack is namedropped just for effect; Keybase Teams being a decent proof-of-concept of a popular kind of application to show that the ideas behind Keybase can be used to build real products.
That being said, Keybase has been moving more and more towards building these higher-level services on top of (and app-wise, deeply integrated into) their core offering: Chat, File locker, etc; presumably other than delivering value these offerings make the company easier to position in the grand graph of services, and more palatable for raising capital or as a future acquisition target.
Re: Keybase's mission is to make encryption mainstream
#5Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it.
https://itunes.apple.com/us/app/google-authenticator/id38849...
Can anyone comment on their 2fa approach to google?
Re: Keybase's mission is to make encryption mainstream
#6Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it. https://itunes.apple.com/us/app/google-authenticator/id38849... Can anyone comment on their 2fa approach to google?
On Android, I use FreeOTP; I can make backups with `adb`.
Separately, I use KeepassXC (https://keepassxc.org) and store all my 2fa seeds in a dedicated (separate) 2fa database which I keep locked. You can also keep it in the same database as your password db if you want to trade the 2nd factor for convenience but still get the added benefit of one time passwords.
Re: Keybase's mission is to make encryption mainstream
#7Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it. https://itunes.apple.com/us/app/google-authenticator/id38849... Can anyone comment on their 2fa approach to google?
I always (usually) get a copy of the string token when adding a "google" 2fa. I store this in a password manager.
This allows me to have more confidence in recovery, as well as adding more devices, etc.
Re: Keybase's mission is to make encryption mainstream
#8Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it. https://itunes.apple.com/us/app/google-authenticator/id38849... Can anyone comment on their 2fa approach to google?
I thought Google Authenticator was not recommended, and that Google was fully backing 'Duo'
Re: Keybase's mission is to make encryption mainstream
#9Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it. https://itunes.apple.com/us/app/google-authenticator/id38849... Can anyone comment on their 2fa approach to google?
Always save the keys (or the scanner code) whenever you add them to Authenticator. Then, when you get a new phone (or whatever) you can just re-import the keys.
Re: Keybase's mission is to make encryption mainstream
#10Tangent, but the article mentions using Google Authenticator -- I was going to start using that recently, but the reviews indicated it had some really big problems with restoring when you get a new phone etc and Google isn't really maintaining it. https://itunes.apple.com/us/app/google-authenticator/id38849... Can anyone comment on their 2fa approach to google?
[deleted]