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
The recipient receives a Megolm session, say with session ID aaaaaa, and then receives room events encrypted with a different session ID, say bbbbbb. Room messages encrypted with bbbbbb only start appearing after aaaaaa is sent. Both aaaaaa and bbbbbb are for the same room ID. Room messages encrypted with aaaaaa are never encountered.
So it seems like room messages are being encrypted using a different session from what is sent out to the recipients.
Unsure what client the sender is using (could even be a non-Element client). Recipient in this case is using Element X iOS.
The text was updated successfully, but these errors were encountered:
Given we've only seen this once, and don't know which client was doing it, I don't think this is actionable as it stands. Let's reopen if we ever see it again (particularly if we get more details of the sender side client).
From a rageshake:
The recipient receives a Megolm session, say with session ID
aaaaaa
, and then receives room events encrypted with a different session ID, saybbbbbb
. Room messages encrypted withbbbbbb
only start appearing afteraaaaaa
is sent. Bothaaaaaa
andbbbbbb
are for the same room ID. Room messages encrypted withaaaaaa
are never encountered.So it seems like room messages are being encrypted using a different session from what is sent out to the recipients.
Unsure what client the sender is using (could even be a non-Element client). Recipient in this case is using Element X iOS.
The text was updated successfully, but these errors were encountered: