-
Notifications
You must be signed in to change notification settings - Fork 19
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
Cannot message particular user due to "identityFailure" #53
Comments
Does not happen on my system (with signald 0.13.1). I do not know how to reproduce this issue. :( I only have old, known contacts and groups to test with, though. Does this happen with everyone or just some contacts? Could it be an issue with a new official client version, re-generated keys on new or known contacts? |
Only one particular contact, as far as I can see.
My best guess is re-generated keys. In the mobile client, it says "Deine Sicherheitsnummer mit hat sich geändert." (Apparently you speak German, so I think sticking to the original text is a good idea.) It does not seem to be related to whether I have a contact with them or not. I don't have information about client versions. |
Maybe I can force key re-generation on one of my test clients and reproduce this error. And, yes, German is my main language. :) |
Today, I had the opportunity to test this since I accidentally wiped one of my test devices. Commit 89dd6ff now detects the problem. To overcome it, I would need to implement sending a trust request. Much to do for something I expect to happen infrequently. I want to keep this issue open so I do not forget about it. |
pidgin -d
prints:The returned string in
identityFailure
is always the same; presumably it's some kind of "new public key".I couldn't find anything about this error in the entire repository. How do I fix this "broken" state?
The text was updated successfully, but these errors were encountered: