From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Loganaden Velvindron <logan@hackers.mu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4] Allow use of TLS 1.3
Date: Thu, 29 Mar 2018 17:03:08 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1803291702580.5026@qfpub.tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180329101418.GA7736@voidlinux>
Hi Logan,
On Thu, 29 Mar 2018, Loganaden Velvindron wrote:
> Add a tlsv1.3 option to http.sslVersion in addition to the existing
> tlsv1.[012] options. libcurl has supported this since 7.52.0.
>
> This requires OpenSSL 1.1.1 with TLS 1.3 enabled or curl built with
> recent versions of NSS or BoringSSL as the TLS backend.
Thank you,
Johannes
next prev parent reply other threads:[~2018-03-29 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 10:14 [PATCH v4] Allow use of TLS 1.3 Loganaden Velvindron
2018-03-29 15:03 ` Johannes Schindelin [this message]
2018-03-29 20:40 ` Junio C Hamano
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.6.1803291702580.5026@qfpub.tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=logan@hackers.mu \
/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).