net/haproxy/patches/0007-DOC-update-the-list-of-OpenSSL-versions-in-the-READM.patch

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