aboutsummaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)Author
2015-11-24build: Install zsh completionDaniel Shahaf
Fixes #534 Closes #537
2015-10-23build: Fix mingw ssl gdi32 orderJay Satiro
- If mingw ssl make sure -lgdi32 comes after ssl libs - Allow PKG_CONFIG to set pkg-config location and options Bug: https://github.com/bagder/curl/pull/501 Reported-by: Kang Lin
2015-10-20vtls: added support for mbedTLSJonas Minnberg
closes #496
2015-10-18configure: add PSL to the list of featuresDaniel Stenberg
... to make test 1014 work again after e77b5b7453.
2015-10-17cookies: Add support for Mozilla's Publix Suffix ListTim Rühsen
Use libpsl to check the domain value of Set-Cookie headers (and cookie jar entries) for not being a Publix Suffix. The configure script checks for "libpsl" by default. Disable the check with --without-libpsl. Ref: https://publicsuffix.org/ Ref: https://github.com/publicsuffix/list Ref: https://github.com/rockdaboot/libpsl
2015-10-07configure: build silently by defaultDaniel Stenberg
'make V=1' will make the build verbose like before
2015-09-22gnutls: Support CURLOPT_KEYPASSWDMike Crowe
The gnutls vtls back-end was previously ignoring any password set via CURLOPT_KEYPASSWD. Presumably this was because gnutls_certificate_set_x509_key_file did not support encrypted keys. gnutls now has a gnutls_certificate_set_x509_key_file2 function that does support encrypted keys. Let's determine at compile time whether the available gnutls supports this new function. If it does then use it to pass the password. If it does not then emit a helpful diagnostic if a password is set. This is preferable to the previous behaviour of just failing to read the certificate without giving a reason in that case. Signed-off-by: Mike Crowe <mac@mcrowe.com>
2015-08-30configure: check for HMAC_Update in opensslDaniel Stenberg
Turns out HMAC_Init is now deprecated in openssl master (and I spelled HMAC_Init_ex wrong in previous commit)
2015-08-22configure: detect latest boringsslDaniel Stenberg
Since boringssl brought back DES_set_odd_parity again, it cannot be used to differentiate from boringssl. Using the OPENSSL_IS_BORINGSSL define seems better anyway. URL: https://android.googlesource.com/platform/external/curl/+/f551028d5caab29d4b4a4ae8c159c76c3cfd4887%5E!/ Original-patch-by: Bertrand Simonnet Closes #393
2015-08-22configure: change functions to detect openssl (clones)Daniel Stenberg
... since boringssl moved the former ones and the check started to fail. URL: https://android.googlesource.com/platform/external/curl/+/f551028d5caab29d4b4a4ae8c159c76c3cfd4887%5E!/ Original-patch-by: Bertrand Simonnet
2015-08-10Revert "configure: disable libidn by default"Daniel Stenberg
This reverts commit e6749055d65398315fd77f5b5b8234c5552ac2d3. ... since libidn has since been fixed.
2015-07-25configure: check if OpenSSL linking wants -ldlDaniel Stenberg
To make it easier to link with static versions of OpenSSL, the configure script now checks if -ldl is needed for linking. Help-by: TJ Saunders
2015-07-24configure: add --disable-rt optionMichał Fita
This option disables any attempts in configure to create dependency on stuff requiring linking to librt.so and libpthread.so, in this case this means clock_gettime(CLOCK_MONOTONIC, &mt). We were in need to build curl which doesn't link libpthread.so to avoid the following bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16628.
2015-06-29configure: disable libidn by defaultDaniel Stenberg
For security reasons, until there is a fix. Bug: http://curl.haxx.se/mail/lib-2015-06/0143.html Reported-by: Gustavo Grieco, Feist Josselin
2015-05-18Require nghttp2 v1.0.0Tatsuhiro Tsujikawa
This commit requires nghttp2 v1.0.0 to compile, and migrate to v1.0.0, and utilize recent version of nghttp2 to simplify the code, First we use nghttp2_option_set_no_recv_client_magic function to detect nghttp2 v1.0.0. That function only exists since v1.0.0. Since nghttp2 v0.7.5, nghttp2 ensures header field ordering, and validates received header field. If it found error, RST_STREAM with PROTOCOL_ERROR is issued. Since we require v1.0.0, we can utilize this feature to simplify libcurl code. This commit does this. Migration from 0.7 series are done based on nghttp2 migration document. For libcurl, we removed the code sending first 24 bytes client magic. It is now done by nghttp2 library. on_invalid_frame_recv callback signature changed, and is updated accordingly.
2015-04-26configure: follow-up fix for krb5-configDaniel Stenberg
commit 5b66860652 was incomplete so here's a follow-up fix Reported-by: Dagobert Michelsen Bug: https://github.com/bagder/curl/commit/5b668606527613179d0349f21b4ab0df2971e3d2#commitcomment-10473445
2015-04-20configure --with-nss: remove unneeded libs from the fallbackMostyn Bramley-Moore
2015-04-17configure --with-nss: drop redundant if statementKamil Dudka
2015-04-17configure --with-nss=PATH: query pkg-config if availableKamil Dudka
Bug: https://github.com/bagder/curl/pull/171
2015-04-11cyassl: Include the CyaSSL build configJay Satiro
CyaSSL >= 2.6.0 may have an options.h that was generated during its build by configure.
2015-03-30configure: Use KRB5CONFIG for krb5-configDagobert Michelsen
Allows the user to easier override its path. Bug: http://curl.haxx.se/bug/view.cgi?id=1486
2015-03-26build: link curl to openssl libraries when openssl support is enabledPaul Howarth
This fixes a build failure where openssl and libmetalink are used together and the system linker does not do implicit linking (e.g. Fedora 13 and later releases). The MD5 functions required for metalink support must be pulled in from the openssl crypto library. This is similar to commit c6e7cbb94e669b85d3eb8e015ec51d0072112133, which fixes the same sort of problem for NSS builds.
2015-03-19cyassl: detect the library as renamed wolfsslDan Fandrich
This change was made in CyaSSL/WolfSSL ver. 3.4.0
2015-03-05configure: follow-up fix from 709cf76f6Daniel Stenberg
OpenSSL handling was a little broken.
2015-03-05openssl: remove all uses of USE_SSLEAYDaniel Stenberg
SSLeay was the name of the library that was subsequently turned into OpenSSL many moons ago (1999). curl does not work with the old SSLeay library since years. This is now reflected by only using USE_OPENSSL in code that depends on OpenSSL.
2015-01-22configure: remove detection of the old yassl emulation APIDaniel Stenberg
... as that is ancient history and not used.
2015-01-22BoringSSL: fix build for non-configure buildsDaniel Stenberg
HAVE_BORINGSSL gets defined now by configure and should be defined by other build systems in case a BoringSSL build is desired.
2015-01-22configure: fix BoringSSL detection and detect libressslDaniel Stenberg
2015-01-22BoringSSL: detected by configure, switches off NTLMDaniel Stenberg
2015-01-18ldap: Renamed the CURL_LDAP_WIN definition to USE_WIN32_LDAPSteve Holme
For consistency with other USE_WIN32_ defines as well as the USE_OPENLDAP define.
2014-12-27code/docs: Use correct case for IPv4 and IPv6Steve Holme
For consistency, as we seem to have a bit of a mixed bag, changed all instances of ipv4 and ipv6 in comments and documentations to use the correct case.
2014-12-26code/docs: Use Unix rather than UNIX to avoid use of the trademarkSteve Holme
Use Unix when generically writing about Unix based systems as UNIX is the trademark and should only be used in a particular product's name.
2014-12-26configure: Use camel case for UNIX sockets feature outputSteve Holme
To match the curl --version output.
2014-12-07smb: Build with SSPI enabledBill Nagel
Build SMB/CIFS protocol support when SSPI is enabled.
2014-12-04libcurl: add UNIX domain sockets supportPeter Wu
The ability to do HTTP requests over a UNIX domain socket has been requested before, in Apr 2008 [0][1] and Sep 2010 [2]. While a discussion happened, no patch seems to get through. I decided to give it a go since I need to test a nginx HTTP server which listens on a UNIX domain socket. One patch [3] seems to make it possible to use the CURLOPT_OPENSOCKETFUNCTION function to gain a UNIX domain socket. Another person wrote a Go program which can do HTTP over a UNIX socket for Docker[4] which uses a special URL scheme (though the name contains cURL, it has no relation to the cURL library). This patch considers support for UNIX domain sockets at the same level as HTTP proxies / IPv6, it acts as an intermediate socket provider and not as a separate protocol. Since this feature affects network operations, a new feature flag was added ("unix-sockets") with a corresponding CURL_VERSION_UNIX_SOCKETS macro. A new CURLOPT_UNIX_SOCKET_PATH option is added and documented. This option enables UNIX domain sockets support for all requests on the handle (replacing IP sockets and skipping proxies). A new configure option (--enable-unix-sockets) and CMake option (ENABLE_UNIX_SOCKETS) can disable this optional feature. Note that I deliberately did not mark this feature as advanced, this is a feature/component that should easily be available. [0]: http://curl.haxx.se/mail/lib-2008-04/0279.html [1]: http://daniel.haxx.se/blog/2008/04/14/http-over-unix-domain-sockets/ [2]: http://sourceforge.net/p/curl/feature-requests/53/ [3]: http://curl.haxx.se/mail/lib-2008-04/0361.html [4]: https://github.com/Soulou/curl-unix-socket Signed-off-by: Peter Wu <peter@lekensteyn.nl>
2014-12-02configure: Fixed inclusion of SMB when no crypto engines availableSteve Holme
2014-11-29smb: Added configuration options for SMBBill Nagel
Added --enable-smb and --disable-smb configuration options for the upcoming SMB/CIFS protocol support.
2014-11-15tool: Use Kerberos for supported featuresMichael Osipov
2014-11-11configure: Fixed inclusion of krb5 when CURL_DISABLE_CRYPTO_AUTH is definedSteve Holme
Commit fe0f8967bf fixed a problem with krb5 not being defined as a supported feature when HAVE_GSSAPI is defined, however, it should only be included if CURL_DISABLE_CRYPTO_AUTH is not set, like when SPNEGO is listed as a feature.
2014-11-10configure: assume krb5 when gss-api worksDaniel Stenberg
To please test 1014 while we work out if this is truly the a correct assumption.
2014-11-09libssh2: detect features based on version, not configure checksDaniel Stenberg
... so that non-configure builds get the correct functions too based on the libssh2 version used.
2014-11-09configure: Fixed NTLM missing from features when CURL_DISABLE_HTTP definedSteve Holme
2014-11-07configure: Added krb5 to the supported featuresSteve Holme
2014-10-29configure.ac: remove checks for OpenSSL NPN/ALPN funcs againDaniel Stenberg
... since the conditional in the code are now based on OpenSSL versions instead to better support non-configure builds.
2014-08-26Compile with latest nghttp2Tatsuhiro Tsujikawa
2014-08-25configure.ac: Add support for recent GSS-API implementations for HP-UXMichael Osipov
By default, configure script assumes that libcurl will use the HP-supplied GSS-API implementation which does not have krb5-config. If a dev needs a more recent version which has that config script, the change will allow to pass an appropriate GSSAPI_ROOT.
2014-07-23configure/features: Add feature and version info for GSS-API and SPNEGOMichael Osipov
2014-07-18build: link curl to NSS libraries when NSS support is enabledAlessandro Ghedini
This fixes a build failure on Debian caused by commit 24c3cdce88f39731506c287cb276e8bf4a1ce393. Bug: http://curl.haxx.se/mail/lib-2014-07/0209.html
2014-07-16Remove all traces of FBOpenSSL SPNEGO supportDavid Woodhouse
This is just fundamentally broken. SPNEGO (RFC4178) is a protocol which allows client and server to negotiate the underlying mechanism which will actually be used to authenticate. This is *often* Kerberos, and can also be NTLM and other things. And to complicate matters, there are various different OIDs which can be used to specify the Kerberos mechanism too. A SPNEGO exchange will identify *which* GSSAPI mechanism is being used, and will exchange GSSAPI tokens which are appropriate for that mechanism. But this SPNEGO implementation just strips the incoming SPNEGO packet and extracts the token, if any. And completely discards the information about *which* mechanism is being used. Then we *assume* it was Kerberos, and feed the token into gss_init_sec_context() with the default mechanism (GSS_S_NO_OID for the mech_type argument). Furthermore... broken as this code is, it was never even *used* for input tokens anyway, because higher layers of curl would just bail out if the server actually said anything *back* to us in the negotiation. We assume that we send a single token to the server, and it accepts it. If the server wants to continue the exchange (as is required for NTLM and for SPNEGO to do anything useful), then curl was broken anyway. So the only bit which actually did anything was the bit in Curl_output_negotiate(), which always generates an *initial* SPNEGO token saying "Hey, I support only the Kerberos mechanism and this is its token". You could have done that by manually just prefixing the Kerberos token with the appropriate bytes, if you weren't going to do any proper SPNEGO handling. There's no need for the FBOpenSSL library at all. The sane way to do SPNEGO is just to *ask* the GSSAPI library to do SPNEGO. That's what the 'mech_type' argument to gss_init_sec_context() is for. And then it should all Just Work™. That 'sane way' will be added in a subsequent patch, as will bug fixes for our failure to handle any exchange other than a single outbound token to the server which results in immediate success.
2014-07-14configure: respect host tool prefix for krb5-configMichał Górny
Use ${host_alias}-krb5-config if available. This improves cross- compilation support and fixes multilib on Gentoo (at least).