RFC: Moving SwiftNIO SSL to BoringSSL

[Jean-Daniel]

@lukasa

Naturally, on the long time scale these features will ship in regular OpenSSL versions shipped with LTS distributions. But those timescales are long . TLS1.3 has shipped, and is used for a huge swathe of internet traffic today, yet is completely unavailable to anyone deploying on Ubuntu 18.04. That means that there will be applications in place in 2023 that still have no TLS1.3 implementation. Given that TLS 1.0 and 1.1 are being deprecated shortly, that leaves those implementations in a very lonely space in the protocol support tensor field.

They plan to back port OpenSSL 1.1.1 on 18.04 (there is already an SRU open), but the process is very slow. If we are lucky, maybe TLS 1.3 will be available on 18.04 before 2020.

And I think LibreSSL didn't even start to work on TLS 1.3.

I would really appreciate to don't have to bother with this kind of details when I have to deploy some apps, so I'm very exited about having BoringSSL embedded in Swift NIO.