Thanks. For what I understand I found on http://blogs.msdn.com/b/phkelley/archive/2014/01/20/adding-a-corporate-or-self-signed-certificate-authority-to-git-exe-s-store.aspx
a note: *(Note: *In the Git for Windows 2.x series, the path has changed to C:\Program Files (x86)\Git\mingw32\ssl\certs\ca-bundle.crt.) Thus, what happens (or seems to happen) is that git is looking for certificates in the wrong location. Once you manage to tell it where the new location for ca-bundle is things work again. I was surprised that the upgrade process form 1.9.* wouldn't take care automatically of this. Maybe this is only a problem of git for windows, and maybe not so many people upgraded but I could not find many complaints about this on the net. Thanks Maurizio > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
