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

lost encrypted messages after providing passphrase #13388

Closed
ousia opened this issue Apr 26, 2020 · 2 comments
Closed

lost encrypted messages after providing passphrase #13388

ousia opened this issue Apr 26, 2020 · 2 comments

Comments

@ousia
Copy link

ousia commented Apr 26, 2020

Description

I have just confirmed that encrypted messages go lost after providing the right passphrase.

If I follow the steps below, what I get from these sent messages in next sessions is:

Unable to decrypt: The sender's device has not sent us the keys for this message.

Steps to reproduce

  1. Log in to your account.
  2. Send a message in an encrypted room (don’t provide the passphrase).
  3. Proceed to logout and provide the passphrase.
  4. Backup is restored (and click OK). Read previously encrypted messages.
  5. Proceed to logout again and click on Sign out confirmation button.
  6. Log in again.
  7. Connect session to key backup (or simply provide your passphrase to read encrypted messages).
  8. Confirm (sorry, but with horror) that the message you sent from your previous session is lost forever.

What I think everyone would expect is that encryption backup was actually performed.

Version information

@jryans
Copy link
Collaborator

jryans commented Apr 27, 2020

It would be interesting to know how this plays out in cross-signing world once 1.6 releases. It would also be good to have debug logs to be able to investigate. Once 1.6 has released, please retest and submit debug logs via Settings -> Help -> Submit debug logs.

@kittykat
Copy link
Contributor

We cannot reproduce this issue so I will close it for now. If you are still experiencing it, please reply with @kittykat and I will reopen it for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants