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

Chat history for members before they joined shows: Unable to decrypt - Unknown message inbox #2226

Closed
joeyoropesa-dev opened this issue Jan 13, 2024 · 1 comment
Labels
A-E2EE O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@joeyoropesa-dev
Copy link

joeyoropesa-dev commented Jan 13, 2024

Steps to reproduce

  1. Where are you starting? What can you see?
    The title says everything
  2. What do you click?

Basically after turned on end-to-end encryption (by default when someone makes an room in the app), my friend that is the owner there invited first it's staff team but after sending some messages for members there, and talked a little bit there the owner and me find out very soon that after each joining of an new member (starting from me), the member was unable to decrypt anything with another message that says that the member doesn't have the keys to decrypt it.

The owner tried to see can we turn off end-to-end encryption somehow and I find out very soon that it's impossible to disable it so I've told that to the owner and he tried to change chat history visibility to Anyone, after 2-3 days nothing happens - the older messages and posts there was never decrypted - they just changed the message status to (Unable to decrypt: Unknown message inbox)
5. More steps…
The issue is already explained with steps too

Outcome

What did you expect?

I've expected that from the owner client app since the owner have those keys ti decrypt those messages, owner keys will be used by that client app to globally decrypt those messages (sent them to the server remotely) or to sent those keys remotely to each member that is invited and going to be invited to access fully the chat history in the target room. If that cannot be done, at least an feature in Element should be implemented sooner or later that will create an new menu for these encrypted message that is called (get keys remotely) and those keys should be requested from the owner client and from the moment the owner is online, the keys should be shared temporary to the server just to sent it to the another client (member) that should accept keys and keys will be automatically downloaded.

For easier method, this feature could work faster if the owner in it's chat history visibility choose an option (also part of wanted feature implementation) "Anyone (remotely)" and from that moment, owner keys for each message in the history would be uploaded safetly to the matrix server and every future encrypted messages will have those keys both in client (an app) and the server but no one will be able to locate nor use those keys from the server - only it can be used by clients in the rooms where the chat history visibility setting "Anyone (remotly)" is turned on by the owner itself for safety reasons.

What happened instead?

Just what the title says.

p.s This is both feature request and report in once

Your phone model

Xiaomi Mi 11 Lite 5G NE (codename lisa)

Operating system version

MIUI 14 based on Android 13 (Stock ROM by Xiaomi)

Application version and app store

Official Element app from play store v1.6.10 and Element X app from play store 0.4.0

Homeserver

matrix.org

Will you send logs?

Yes

Are you willing to provide a PR?

Yes

@joeyoropesa-dev joeyoropesa-dev added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jan 13, 2024
@bmarty bmarty added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely A-E2EE labels Jun 26, 2024
@manuroe manuroe added T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements and removed T-Defect Something isn't working: bugs, crashes, hangs and other reported problems labels Jul 4, 2024
@poljar
Copy link
Contributor

poljar commented Jul 4, 2024

Since this claims that the invite happened before the messages I think those messages should have been decryptable.

I think that his is a duplicate of matrix-org/matrix-rust-sdk#3529 which was fixed by matrix-org/matrix-rust-sdk#3533.

@poljar poljar closed this as completed Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

No branches or pull requests

4 participants