Enrique Tobis twosigma.com> writes:
> There is something I don't understand, though. Johan must be configuring
his proxy either a) through git
> config files; or b) through environment variables. Johan says his proxy
uses NTLM authentication. If he
> is doing a), then my change should not have ha
Enrique Tobis twosigma.com> writes:
> run GIT_CURL_VERBOSE=1 git pull and send the output. That should show the
> failing authentication method.
Please see the file in attachment,
greetings,
Johan
$ GIT_CURL_VERBOSE=1 /bin/git pull
* STATE: INIT => CONNECT handle 0x20081bd0; line 1090 (conn
Enrique Tobis twosigma.com> writes:
> Johan: how are you configuring your proxy? Git configuration or
environment variables? Also, could you
I'm just using the https_proxy environment variable, not the git configuration:
$ export https_proxy=http://:@myproxy:8080
Sorry for the multiple at
Johan Laenen gmail.com> writes:
I'm not the only one. Another cygwin user is experiencing the exact same
problem, see http://permalink.gmane.org/gmane.os.cygwin/155039 for more info.
greetings,
Johan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the bo
Enrique Tobis twosigma.com> writes:
>
> Hey!
>
> I'm really sorry to hear that.
>
> That change should enable more forms of authentication with your proxy,
but it does cause libcurl to choose
> the one it finds most secure, according to the docs
> (http://curl.haxx.se/libcurl/c/CURLOPT_HTTPAUT
Commit 5841520b makes it impossible to connect to github from behind my
company's firewall.
I'm running CYGWIN_NT-6.1 and the default git version 2.5.3 complains with a
fatal error when trying to git pull:
$ /bin/git --version
git version 2.5.3
$ /bin/git pull
fatal: unable to access 'https://git
6 matches
Mail list logo
