Fingercomp 37 Posted September 9, 2016 Share Posted September 9, 2016 The RFC 5246 describes the TLS 1.2 protocol that's very heavily used today to encrypt the traffic sent over regular sockets. Have you noticed the "https" part of this page's URL? It means that a HTTP server listens, generally, on the 443 port for HTTP requests sent over a TLS connection. Currently you can only send HTTPS requests, there's no built-in solution for establishing TLS sockets to send arbitrary data. An issue on GitHub asks exactly for this feature to be added. Now, look at the date of posting. After 1.5 years, we still don't have TLS socket support. Oh, maybe, not really now. Yes, I have a fully working TLS 1.2 implementation (without certificate validation, though). It uses the tier 2 data card (it provides the secure random and hashing functions), and the Computronics's advanced cipher block (RSA encryption). And it isn't even incredibly slow! It only takes 4 seconds to connect. I've tried to connect to some https servers, and all of them worked perfectly. The library is hosted on my OpenPrograms repository, and can be installed via OPPM: oppm install libtls. Here's my another creation that uses the library: a simple and dumb (yet working, huh) HTTP 1.1 library. It's solely purpose is to allow to specify the request method (which also has its own issue, that, unfortunately, is still open), like PUT or PATCH. It uses raw sockets or TLS sockets to do so. It's also hosted on my repository, and can be downloaded via OPPM (oppm install libhttp), too. Hopefully you'll make use of these two libraries I've written. Quote Link to post Share on other sites