-
Notifications
You must be signed in to change notification settings - Fork 185
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
Fix corner cases for registration reset #1105
Conversation
@@ -713,13 +713,8 @@ export class RegistrationTabs extends React.Component<{}, State> { | |||
} | |||
|
|||
private async resetRegistration() { | |||
await window.Signal.Data.removeAllIdentityKeys(); | |||
await window.Signal.Data.removeAllPrivateConversations(); | |||
window.Whisper.Registration.remove(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does this do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This removes all keypairs and conversations as well as marks signals registration as not done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to clarify just talking about 718, which I understand you have to said:
marks signals registration as not done
Why do we no longer need that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Registration.remove()
calls storage.remove('chromiumRegistrationDone');
so it's just removing a field from the storage, if we wipe the storage then it's the same behaviour
One of the cases was that the file server tokens weren't removed causing the a fresh registration to upload device links to a different user.
I've changed the reset so it removed all data, and from debugging it doesn't seem to cause issues but i will keep testing.