W/SyncthingNativeCode(7710): <DATE> http: TLS handshake error from 127.0.0.1:xxxxx: tls: client offered and unsupported, maximum protocol; version 300
W/SyncthingNativeCode(7710): <DATE> http: TLS handshake error from 127.0.0.1:xxxxx: tls: client offered and unsupported, maximum protocol; version 301
It seems like the latest syncthing binary requires a version of TLS that is not supported by Android 4.4.4. The question is, is there a way to enable older TLS versions for the binary via environment variables or something?
I suspect that the issue in case is that the Android app cannot communicate with the Go binary, since the Go binary expects TLS cipher suits the Java part does not support. So actually it would be something we’d need to address in the Java part.
But given that we already have targetSdkVersion 26 and minSdkVersion 16, it should be possible to try the workaround with the wrapped SSLSocketFactory that @silverbluep mentioned above.
If we want to do that, I think @silverbluep should open an issue in the issue tracker on Github.
Do I get this right: tls 1.2 was enabled in a recent syncthing update 0.14.51? .52? and after this, Android 4.4 and earlier cannot access the rest api on https because of the tls version enforcement from the native binary? I’m asking because some weeks ago I ran syncthing android successfully on an old android 4.1 phone.
Luckily for me .39 (I think it was) worked just fine with my old 4.0.1 tablet when the screen broke and I needed to transfer 50 gigs of data… and the other physical interfaces were broken. I found syncthing then and it did the job. Otherwise I wouldn’t be here now - with synchting running on everything I’m using