https://bz.apache.org/bugzilla/show_bug.cgi?id=68080
--- Comment #5 from Bernard Spil <br...@freebsd.org> --- (In reply to Yann Ylavic from comment #2) > Created attachment 39349 [details] > Unset MODSSL_HAVE_ENGINE_API for OPENSSL_NO_ENGINE > > I'm wondering if we still want to allow for "SSLCryptoDevice builtin" when > OPENSSL_NO_ENGINE is set. I don't know how much this setting is used nor if > we should care, but given that "builtin" is the same as no SSLCryptoDevice > maybe we could still let httpd start even if it's built against openssl >= 3 > or OPENSSL_NO_ENGINE. > The ENGINE api is deprecated in openssl >= 3 so in r1908537 we defined/used > MODSSL_HAVE_ENGINE_API to compile out any code using it, maybe we could do > that too for OPENSSL_NO_ENGINE like in the this patch? Does it work for your > case? The 2.4.x branch does not have MODSSL_HAVE_ENGINE_API at all, any hint on what branch to test that is similar to what I can expect to see as 2.4.59? I'm trying to create a patch for the FreeBSD port (I'm part of the apache team in FreeBSD ports). May well go with OpenBSD's solution: settubg ac_cv_func_ENGINE_init=no in configure's env. (https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/ports/www/apache-httpd/Makefile?rev=1.126.2.2&content-type=text/plain). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
