Reputation: 316
Impact of decommission TLS 1.0 TLS 1.1 on iOS app
I am checking the impact on iOS app upon decommission of TLS 1.0/TLS 1.1 & commission TLS 1.2 on server side.
Before adding support for TLS 1.2 on server side, I am assuming "URLSessionConfiguration.default.tlsMinimumSupportedProtocol = SSLProtocol.tlsProtocol12"; is the only way we can test its impact on iOS app(both URLSession/NSURLConnection & WKWebView/UIWebView). Could you please confirm the same. Also let me know if there is another way to do that.
After adding support for only TLS 1.2(removing TLS1.0 & TLS1.1) on server side(www.nist.gov, https://github.com, https://fancyssl.hboeck.de) I tried to load the page in WKWebView by setting "URLSessionConfiguration.default.tlsMaximumSupportedProtocol = SSLProtocol.tlsProtocol11" but seems like it works. My expectation was it should not work. (Tried it on iOS 8 Simulator with iOS 11.2)
Posted same question here too
Upvotes: 1
Views: 1672
Answers (1)
Related Questions
- Why iOS 13.x below the 13.4 version is still using TLS 1.0/1.1 and how to force it to use TLS 1.2 and above?
- iOS 13 TLS issue
- iOS 7 and TLS1.2 support
- How to Enable TLS 1.2, 1.1,1.0, and SSL in iOS app?
- TLS V 1.1 and TLS V 1.2 iOS issue
- Does iOS "app transport security enforcement“ mean I need to switch APIs to https?
- Will I be forced to update my iOS app in HTTPS in 2017?
- iOS App Transport Security not accepting TLSv1.2 connection and plist exceptions not making any difference
- iOS app communicating with https only and Apple Transport Security Impact
- Install TLS 1.2 Certificate on iOS App