Skip to content
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

Room keys not stored when room doesn't yet exist #652

Open
TobiasFella opened this issue May 6, 2023 · 1 comment
Open

Room keys not stored when room doesn't yet exist #652

TobiasFella opened this issue May 6, 2023 · 1 comment
Labels
bug/fix The library doesn't work as expected E2EE End-to-end encryption is affected

Comments

@TobiasFella
Copy link
Member

  1. A invites B to a room and sends a message
  2. (in some situations) B will receive the to-device message with the key before receiving the invitation to the room, causing libquotient to not store the room key
  3. Profit :)
@KitsuneRal
Copy link
Member

Ooph...
While rebasing the per-connection E2EE code a couple of hours ago, it occurred to me that holding Megolm keys in a dictionary inside the ConnectionEncryptionData object might make the Room code less cumbersome. This is apparently the case to move those keys there and store them whether a room with a given id exists or not.

@KitsuneRal KitsuneRal added the bug/fix The library doesn't work as expected label May 6, 2023
@KitsuneRal KitsuneRal added the E2EE End-to-end encryption is affected label Apr 15, 2024
@KitsuneRal KitsuneRal moved this to 0.9 - To Do in libQuotient 1 May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/fix The library doesn't work as expected E2EE End-to-end encryption is affected
Projects
Status: 0.9 - To Do
Development

No branches or pull requests

2 participants