-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot pair to Sailfish OS #784
Comments
It looks like the Sailfish OS app forces TLS v1.0: // Configure for ssl
QSslConfiguration sslConfig;
sslConfig.setCiphers(socketCiphers);
sslConfig.setProtocol(QSsl::TlsV1_0); Since GLib 2.42.1, SSL 3.0 is no longer supported. See: https://developer.gnome.org/gio/stable/GTlsClientConnection.html#g-tls-client-connection-set-use-ssl3 You should open an upstream issue in cc @R1tschY |
Thank you for your investigation. I created a issue and will soon fix it. |
@R1tschY I've updated the app to 0.5.1-1 (from openrepos) and I still can't connect
|
Hmm, you aren't running GSConnect in a virtual machine are you? If not, by my reading, Sailfish's certificate verification is effectively the same as KDE Connect. |
Oh nevermind I was dumb I forgot to save the firewall from runtime to permanent configuration and rebooted in between. And no, I'm not running anything in a VM, but there's a different issue now: when I click pair my sailfish connect app gives me a pairing request notification, but it won't pair. The generated support log is empty. Tapping on my PC does nothing. My laptop was paired with the regular KDE desktop app a while ago. |
To be clear, because a lot of people miss this, you have to leave the generate support dialog open while trying to log a problem. There should at least be a pair packet in the log if it was received correctly. Because of many (erroneous) claims about leaking private information, debugging messages are only printed when the dialog is open. |
|
Holy crap! Thanks, new GitHub Android app! Instead of replying to @psrcek I somehow managed to EDIT their message! Wow, not cool. Restored from the edit history, so at least there's that safety net. Still, apologies, no idea how that happened. |
Is there no response packet from the Sailfish device? The side requesting the pair should send one of those, and the accepting side should send back basically the same packet. Did you initiate this from GSConnect or Sailfish? |
Initiated it from GSConnect. Initiating from Sailfish does literally nothing. |
I could start up wireshark or burp suite or somethning if that helps? |
This is starting to sound like another firewall problem. Are you sure you have ports |
This is true for Sailfish as well? It seems like your phone is receiving pair requests fine, but GSConnect is not receiving anything in response. |
I have no firewall on sailfish. Or at least I'm not aware of one... |
Hmm, not sure what to say then. GSConnect isn't logging any errors and nothing has changed in that code path for a long time. As far as I know, that's also true of the Sailfish app. You may have to debug the Sailfish app or check with a tool like wireshark to see if something is blocking packets on the network. |
hehe.. I found my problem. A system update fixed it.. thanks a lot for your help though! 10/10 tech support! 🎉 |
(That happened to me a second time, BTW! I have since uninstalled that broken piece of... app. Avoid with extreme prejudice, at least until they work the bugs out. Their mobile web interface is better anyway, using Chrome for Android. For instance, the web editor can autocomplete @-mentions, even on my phone, a feature inexplicably missing from the dedicated Android app.) |
Describe the bug
Cannot pair to a phone running SailfishOS.
Steps To Reproduce:
Expected behavior
I should be able to pair my devices.
Screenshots
Support Log
System Details (please complete the following information):
uname -a
:Linux daweed 5.5.8-arch1-1 #1 SMP PREEMPT Fri, 06 Mar 2020 00:57:33 +0000 x86_64 GNU/Linux
GSConnect environment (if applicable):
Additional Notes:
I've opened ports 1716-1764 tcp/udp in my firewall settings
The text was updated successfully, but these errors were encountered: