git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate

From
Daniel Stenberg <daniel@haxx.se>
Date
Feb 22, 2008, 10:53 UTC
Message-ID
<Pine.LNX.4.64.0802221149210.13958@yvahk3.pbagnpgbe.fr>
In-Reply-To
<e26d18e40802211727w4f7f5b37vc73a756f6b384289@mail.gmail.com>
On Thu, 21 Feb 2008, Anatoly Yakovenko wrote:
Show 8 quoted lines
> $ 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)

That's the very problem Mike Hommey's recent patch addresses. Verifying a peer's certificate is done with two different libcurl options:

* VERIFYPEER verifies the server's certificate against a local CA cert bundle
* VERIFYHOST verifies that the name in the server certificate matches the host
   you're talking to

For this particular case, you can in fact also make it work by making sure the server's certificate has the IP address as a "subjectAltName".

Previous: Anatoly Yakovenko
Message 9 of 9 in “GIT_SSL_NO_VERIFY=1 over http doesn't ignore a different ip address for the signed certificate”
  1. Anatoly YakovenkoFeb 20, 2008
  2. Mike HommeyFeb 21, 2008
  3. Anatoly YakovenkoFeb 21, 2008
  4. Daniel StenbergFeb 21, 2008
  5. Don't verify host name in SSL certs when GIT_SSL_NO_VERIFY is setMike Hommey, Feb 21, 2008
  6. Junio C HamanoFeb 21, 2008
  7. Mike HommeyFeb 21, 2008
  8. Anatoly YakovenkoFeb 22, 2008
  9. Daniel StenbergFeb 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.