From: Daniel Stenberg <daniel@haxx.se>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'Jeff King'" <peff@peff.net>,
"'Daniel Carpenter'" <dc@ammonit.com>,
"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
git@vger.kernel.org
Subject: RE: http.sslVersion only specifies minimum TLS version, later versions are allowed
Date: Mon, 3 May 2021 23:09:47 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.2105032306580.30150@fvyyl> (raw)
In-Reply-To: <000c01d7405f$823fd090$86bf71b0$@nexbridge.com>
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 above.
Yes, and as "3.0-fips" is not a TLS version at all I think it would complicate
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.
--
/ daniel.haxx.se
next prev parent reply other threads:[~2021-05-03 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 11:56 http.sslVersion only specifies minimum TLS version, later versions are allowed 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 [this message]
2021-05-03 21:23 ` Randall S. Becker
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.2105032306580.30150@fvyyl \
--to=daniel@haxx.se \
--cc=avarab@gmail.com \
--cc=dc@ammonit.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 public inbox
https://80x24.org/mirrors/git.git
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).