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

Element messenger should store a backup of the encryption and secure backup keys on the messenger #1104

Closed
Ambioid opened this issue Jul 25, 2023 · 1 comment

Comments

@Ambioid
Copy link

Ambioid commented Jul 25, 2023

Your use case

Problem:

When you log onto element, there are 2 ways to access your old data. Entering in your backup keys, or verifying from another device. As most users usually don't manage their backup keys at all, this means there is only 1 way to recover messages, verifying from a signed-in device. This is a problem when users log out on multiple devices at once, making it possible for them to lose all factors of authentication, and losing all their messages.

Proposed change:

I propose that, in addition to prompting the users to store the backup keys as a .txt on their computer, element should store a second backup key on device in the app's data directory, which would mean that even if the user didn't conciously store their backup keys, element could still automatically apply the encryption keys, just by virtue of being previously logged on with this device.

Have you considered any alternatives?

No response

Additional context

No response

@t3chguy
Copy link
Member

t3chguy commented Jul 26, 2023

They are in the app's data directory. But for privacy & security when you log out we wipe all app data so that you do not leak anything to a future user of the machine (think work computers or libraries) - this is not something we wish to support. I suggest you look at element-hq/element-meta#922 instead

@t3chguy t3chguy closed this as completed Jul 26, 2023
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

2 participants