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
Because of a wrong OTK uploaded to the server (#3721, #3817), devices may not able to establish valid olm sessions between them.
The olm unwedge mechanism seems not to work in this case.
The scenario is:
Bob succeeds (unfortunately) to publish a duplicate OTK (badBobOTK)
Alice sends a message to Bob. She shares the new megom key using a new olm session based on badBobOTK
Bob fails to start this inbound olm session (with error BAD_MESSAGE_KEY_ID)
Bob cannot get the megolm key for the the olm message
Bob cannot decode Alice's message
All messages sent by Alice will be undecryptable for Bob. The olm session stays broken forever.
The text was updated successfully, but these errors were encountered:
Because of a wrong OTK uploaded to the server (#3721, #3817), devices may not able to establish valid olm sessions between them.
The olm unwedge mechanism seems not to work in this case.
The scenario is:
BAD_MESSAGE_KEY_ID
)The text was updated successfully, but these errors were encountered: