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

Unable to decrypt anything else than what I send by myself #9169

Closed
Mikaela opened this issue Mar 14, 2019 · 5 comments
Closed

Unable to decrypt anything else than what I send by myself #9169

Mikaela opened this issue Mar 14, 2019 · 5 comments
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Mar 14, 2019

Description

Kuvakaappaus 2019-03-14 11-34-02

I can only read messages I send from this device regardless of trusting all devices.

Steps to reproduce

  • I have no idea.

I expect to be able to read all messages from everyone, especially as I have key backup enabled and trust all my devices from all my devices.

Log: sent

Version information

  • Platform: desktop

For the desktop app:

@Mikaela
Copy link
Contributor Author

Mikaela commented Mar 14, 2019

Screenshot_20190314-114159

Interestingly my phone has a warning mark for the Riot from which I sent logs and it says both key ID and fingerprint key ID to be none and that the sender is unknown device.

@dbkr
Copy link
Member

dbkr commented Mar 14, 2019

The device key has changed here, so this is probably another instance of #9107. Interestingly this is an Electron client. The appearance of the bug doesn't seem to coincide with a client update so it looks like chromium is deleting the indexeddb in the same way.

@lampholder lampholder added T-Defect P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-E2EE labels Mar 18, 2019
@Mikaela
Copy link
Contributor Author

Mikaela commented Aug 6, 2019

I sent another debug log for this, the only change is that Riot version is now 1.3.0 (and Debian Testing is nowadays 11/Bullseye).

@Mikaela
Copy link
Contributor Author

Mikaela commented Aug 10, 2019

I have "resolved" this by removing all devices from my account and running rm -rf ~/.var/app/im.riot.Riot and clearing data on my Androids.

@poljar
Copy link
Contributor

poljar commented Nov 4, 2021

We're now notifying the user about the error state here via #9109. I'm afraid there's not much more we can do if indexeddb gets cleared.

@poljar poljar closed this as completed Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

4 participants