Loading docs/FAQ +1 −1 Original line number Diff line number Diff line Loading @@ -427,7 +427,7 @@ FAQ curl can be built to use one of the following SSL alternatives: OpenSSL, GnuTLS, yassl, NSS, PolarSSL, axTLS, Secure Transport (native iOS/OS X), WinSSL (native Windows) or qssl (native IBM i). They all have their pros WinSSL (native Windows) or GSKit (native IBM i). They all have their pros and cons, and we try to maintain a comparison of them here: http://curl.haxx.se/docs/ssl-compared.html Loading docs/FEATURES +2 −2 Original line number Diff line number Diff line Loading @@ -178,7 +178,7 @@ FOOTNOTES ========= *1 = requires OpenSSL, GnuTLS, NSS, yassl, axTLS, PolarSSL, WinSSL (native Windows), Secure Transport (native iOS/OS X) or qssl (native IBM i) Windows), Secure Transport (native iOS/OS X) or GSKit (native IBM i) *2 = requires OpenLDAP *3 = requires a GSS-API implementation (such as Heimdal or MIT Kerberos) or SSPI (native Windows) Loading @@ -186,7 +186,7 @@ FOOTNOTES currently supported *5 = requires nghttp2 and possibly a recent TLS library *6 = requires c-ares *7 = requires OpenSSL, NSS, qssl, WinSSL or Secure Transport; GnuTLS, for *7 = requires OpenSSL, NSS, GSKit, WinSSL or Secure Transport; GnuTLS, for example, only supports SSLv3 and TLSv1 *8 = requires libssh2 *9 = requires OpenSSL, GnuTLS, NSS, yassl, Secure Transport or SSPI (native Loading docs/INTERNALS +1 −1 Original line number Diff line number Diff line Loading @@ -43,7 +43,7 @@ Portability cyassl 2.0.0 openldap 2.0 MIT krb5 lib 1.2.4 qsossl V5R3M0 GSKit V5R3M0 NSS 3.14.x axTLS 1.2.7 PolarSSL 1.3.0 Loading docs/libcurl/curl_easy_getinfo.3 +2 −2 Original line number Diff line number Diff line Loading @@ -222,8 +222,8 @@ request was done. The struct reports how many certs it found and then you can extract info for each of those certs by following the linked lists. The info chain is provided in a series of data in the format "name:content" where the content is for the specific named data. See also the certinfo.c example. NOTE: this option is only available in libcurl built with OpenSSL, NSS, GSKit or QsoSSL support. (Added in 7.19.1) this option is only available in libcurl built with OpenSSL, NSS or GSKit support. (Added in 7.19.1) .IP CURLINFO_TLS_SESSION Pass a pointer to a 'struct curl_tlssessioninfo *'. The pointer will be initialized to refer to a 'struct curl_tlssessioninfo *' that will contain an Loading docs/libcurl/opts/CURLOPT_CERTINFO.3 +1 −1 Original line number Diff line number Diff line Loading @@ -29,7 +29,7 @@ CURLOPT_CERTINFO \- request SSL certificate information CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CERTINFO, long certinfo); .SH DESCRIPTION Pass a long set to 1 to enable libcurl's certificate chain info gatherer. With this enabled, libcurl (if built with OpenSSL, NSS, GSKit or QsoSSL) will this enabled, libcurl (if built with OpenSSL, NSS or GSKit) will extract lots of information and data about the certificates in the certificate chain used in the SSL connection. This data may then be retrieved after a transfer using \fIcurl_easy_getinfo(3)\fP and its option Loading Loading
docs/FAQ +1 −1 Original line number Diff line number Diff line Loading @@ -427,7 +427,7 @@ FAQ curl can be built to use one of the following SSL alternatives: OpenSSL, GnuTLS, yassl, NSS, PolarSSL, axTLS, Secure Transport (native iOS/OS X), WinSSL (native Windows) or qssl (native IBM i). They all have their pros WinSSL (native Windows) or GSKit (native IBM i). They all have their pros and cons, and we try to maintain a comparison of them here: http://curl.haxx.se/docs/ssl-compared.html Loading
docs/FEATURES +2 −2 Original line number Diff line number Diff line Loading @@ -178,7 +178,7 @@ FOOTNOTES ========= *1 = requires OpenSSL, GnuTLS, NSS, yassl, axTLS, PolarSSL, WinSSL (native Windows), Secure Transport (native iOS/OS X) or qssl (native IBM i) Windows), Secure Transport (native iOS/OS X) or GSKit (native IBM i) *2 = requires OpenLDAP *3 = requires a GSS-API implementation (such as Heimdal or MIT Kerberos) or SSPI (native Windows) Loading @@ -186,7 +186,7 @@ FOOTNOTES currently supported *5 = requires nghttp2 and possibly a recent TLS library *6 = requires c-ares *7 = requires OpenSSL, NSS, qssl, WinSSL or Secure Transport; GnuTLS, for *7 = requires OpenSSL, NSS, GSKit, WinSSL or Secure Transport; GnuTLS, for example, only supports SSLv3 and TLSv1 *8 = requires libssh2 *9 = requires OpenSSL, GnuTLS, NSS, yassl, Secure Transport or SSPI (native Loading
docs/INTERNALS +1 −1 Original line number Diff line number Diff line Loading @@ -43,7 +43,7 @@ Portability cyassl 2.0.0 openldap 2.0 MIT krb5 lib 1.2.4 qsossl V5R3M0 GSKit V5R3M0 NSS 3.14.x axTLS 1.2.7 PolarSSL 1.3.0 Loading
docs/libcurl/curl_easy_getinfo.3 +2 −2 Original line number Diff line number Diff line Loading @@ -222,8 +222,8 @@ request was done. The struct reports how many certs it found and then you can extract info for each of those certs by following the linked lists. The info chain is provided in a series of data in the format "name:content" where the content is for the specific named data. See also the certinfo.c example. NOTE: this option is only available in libcurl built with OpenSSL, NSS, GSKit or QsoSSL support. (Added in 7.19.1) this option is only available in libcurl built with OpenSSL, NSS or GSKit support. (Added in 7.19.1) .IP CURLINFO_TLS_SESSION Pass a pointer to a 'struct curl_tlssessioninfo *'. The pointer will be initialized to refer to a 'struct curl_tlssessioninfo *' that will contain an Loading
docs/libcurl/opts/CURLOPT_CERTINFO.3 +1 −1 Original line number Diff line number Diff line Loading @@ -29,7 +29,7 @@ CURLOPT_CERTINFO \- request SSL certificate information CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CERTINFO, long certinfo); .SH DESCRIPTION Pass a long set to 1 to enable libcurl's certificate chain info gatherer. With this enabled, libcurl (if built with OpenSSL, NSS, GSKit or QsoSSL) will this enabled, libcurl (if built with OpenSSL, NSS or GSKit) will extract lots of information and data about the certificates in the certificate chain used in the SSL connection. This data may then be retrieved after a transfer using \fIcurl_easy_getinfo(3)\fP and its option Loading