3 ms·
They could have made something like: the client generates a key pair, encrypts the public key with the server’s public key, sends it to the server with a no
by andrewflnr 13y ago
They could have made something like: the client generates a key pair,
encrypts the public key with the server’s public key, sends it to the server
with a nonce, and the server sends back the nonce encrypted with the
client’s public key. Simple and easy.
Just out of curiosity, is it really that easy if you're using verified components? I would naively assume (and hope) so, but then everyone tells me that crypto is fraught with subtle ways to shoot your users in the feet, including if you misuse verified primitives. If yes, I'll continue making pie-in-the-sky plans using the magic of public-key cryptography. :)
- fleitz 13y agoNot really, that is also vulnerable to man in the middle attacks. You need cert pinning or a fool proof trust system to verify the server key.
- comex 13y agoNot if the server key is just hardcoded into the app, which can be appropriate in some cases; of course, that raises the question of how to secure the app download, but that's usually done over a separate protocol anyway.
- geal 13y agoIn fact, the app ships with a bunch of RSA 2048 keys that are used for that part. But there is no revocation support.
- fleitz 13y agoYeah that's generally the downside of cert pinning / hardcoding. The upside is people can't install extra certs.