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

Re: Git 1.7.5 problem with HTTPS

From
DSDmitry Smirnov <divis1969@gmail.com>
Date
Nov 16, 2011, 10:10 UTC
Message-ID
<CACf55T6rUiE8Pm3s16oFgJ1ueTAdOwOz_+XptE-tZM1z9fcq+w@mail.gmail.com>
In-Reply-To
<alpine.DEB.2.00.1111161008430.19479@tvnag.unkk.fr>
> I'd say that isn't very likely and you could easily snoop on the network to> figure that out for sure
In the very first message I wrote that there is strange tcpdump record:
21      3.815135        X.X.X.X Y.Y.Y.Y TLSv1   215     Ignored Unknown Record
In this record there is some binary dump followed by an uncripted text:
GET /pub/scm/git/git.git/info/refs?service=git-upload-pack HTTP/1.1
User-Agent: git/1.7.5.4 Host: git.kernel.org Accept: */* Pragma:
no-cache

This packet is recorded before negotiation complete, so I'm wondering who is guilty: git or curl? What Git is providing to libcurl? Can I log it?

> curl will send the HTTP request once the TLS negotiation has completed as
> told by the TLS library. I believe you said you're using GnuTLS, are you
> using a recent version?
I'm using the version that comes with Ubuntu 11.10.
Previous: Daniel StenbergNext: Jonathan Nieder
Message 9 of 13 in “Git 1.7.5 problem with HTTPS”
  1. Dmitry SmirnovNov 15, 2011
  2. Shawn PearceNov 15, 2011
  3. Junio C HamanoNov 15, 2011
  4. Dmitry SmirnovNov 16, 2011
  5. Junio C HamanoNov 16, 2011
  6. Tay Ray ChuanNov 16, 2011
  7. Dmitry SmirnovNov 16, 2011
  8. Daniel StenbergNov 16, 2011
  9. Dmitry SmirnovNov 16, 2011
  10. Jonathan NiederNov 16, 2011
  11. Dmitry SmirnovNov 16, 2011
  12. Haitao LiNov 16, 2011
  13. Dmitry SmirnovNov 17, 2011

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.