git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3] Allow use of TLS 1.3

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 26, 2018, 21:38 UTC
Message-ID
<nycvar.QRO.7.76.6.1803262336070.77@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
In-Reply-To
<20180326092423.GA7521@voidlinux>
Hi Logan,
On Mon, 26 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.
> 
> Signed-off-by: Loganaden Velvindron <logan@hackers.mu>

Can we *please* also add that OpenSSL 1.1.* is required (or that cURL is built with NSS or BoringSSL as the TLS backend)?

See https://public-inbox.org/git/nycvar.QRO.7.76.6.1803240035300.77@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz/ for my original please.

I deem this information *really* important because a lot of Git packages are still built against OpenSSL 1.0.2 (e.g. Git for Windows) and *won't* benefit immediately from your patch.

Ciao, Johannes

Previous: Loganaden VelvindronNext: Daniel Stenberg
Message 2 of 3 in “Allow use of TLS 1.3”
  1. Allow use of TLS 1.3Loganaden Velvindron, Mar 26, 2018
  2. Johannes SchindelinMar 26, 2018
  3. Daniel StenbergMar 26, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.