-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl 7.60.0 can list & work with openssl engines while curl 7.61.1 can't #3023
Comments
Well I tried with 7.61.1 too. No more success :
|
Then there's a different problem... |
No luck in bisecting the 158 commits between 7_60_0 and 7_61_0. Lot of unrelated errors at compile time. |
That sounds even weirder. Most commits we merge have been verified to build cleanly on numerous platforms and build combos. So even if there's an occasional build failure, they should be rare. |
You are right, sorry. Mistake was on my side because I did not run buildconf between each bisect. So, bisecting properly between 7_60_0 and 7_61_0 confirms that 38203f1 is the first bad commit. Unfortunately, d6417f6 does not solve the issue; SSL engine list is still empty after this commit. No more success after checking out 1599dfc. |
Is this the missing piece? diff --git a/lib/vtls/openssl.c b/lib/vtls/openssl.c
index 230eea2d0..551298926 100644
--- a/lib/vtls/openssl.c
+++ b/lib/vtls/openssl.c
@@ -976,11 +976,11 @@ static int Curl_ossl_init(void)
char *keylog_file_name;
#endif
OPENSSL_load_builtin_modules();
-#ifdef HAVE_ENGINE_LOAD_BUILTIN_ENGINES
+#ifdef USE_OPENSSL_ENGINE
ENGINE_load_builtin_engines();
#endif
/* OPENSSL_config(NULL); is "strongly recommended" to use but unfortunately
that function makes an exit() call on wrongly formatted config files |
That is the perfect missing piece, thank you! |
excellent! 👍 |
Obtained from: curl/curl#3023 (cherry picked from commit 3c0078e)
Obtained from: curl/curl#3023
In the following, openssl is openssl @1.0.2p_0. The same openssl.cnf is used for both test
I did this
I expected the following
operating system
Mac OS 10.13.6 & MacPorts 2.5.3
The text was updated successfully, but these errors were encountered: