You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: