mirror of
https://github.com/curl/curl.git
synced 2026-07-24 15:07:21 +03:00
gskit: remove
We remove support for building curl with gskit. - This is a niche TLS library, only running on some IBM systems - no regular curl contributors use this backend - no CI builds use or verify this backend - gskit, or the curl adaption for it, lacks many modern TLS features making it an inferior solution - build breakages in this code take weeks or more to get detected - fixing gskit code is mostly done "flying blind" This removal has been advertized in DEPRECATED in Jan 2, 2023 and it has been mentioned on the curl-library mailing list. It could be brought back, this is not a ban. Given proper effort and will, gskit support is welcome back into the curl TLS backend family. Closes #11460
This commit is contained in:
parent
08b9f246f4
commit
78d6232f1f
33 changed files with 35 additions and 1995 deletions
|
|
@ -165,71 +165,6 @@ When specifying multiple cipher names, separate them with colon (`:`).
|
|||
`TLS_AES_128_CCM_8_SHA256`
|
||||
`TLS_AES_128_CCM_SHA256`
|
||||
|
||||
## GSKit
|
||||
|
||||
Ciphers are internally defined as [numeric
|
||||
codes](https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/gsk_attribute_set_buffer.htm). libcurl
|
||||
maps them to the following case-insensitive names.
|
||||
|
||||
### SSL2 cipher suites (insecure: disabled by default)
|
||||
|
||||
`rc2-md5`
|
||||
`rc4-md5`
|
||||
`exp-rc2-md5`
|
||||
`exp-rc4-md5`
|
||||
`des-cbc-md5`
|
||||
`des-cbc3-md5`
|
||||
|
||||
### SSL3 cipher suites
|
||||
|
||||
`null-md5`
|
||||
`null-sha`
|
||||
`rc4-md5`
|
||||
`rc4-sha`
|
||||
`exp-rc2-cbc-md5`
|
||||
`exp-rc4-md5`
|
||||
`exp-des-cbc-sha`
|
||||
`des-cbc3-sha`
|
||||
|
||||
### TLS v1.0 cipher suites
|
||||
|
||||
`null-md5`
|
||||
`null-sha`
|
||||
`rc4-md5`
|
||||
`rc4-sha`
|
||||
`exp-rc2-cbc-md5`
|
||||
`exp-rc4-md5`
|
||||
`exp-des-cbc-sha`
|
||||
`des-cbc3-sha`
|
||||
`aes128-sha`
|
||||
`aes256-sha`
|
||||
|
||||
### TLS v1.1 cipher suites
|
||||
|
||||
`null-md5`
|
||||
`null-sha`
|
||||
`rc4-md5`
|
||||
`rc4-sha`
|
||||
`exp-des-cbc-sha`
|
||||
`des-cbc3-sha`
|
||||
`aes128-sha`
|
||||
`aes256-sha`
|
||||
|
||||
### TLS v1.2 cipher suites
|
||||
|
||||
`null-md5`
|
||||
`null-sha`
|
||||
`null-sha256`
|
||||
`rc4-md5`
|
||||
`rc4-sha`
|
||||
`des-cbc3-sha`
|
||||
`aes128-sha`
|
||||
`aes256-sha`
|
||||
`aes128-sha256`
|
||||
`aes256-sha256`
|
||||
`aes128-gcm-sha256`
|
||||
`aes256-gcm-sha384`
|
||||
|
||||
## WolfSSL
|
||||
|
||||
`RC4-SHA`,
|
||||
|
|
|
|||
|
|
@ -6,18 +6,6 @@ email the
|
|||
as soon as possible and explain to us why this is a problem for you and
|
||||
how your use case cannot be satisfied properly using a workaround.
|
||||
|
||||
## gskit
|
||||
|
||||
We remove support for building curl with the gskit TLS library in August 2023.
|
||||
|
||||
- This is a niche TLS library, only running on some IBM systems
|
||||
- no regular curl contributors use this backend
|
||||
- no CI builds use or verify this backend
|
||||
- gskit, or the curl adaption for it, lacks many modern TLS features making it
|
||||
an inferior solution
|
||||
- build breakages in this code take weeks or more to get detected
|
||||
- fixing gskit code is mostly done "flying blind"
|
||||
|
||||
## mingw v1
|
||||
|
||||
We remove support for building curl with the original legacy mingw version 1
|
||||
|
|
@ -57,3 +45,5 @@ curl will remove the support for space-separated names in July 2024.
|
|||
- NPN
|
||||
- Support for systems without 64 bit data types
|
||||
- NSS
|
||||
- gskit
|
||||
|
||||
|
|
|
|||
6
docs/FAQ
6
docs/FAQ
|
|
@ -423,9 +423,9 @@ FAQ
|
|||
|
||||
curl can be built to use one of the following SSL alternatives: OpenSSL,
|
||||
libressl, BoringSSL, AWS-LC, GnuTLS, wolfSSL, mbedTLS, Secure Transport
|
||||
(native iOS/OS X), Schannel (native Windows), GSKit (native IBM i), BearSSL,
|
||||
or Rustls. They all have their pros and cons, and we try to maintain a
|
||||
comparison of them here: https://curl.se/docs/ssl-compared.html
|
||||
(native iOS/OS X), Schannel (native Windows), BearSSL or Rustls. They all
|
||||
have their pros and cons, and we try to maintain a comparison of them here:
|
||||
https://curl.se/docs/ssl-compared.html
|
||||
|
||||
2.4 Does curl support SOCKS (RFC 1928) ?
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,6 @@ versions of libs and build tools.
|
|||
- wolfSSL 2.0.0
|
||||
- OpenLDAP 2.0
|
||||
- MIT Kerberos 1.2.4
|
||||
- GSKit V5R3M0
|
||||
- Heimdal ?
|
||||
- nghttp2 1.15.0
|
||||
- WinSock 2.2 (on Windows 95+ and Windows CE .NET 4.1+)
|
||||
|
|
|
|||
|
|
@ -60,9 +60,8 @@ the case insensitive name of the particular backend to use when curl is
|
|||
invoked. Setting a name that is not a built-in alternative will make curl
|
||||
stay with the default.
|
||||
|
||||
SSL backend names (case-insensitive): **bearssl**, **gnutls**, **gskit**,
|
||||
**mbedtls**, **openssl**, **rustls**, **schannel**, **secure-transport**,
|
||||
**wolfssl**
|
||||
SSL backend names (case-insensitive): **bearssl**, **gnutls**, **mbedtls**,
|
||||
**openssl**, **rustls**, **schannel**, **secure-transport**, **wolfssl**
|
||||
.IP "HOME <dir>"
|
||||
If set, this is used to find the home directory when that is needed. Like when
|
||||
looking for the default .curlrc. *CURL_HOME* and *XDG_CONFIG_HOME*
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ abort the connection before sending or receiving any data.
|
|||
|
||||
PEM/DER support:
|
||||
|
||||
7.39.0: OpenSSL, GnuTLS and GSKit
|
||||
7.39.0: OpenSSL and GnuTLS
|
||||
|
||||
7.43.0: wolfSSL
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ The variables available are:
|
|||
.TP 15
|
||||
**certs**
|
||||
Output the certificate chain with details. Supported only by the OpenSSL,
|
||||
GnuTLS, Schannel, GSKit and Secure Transport backends. (Added in 7.88.0)
|
||||
GnuTLS, Schannel and Secure Transport backends. (Added in 7.88.0)
|
||||
.TP
|
||||
**content_type**
|
||||
The Content-Type of the requested document, if there was any.
|
||||
|
|
@ -105,7 +105,7 @@ The http method used in the most recent HTTP request. (Added in 7.72.0)
|
|||
.TP
|
||||
**num_certs**
|
||||
Number of server certificates received in the TLS handshake. Supported only by
|
||||
the OpenSSL, GnuTLS, Schannel, GSKit and Secure Transport backends. (Added
|
||||
the OpenSSL, GnuTLS, Schannel and Secure Transport backends. (Added
|
||||
in 7.88.0)
|
||||
.TP
|
||||
**num_connects**
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ typedef enum {
|
|||
CURLSSLBACKEND_OPENSSL = 1, /* or one of its forks */
|
||||
CURLSSLBACKEND_GNUTLS = 2,
|
||||
CURLSSLBACKEND_NSS = 3,
|
||||
CURLSSLBACKEND_GSKIT = 5,
|
||||
CURLSSLBACKEND_GSKIT = 5, /* deprecated */
|
||||
CURLSSLBACKEND_POLARSSL = 6, /* deprecated */
|
||||
CURLSSLBACKEND_WOLFSSL = 7,
|
||||
CURLSSLBACKEND_SCHANNEL = 8,
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ specific backend at first use. If no selection is done by the program using
|
|||
libcurl, this variable's selection will be used. Setting a name that is not a
|
||||
built-in alternative will make libcurl stay with the default.
|
||||
|
||||
SSL backend names (case-insensitive): BearSSL, GnuTLS, gskit, mbedTLS,
|
||||
SSL backend names (case-insensitive): BearSSL, GnuTLS, mbedTLS,
|
||||
nss, OpenSSL, rustls, Schannel, Secure-Transport, wolfSSL
|
||||
.IP HOME
|
||||
When the netrc feature is used (\fICURLOPT_NETRC(3)\fP), this variable is
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ if(curl) {
|
|||
}
|
||||
.fi
|
||||
.SH AVAILABILITY
|
||||
This option is only working in libcurl built with OpenSSL, Schannel, GSKit or
|
||||
This option is only working in libcurl built with OpenSSL, Schannel or
|
||||
Secure Transport support. Schannel support added in 7.50.0. Secure Transport
|
||||
support added in 7.79.0.
|
||||
|
||||
|
|
|
|||
|
|
@ -63,8 +63,8 @@ if(curl) {
|
|||
}
|
||||
.fi
|
||||
.SH AVAILABILITY
|
||||
Added in 7.34.0. Deprecated since 7.48.0 and supported OpenSSL, GnuTLS,
|
||||
NSS and gskit only up until this version was released.
|
||||
Added in 7.34.0. Deprecated since 7.48.0 and supported OpenSSL, GnuTLS, and
|
||||
NSS only up until this version was released.
|
||||
.SH RETURN VALUE
|
||||
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
|
||||
.SH "SEE ALSO"
|
||||
|
|
|
|||
|
|
@ -57,18 +57,15 @@ struct curl_tlssessioninfo {
|
|||
The \fIbackend\fP struct member is one of the defines in the CURLSSLBACKEND_*
|
||||
series: CURLSSLBACKEND_NONE (when built without TLS support),
|
||||
CURLSSLBACKEND_WOLFSSL, CURLSSLBACKEND_SECURETRANSPORT, CURLSSLBACKEND_GNUTLS,
|
||||
CURLSSLBACKEND_GSKIT, CURLSSLBACKEND_MBEDTLS, CURLSSLBACKEND_NSS,
|
||||
CURLSSLBACKEND_OPENSSL, CURLSSLBACKEND_SCHANNEL or
|
||||
CURLSSLBACKEND_MESALINK. (Note that the OpenSSL forks are all reported as just
|
||||
OpenSSL here.)
|
||||
CURLSSLBACKEND_MBEDTLS, CURLSSLBACKEND_NSS, CURLSSLBACKEND_OPENSSL,
|
||||
CURLSSLBACKEND_SCHANNEL or CURLSSLBACKEND_MESALINK. (Note that the OpenSSL
|
||||
forks are all reported as just OpenSSL here.)
|
||||
|
||||
The \fIinternals\fP struct member will point to a TLS library specific pointer
|
||||
for the active ("in use") SSL connection, with the following underlying types:
|
||||
.RS
|
||||
.IP GnuTLS
|
||||
\fBgnutls_session_t\fP
|
||||
.IP gskit
|
||||
\fBgsk_handle\fP
|
||||
.IP NSS
|
||||
\fBPRFileDesc *\fP
|
||||
.IP OpenSSL
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ if(curl) {
|
|||
}
|
||||
.fi
|
||||
.SH AVAILABILITY
|
||||
This option is supported by the OpenSSL, GnuTLS, Schannel, GSKit and Secure
|
||||
This option is supported by the OpenSSL, GnuTLS, Schannel and Secure
|
||||
Transport backends. Schannel support added in 7.50.0. Secure Transport support
|
||||
added in 7.79.0.
|
||||
.SH RETURN VALUE
|
||||
|
|
|
|||
|
|
@ -102,8 +102,6 @@ PEM/DER support:
|
|||
|
||||
7.39.0: OpenSSL, GnuTLS
|
||||
|
||||
7.39.0-7.48.0,7.58.1+: GSKit
|
||||
|
||||
7.43.0: wolfSSL
|
||||
|
||||
7.47.0: mbedTLS
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ footer:
|
|||
.SH AVAILABILITY
|
||||
PEM/DER support:
|
||||
|
||||
7.52.0: GSKit, GnuTLS, OpenSSL, mbedTLS, wolfSSL
|
||||
7.52.0: GnuTLS, OpenSSL, mbedTLS, wolfSSL
|
||||
|
||||
sha256 support:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue