Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Use instead of com.hurlant.crypto.tls.TLSSocket #68

luciferous opened this Issue · 10 comments

4 participants


No description provided.


What's advantage using SecureSocket?


It sounds like something worthwhile in the long-run, but the Linux issue is a problem.

Also, I note on the page that SecureSocket doesn't allow overriding self-signed certs easily which would be a major impediment for development. It's unclear to me from the description if a self-signed cert that is accepted manually by the browser would also be accepted by SecureSocket (which is how native WebSockets work in firefox). And it might differ between browsers how the trust chain works for SecureSocket.

So I would personally be cautious of switching until SecureSocket is proven out on multiple browsers and OS platforms.

Although, since I am the one who added the as3crypto support I could be biased. ;-)


I'm interested in maintaining a branch with SecureSocket. Hopefully it matures to acquire feature-parity with as3crypto.

@gimite The advantage of using something native to Flash is eliminating the need to rely on a 3rd party dependency.


Would this also reduce the swf file size? I seem to remember it got a lot bigger when the wss support was added. Would be a big win :)


If the advantage is just that it's standard library and it possibly reduces SWF file size, but it has some issues such as one in Linux, then I will not switch to SecureSocket for now. 172KB wouldn't be much issue with network/devices recently...


@gimite Would you be open to host a SecureSocket branch?


I don't plan to do that myself for now. It's open source, so anyone who want can do it.


I think hurlant feels safer.


Related note: #122 reported that SSL communicatoin fails with current implementation in some environment and the issue doesn't happen with SecureSocket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.