list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <>
To: "'Daniel Stenberg'" <>
Cc: "'Jeff King'" <>,
	"'Daniel Carpenter'" <>,
	"'Ævar Arnfjörð Bjarmason'" <>,
Subject: RE: http.sslVersion only specifies minimum TLS version, later versions are allowed
Date: Mon, 3 May 2021 17:23:33 -0400	[thread overview]
Message-ID: <000d01d74062$95cf6a50$c16e3ef0$> (raw)
In-Reply-To: <nycvar.QRO.7.76.2105032306580.30150@fvyyl>

On May 3, 2021 5:10 PM, Daniel Stenberg wrote:
>Subject: RE: http.sslVersion only specifies minimum TLS version, later
>are allowed
>On Mon, 3 May 2021, Randall S. Becker wrote:
>> What if http.sslVersion=v1[,v2]... were supported, so there would be
>> an enumeration of allowed versions.
>That doesn't map very well to the options libcurl provide.
>> The benefit of an enumeration is that you could force something like
>> 3.0-fips if your environment requires a FIPS-certified version for
>> communication. Admittedly this is a different use case than discussed
>Yes, and as "3.0-fips" is not a TLS version at all I think it would
>matters in a wrong direction.
>You can build libcurl to use use a FIPS compatible crypto library today,
but if you
>do then you still select TLS version using the same options like before.

Sadly, curl_version_info_data.ssl_version does not provide this level of
detail. Maybe it should, but I'm not about to go there.


      reply	other threads:[~2021-05-03 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 11:56 Daniel Carpenter
2021-05-03 13:55 ` Ævar Arnfjörð Bjarmason
2021-05-03 14:10   ` Jeff King
2021-05-03 15:02     ` Daniel Carpenter
2021-05-03 20:46       ` Jeff King
2021-05-03 20:56         ` Daniel Stenberg
2021-05-03 21:01         ` Randall S. Becker
2021-05-03 21:09           ` Daniel Stenberg
2021-05-03 21:23             ` Randall S. Becker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000d01d74062$95cf6a50$c16e3ef0$' \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).