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

Roster issues when contact registers a new key #1171

Closed
daniele-athome opened this issue Apr 9, 2018 · 0 comments
Closed

Roster issues when contact registers a new key #1171

daniele-athome opened this issue Apr 9, 2018 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@daniele-athome
Copy link
Member

daniele-athome commented Apr 9, 2018

When a contact registers a new key, the server invalidates the roster from the previous account (i.e. sends unsubscribe to all buddies). This causes some weird behaviour in sending/receiving messages because, if the contact hasn't connected yet, the unsubscribe was not delivered yet, so it didn't happen.
This also mean that for a moment the two users are authorized, which can't happen. This part needs also a fix on the server.

There is also another issue with key fingerprint mismatch that is causing the users database to have 2 records with different fingerprint and same timestamp (which can't happen).

Issue #1127 might be somewhat related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant