On Wed, 6 Apr 2022 at 09:37, William Lallemand <wlallem...@haproxy.org> wrote: > > Hello David, > > On Tue, Apr 05, 2022 at 07:07:47PM +0100, David CARLIER wrote: > > Hi, I recall there is a openssl3 port ongoing perhaps ? > > > > but here a little "band-aid" proposal for the actual master branch. > > > > From 2d76cb9f249b9519d2b102133b224716965f3f02 Mon Sep 17 00:00:00 2001 > > From: David Carlier <devne...@gmail.com> > > Date: Tue, 5 Apr 2022 19:03:05 +0100 > > Subject: [PATCH] BUID/MINOR: ssl fix warning build with openssl 3 > > > > fix warning build from various deprecated apis from the 3.x release. > > I'm not sure what deprecated warning you are seeing, I only have the one about > the Engine API, that will be disabled by default later.
Fair enough by my old question > I recall there is a openssl3 port ongoing perhaps ? I was trying to see if the said 3.x portage work is close to be merged to master then yes my patch is useless. Otherwise > but here a little "band-aid" proposal for the actual master branch. my patch is just a temporary fix. > > > --- > > include/haproxy/openssl-compat.h | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/include/haproxy/openssl-compat.h > > b/include/haproxy/openssl-compat.h > > index 87bb5109c..8a252aef9 100644 > > --- a/include/haproxy/openssl-compat.h > > +++ b/include/haproxy/openssl-compat.h > > @@ -2,6 +2,7 @@ > > #define _HAPROXY_OPENSSL_COMPAT_H > > #ifdef USE_OPENSSL > > > > +#define OPENSSL_API_COMPAT 0x10100000L > > #include <openssl/bn.h> > > #include <openssl/crypto.h> > > #include <openssl/ssl.h> > > -- > > 2.34.1 > > That is not a good idea in my opinion, the goal is a real portage to the 3.0 > API, once it's done it is supposed to compile with OPENSSL_NO_DEPRECATED > defined. > > -- > William Lallemand
