Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: handshake version shown as TLS1.0 even TLS1.2 set as minimum supported version in libcurl
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_cool.haxx.se>
Date: Thu, 8 Oct 2020 00:33:34 +0200 (CEST)
On Wed, 7 Oct 2020, nallasivan k via curl-users wrote:
> usign the above API , I set TLS1.2 as minimum supported TLS version, but
> still i could see the Handshake version shown in tLS1.0 .
Isn't that just what it shows because it is part of the TLS handshake?
If you use that option and connect to a server that only offers TLS < 1.2,
you can easily verify that curl won't successfully connect to it.
Date: Thu, 8 Oct 2020 00:33:34 +0200 (CEST)
On Wed, 7 Oct 2020, nallasivan k via curl-users wrote:
> usign the above API , I set TLS1.2 as minimum supported TLS version, but
> still i could see the Handshake version shown in tLS1.0 .
Isn't that just what it shows because it is part of the TLS handshake?
If you use that option and connect to a server that only offers TLS < 1.2,
you can easily verify that curl won't successfully connect to it.
--
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-10-08