On 15/12/2016 19:03, Lukas Tribus wrote:
Hi Igor,
Am 14.12.2016 um 20:47 schrieb Igor Pav:
Hi Lukas, in fact, openssl already gets early TLS 1.3 adoption in dev,
will release in 1.1.1, and BoringSSL supports TLSv1.3 already.
That's nice, and in fact since 1.1.1 will be API compatible with 1.1.0
[1] *and* support
TLS 1.3 (or whatever we end up calling it [2]), this shouldn't require
any changes in
haproxy at all.
haproxy might be able to use it as soon as the underlying lib supports
it. But it might be good to update the doc and configuration like
no-tls13, force-tls13 and so on.
--
Bertrand
