From: William Lallemand Date: Tue, 27 Oct 2026 15:13:40 +0000 (+0000) Subject: DOC: configuration: clarify SCT support by TLS library and version X-Git-Tag: v3.5-dev10~5 X-Git-Url: https://git.kaiwu.me/$%7BISSUES%7D/static/gitweb.js?a=commitdiff_plain;h=7efd0b7ada8558cbecd137c1c8d8097d2d8916f6;p=haproxy.git DOC: configuration: clarify SCT support by TLS library and version List the TLS versions and libraries supporting SCT delivery, and indicate that QUIC is unsupported. This should be backported with the SCTL fixes. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 8d6822653..ecf11d16e 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -18196,6 +18196,10 @@ crt valid Signed Certificate Timestamp List, as described in RFC. File is parsed to check basic syntax, but no signatures are verified. + SCT delivery over TLS 1.2 and earlier is supported with OpenSSL 1.0.2 and + later or AWS-LC. TLS 1.3 requires OpenSSL 1.1.1 and later or AWS-LC. SCT + delivery over QUIC is not supported. + There are cases where it is desirable to support multiple key types, e.g. RSA and ECDSA in the cipher suites offered to the clients. This allows clients that support EC certificates to be able to use EC ciphers, while