https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #47 from Malte Deiseroth <msdeiser...@gmx.net> --- (In reply to Brian from comment #46) > We can probably disregard tests done with the stable version in the Store. > For now, we're focused on the latest builds, containing tentative fixes in > both KDEConnect-Android and GSConnect. > > @Albert, do you have any logs (both KDEConnect and GSConnect) and Wireshark > traces of your recent failures (using *all* the changes you've made so far)? > With these, we should be able to determine at what precise stage the key > negotiation fails, and see where the applications still fall short. > > (FYI, you can decrypt GSConnect's TLS traffic in Wireshark using steps > explained here: > https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/ > 1548#discussioncomment-4682656 and > https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/ > 1548#discussioncomment-5273879) I installed kde connect master via android builder on my phone. I installed the gsconnect from Alberts repo https://github.com/albertvaka/gnome-shell-extension-gsconnect/compare/main...ecdsa-keys and obtained a dump with: ´sudo tcpdump -v -i wlp3s0 -w kde_connect_dump.pcap dst 192.168.11.95´ with the local ip address of my phone. During capturing I repaired my phone and clicked the mount button of kde-connect. I then opened nautilus and tried to browse files on the phone. This resulted in a permission denied error. I then stopped the capture. You can download the capture here: https://nextcloud.deiseroth.de/s/GHH4sg5JMiXRyar -- You are receiving this mail because: You are watching all bug changes.
