threads / discuss / 39014

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

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

## tl;dr

2 messages between Apr 6, 2015 and Apr 7, 2015.

replies: 1people: 2as markdown or json

Steven Huang· Apr 6, 2015, 12:27 UTC · lore
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.
-- 
Luxing Huang
Kevin D· Apr 7, 2015, 10:42 UTC · re: Steven Huang · lore

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

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.

← back to recent threads