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

Device keys change if indexeddb data gets deleted #9107

Closed
rxl881 opened this issue Mar 11, 2019 · 2 comments
Closed

Device keys change if indexeddb data gets deleted #9107

rxl881 opened this issue Mar 11, 2019 · 2 comments

Comments

@rxl881
Copy link
Contributor

rxl881 commented Mar 11, 2019

Description

UTDs from existing Linux chrome client that has worked previously. All other devices continue to work. Unable to fix by verifying devices or requesting re-sharing of keys.

For the web app:

@dbkr
Copy link
Member

dbkr commented Mar 11, 2019

What has happened here is that Rick's device has had its indexeddb data deleted (presumably he got low on disk space and Chrome looked for things to sacrifice). When this happens, the device keeps the same device ID (because that's in localstorage) but gets new keys (because those are in indexeddb). The result being that any device that has seen his device before will refuse the key change and therefore e2e will break between the two devices.

@dbkr dbkr changed the title UTDs from existing Linux chrome client that has worked previously. Device keys change if indexeddb data gets deleted Mar 11, 2019
@lampholder
Copy link
Member

We're going to draw this occurrance to users' attention with #9109 so we can probably close this.

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

No branches or pull requests

3 participants