From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Https proxy auth issue with git in cygwin 2.2.1
Date: Mon, 21 Sep 2015 10:31:00 -0000 [thread overview]
Message-ID: <20150921103100.GF14466@dinwoodie.org> (raw)
In-Reply-To: <CAFkLm6xW=5uUP+CRrmUontqPzqAZ+r4WdwjVAhP+XTvs53JmFQ@mail.gmail.com>
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
next prev parent reply other threads:[~2015-09-21 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 6:55 Lukasz Pielak
2015-09-21 10:20 ` Andrey Repin
2015-09-21 10:32 ` Lukasz Pielak
2015-09-21 10:31 ` Adam Dinwoodie [this message]
2015-09-21 10:39 ` Achim Gratz
2015-09-25 7:20 ` LukaszPielak
2015-10-05 20:23 ` Adam Dinwoodie
2015-10-16 12:30 ` Johan Laenen
2015-11-23 22:40 ` Adam Dinwoodie
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=20150921103100.GF14466@dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).