Use native chrome ssl sockets #433
This looks pretty similar to a change by @flackr, but submitting anyway in case there's something I'm missing.
Previously, we relied on a pure javscript ssl implementation called forge
As a result, secure sockets were not secure.
This solves the problem by using the (present since Chrome 38) secure
As you pointed out I have a similar change https://github.com/flackr/circ/tree/chrome-sockets-tcp-secure. The issue I found when trying this is that chrome.socket requires additional attestation which fails on many SSL irc servers. For example, when connecting to freenode: