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

E2E: "set up new recovery options" UI for key backup confusing #8884

Closed
matthijskooijman opened this issue Feb 22, 2019 · 1 comment
Closed

Comments

@matthijskooijman
Copy link

Description

I just played around with the key backup, and was a bit confused. One of the things that confused me, was the "Set up new recovery options" UI.

This UI is offered when you click "Use key backup" on a new device or "Restore from backup" on a device that is already setup to use key backup:

image

When you click "set up new recovery options", you get this UI, which I believe is the same as when you start using key backup for the first time:

image

The wording "Set up new recovery options" suggested to me that this would extend the existing backup setup with more recovery options (e.g. to allow downloading the recovery key or change the passphrase). However, it seems that his instead completely replaces the existing backup setup. If you do this on an existing device, I believe it will just create a new backup, with the same contents, and a new passphrase and/or recovery key. However, if you do this on a new device, I believe it will replace the old backup, possibly deleting your key backups (or, at least, if older versions of backups are kept, making them harder to reach). This could use some more specific warnings, perhaps?

This might be related to my remark at #8814 (comment) that wonders whether the passphrase should really be a "recovery passphrase". If you don't think of it like this, then "set up recovery options" does not mean "set a new passphrase and/or recovery key".

Version information

https://riot.im/app
matrix-react-sdk version:
riot-web version: 1.0.1
olm version: 3.0.0

@kittykat
Copy link
Contributor

I'm going to close this issue for now as the UI has changed significantly. If you are still experiencing the issue, please file a new one with details of what could be improved

Screenshot from 2021-11-30 17-59-56
Screenshot from 2021-11-30 17-59-40
Screenshot from 2021-11-30 17-59-22

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