The decision to switch the default to wolfSSL was taken because of
hostapd back from when curl was in base. Unfortunately, not only is
wolfSSL bigger but it has also been causing issues recently. There's
also no relation between hostapd and curl.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
(cherry picked from commit 0a65e4c6fa
)
164 lines
3.1 KiB
Text
164 lines
3.1 KiB
Text
if PACKAGE_libcurl
|
|
|
|
comment "SSL support"
|
|
|
|
choice
|
|
prompt "Selected SSL library"
|
|
default LIBCURL_MBEDTLS
|
|
|
|
config LIBCURL_MBEDTLS
|
|
bool "mbed TLS"
|
|
|
|
config LIBCURL_WOLFSSL
|
|
bool "wolfSSL"
|
|
|
|
config LIBCURL_OPENSSL
|
|
bool "OpenSSL"
|
|
|
|
config LIBCURL_GNUTLS
|
|
bool "GNUTLS"
|
|
|
|
config LIBCURL_NOSSL
|
|
bool "No SSL support"
|
|
|
|
endchoice
|
|
|
|
comment "Supported protocols"
|
|
|
|
config LIBCURL_DICT
|
|
bool "DICT protocol"
|
|
default n
|
|
|
|
config LIBCURL_FILE
|
|
bool "FILE protocol"
|
|
default y
|
|
|
|
config LIBCURL_FTP
|
|
bool "FTP / FTPS protocol"
|
|
default y
|
|
|
|
config LIBCURL_GOPHER
|
|
bool "Gopher protocol"
|
|
default n
|
|
|
|
config LIBCURL_HTTP
|
|
bool "HTTP / HTTPS protocol"
|
|
default y
|
|
|
|
config LIBCURL_COOKIES
|
|
bool "Enable Cookies support"
|
|
depends on LIBCURL_HTTP
|
|
default y
|
|
|
|
config LIBCURL_IMAP
|
|
bool "IMAP / IMAPS protocol"
|
|
default n
|
|
|
|
config LIBCURL_LDAP
|
|
bool "LDAP protocol"
|
|
default n
|
|
|
|
config LIBCURL_LDAPS
|
|
bool "Enable LDAPS support"
|
|
depends on LIBCURL_LDAP && !LIBCURL_NOSSL
|
|
default y
|
|
|
|
config LIBCURL_POP3
|
|
bool "POP3 / POP3S protocol"
|
|
default n
|
|
|
|
config LIBCURL_RTSP
|
|
bool "RTSP protocol"
|
|
depends on LIBCURL_HTTP
|
|
default n
|
|
config LIBCURL_NO_RTSP
|
|
string "RTSP require HTTP protocol"
|
|
depends on !LIBCURL_HTTP
|
|
default "!"
|
|
|
|
config LIBCURL_SSH2
|
|
bool "SCP / SFTP protocol"
|
|
default n
|
|
|
|
config LIBCURL_SMB
|
|
bool "SMB protocol (CIFS)"
|
|
depends on LIBCURL_CRYPTO_AUTH && (LIBCURL_GNUTLS || LIBCURL_OPENSSL)
|
|
default n
|
|
config LIBCURL_NO_SMB
|
|
string "SMB require 'cryptographic authentication' and either 'GnuTLS' or 'OpenSSL'"
|
|
depends on !LIBCURL_CRYPTO_AUTH || (!LIBCURL_GNUTLS && !LIBCURL_OPENSSL)
|
|
default "!"
|
|
|
|
config LIBCURL_SMTP
|
|
bool "SMTP / SMTPS protocol"
|
|
default n
|
|
|
|
config LIBCURL_TELNET
|
|
bool "TELNET protocol"
|
|
default n
|
|
|
|
config LIBCURL_TFTP
|
|
bool "TFTP protocol"
|
|
default n
|
|
|
|
config LIBCURL_NGHTTP2
|
|
bool "HTTP2 protocol"
|
|
default y
|
|
|
|
comment "Miscellaneous"
|
|
|
|
config LIBCURL_PROXY
|
|
bool "Enable proxy support"
|
|
default y
|
|
|
|
config LIBCURL_CRYPTO_AUTH
|
|
bool "Enable cryptographic authentication"
|
|
default n
|
|
|
|
config LIBCURL_TLS_SRP
|
|
bool "Enable TLS-SRP authentication"
|
|
default n
|
|
|
|
config LIBCURL_LIBIDN2
|
|
bool "Enable IDN2 support"
|
|
default n
|
|
|
|
config LIBCURL_THREADED_RESOLVER
|
|
bool "Enable threaded DNS resolver"
|
|
default n
|
|
help
|
|
Enable POSIX threaded asynchronous DNS resolution
|
|
|
|
config LIBCURL_ZLIB
|
|
bool "Enable zlib support"
|
|
default n
|
|
|
|
config LIBCURL_ZSTD
|
|
bool "Enable zstd support"
|
|
default n
|
|
|
|
config LIBCURL_UNIX_SOCKETS
|
|
bool "Enable unix domain socket support"
|
|
default n
|
|
help
|
|
Enable HTTP over unix domain sockets.
|
|
To use this with the curl command line, you specify the socket path to the new --unix-domain option.
|
|
This feature is actually not limited to HTTP, you can do all the TCP-based protocols
|
|
except FTP over the unix domain socket, but it is only HTTP that is regularly used this way.
|
|
The reason FTP isn't supported is of course its use of two connections
|
|
which would be even weirder to do like this.
|
|
|
|
config LIBCURL_LIBCURL_OPTION
|
|
bool "Enable generation of C code"
|
|
default n
|
|
|
|
config LIBCURL_VERBOSE
|
|
bool "Enable verbose error strings"
|
|
default n
|
|
|
|
config LIBCURL_NTLM
|
|
bool "Enable NTLM support"
|
|
depends on LIBCURL_CRYPTO_AUTH && !LIBCURL_NOSSL
|
|
default n
|
|
|
|
endif
|