-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
--with-gnutls --with-openssl enables USE_TLS_SRP, even when OpenSSL/LibreSSL doesn't support it; build fails #5865
Comments
I'm curious why two TLS back ends are even allowed, it would make no sense |
@emilengler it should make sense, see #2665 |
@emilengler to allow the application to select the specific TLS backend in run-time rather than just one at build time. Supported since libcurl 7.56.0. See |
USE_TLS_SRP will be true if any TLS backend can use SRP, HAVE_OPENSSL_SRP is defined when OpenSSL can use it. Clarify in the curl_verison_info docs that CURL_VERSION_TLSAUTH_SRP is set if at least one of the supported backends offers SRP. Reported-by: Stefan Strogin Fixes #5865
Hello @bagder, I really appreciate you taking your time to fix this, but I'm trying to compile curl on Gentoo (from the official repository) with libressl as the ssl provider and I'm experiencing the same issue (extract from the build log after compilation failed):
I saw that the PR you opened hasn't been merged. Was this intentional? Are these changes going to make it into production anytime? |
See above. This was fixed in commit 68a5132 which is not part of 7.72.0 but is part of 7.73.0... |
You saw wrong.
|
./configure --with-ssl --with-nettle --with-gnutls --with-openssl
configure.log
checking for SRP_Calc_client_key in -lcrypto... no
checking for gnutls_srp_verifier in -lgnutls... yes
checking whether to enable TLS-SRP authentication... yes
Then
make
...It's LibreSSL 3.2.1, but the version is irrelevant, because SRP was removed from LibreSSL in 2014.
The text was updated successfully, but these errors were encountered: