git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin D <me@ikke.info>
To: Steven Huang <steven@accsc.im>
Cc: git@vger.kernel.org
Subject: Re: [Feature REQ]Add CURLOPT_SSL_CIPHER_LIST to git for allowing custom cipher usages
Date: Tue, 7 Apr 2015 12:42:15 +0200	[thread overview]
Message-ID: <20150407104215.GD9387@vps892.directvps.nl> (raw)
In-Reply-To: <20150406122753.GA29626@desktop.luxing.im>

On Mon, Apr 06, 2015 at 09:27:53AM -0300, Steven Huang wrote:
> 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.

      reply	other threads:[~2015-04-07 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 12:27 [Feature REQ]Add CURLOPT_SSL_CIPHER_LIST to git for allowing custom cipher usages Steven Huang
2015-04-07 10:42 ` Kevin D [this message]

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=20150407104215.GD9387@vps892.directvps.nl \
    --to=me@ikke.info \
    --cc=git@vger.kernel.org \
    --cc=steven@accsc.im \
    /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 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 NNTP newsgroup(s).