https://bugs.kde.org/show_bug.cgi?id=402102
Francisco Gonzalez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=402102
Simon changed:
What|Removed |Added
CC||si...@ergotech.com
--- Comment #3 from Simon ---
Did y
https://bugs.kde.org/show_bug.cgi?id=402102
--- Comment #2 from Francisco Gonzalez ---
This is the datagram received on UDP channel before pairing:
kdeconnect.core: Datagram
{"id":1544834411076,"type":"kdeconnect.identity","body":{"deviceId":"c3bedee7133dbc3a","deviceName":"gzmorell@mia2","proto
https://bugs.kde.org/show_bug.cgi?id=402102
--- Comment #1 from Francisco Gonzalez ---
The problem seems to be with the id of the phone. The id it sends is not the
same as the CN (common name) of the SSL certificate that the smartphone sends.
When kdeconnect tries to open a QSslSocket to download
