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

Make Settings: Security & Privacy page wrt. Secure Backup less confusing #27962

Open
barathrm opened this issue Aug 24, 2024 · 2 comments
Open
Labels
A-E2EE A-E2EE-Key-Backup O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement

Comments

@barathrm
Copy link

Your use case

I dont' know whether this is a bug or bad UX or me missing something basic.

What would you like to do?

Understand the context of cross-signing vs secure backup and why there are seemingly two buttons for the same thing.

I'm trying to figure out why every time I start element desktop it asks my to verify, even though I've already cross-verified the session and all my sessions have a green shield (#27710).

I go to settings/Security & Privacy and see the following

image

Note that under cross-signing it says that it's not set up, but the button under it is for "Set up Secure Backup", which does not sound like the same thing. I've always used cross-signing only. There seems to be a dedicate section for secure backup, with its own dedicated button "Set up". Both seem to start the same UX flow.

I'm now left with some confusing thoughts, chief among them

  • Is cross-signing fixed by setting up secure backups?

Have you considered any alternatives?

No response

Additional context

No response

@barathrm
Copy link
Author

Addendum; if my cross-signing is broken, is this message from the Sessions part of Settings misleading/false?

image

@dosubot dosubot bot added A-E2EE A-E2EE-Key-Backup O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist labels Aug 24, 2024
@barathrm
Copy link
Author

Possibly related to #26468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE A-E2EE-Key-Backup O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement
Projects
None yet
Development

No branches or pull requests

1 participant