DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=GJBy4F781QMzAQjvtBYKZBE9LHzyLP
	5hnfzBWW5c1OiclJ5+2eG1WifKDuA2rEQwqO0TbT958CBTvEMFAh+cnzG5vPPtLz
	2ON41wGG+ivpxSmThubU6rJmQ0Vk8eNuNWScRLI9Y/4Q+ugaxGGYEPC69jTnedEU
	KB6DuLcVye9hQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 21 Sep 2015 11:31:00 +0100
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Https proxy auth issue with git in cygwin 2.2.1
Message-ID: <20150921103100.GF14466@dinwoodie.org>
References: <CAFkLm6xW=5uUP+CRrmUontqPzqAZ+r4WdwjVAhP+XTvs53JmFQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAFkLm6xW=5uUP+CRrmUontqPzqAZ+r4WdwjVAhP+XTvs53JmFQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Mon, Sep 21, 2015 at 08:54:39AM +0200, Lukasz Pielak wrote:
> In the latest Cygwin 2.2.1. git doesn’t work with proxy authentication.

What do you mean by proxy authentication here?  What do you have
configured, and how?

> The git version is 2.5.1 and the curl version is 7.43.
> The error prints fatal: unable to access
> 'https://github.com/mockito/mockito.git/': Unknown SSL protocol error
> in connection to github.com:443

WJFFM with those versions, but then I'm not using any sort of web proxy.

> In my previous Cygwin 1.7.35 (with curl 7.41) this problem didn’t
> exist. Git for windows (git 2.5.1 version, but curl is 7.44) seems to
> work too.

Are you able to test any other combinations of these?  I don't think the
results for Git for Windows are going to be particularly informative --
there are too many variables between that build and Cygwin's -- but
knowing whether it's the bump from Cygwin v1.7.35 to v2.2.1, or from
Curl v7.41 to v7.43, would be potentially useful.

> I assume that  there is a bug in curl rather than in git.

As an interim solution, does using ssh instead of https work?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple