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

Fix corner cases for registration reset #1105

Merged
merged 2 commits into from
Apr 30, 2020
Merged

Fix corner cases for registration reset #1105

merged 2 commits into from
Apr 30, 2020

Conversation

Mikunj
Copy link

@Mikunj Mikunj commented Apr 27, 2020

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.

@Mikunj Mikunj requested review from neuroscr and Bilb April 27, 2020 04:59
@@ -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();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this do?

Copy link
Author

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

Copy link

@neuroscr neuroscr Apr 27, 2020

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?

Copy link
Author

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

@Bilb Bilb merged commit 5564bfa into oxen-io:clearnet Apr 30, 2020
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

Successfully merging this pull request may close these issues.

None yet

3 participants