I'm creating a mobile app which has chat feature in it. Since I wanted to make it secure, I'll do some encryption to messages and the data. I'm thinking of using End-To-End encryption for it but I've got some issues.

Each user will have private and public keys to encrypt and decrypt the data (asymmetric key encryption) and I figured out how to exchange this keys between. So End-To-End encrypted messaging is done.

Here are my issues:

If user changes the device or reinstalls the app, the private key which stored on client will be lost. I know I can create new key pairs for future messages but how can I restore the old ones?

I thought storing the private key in server but it won't be secure at all. I thought storing the private key after encrypting it with user password, it would be secure since I don't know the user's password, but it fails too if user lost his/her password and re-creates one with a "lost my password email".

And another issue is if some legal issue happens, I can't give the chat logs to police because I don't have the decrypted messages or I don't know how to decrypt them because I don't have the private key.

So, how should I handle this issues? How does WhatsApp do it while using End-To-End encryption? You can restore the old messages in WhatsApp after changing device, updating or re-installing the app etc...

I read something about re-encrypting and re-sending the messages from the other user. (Receiver-Sender) But I don't know how effective it would be tho.

Any help would be great. Thanks for all information and help.

  • 35
    "Each user will have private and public keys to encrypt and decrypt the data ..." - sounds for me like a bad design from start since it provides no forward secrecy: once the private key is compromised all intercepted older messages can be read too by an attacker. For anything related to crypto it is recommend to not run your own design here but use existing widely discussed and established designs, like the Signal protocol. Commented Feb 22, 2021 at 7:45
  • 9
    Here's how WhatsApp does it.
    – defalt
    Commented Feb 22, 2021 at 8:31
  • @SteffenUllrich i meant a key exchange like diffie hellman by there. I'm not trying to create my own design but i'm trying to choose the best designs and combine them to create a hybrid system. If i didnt understand wrong, using private-public keys to exchange shared key, (async and sync) is a hybrid system. It must be good for security and speed but recovery and legal cases is what bothers me. Thats why i've asked my question.
    – Eagleclaw
    Commented Feb 22, 2021 at 9:59
  • 26
    If you can decrypt messages for the police, then it's not e2ee. The backup shoud be done locally by the client and it should be encrypted. Derive a key from user's password like Signal does or store the key at server but not the backup like WhatsApp does.
    – defalt
    Commented Feb 22, 2021 at 10:19
  • 1
    @Eagleclaw I don't think Diffie-Hellman is exactly what you think it is. DH is a way for the two parties to mutually derive ephemeral, shared key material on-the-fly with no prior knowledge of anything by either party. There are no public keys involved in DH itself. However, lots of schemes (such as TLS) use public key cryptography for one or both sides to authenticate themselves to the other (which is required if you want to be sure that you're not being MitM'd.) Once the DH and authentication are done, shared-key encryption is normally used to encrypt the actual messages exchanged.
    – reirab
    Commented Feb 24, 2021 at 23:34

4 Answers 4


You have found another example of the balance security vs usability. If you want true E2E encryption, end users are responsible for their keys and for possible backups of their messages. Full stop.

If you stray from that path, you will fall in a grey zone where everything is E2E encrypted but some features allow to recover messages. Said differently: even if traffic were encrypted, the software can still access old messages - which defeats the point of E2E. WhatsApp, for example, chose to implement the ability for a user to ask for a re-send of all their passed (received) messages without the sender being aware of that. If a user genuinely changes their smartphone, they "automagically" recover all of their old messages. Great... But that means that the application contains all what is required for the system to ask to send everything to a rogue address. Gulp...

That being said, you will have to make some executive decisions here. Provided that you and your users are aware that any recovery option does lower the overall security, that will be fine. Do not worry too much -- while most users insist for everything they send or receive to be strongly E2E encrypted, for most users it is far more important to be able to recover their messages than to totally prevent an attacker from accessing them... For better or for worse, most users aren't aware of the full definitions of E2E encryption and strong cryptography, and are usually satisfied with them being claimed

  • 5
    WhatsApp resends only those messages that were not delivered before the recepient uninstalled WhatsApp. WhatsApp web service asks sender to resend undelivered messages by renegotiating keys with the recipient. The retention period of undelivered messages is 30 days. Chat history is restored by either cloud backup or local chat backup.
    – defalt
    Commented Feb 22, 2021 at 9:59
  • You explained the two scenario that i'm thinking of. Either i go full e2e which is the safest for user but i'm losing the ability to backup messages for user or in a legal case sharing that messages with police. Or i encrypt messages as mush as i can but with a backdoor. This gives me the ability to do what i cant do in full e2e but if there is a backdoor that i can use, so can attackers use that too which is not safe at all.
    – Eagleclaw
    Commented Feb 22, 2021 at 10:06
  • @defalt: I know that WhatsApp do their best to secure the resend feature. Yet it resends message without the sender being aware of it. Commented Feb 22, 2021 at 10:44
  • 2
    @SergeBallesta and so as a user, you can nerver be sure that your whatsApp client doesn't do a cc:FBI anyway (routinely or upon request) Commented Feb 22, 2021 at 17:36
  • 1
    @Eagleclaw If a platform claimed E2EE and also could cooperate with authorities, it would be suspect. If the system has any kind of backdoor, that is the front door for hackers and OPSEC.
    – Snives
    Commented Feb 25, 2021 at 3:51

