Right now I'm developing an application using Xamarin.Forms. I ran into a problem with the TLS protocol.
My application uses an API. Because of security reasons the API uses HTTPS. This week we decided to remove the support of TLS 1.0 to accept only TLS 1.1 and 1.2 on the server side, but after we made this change, I noticed that my application stoped working.
While debugging I noticed that the call of the API throws an exception (I'm using HttpClient class from .Net). By searching for solutions on the Internet, I saw that many people think the problem is related to TLS support.
I solved this problem on Android and iOS using a plugin named ModernHTTPClient but one of my customers reported me that on his device running on Android they still have the problem (he's running a device with Android 4.2).
Checking Android documentation I saw that this version have support but is not enable by default, and the hard part is that there's not much documentation in the Internet about how I can activate this.
Any advice of how I can activate this? Did Xamarin.Android have native support for TLS 1.1 and up?
Thanks
ModernHTTPClient should use the platforms' native HTTP handling. Looks like for now you can build it manually using this pull: https://github.com/paulcbetts/ModernHttpClient/pull/210
Related
I am getting an SSL error only when using while using WordPress for IOS I cannot view nor connect to my wordpress site from my IOS devices. After over a week of troubleshooting with my host and wordpress for ios the issues still persist and no one seem to figure out what the problem is.
iOS has new TLS restrictions as of iOS 13. I created a package written in Obj-C to handle sockets, and I also included a lot of good info in the readme about how to correctly configure certificates given the new restrictions.
https://github.com/eamonwhiter73/IOSObjCWebSockets/tree/master
I am trying to find what is the default implementation of BlackBerry for TLS protocol. Does it default to 1.0 or 1.1 or 1.2.
I am trying to find 1. What versions are TLS are supported 2. What is the default?
I have an app on BB world that connects to a back office server. The server team has decided to deprecate TLSv1.0. I am trying to find if this will impact my customers?
Current versions of BB10 do indeed support TLS 1.2 which you can test by using tools provided by SSL Labs. Unfortunately that is not the end of the story.
TLS is a protocol which specifies how to set up and use an encrypted connection. It does not set absolute requirements on encryption algorithm support however. I am aware of one documented case of an issue connecting with some Exchange Active Sync servers because the BB10 device and the server as configured do not have any cypher suites in common. Other EAS servers that are configured differently do not present this issue to BB10 devices.
What you need to do is find out specifically how the server team is going to configure TLS, and what they are going to accept for connections.
I am a new to flex programming. Recently apple has change policy and from 1 June 2016 any app in appstore must supports IPv6 network only as per new policy. So when i test my new version of an application in IPhone it could not able to communicate with webservice. however previous version were working fine.
In my Application I am using mx.rpc.remoting.RemoteObject.RemoteObject and URLMonitor.
My web services is created in BlazeDS
I am using flex 4.6 AIR 22.
Is mx.rpc.remoting.RemoteObject.RemoteObject can handle IPv6? I am not using any hardcode IP like "0.0.0.0".
Please suggest me any ANE for URLMonitor also
Thanks
Zalak L.
I have the same problem, and after more than 4 code modifications and submissions to Apple review, I think the problem is about AMF protocol. It's not compatible with ipv6. The call to the server is not fired.
Now I'm modifing my service facade tu use URLLoader instead of RemoteObjects.
upon running my app in ios9 simulator, i get app transport security related issues because some of my urls are not using https. I tried it in an ipad with ios9 and its working fine.
Upon release of ios9, should I expect my live app (sdk 8) to fail on ios9 devices? Just making sure if late appstore updates are safe.
Thanks!
Reference
If you’re developing a new app, you should use HTTPS exclusively. If you have an existing app, you should use HTTPS as much as you can right now, and create a plan for migrating the rest of your app as soon as possible. In addition, your communication through higher-level APIs needs to be encrypted using TLS version 1.2 with forward secrecy. If you try to make a connection that doesn't follow this requirement, an error is thrown. If your app needs to make a request to an insecure domain, you have to specify this domain in your app's Info.plist file.
I have written a summary and ways to how to check Acceptability of Webservice for iOS 9's App transport security
https://medium.com/#Mrugraj/app-transport-security-b7910c4fc70f
It have two ways
Using Curl
$ curl -v https://github.com/
Trying 192.30.252.130...
Using online tool like - https://www.ssllabs.com/ssltest/index.html
TLDR: Is there any way to configure iOS SSL cipher suites for a mobile-device-initiated, REST-over-TLS network connection, without using non-iOS-native HTTP or SSL libraries. If so, where is the API documented and are there any examples?
Details: I am working with others to develop an iOS mobile application and we are unable to locate details about how to force the native iOS crypto libraries to use a specific version of SSL/TLS, or specific cipher suites. This is for a custom REST application, so the approach would have to be possible to connect via HTTP over TLS.
The app is written in Objective-C. We are trying to stay within iOS native functionality without including a separate SSL/TLS library.
I did try to search for an answer on SO, but I didn't find anything that seemed to cover the question.