Device::encryptionInfo states to return the SHA1 sums of the local and remote certificates. Actually returned are the DER (binary) encoded local certificate, as well as the PEM (base64) encoded remote certificate. See attached patch for a possible fix. Reproducible: Always Steps to Reproduce: 1. kdeconnect-cli --encryption-info --device <device> Actual Results: SHA1 fingerprint of your device certificate is: XX:XX:XX:XX: ::::::*:H:÷ SHA1 fingerprint of remote device certificate is: --:--:-B:EG:IN: C:ER:TI:FI:CA:TE:--:--:- :XX:XX:XX:... ... ... ...XX:XX Expected Results: SHA1 fingerprint of your device certificate is: f9:5c:b3:0c:57:aa:31:5c:fc:13:0a:cc:de:9b:df:07:f9:5c:90:79 SHA1 fingerprint of remote device certificate is: 6c:b1:4d:c1:18:d7:81:32:da:10:96:8e:4e:4b:eb:94:e6:dc:1d:f8
Created attachment 100807 [details] core/device.cpp patch
Thanks for the patch! Could you please provide me with your name and email? So I can apply it in your name, for authoring reasons. Contact me at albertvaka@gmail.com if you don't want to make it public.
I am very happy you accepted my very first open source contribution. Thank you for your work on kdeconnect. -- Thomas Posch
Thanks to you! I'm happy you decided to contribute and I look forward to more patches from you :)
Git commit a759cdf678c80837a3737dac7a0c0cfb42329720 by Albert Vaca, on behalf of Thmoas Posch. Committed on 29/08/2016 at 18:41. Pushed by albertvaka into branch '1.x'. Device::encryptionInfo returned the entire certificate instead of the hash M +11 -8 core/device.cpp http://commits.kde.org/kdeconnect-kde/a759cdf678c80837a3737dac7a0c0cfb42329720