From: "Anatoly Yakovenko" <aeyakovenko@gmail.com>
To: "Mike Hommey" <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate
Date: Thu, 21 Feb 2008 17:27:20 -0800 [thread overview]
Message-ID: <e26d18e40802211727w4f7f5b37vc73a756f6b384289@mail.gmail.com> (raw)
In-Reply-To: <20080221190954.GA24759@glandium.org>
On Thu, Feb 21, 2008 at 11:09 AM, Mike Hommey <mh@glandium.org> wrote:
> On Thu, Feb 21, 2008 at 10:57:58AM -0800, Anatoly Yakovenko wrote:
> > 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.
>
> What is the exact message ?
$ GIT_SSL_NO_VERIFY=1 GIT_CURL_VERBOSE=1 git clone
https://aeyakovenko@127.0.0.1/git
i get this as an error:
error: SSL: certificate subject name 'localhost' does not match target
host name '127.0.0.1' (curl_result = 51, http_code = 0, sha1 =
4590de71622f1a90f906413fd7f63d5553cd5f93)
cloning https://aeyakovenko@localhost/git works fine
next prev parent reply other threads:[~2008-02-22 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 23:35 GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate Anatoly Yakovenko
2008-02-21 6:42 ` Mike Hommey
2008-02-21 18:57 ` Anatoly Yakovenko
2008-02-21 19:04 ` Daniel Stenberg
2008-02-21 19:23 ` [PATCH] Don't verify host name in SSL certs when GIT_SSL_NO_VERIFY is set Mike Hommey
2008-02-21 23:10 ` Junio C Hamano
2008-02-21 19:09 ` GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate Mike Hommey
2008-02-22 1:27 ` Anatoly Yakovenko [this message]
2008-02-22 10:53 ` Daniel Stenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e26d18e40802211727w4f7f5b37vc73a756f6b384289@mail.gmail.com \
--to=aeyakovenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).