]> git.ipfire.org Git - thirdparty/haproxy.git/commitdiff
DOC: install: remove boringssl from the list of supported libraries
authorWilliam Lallemand <wlallemand@haproxy.com>
Mon, 10 Jun 2024 16:42:13 +0000 (18:42 +0200)
committerWilliam Lallemand <wlallemand@haproxy.com>
Mon, 10 Jun 2024 16:54:28 +0000 (18:54 +0200)
BoringSSL support is known to be broken since 2021, it was removed from
the CI at this time and never fixed.
(30ee2965b66f20a2649323ca36029bf2440e34b9)

Even the QUIC code for boringSSL was removed in 2022.
(e06f7459faf36f5f63092cb6ce89d281dfc4ee6a)

INSTALL

diff --git a/INSTALL b/INSTALL
index af8c483e054099dc98ca13c491aac770d7d2dc6b..016b50009f77e90f02737ae5b9d81563d6dc542d 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -252,7 +252,7 @@ https://github.com/openssl/openssl/issues/17627). If a migration to 3.x is
 mandated by support reasons, at least 3.1 recovers a small fraction of this
 important loss.
 
-Four OpenSSL derivatives called LibreSSL, BoringSSL, QUICTLS, and AWS-LC are
+Three OpenSSL derivatives called LibreSSL, QUICTLS, and AWS-LC are
 reported to work as well. While there are some efforts from the community to
 ensure they work well, OpenSSL remains the primary target and this means that
 in case of conflicting choices, OpenSSL support will be favored over other