[kdeconnect] [Bug 387532] kdeconnect -l cause paired device to become unpaired

https://bugs.kde.org/show_bug.cgi?id=387532 --- Comment #5 from Yuxuan Shui --- I guess two changes are needed: 1. verify the CN in certificate sent by the device 2. on android, detect device id changes (happens after user wipe the device and restore apps from backup) --

[kdeconnect] [Bug 387532] kdeconnect -l cause paired device to become unpaired

https://bugs.kde.org/show_bug.cgi?id=387532 --- Comment #4 from Yuxuan Shui --- This problem goes away after clear data on the Android side. So probably the Android app is sending conflicting device IDs? Maybe kdeconnect should reject pair requests like this? -- You are

[kdeconnect] [Bug 387532] kdeconnect -l cause paired device to become unpaired

https://bugs.kde.org/show_bug.cgi?id=387532 --- Comment #3 from Yuxuan Shui --- This problem persists after I remove ~/.config/kdeconnect -- You are receiving this mail because: You are watching all bug changes.

[kdeconnect] [Bug 387532] kdeconnect -l cause paired device to become unpaired

https://bugs.kde.org/show_bug.cgi?id=387532 --- Comment #2 from Yuxuan Shui --- Seems like, the CN= field in the certificate is different from the device ID. Actually, that CN is the same as the device ID my phone used to have (I wiped my phone and the ID changed). -- You

[kdeconnect] [Bug 387532] kdeconnect -l cause paired device to become unpaired

https://bugs.kde.org/show_bug.cgi?id=387532 --- Comment #1 from Yuxuan Shui --- Possibly related lines in log: kdeconnect.core: Starting client ssl (but I'm the server TCP socket) kdeconnect.core: Failing due to ("The host name did not match any of the valid hosts for this