Issue #173 -- Enabling TLS 1.1 & 1.2 on Android Versions prior to Lollipop #210
Conversation
… Lollipop Error when connecting from Android to a server that does not support TLS 1.0
|
Is there any plan to merge this pull? |
|
This is becoming a huge issue for one of my clients. They just upgraded their API enpoint, which is breaking apps in the field. What can I do to help get this merged? |
|
Just take the branch compile it and use it. You can take a look changes and if you want you add aditional changes to fit your needs. Please note that you will have some limitations regarding supported cipher suites. You can check the list of supported cihper suits on the Android site. It is possible that your client force usage, or in other words disable certain cipher suits for certain version of TLS. Meaning if they require (for security reasons) to use specific cipher suites, they will normally disable some weak/or not strong sipher suites and your application will not be able to communicate, even with TLS 1.2. |
|
It's also possible to achieve the same thing using reflection. I was able to grab the private "client" of the parent and set it. It would be nice if some of those fields were protected rather than private. |
|
Hey ! Any plan to merge this ? |
|
+1 |
Updated OKHttp libraries Remove validation of client certificates for class HostnameVerifier - OkHttpNetworkHandler
|
I really need this too :( |
|
Is anyone able to build branch 8eea4ad? I'm getting ambiguous reference errors (OperationCanceledException) and obsolete errors (ClientCipherSuitesCallback) on file OkHttpNetworkHandler in the Android project. I am too looking for a 1.2 TLS solution on lower Android versions. |
|
You can do it with the native handler provided by Xamarin: Hope it helps! |
8 participants
Error when connecting from Android to a server that does not support
TLS 1.0