On Tue, 4 Jun 2013, Janusz Harkot wrote:

> valid point, but from what you can find on the web, the only solution 
> provided everywhere was to disable certificate checking… so maybe that's not 
> me, but this is first time someone spent some time to check whats going on 
> :)

I don't disagree with that. You may be right.

But I am the maintainer of libcurl and I have *never* gotten a report about 
this before, and I rather base my actions and assumptions on true reports from 
actual developers with whom I can discuss and delve into details with (like 
you and me right now). Basing decisions on vague statements posted elsewhere 
by unknown people is for sure a road into sadness.

Anyway, now I'm off topic. I'm glad you could fix the problem. Thanks for 
flying git + libcurl! =)

-- 

  / daniel.haxx.se