JohnnyZ
The corefxlab libuv pipeline does not support tls.
You have to build everything from scratch. But with the pipelining, it is much easier.
Most of the implementations relying on new classes such as span, memory buffers. Too much of dependencies to pull over individually.
Please let me know how it goes. I plan to do this once net core 2 going into a reasonably stable state I can start over with new classes.
That one intensively use new io memory namespace and new span which is not available yet (only in net core 2.0). That is the reason I am waiting at the...
tls is all about open connections and negotiate then encrypt. It has to happen in the beginning, that makes it very hard to do some 'just plug it in'. Why...
NetUV is going to stay on net standard 1.6 for quite some time. There are few options for ssl, for instance https://github.com/Drawaes/Leto Or open to the libuv approach, see https://github.com/libuv/libuv/issues/1128
Another option will be managed ssl stream from .net. I haven't completely made my mind yet.
Tls will be added for sure. The question is SslStream or openSsl at the moment.
SslStream is not quite there yet. see https://github.com/aspnet/KestrelHttpServer/tree/dev/src/Kestrel.Tls