This is nice, but I really wonder why they don't focus on more important things. For example this issue I opened over a year ago, asking them to use end-to-end encryption by default and for group chats: https://github.com/DrKLO/Telegram/issues/156
Probably because features are more important than security, sigh.
It's not that easy: How would you exchange the private keys when using multiple clients? This would require to user to transfer the private key files or to remember a secure password. Both options aren't possible for usability reasons if you want to beat WhatsApp.
Comments
This is nice, but I really wonder why they don't focus on more important things. For example this issue I opened over a year ago, asking them to use end-to-end encryption by default and for group chats: https://github.com/DrKLO/Telegram/issues/156
Probably because features are more important than security, sigh.
I second that notion. It comes down to priorities and right now bots > security.
It's not that easy: How would you exchange the private keys when using multiple clients? This would require to user to transfer the private key files or to remember a secure password. Both options aren't possible for usability reasons if you want to beat WhatsApp.
This has been discussed a lot in the issue thread. Key exchange really isn't the issue.
Scanning a QR code or creating a secure connection between the clients to exchange the keys isn't that hard.
What when I want to login at a computer but don't have my phone with me?
Same as using 1Password — you don't.
You're trading convenience for increased security.
This is why it isn't 'by default'.
End-to-end encryption by default kills one of the advantages of Telegram - crossplatform history synchronisation.
this shouldn't be an issue when the clients share the private key.