Open BenWiederhake opened 3 years ago
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?
Does this happen with everyone or just some contacts?
Only one particular contact, as far as I can see.
Could it be an issue with a new official client version, re-generated keys on new or known contacts?
My best guess is re-generated keys. In the mobile client, it says "Deine Sicherheitsnummer mit
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.
My best guess is re-generated keys.
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?