The premise of end-to-end encryption (E2EE) is that the client is secure and trustworthy, your end devices is secure and trustworthy, but the network and server need not be trusted. You've read all the code in the client, or someone you trust has done so for you. But after loading the code onto your phone -- installing the Keybase app -- and starting a chat with your friend, you still need to verify that the server sent you the right encryption key. Since you can't host your own server, it has to be the Keybase, Inc's server that sends you the encryption key of your friend.
It's pretty standard for E2EE software that the (client) code is open, the server sends you the encryption key, and you can check the encryption keys out of band. In Signal you check the safety number, in Wire you check the device fingerprints, and in Telegram you check the encryption key. If they match, you know (based on the open client code and the cryptography it uses) that there is no (wo)man in the middle.
How does this work with Keybase? Their documentation explains parts of it:
Alice and Bob share a symmetric encryption key, which they pass through the server by encrypting it to each of their devices' public encryption keys.
Okay, so either we verify the symmetric key (identical on both phones), or we verify the public key (I should be able to display mine on my phone, and my friend will call up what their phone thinks my public key is, and that should match).
The weird thing is that there is no button to do either of this. The documentation doesn't mention any and I can't find it when looking around.
Further on, it explains the public keys are put into your signature chain:
All Keybase devices publish a
crypto_boxpublic key and a
crypto_signpublic key when they're first provisioned. Those keys live in the user's signature chain [...] A chat symmetric encryption key is 32 random bytes. It's shared by everyone in the chat, [...] When a new device needs this shared key, another device that has it will encrypt it with the new device's public
crypto_boxkey and then upload it to the Keybase server.
So if I'm reading this right, when my friend opens a new chat with me, their client generates the shared secret, it will take the public key from the
crypto_box inside my signature chain, and upload that to Keybase's server so that I can download and decrypt it, and thereby establish the shared secret and start the chat.
... but where does that signature chain come from? This has to be fetched from Keybase servers, so since there is no way to display it, I have to trust the server to send me the right key. How does that make sense when they claim "all messages are secure, end-to-end encrypted"?
There is some documentation that goes through some verification step by step, but aside from that it's broken (there is no "sigs" field in "root_desc", the result of
root.json?hash=X), this is not something I can do on my phone. A malicious server could return the correct answers to my command line client while telling the mobile app that the signature chain contains an entirely different key (namely the one the malicious actor uses to perform the (W)MitM).
Somehow, when this comes up in conversation, this blockchain thing is given as the reason why it's secure without needing to verify anything yourself, but I can't figure out how it works.
Do Keybase chats require any kind of key to be manually verified for end-to-end encryption, or does the blockchain data (which the app could verify silently under the hood) somehow prevent us from having to compare fingerprints/keys/sigchains?
- If we do need to compare fingerprints/keys/sigchains, how can that be done in the Keybase app?
Update: A friend linked this GitHub issue, where it is basically said that the whole blockchain thing isn't yet done by the app. Leaving in the middle whether (something like) SPV is a good solution, it is currently not implemented. That strikes out the first option if I'm not mistaken.
Since the app also seems not to allow fulfilling the second option (comparing keys), I guess this concludes that there is no E2EE currently implemented in Keybase? An attack is hard to pull off: even a malicious server (very ideal position) would have to MITM from the start, so they have to have some prior knowledge in whom to target. But we do trust the server to be honest at least some of the time. Or am I still missing some way that makes this true end to end encryption?
Update 2: It was mentioned on hacker news that the app should check third party proofs by itself. This is not exactly what end to end encryption means since it still relies on third parties, but nevertheless, having to own 2 or more companies' servers before being able to MITM someone's keys (which are additionally TOFU'd) should give quite some confidence.
However, when checking in Wireshark whether it actually does this (ask the Twitter API for the proof string and verify the signature with the the public key it received from Keybase), Keybase on my phone did not contact Twitter at all. (It did proudly proclaim that the new chat was end to end encrypted.)
For those wondering whether the Wireshark test controls for various things:
- The username with whom a chat was started was never typed into the test system (the one that started the chat) prior to the packet capture.
- The two accounts never had any sort of contact before, on any device. They also don't follow each other. Until the chat was established, the other party did not even know my username, so they could not have triggered anything either.
- The packet capture started before the username was typed into the search field on the test device and ended only after Keybase completely established the chat and claimed it was end to end encrypted.
- Twitter seems to host all its services on its own IP range, and none of the IPs the test system talked to during chat establishment fell inside that range. If this assumption is false and the Keybase client uses endpoints outside of
184.108.40.206/21, please comment. I checked all IPs and all are implausible to be a front for Twitter (details on hacker news), but I would be interested to know if Twitter publishes tweets on Amazon Web Services' Simple Storage Service or something.
- It is deemed implausible for the mobile Keybase client to simply have downloaded all signature chains from all users that exist on Keybase and to have checked all their proofs prior to starting the packet capture. This is the only way I can think of how the third party hosted proof could have been verified prior to the packet capture.