From: Anatoly Yakovenko <aeyakovenko@gmail.com>
Date: Thu, 21 Feb 2008 18:57:58 GMT
Subject: Re: GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate
Message-ID: <e26d18e40802211057o255246f3p31800c73eb8391ec@mail.gmail.com>
In-Reply-To: <20080221064252.GA16036@glandium.org>

yep, it tells me that the certificate is rejected because it was
signed for a different ip then the one i am connected too.  while this
is a security threat, browsers will let you ignore it, so i expect
that libcurl or git should be able to ignore that error as well.

On Wed, Feb 20, 2008 at 10:42 PM, Mike Hommey <mh@glandium.org> wrote:
>
> On Wed, Feb 20, 2008 at 03:35:54PM -0800, Anatoly Yakovenko wrote:
>  > I am not sure if its a bug in curl or git, but despite setting
>  > GIT_SSL_NO_VERIFY=1, if i use a different ip address or hostname then
>  > the certificate was signed for, git fails to push changes.
>
>  Can you try with GIT_CURL_VERBOSE=1 ? The trace message will probably
>  help understanding what happens.
>
>  Mike
>