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

RE: Error after update from 2.31.1 -> 2.36: Unable to negotiate with IP port X: no matching host key type found.

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Apr 26, 2022, 15:52 UTC
Message-ID
<049d01d85985$9ffe3870$dffaa950$@nexbridge.com>
In-Reply-To
<20220426144914.nyaohjqqqlotxnnm@carlos-mbp.lan>
On April 26, 2022 10:49 AM, Carlo Marcelo Arenas Belón wrote:
Show 15 quoted lines
>On Tue, Apr 26, 2022 at 02:05:14PM +0000, Elektronik (C.Gerhardt GmbH & Co. KG)
>wrote:
>>
>> I found that after an update from git 2.31.1. to 2.36 the authentication to our git
>server (running gitea 1.13.1) fails. We are getting the following error:
>
>I am guessing the issue might be the one documented in the following git for
>windows issue:
>
>  https://github.com/git-for-windows/git/issues/3468
>
>The problem is not with git (neither a git for windows) specific issue, but with the
>underlying version of openssh that is used in your server and the best course of
>option is to upgrade that and generate a new host key, but there are other
>options shown in that ticket that might help in the meanwhile.
I noticed this prior to 2.36.0, so I do no think it is related to git. Switching OpenSSH versions triggered this situation.
Previous: Carlo Marcelo Arenas BelónNext: brian m. carlson
Message 3 of 5 in “Error after update from 2.31.1 -> 2.36: Unable to negotiate with IP port X: no matching host key type found.”
  1. Elektronik (C.Gerhardt GmbH & Co. KG)Apr 26, 2022
  2. Carlo Marcelo Arenas BelónApr 26, 2022
  3. rsbecker@nexbridge.comApr 26, 2022
  4. brian m. carlsonApr 26, 2022
  5. AW: Error after update from 2.31.1 -> 2.36: Unable to negotiate with IP port X: no matching host key type found.Elektronik (C.Gerhardt GmbH & Co. KG), Apr 27, 2022

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.