From: rh <richard_hubbe11@lavabit.com>
Date: Tue, 09 Apr 2013 19:40:44 GMT
Subject: Re: segfault in git-remote-http
Message-ID: <20130409124044.908c160c718cc357a139354e@lavabit.com>
In-Reply-To: <20130409174735.GA23494@sigill.intra.peff.net>

On Tue, 9 Apr 2013 13:47:36 -0400
Jeff King <peff@peff.net> wrote:

> On Tue, Apr 09, 2013 at 10:41:34AM -0700, rh wrote:
> 
> > > git-remote-http does not touch the openssl code itself at all. We
> > > only talk to curl, which handles all of the ssl (and may even be
> > > built on gnutls). So if that is the problem, then I think it may
> > > be a libcurl bug, not a git one.
> > 
> > Thanks, I see git-remote-{http,https,ftp,ftps} are the same size.
> > Minor nitpick but shouldn't the error thrown say git-remote-https?
> 
> They are all hardlinks to the same program (or copies if your platform

Yes they are hardlinks.

> does not support hardlinks or symlinks). But I'm not sure which error
> you are talking about. We can figure out inside the program which
> program was invoked by checking argv, but I do not see us printing
> remote-http anywhere.

I wasn't clear in my initial report....and may have omitted a
significant fact. The "git clone" returned right away and I saw no
error. The error shows up in dmesg via syslog, something like
git-remote-http[1234]: segfault at xxxxxxxx blah blah in libcrypto