But why trust a third party to hold your private key?
Why trust them to not store the plaintext when you encrypt/decrypt with them?
11–20 of 126 posts
But why trust a third party to hold your private key?
Why trust them to not store the plaintext when you encrypt/decrypt with them?
It's pretty awesome how simple it is to use. But why trust a third party to hold your private key? Why trust them to not store the plaintext when you encrypt/decrypt with them?
Can anyone from Keybase shed light on the reasoning behind this? It sounds like you are moving away from programmer-friendly API libraries and into GUI apps. Even if they're open source, as a developer I really liked your up-front API. Will you still be providing those APIs?
Awesome! I hope some of this $ will help to shorten the waiting list queue...
Edit: I don't have any more!
> The Node reference client to our PGP directory will be retired. (PGP support will continue, of course.) Can anyone from Keybase shed light on the reasoning behind this? It sounds like you are moving away from programmer-friendly API libraries and into GUI apps. Even if they're open source, as a developer I really liked your up-front API. Will you still be providing those APIs?
PGP support will continue, always, it's just that you won't need to have PGP on all your devices -- just the ones you use PGP on. Your PGP key will be part of a family of keys you're known by. If you install Keybase and have no idea what PGP is we don't make you get a PGP key.
By switching to device-specific keys via apps on every platform, we can solve security and convenience problem at the same time. As the blog post says, this can only work if you can bring pairs of devices together. Which has only been possible and convenient the last couple years.
http://i.imgur.com/3VAMerv.png
(from https://twofactorauth.org/)
=)
I feel like there is a huge gap between potent, but still hobby, project and series A funding.