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

Re: git access using SSL certificates

From
ILIlari Liusvaara <ilari.liusvaara@elisanet.fi>
Date
Jun 29, 2010, 00:46 UTC
Message-ID
<20100629004631.GA14854@LK-Perkele-V2.elisa-laajakaista.fi>
In-Reply-To
<6E28EE29-0FFA-4467-AE10-76ED2AEF79A5@uab.edu>
On Mon, Jun 28, 2010 at 05:39:03PM -0500, Shantanu Pavgi wrote:
Show 6 quoted lines
> 
> Tried with Git 1.7.1 on Mac: Doesn't work, same error. 
> Tried from another CentOS box with Git 1.7.1 and it worked fine. 
> 
> In all failed cases apache logs indicate: <timestamp> [error] Re-negotiation
> request failed. 
 
Renegotiation failed? There has been TLS security hole regarding to
renegotiation, and many patched TLS implementations do not allow renegotiation
unless the other side is patched too.

Maybe only one of the sides is patched? Both should be patched. One way to find out if server is patched is to connect with client (e.g. Gnutls 2.10) that supports safe renegotiation and disallow connecting to unpatched servers and see if it connects or not.

-Ilari
Previous: Shantanu Pavgi
Message 5 of 5 in “git access using SSL certificates”
  1. Shantanu PavgiJun 28, 2010
  2. Shantanu PavgiJun 28, 2010
  3. Ilari LiusvaaraJun 28, 2010
  4. Shantanu PavgiJun 28, 2010
  5. Ilari LiusvaaraJun 29, 2010

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.