From: Giovanni Funchal Date: Fri, 08 Aug 2008 15:13:30 GMT Subject: Re: Can't get git clone over https with proxy and invalid certificate... Message-ID: In-Reply-To: <20080808142819.GJ28749@spearce.org> Hello, Well, turns out that my problem was that my gcc doesn't like the `-R' switch!! Strangely enough, ./configure does not check this!! (one should define Makefile's existing option NO_R_TO_GCC_LINKER) While this seems pretty serious, gcc only shows a tiny message while compiling ("unrecognized option -R"), not even a warning, and compiles anyway. So if you "make all install doc install-doc" like me, you won't see the bug. I think git build system could be improved somehow to check for that. I'll perhaps try to make a patch to this during the weekend. Regards, -- Giovanni On Fri, Aug 8, 2008 at 4:28 PM, Shawn O. Pearce wrote: > Giovanni Funchal wrote: >> Ok, so I have created the following ~/.curlrc: >> netrc >> proxytunnel >> insecure >> proxy = http://proxyserver.com:8080 >> proxy-user = proxyuser:proxypassword > ... >> $ git clone https://remoteuser@remoteserver.com/.git/ >> Initialized empty Git repository in /home/user/.git/ >> error: Proxy requires authorization! >> warning: remote HEAD refers to nonexistent ref, unable to checkout. > > Last time I used Git with an HTTP proxy that required authentication > I was doing it with an environment variable: > > http_proxy=http://me:pass@proxyserver.com:8080 git clone ... > > Fortunately this was on a Windows desktop where I was the only > user who was logged into the system, so leaking my password into my > environment for a short duration was about the same risk as putting > into a ~/. file. > > -- > Shawn. >