Re: App linked with older SDK get SSL error -9806, newer linkage avoids it
Re: App linked with older SDK get SSL error -9806, newer linkage avoids it
- Subject: Re: App linked with older SDK get SSL error -9806, newer linkage avoids it
- From: "Quinn \"The Eskimo!\"" <email@hidden>
- Date: Tue, 10 Mar 2015 07:53:34 -0700
On 9 Mar 2015, at 20:31, Daniel Jalkut <email@hidden> wrote:
> I don’t want to share the URL before I get his clearance to do so, but does this sound familiar to anybody?
It's very likely related to TN2287 "iOS 5 and TLS 1.2 Interoperability Issues".
<https://developer.apple.com/library/ios/technotes/tn2287/_index.html>
While this technote was written for iOS, I believe the same applies to OS X (with OS X 10.7 standing in for iOS 5).
I suspect that the server is requiring TLS 1.2, hence this failure when you link with the old SDK. You could test that theory by (temporarily) linking with the new SDK and then hand-wiring a specific TLS version to see which ones work and which ones fail. How you do that depends on what API you're using. If this is CFHTTPStream code, you'll need to get the Secure Transport context (kCFStreamPropertySSLContext) and set the min and max version in that (SSLSetProtocolVersionMin, SSLSetProtocolVersionMax).
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden