If you just want to share your public key safely, a .well-known directory on your domain works these days: https://wiki.gnupg.org/WKD
Ask HN: Keybase Alternatives?
61–70 of 237 posts
Re: Ask HN: Keybase Alternatives?
#62I'd suspect this is jumping the gun a lot bit. Keybase was running a free service for years and has matured a lot in the last year (post crypto debacle). There's nothing stopping them from 1. Letting Keybase go into maintenance mode. 2. Donating the server to a foundation. 3. Open sourcing there server. In all these scenarios Zoom gets better security which is a win for the world :)
> In all these scenarios Zoom gets better security
I'm more worried about the scenarios in which keybase gets worse security. Zoom's attitude to security is terrible.
Re: Ask HN: Keybase Alternatives?
#63Earlier quoted context omitted.
That would be really great, but feels like very unlikely as well. If they could open source it, why didn't they do it before?
Probably, because it provided them with more likely paths to monetization having everyone dependent on their server infrastructure. An argument could be made that if Zoom wants to build positive equity with the security community then open sourcing the Keybase server might be a good way to do that.
The only positive Zoom is interested in is the rate of growth in their bank account.
Re: Ask HN: Keybase Alternatives?
#64Re: Ask HN: Keybase Alternatives?
#65what do you think about it?
https://www.youtube.com/watch?v=G8Bt3jEhIwA
Re: Ask HN: Keybase Alternatives?
#66Chat: Pick one of the many available. telegram, signal, wickr etc etc KBFS: personally I switched to gpg encrypting important files on a NAS with encrypted backups to amazon glacier and backblaze. Git: gitlab, github, bitbucket (just to name a few) Encrypted messages out-of-band: Just use plain pgp/gpg
> Git: gitlab, github, bitbucket (just to name a few)
None of those hide the contents of your repo from the company that's hosting it. I suppose self-hosted Gitlab hides it the same way that Keybase does (the company's software sees your repo, but it's not stored in plaintext on their disks)
Re: Ask HN: Keybase Alternatives?
#67Re: Ask HN: Keybase Alternatives?
#68I have been working on this decentralized key-value database: https://github.com/kevacoin-project/kevacoin
Together with W3C's draft Decentralized Identifiers (DID: https://www.w3.org/TR/did-core/), it could provide a decentralized alternative.
Not sure what is the best way to verify Twitter/Github account though. This has to be managed by users themselves. E.g. one user posts a proof in the Twitter account, the other user verifies the proof by checking the proof against the public key posted in the database.
Re: Ask HN: Keybase Alternatives?
#69If you just want to share your public key safely, a .well-known directory on your domain works these days: https://wiki.gnupg.org/WKD
Ah that's awesome! I've never heard of that before. Thank you!
Re: Ask HN: Keybase Alternatives?
#70If you just want to share your public key safely, a .well-known directory on your domain works these days: https://wiki.gnupg.org/WKD
Just a quick note on WKD since I've been bitten by this a few days ago: as soon as you set it up, some people will start using your keys automatically, without even knowing it (eg. it seems that ProtonMail automatically uses keys found on a WKD to encrypt outgoing mails). While in itself it's not a bad idea, you'd better prepare for this to avoid looking stupid like me, when you receive a casual encrypted mail and you're not able to read it (my private keys are air-gapped and until now I only expected to receive PGP-encrypted mail if it was worth the effort to read it offline).