App linked with older SDK get SSL error -9806, newer linkage avoids it
App linked with older SDK get SSL error -9806, newer linkage avoids it
- Subject: App linked with older SDK get SSL error -9806, newer linkage avoids it
- From: Daniel Jalkut <email@hidden>
- Date: Mon, 09 Mar 2015 23:31:56 -0400
One of my customers is running into cryptic -9806 SSL connection errors with MarsEdit when connecting to his blog. I’ve confirmed the problems but what is strange is the issues only occur with versions of my app that were built with an older SDK (10.6 in this case). If I build and run my app against a newer SDK such as 10.10, the connection errors don’t occur.
The connection errors occur at seemingly any level of the networking stack, from my direct use of CFNetwork up through implicit use of NSURLConnection via WebKit1 WebViews in my app.
The issue does not affect all SSL URLs, but does seem to affect any SSL negotiation with this specific host. The failure seems to happen at the CONNECT negotiation phase.
I don’t want to share the URL before I get his clearance to do so, but does this sound familiar to anybody? I’m guessing that by linking with the older SDK I'm locking my app into an older code path for some of the SSL stuff?
The customer in question is technically astute and I think he would be eager to e.g. have his certificate repaired or amended if appropriate. The certificate doesn’t show any issues if examined for trust in e.g. Safari.
Any hints about how I might be able to track down the cause of the connection failures and either work around them in the app (short of linking against a later SDK, I’m not ready yet for production releases), or advise him how to work around it by changing the configuration of the server?
Daniel
_______________________________________________
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