You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

36 lines
1.6 KiB

  1. From 8d99949c4c51d95c14fb2b09d18e1cff058f0c17 Mon Sep 17 00:00:00 2001
  2. From: Willy Tarreau <w@1wt.eu>
  3. Date: Tue, 18 Jul 2017 06:58:16 +0200
  4. Subject: [PATCH 07/18] DOC: update the list of OpenSSL versions in the README
  5. 1.1.0 is also supported nowadays. Also mention the best effort support
  6. for derivatives.
  7. (cherry picked from commit 7ab16868bc6e9d5ef879e1046effa035789835cc)
  8. Signed-off-by: Willy Tarreau <w@1wt.eu>
  9. ---
  10. README | 8 ++++++--
  11. 1 file changed, 6 insertions(+), 2 deletions(-)
  12. diff --git a/README b/README
  13. index 839d06ec..8ad70e66 100644
  14. --- a/README
  15. +++ b/README
  16. @@ -113,8 +113,12 @@ build fails due to missing symbols such as deflateInit(), then try again with
  17. Your are strongly encouraged to always use an up-to-date version of OpenSSL, as
  18. found on https://www.openssl.org/ as vulnerabilities are occasionally found and
  19. you don't want them on your systems. HAProxy is known to build correctly on all
  20. -currently supported branches (0.9.8, 1.0.0, 1.0.1 and 1.0.2 at the time of
  21. -writing). Branch 1.0.2 is recommended for the richest features.
  22. +currently supported branches (0.9.8, 1.0.0, 1.0.1, 1.0.2 and 1.1.0 at the time
  23. +of writing). Branch 1.0.2 is currently recommended for the best combination of
  24. +features and stability. Asynchronous engines require OpenSSL 1.1.0 though. It's
  25. +worth mentionning that some OpenSSL derivatives are also reported to work but
  26. +may occasionally break. Patches to fix them are welcome but please read the
  27. +CONTRIBUTING file first.
  28. To link OpenSSL statically against haproxy, build OpenSSL with the no-shared
  29. keyword and install it to a local directory, so your system is not affected :
  30. --
  31. 2.13.0