-
Notifications
You must be signed in to change notification settings - Fork 16
Users whose servers were unreachable when you logged in will send you undecryptable messages #2314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A solution to this might go something along the lines of:
This would require Bob's client to keep a journal of which users it tried to send a given megolm key to (which might also be useful for dealing with wedged olm sessions more promptly (#1992). (That might well be be better done after MegolmV2?) |
When Bob's server sends the to-device messages to Alice's server, it could also include the |
There is a race condition here where this check returns false (up-to-date list) and before the event is delivered the client logs in on a new device. |
I'd argue that's less a race, and more that, objectively, Bob logged in after the message was sent, and therefore shouldn't expect to decrypt the event any more than he would if he logged in 3 weeks later. In other words, it's #2313 rather than this issue which is really specific to the parallelism due to federation. |
Migrating from element-hq/synapse#2165:
The text was updated successfully, but these errors were encountered: