Skip to content

messages sent while offline cannot be decrypted #4853

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

Open
huguesdk opened this issue Jan 4, 2022 · 1 comment
Open

messages sent while offline cannot be decrypted #4853

huguesdk opened this issue Jan 4, 2022 · 1 comment
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@huguesdk
Copy link

huguesdk commented Jan 4, 2022

Steps to reproduce

  1. being offline, send several messages to an existing contact (to which you didn’t send a message in a little while, in my case, if it matters)
  2. go back online, and wait for the messages to be sent

Outcome

what did you expect?

that the recipient could decrypt the messages

what happened instead?

the message could not be decrypted by the recipient. sending extra messages while being online did not solve the problem. i eventually used /discardsession and messages sent after that were able to be decrypted, but not the previous ones.

note that this happened with existing devices (sessions) that sent many messages successfully to each other for a long time. no new sessions are involved in this.

it seems to me that element created a new cryptographic session, but because it was offline, it could not ask the server for the device (session) list of the other user. having something like matrix-org/matrix-doc#3354 would probably help with this. 😉

this happened between users on separate homeservers: synapse 1.44.0 sending to synapse 1.33.2.

Your phone model

No response

Operating system version

android 9

Application version and app store

element 1.3.12 from google play

Homeserver

No response

Will you send logs?

No

@huguesdk huguesdk added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jan 4, 2022
@ouchadam
Copy link
Contributor

ouchadam commented Jan 5, 2022

I've also encountered this and it's caused by the senders device being offline during a key rotation.

The key requests fail along with the sending of the original messages (due to being offline), the failed messages will retry when the device reconnects but the keys either aren't sent or are sent too late, which ends up with the end user receiving encrypted messages without the keys needed to decrypt them

@ouchadam ouchadam added A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

2 participants