On Sun, Nov 24, 2013 at 01:54:34PM +0100, Stefan Beller wrote: > Here is the output of > sb@sb:/tmp$ GIT_TRANSPORT_HELPER_DEBUG=1 git clone https://github.com/Bertram25/ValyriaTear.git tmp Thanks. I think I see what is going on. We finish the helper conversation here: > Checking connectivity... done. > Debug: Disconnecting. > error: git-remote-https died of signal 13 > sb@sb:/tmp$ which means that remote-https is trying to exit, and is cleaning up any curl connections. The actual SIGPIPE in the strace is here: [pid 28319] write(3, "\25\3\2\0...[binary goo]...", 27) = -1 EPIPE (Broken pipe) and if you walk backwards, fd 3 is: [pid 28319] socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3 ... [pid 28319] connect(3, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("192.30.252.131")}, 16 ) = -1 EINPROGRESS (Operation now in progress) So it's sending binary junk to the https socket while trying to exit, which makes me guess that it's something to do with terminating the SSL session, but the server has already hung up. Which would make it a curl problem. Googling "curl sigpipe" seems to come up with a report of this exact case: http://curl.haxx.se/mail/archive-2013-01/0003.html with a bug opened here: http://sourceforge.net/p/curl/bugs/1180/ Looks like the fix went into curl 7.32.0. I have 7.33.0, which seems fine. Can you confirm that your libcurl is a bit older? -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html