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

Re: [Feature REQ]Add CURLOPT_SSL_CIPHER_LIST to git for allowing custom cipher usages

From
Kevin D <me@ikke.info>
Date
Apr 7, 2015, 10:42 UTC
Message-ID
<20150407104215.GD9387@vps892.directvps.nl>
In-Reply-To
<20150406122753.GA29626@desktop.luxing.im>
On Mon, Apr 06, 2015 at 09:27:53AM -0300, Steven Huang wrote:
Show 17 quoted lines
> Hi,
> 
>     We know git uses cURL to grab https repositories from the Internet. Nowadays
>     the SSL-enabled git repos are getting more and more, especially self-hosted
>     ones.
> 
>     Some of the websites including those enabled by CloudFlare, however, does
>     not support common encryption ciphers provided by cURL. For example,
>     TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 will not be support by default in
>     both cURL or git, and it is not a common cipher, Debian/RHEL does not even
>     support it by default (but Fedora does, maybe others, didn't test).
> 
>     Is it possible to add this feature (this opt is set by calling by curl
>     --cipher cipher_name) to git, allowing custom cipher usage?
> 
>     Thank you very much.
>

curl through git will honor settings in ~/.curlrc. So you can just add the cipher to your ~/.curlrc, and it should work.

Previous: Steven Huang
Message 2 of 2 in “[Feature REQ]Add CURLOPT_SSL_CIPHER_LIST to git for allowing custom cipher usages”
  1. Steven HuangApr 6, 2015
  2. Kevin DApr 7, 2015

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.