romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-08 04:47:15 +03:00
Code Issues Projects Releases Packages Wiki Activity

or higher -> or greater 11 docs 3

Browse source
This commit is contained in:
Viktor Szakats 2026-05-26 18:58:01 +02:00
parent 4b2c4c9e2e
commit ce4d34e28f
No known key found for this signature in database
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/cmdline-opts/proxy-tls13-ciphers.md
View file

@ -26,8 +26,8 @@ Read up on TLS 1.3 cipher suite details on this URL:
https://curl.se/docs/ssl-ciphers.html
This option is used when curl is built to use OpenSSL 1.1.1 or higher,
Schannel, wolfSSL, or mbedTLS 3.6.0 or higher.
This option is used when curl is built to use OpenSSL 1.1.1 or greater,
Schannel, wolfSSL, or mbedTLS 3.6.0 or greater.
Before curl 8.10.0 with mbedTLS or wolfSSL, TLS 1.3 cipher suites were set
by using the --proxy-ciphers option.

2
docs/cmdline-opts/proxy-tlsv1.md
View file

@ -15,6 +15,6 @@ Example:
# `--proxy-tlsv1`
Use at least TLS version 1.x when negotiating with an HTTPS proxy. That means
TLS version 1.0 or higher
TLS version 1.0 or greater
Equivalent to --tlsv1 but for an HTTPS proxy context.

2
docs/cmdline-opts/pubkey.md
View file

@ -22,4 +22,4 @@ file.
curl attempts to automatically extract the public key from the private key
file, so passing this option is generally not required. Note that this public
key extraction requires libcurl to be linked against a copy of libssh2 1.2.8
or higher that is itself linked against OpenSSL. (Added in 7.39.0.)
or greater that is itself linked against OpenSSL. (Added in 7.39.0.)