-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Key backup dialog doesn't show correct backup state #20005
Comments
Might be related: I see the message "This session is not backing up your keys, but you do have an existing backup you can restore from and add to going forward.", even though I have connected to my backup several times. The message does not disappear. I'm on Element-Desktop 1.9.6, Flatpak, Ubuntu 20.04.3 LTS. |
I believe the dialog is correct, just confusing:
However, there is still one bug here: it looks like it's possible to make a key backup that can't be decrypted, as follows:
Maybe what this means is that whatever existing encrypted content that was in the backup you just connected to can't be decrypted, but future content put in that backup will work properly. |
Another issue in the dialogs is that "Connect this session to Key Backup" may prompt you for your Security Key twice, despite the first prompt being successful, the second prompt saying "This looks like a valid Security Key" when you paste it in the text input field, and the inevitable appearance of an error dialog that says "Security Key mismatch / Backup could not be decrypted with this Security Key: please verify that you entered the correct Security Key." A way to reproduce this is:
Notably, this doesn't happen when entering your Security Phrase/Key right after logging in, at the "Verify this device" step. Also, at the 2nd Security Key prompt, you can paste in any syntactically-valid key for the dialog to say "This looks like a valid Security Key", not just the one in use for your backup. |
Actually, that second issue is just #23929 |
As @AndrewFerr says, I think this is doing the right hting |
Steps to reproduce
Outcome
What did you expect?
Clearer indication of the backup state
What happened instead?
UI doesn't really correspond to what is happening
Operating system
No response
Browser information
Chromium 96.0.4664.45 (Official Build) Arch Linux (64-bit)
URL for webapp
develop.element.io
Application version
Element version: 2039f1f-react-5e77822bccd3-js-87b920698f4c Olm version: 3.2.3
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: