netty5/handler
Norman Maurer 8950144567 Correctly include TLS1.3 ciphers in the enabled ciphersuites when using BoringSSL (#10388)
Motivation:

BoringSSL behaves differently then OpenSSL and not include any TLS1.3 ciphers in the returned array when calling SSL_get_ciphers(...). This is due the fact that it also not allow to explicit configure which are supported and which not for TLS1.3. To mimic the behaviour expected by the SSLEngine API we should workaround this.

Modifications:

- Add a unit test that verifies enabled protocols / ciphers
- Add special handling for BoringSSL and tls1.3

Result:

Make behaviour consistent
2020-07-02 21:37:04 +02:00
..
src Correctly include TLS1.3 ciphers in the enabled ciphersuites when using BoringSSL (#10388) 2020-07-02 21:37:04 +02:00
pom.xml Add ResolveAddressHandler which can be used to resolve addresses on the fly (#9947) 2020-01-20 19:34:09 +01:00