If user changes the device, reinstalls the app, private key which stored on client will be lost. I know i can create new key pairs for future messages but how can i restore the old ones?

Why do you need to restore the old ones? Generate new keys and distribute. They private key should not leave the device it is generated on. If you need message history, store that locally on the users device, not on your servers - and give the user a option to back it up. This is roughly what Signal does.

I thought storing the private key in server but it wont be secure at all. I thought storing the private key after encrypting it with user password, it would be secure since i dont know the user password, but it fails too if user lost his/her password and re-create with a "lost my password email".

Don't store the keys for the user. Period. That makes E2E kinda meaningless.

And another issue is if some legal issue happens, i cant give the chat logs to police because i dont have the decrypted messages or i dont know how to decrypt them because i dont have the private key.

You can't hand over anything you don't have. If the messages is E2E, and you don't store them, there's nothing you can give the police. That is the point of E2E - the provider doesn't have the messages, and can't reveal them to anyone.

  • Local storage isnt actucally bad idea to keep messages but i dont know how i can use it for multiple devices with a same account. For example Facebook messenger. User can message from either mobile app or web browser. Either way user can access to all informations. I cant user full e2ee in this case or i guess i can use a QR code to connect to other devices and share the info i guess. My problem comes to security vs useability question.
    – Eagleclaw
    Commented Feb 22, 2021 at 10:09
  • 1
    @Eagleclaw if you turn on the E2E encryption feature in fb messenger, it restricts you to only using your mobile. You can't easily do this without weakening E2EE and each platform chooses their trade-offs carefully
    – coagmano
    Commented Feb 23, 2021 at 2:31
  • You could broadcast a copy of each message to the various subscribing devices. Each app would have a different public key which would need to be shared but this implementation would be no different than group messaging. The server would queue the encrypted messages for each device until they picked them up, as usual with E2EE.
    – Snives
    Commented Feb 25, 2021 at 3:39

I'd recommend you to take a look at other platforms (like Matrix and Keybase) on their implementation too. Storing private keys on a server entirely breaks the point of using e2ee, as the server can now basically view all the chats.

What I'd recommend using is some kind of Paper Key/Seed Phrase (check BIP39) which can be printed/written on a paper, even memorized, and make it clear that losing this key can result in losing access to old chats. You can optionally allow users to make cloud backup of the keys (I highly discourage it), for those who do not wish to take the benefits of e2ee. I'd encourage to notify the other user if this is the case.

Also I'd recommend checking Matrix.org's implementation of Multi device cross signing, for a guide on how to allow multi-device support.

Also I'd recommend reading keybase.io's blog posts [1][2][3][4][5] on how their system works.

Personally I do not really see a point in reinventing the wheel, matrix.org's implementation does exactly what you want, and you can compliment with your own features/webapp (Think of matrix.org as Email and your app as Gmail).


Most good options have already been covered in the previous answers. There is one other option that is worth mentioning: allowing the user to export the private key, and storing it somewhere they consider secure, perhaps in their password manager. This approach has several shortcomings but also a few advantages: It achieves recoverability without completely losing the point of e2ee, as your servers will never have access to the private key. On the con side, it does leave the safety of the private key in your users' hands, even more than before, and opens them up to phishing attacks where someone might try and trick them into sending their private keys to an adversarial party. You'll have to consider what level of expertise there is in your expected user base. This approach might be fine if you're targeting people from this community, but if you're targeting our grandma's, I probably would not advise it.

  • 1
    I thought something similar yesterday. My thinking was backing up the private key on OS Cloud service like Google Drive, iCloud etc. Since cloud provider doesnt have the messages, they cant get the messages and since i dont have the private key, i cant get the messages aswell. The idea is the same tho. I might use the idea of exporting too, not a bad idea. Ofc i'll warn the user to not share that key with anyone else, use only for recover tho. Thanks for your answer...
    – Eagleclaw
    Commented Feb 24, 2021 at 12:04
  • It's still better to allow the user to provide a password to the app, which is used to generate a longer private key. Then only store the hash of the password to validate their login, also on the app. Then the app would never store their password, or their private key. Only at login would the private key get regenerated to decrypt the local database.
    – Snives
    Commented Feb 25, 2021 at 3:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .