https://bugs.kde.org/show_bug.cgi?id=501352
Bug ID: 501352
Summary: Old certificate used when calculating verification key
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: dan...@landau.fi
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
SUMMARY
The verification key shown is wrong when the other device has been paired
before, but has since changed certificate.
STEPS TO REPRODUCE
1. Pair a device
2. Change certificate/key on the other device
3. Perhaps restart KDE Connect Android (not sure if required)
4. KDE Connect Android now shows the device as remembered device currently
unavailable
5. Unpair it
6. Now it shows up in Available devices and you can pair it but the
verification key is wrong.
You can force stop and restart KDE Connect Android at this point, and the
verification key is correct.
I don't have 100% conclusive proof that it's the other side certificate, but
IMO that's a very plausible reason for the effect I'm seeing.
--
You are receiving this mail because:
You are watching all bug changes.
