Am 05.06.26 um 20:43 schrieb Steffen:
OpenSSL 4 issue is best you report it at the list [email protected]
.apache.
https://httpd.apache.org/lists.html#http-dev
Op 5 jun 2026 om 19:16 heeft Steffen <[email protected]> het
volgende geschreven:
Maybe some clues :
https://openssl-library.org/post/2025-12-18-remove-engines/?shem=rimspwouoe,
Op 5 jun 2026 om 16:57 heeft Peter Kitson <[email protected]> het
volgende geschreven:
Hello Steffen,
Ok, so my build with OpenSSL 4.0 fails. It's apr-util (1.6.3) that's
complaining since the ENGINE API has been removed from the OpenSSL
4.0.0 libraries.
/[ 90%] Built target aprutil-1
[ 90%] Building C object
CMakeFiles/apr_crypto_openssl-1.dir/crypto/apr_crypto_openssl.c.obj
apr_crypto_openssl.c
[ 91%] Building RC object
CMakeFiles/apr_crypto_openssl-1.dir/libaprutil.rc.res
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384
Copyright (C) Microsoft Corporation. All rights reserved.
[ 92%] Linking C shared library apr_crypto_openssl-1.dll
LINK: command
"C:\PROGRA~1\MICROS~1\18\COMMUN~1\VC\Tools\MSVC\1451~1.362\bin\Hostx64\x64\link.exe
/nologo @CMakeFiles\apr_crypto_openssl-1.dir\objects1.rsp
/out:apr_crypto_openssl-1.dll /implib:apr_crypto_openssl-1.lib
/pdb:C:\Development\apache24\build\apr-util\apr_crypto_openssl-1.pdb
/dll /version:0.0 /machine:x64 /INCREMENTAL:NO libaprutil-1.lib
C:\Apache24\lib\libapr-1.lib C:\Apache24\lib\libapriconv-1.lib
C:\Apache24\lib\libssl.lib C:\Apache24\lib\libcrypto.lib
C:\Apache24\lib\libexpat.lib kernel32.lib user32.lib gdi32.lib
winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
comdlg32.lib advapi32.lib /MANIFEST:EMBED,ID=2" failed (exit code
1120) with the following output:
Creating library apr_crypto_openssl-1.lib and object
apr_crypto_openssl-1.exp
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_by_id referenced in function crypto_make
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_load_builtin_engines referenced in function crypto_init
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_register_all_complete referenced in function crypto_init
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_free referenced in function crypto_cleanup
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_init referenced in function crypto_make
apr_crypto_openssl.c.obj : error LNK2019: unresolved external symbol
ENGINE_finish referenced in function crypto_cleanup
apr_crypto_openssl-1.dll : fatal error LNK1120: 6 unresolved externals/
/etc/
Since there no update to APR yet (or is there?), do you know of any
configure option for OpenSSL 4.0, to retain ENGINE API functionality
for now?
Regards
Pete
---------- Forwarded message ---------
From: *Peter Kitson* <[email protected]>
Date: Fri, 5 Jun 2026 at 14:57
Subject: Re: [VOTE] Release httpd-2.4.68-rc1 as httpd-2.4.68-Apache
Mail Archives
To: Steffen <[email protected]>
Hmm, I'm not sure.
Last time I tried the OpenSSL 4 series, it wouldn't link with the
APR libraries, due to changes to remove the ENGINE API.
I presume that's what @nono303 refers to when his recent post
mentions "Fix OpenSSL 4.0 Compat" -
https://www.apachelounge.com/viewtopic.php?p=44373#44373 and whether
fix https://github.com/apache/httpd/pull/642 has found it's way into
the new release candidate.
So downloading the 2.4.68-rc1, I can see this at the top of the changes:
Changes with Apache 2.4.68
*) mod_ssl, ab: Add support for OpenSSL 4.0. [Joe Orton]
So having built the new release candidate with our current OpenSSL
3.6.2, I'll repeat the build with OpenSSL 4.0.0 and see what happens.
Regards
Pete
On Fri, 5 Jun 2026 at 14:05, Steffen <[email protected]> wrote:
Shall we try OpenSSL 4 , give it a try.
Begin doorgestuurd bericht:
*Van:* Steffen <[email protected]>
*Datum:* 5 juni 2026 om 15:01:47 CEST
*Aan:* Peter Kitson <[email protected]>
*Onderwerp:* *[VOTE] Release httpd-2.4.68-rc1 as
httpd-2.4.68-Apache Mail Archives*
https://lists.apache.org/thread/2knoyt1b68wpddyvc06ktqm55p3ryhd2
The crypto code in apr-util is not yet compatible with OpenSSL 4. The
same holds true for mod_md as bundled with httpd 2.4.68-
If you want to build using OpenSSL 4, you would need to disable mod_md
and to not enable crypto support in apr-util. As a consequence, only
mod_session_crypto would not get build.
I expect we will handle OpenSSL 4 support in apr-util once there will be
a new release of it. The small incompatibility in mod_md will hopefully
get fixed in the next httpd release.
Best regards,
Rainer
