On Oct 30, 2014, at 11:54 PM, Jens Alfke <j...@mooseyard.com> wrote: > >> On Oct 30, 2014, at 8:28 PM, 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. > > Not that I know of. SecureTransport is used by Safari and by most other apps > that use HTTPS, so if it didn't work that would have been a deal-breaker for > shipping any version of the OS. > > You didn't say whether your code works on other versions of OS X…? > > —Jens
Thanks for your reply, Jens. I’m having a particular problem with Chrome that is consistent across all OS versions except Snow Leopard where the behavior is very different. I’m still investigating that aforementioned problem but may have questions about it for the list later. Safari works with our code on Lion, Mavericks and Yosemite but not Mountain Lion, where I’m getting a (server) crash in libcrypto. I need to investigate the ML crash but I suspect it’s an error in my code somewhere. I actually don’t expect Safari on Snow Leopard to work with our code because it appears to me that the implementation of websockets does not meet spec requirements. Firefox works with our server code on Mountain Lion, Mavericks and Yosemite. On both Snow Leopard and Lion, the SSLHandshake returns status 0 but the following payload is a single byte (it should be much more - the websocket handshake sequence). /Mick
_______________________________________________ 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
