Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Send encryption keys to new clients. #2001

Closed
lhunath opened this issue Mar 14, 2017 · 4 comments
Closed

Send encryption keys to new clients. #2001

lhunath opened this issue Mar 14, 2017 · 4 comments

Comments

@lhunath
Copy link

lhunath commented Mar 14, 2017

When a user starts to use a new client that wasn't yet part of his account when an encrypted message was sent, that message is unavailable to this new client. The same is true when a user signs out and back into his account on a client. This is not acceptable - encrypted messages can easily become lost and inaccessible this way.

There should be a mechanism by which new clients can become eligible to receive the encryption tokens necessary to decrypt old messages.

@richvdh
Copy link
Member

richvdh commented Mar 14, 2017

@richvdh richvdh closed this as completed Mar 14, 2017
@lhunath
Copy link
Author

lhunath commented Mar 14, 2017

Isn't this a server-level issue rather than a client issue?

@richvdh
Copy link
Member

richvdh commented Mar 15, 2017

There might need to be some support from the server, but at the end of the day the client will need to do the device verification and encryption necessary to transfer the keys.

Remember that the principle of E2E is that the server cannot be trusted.

@lhunath
Copy link
Author

lhunath commented Mar 15, 2017

Right - makes sense. I couldn't quite figure out what the best place for this report was as it seems more of a feature that should be part of the "spec" / "api" as opposed to any specific implementation. That said, I also wasn't sure official matrix dev happened at vector-im.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants