All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loganaden Velvindron <logan@hackers.mu>
To: git@vger.kernel.org
Subject: [PATCH v2] Allow use of TLS 1.3
Date: Fri, 23 Mar 2018 23:34:35 +0400	[thread overview]
Message-ID: <20180323193435.GA21971@voidlinux> (raw)

Add a tlsv1.3 option to http.sslVersion in addition to the existing 
tlsv1.[012] options. libcurl has supported this since 7.52.0.

Done during IETF 101 Hackathon

Signed-off-by: Loganaden Velvindron <logan@hackers.mu>
---
 Documentation/config.txt | 2 +-
 http.c                   | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index ce9102cea..b18cb9104 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1957,7 +1957,7 @@ http.sslVersion::
 	- tlsv1.0
 	- tlsv1.1
 	- tlsv1.2
-
+	- tlsv1.3
 +
 Can be overridden by the `GIT_SSL_VERSION` environment variable.
 To force git to use libcurl's default ssl version and ignore any
diff --git a/http.c b/http.c
index a5bd5d62c..25eb84c11 100644
--- a/http.c
+++ b/http.c
@@ -62,6 +62,9 @@ static struct {
 	{ "tlsv1.1", CURL_SSLVERSION_TLSv1_1 },
 	{ "tlsv1.2", CURL_SSLVERSION_TLSv1_2 },
 #endif
+#ifdef CURL_SSLVERSION_TLSv1_3
+	{ "tlsv1.3", CURL_SSLVERSION_TLSv1_3 }
+#endif
 };
 #if LIBCURL_VERSION_NUM >= 0x070903
 static const char *ssl_key;
-- 
2.16.2


             reply	other threads:[~2018-03-23 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 19:34 Loganaden Velvindron [this message]
2018-03-23 21:47 ` [PATCH v2] Allow use of TLS 1.3 Daniel Stenberg
2018-03-23 22:04   ` Junio C Hamano
2018-03-24  7:52     ` Loganaden Velvindron
2018-03-24  4:21   ` Loganaden Velvindron
2018-03-24  4:31   ` Loganaden Velvindron
2018-03-24  5:43   ` Loganaden Velvindron
2018-03-23 21:55 ` Junio C Hamano
2018-03-23 22:28   ` Ævar Arnfjörð Bjarmason
2018-03-24  4:23   ` Loganaden Velvindron

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

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

  git send-email \
    --in-reply-to=20180323193435.GA21971@voidlinux \
    --to=logan@hackers.mu \
    --cc=git@vger.kernel.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.