summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* configure --with-nss: remove unneeded libs from the fallbackMostyn Bramley-Moore2015-04-201-1/+1
|
* configure --with-nss: drop redundant if statementKamil Dudka2015-04-171-40/+36
|
* configure --with-nss=PATH: query pkg-config if availableKamil Dudka2015-04-171-5/+25
| | | | Bug: https://github.com/bagder/curl/pull/171
* cyassl: Include the CyaSSL build configJay Satiro2015-04-111-0/+3
| | | | | CyaSSL >= 2.6.0 may have an options.h that was generated during its build by configure.
* configure: Use KRB5CONFIG for krb5-configDagobert Michelsen2015-03-301-2/+6
| | | | | | Allows the user to easier override its path. Bug: http://curl.haxx.se/bug/view.cgi?id=1486
* build: link curl to openssl libraries when openssl support is enabledPaul Howarth2015-03-261-0/+1
| | | | | | | | | | 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.
* cyassl: detect the library as renamed wolfsslDan Fandrich2015-03-191-3/+57
| | | | This change was made in CyaSSL/WolfSSL ver. 3.4.0
* configure: follow-up fix from 709cf76f6Daniel Stenberg2015-03-051-3/+3
| | | | OpenSSL handling was a little broken.
* openssl: remove all uses of USE_SSLEAYDaniel Stenberg2015-03-051-13/+7
| | | | | | | 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.
* configure: remove detection of the old yassl emulation APIDaniel Stenberg2015-01-221-23/+0
| | | | ... as that is ancient history and not used.
* BoringSSL: fix build for non-configure buildsDaniel Stenberg2015-01-221-0/+2
| | | | | HAVE_BORINGSSL gets defined now by configure and should be defined by other build systems in case a BoringSSL build is desired.
* configure: fix BoringSSL detection and detect libressslDaniel Stenberg2015-01-221-1/+16
|
* BoringSSL: detected by configure, switches off NTLMDaniel Stenberg2015-01-221-2/+11
|
* ldap: Renamed the CURL_LDAP_WIN definition to USE_WIN32_LDAPSteve Holme2015-01-181-2/+2
| | | | | For consistency with other USE_WIN32_ defines as well as the USE_OPENLDAP define.
* code/docs: Use correct case for IPv4 and IPv6Steve Holme2014-12-271-4/+4
| | | | | | 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.
* code/docs: Use Unix rather than UNIX to avoid use of the trademarkSteve Holme2014-12-261-7/+7
| | | | | 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.
* configure: Use camel case for UNIX sockets feature outputSteve Holme2014-12-261-1/+1
| | | | To match the curl --version output.
* smb: Build with SSPI enabledBill Nagel2014-12-071-2/+3
| | | | Build SMB/CIFS protocol support when SSPI is enabled.
* libcurl: add UNIX domain sockets supportPeter Wu2014-12-041-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* configure: Fixed inclusion of SMB when no crypto engines availableSteve Holme2014-12-021-1/+4
|
* smb: Added configuration options for SMBBill Nagel2014-11-291-0/+22
| | | | | Added --enable-smb and --disable-smb configuration options for the upcoming SMB/CIFS protocol support.
* tool: Use Kerberos for supported featuresMichael Osipov2014-11-151-1/+1
|
* configure: Fixed inclusion of krb5 when CURL_DISABLE_CRYPTO_AUTH is definedSteve Holme2014-11-111-2/+2
| | | | | | | 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.
* configure: assume krb5 when gss-api worksDaniel Stenberg2014-11-101-1/+1
| | | | | To please test 1014 while we work out if this is truly the a correct assumption.
* libssh2: detect features based on version, not configure checksDaniel Stenberg2014-11-091-6/+0
| | | | | ... so that non-configure builds get the correct functions too based on the libssh2 version used.
* configure: Fixed NTLM missing from features when CURL_DISABLE_HTTP definedSteve Holme2014-11-091-3/+5
|
* configure: Added krb5 to the supported featuresSteve Holme2014-11-071-0/+5
|
* configure.ac: remove checks for OpenSSL NPN/ALPN funcs againDaniel Stenberg2014-10-291-4/+1
| | | | | ... since the conditional in the code are now based on OpenSSL versions instead to better support non-configure builds.
* Compile with latest nghttp2Tatsuhiro Tsujikawa2014-08-261-1/+1
|
* configure.ac: Add support for recent GSS-API implementations for HP-UXMichael Osipov2014-08-251-10/+15
| | | | | | | 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.
* configure/features: Add feature and version info for GSS-API and SPNEGOMichael Osipov2014-07-231-5/+12
|
* build: link curl to NSS libraries when NSS support is enabledAlessandro Ghedini2014-07-181-0/+4
| | | | | | | This fixes a build failure on Debian caused by commit 24c3cdce88f39731506c287cb276e8bf4a1ce393. Bug: http://curl.haxx.se/mail/lib-2014-07/0209.html
* Remove all traces of FBOpenSSL SPNEGO supportDavid Woodhouse2014-07-161-40/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* configure: respect host tool prefix for krb5-configMichał Górny2014-07-141-2/+9
| | | | | Use ${host_alias}-krb5-config if available. This improves cross- compilation support and fixes multilib on Gentoo (at least).
* netrc: fixed thread safety problem by using getpwuid_r if availableDan Fandrich2014-07-131-0/+1
| | | | | | | The old way using getpwuid could cause problems in programs that enable reading from netrc files simultaneously in multiple threads. Reported-by: David Woodhouse
* opts: initial makefileDaniel Stenberg2014-06-171-0/+1
| | | | | with a bonus first rough 'mancheck' target to see which man pages that are still missing
* url-parser: only use if_nametoindex if detected by configureDaniel Stenberg2014-05-261-0/+1
| | | | | | | The previous #ifdef detection wasn't good enough. Bug: http://curl.haxx.se/mail/lib-2014-05/0260.html Reported-by: Chris Young
* configure: fix the nghttp2 detection when not foundDaniel Stenberg2014-05-241-27/+26
|
* configure: detect nghttp2 by defaultDaniel Stenberg2014-05-231-6/+1
|
* configure: add GSS-API to supported featuresDaniel Stenberg2014-05-171-0/+3
| | | | | Bug: http://curl.haxx.se/bug/view.cgi?id=1344 Reported-by: Michael Osipov
* configure: add SPNEGO to supported featuresDaniel Stenberg2014-05-171-0/+3
| | | | | Bug: http://curl.haxx.se/bug/view.cgi?id=1343 Reported-by: Michael Osipov
* configure: Don't set LD_LIBRARY_PATH when cross-compilingAaro Koskinen2014-05-071-5/+6
| | | | | | Most of LD_LIBRARY_PATH adjustments are already guarded, but not all. The patch fixes cross-compilation failure when libidn is present.
* cyassl: Use error-ssl.h when availableDan Fandrich2014-04-231-0/+3
| | | | | Versions since at least 2.9.4 renamed error.h to error-ssl.h, so use whichever one is available.
* configure: use the nghttp2 path correctly with pkg-configDaniel Stenberg2014-04-221-9/+7
| | | | | | | | | When --with-nghttp2 was used (without a given path), the PKG_CONFIG_LIBDIR varialbe could get clobbered and ruin a proper detection of the library. Reported-by: Dilyan Palauzov Bug: http://curl.haxx.se/mail/lib-2014-04/0159.html
* configure: fix wrong commentDilyan Palauzov2014-04-211-1/+1
| | | | copy and paste error
* configure: call it GSS-APIMichael Osipov2014-03-031-15/+15
| | | | ... since that’s how the RFC calls it.
* configure: Tiny fix to honor POSIXnaota2014-02-251-7/+7
| | | | Change "==" to "=" to honor POSIX test construction.
* configure: Fix the --disable-crypto-auth optionDan Fandrich2014-02-171-1/+3
| | | | | It now disables NTLM and GSS authentication methods, and produces compilable code when SSL is enabled.
* openssl: add ALPN supportFabian Frank2014-02-031-1/+3
| | | | | | | | | | | Add ALPN support when using OpenSSL. This will offer ALPN and NPN to the server, who can respond with either one or none of the two. OpenSSL >= 1.0.2 is required, which means as of today obtaining a snapshot from ftp://ftp.openssl.org/snapshot/. See: http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-04 https://github.com/openssl/openssl/blob/ba168244a14bbd056e502d7daa04cae4aabe9d0d/ssl/ssl_lib.c#L1787
* http2-openssl: verify that NPN functionality is presentDaniel Stenberg2014-01-301-1/+2
|
View Lorry Controller Status