Yes, “our server” is a launchd process that uses Secure Transport APIs.
Calling SSLSetProtocolVersionEnabled with kTLSProtocol1Only gives me an -50 error. kSSLProtocolAll gives me error 0. FYI, I’m using the OS X 10.6 SDK because I’m stuck in Xcode 3.2.6. That SDK does not appear to have support for TLS 1.2. /Mick On Oct 31, 2014, at 1:04 AM, Quinn The Eskimo! <eski...@apple.com> wrote: > > On 31 Oct 2014, at 03:28, Mitchell Laurren-Ring <li...@rynosoft.com> wrote: > >> Does Snow Leopard have a flawed or incomplete implementation of SSL? I’m >> unable to get any web browser to connect via secure websockets to our server >> under Snow Leopard. > > I presume that "our server" is code that you wrote that uses the server side > of Secure Transport. If not, let me know. > > I vaguely remember something weird along these lines. What happens if you > force the client to connect via TLS 1.0 rather than TLS 1.2. > > WARNING: This is just for testing. Don't ship this way; TLS 1.2 has > important security fixes. > > 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 (Macnetworkprog@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macnetworkprog/lists%40rynosoft.com > > This email sent to li...@rynosoft.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
