Tai Chi Minh Ralph Eastwood

Okay that would work too! Just to note, the client probably should have a separate context per connection to support features like multiple protocols.

API suggestions here too from libtls: https://github.com/libressl-portable/openbsd/blob/master/src/lib/libtls/tls.h Man page: http://man.openbsd.org/OpenBSD-current/man3/tls_init.3

@sustrik I'm starting to feel that tls support ought to be in its own library (something like a libmill-enabled libtls library - libmilltls) which is separate. What are your thoughts...

Looks good so far - I'm currently working on a more complete API. Currently, the API only supports TCP whereas there's actually no restriction for supporting non-TCP connections. We should...

Excellent, libtls is mainly a wrapper over OpenSSL/LibreSSL API which captures the important parts rather than backwards-compatibility to prehistoric APIs so we know we'd be capturing a good subset of...

v1.0.2 is required for ALPN support so I do recommend it. Without v1.0.2, the API could be made to still work but ignores the ALPN feature. Support for OpenSSL v1.0.2...

Just a note - I won't have time to work on this until the start of September when I'll have significantly more free time.

I've been working on this for the last few days and I've come to the conclusion that this is not the best investment in time. There's a few challenges integrating...

@shehzadkhawar Hi, an update - I'm currently working new support for TLS in dsock. It's still WIP, but you can find it here https://github.com/sustrik/dsock/pull/17

A coincidence! I read up on this yesterday. Currently the best way for this is a thread pool sadly. I think there was some lwn article on this (I'll find...