git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: "Elektronik (C.Gerhardt GmbH & Co. KG)" <elektronik@gerhardt.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	"CRM (C.Gerhardt GmbH & Co. KG)" <crm@gerhardt.de>
Subject: Re: Error after update from 2.31.1 -> 2.36: Unable to negotiate with IP port X: no matching host key type found.
Date: Tue, 26 Apr 2022 07:49:14 -0700	[thread overview]
Message-ID: <20220426144914.nyaohjqqqlotxnnm@carlos-mbp.lan> (raw)
In-Reply-To: <VI1PR05MB6495349A4C42AA568A665D7BCCFB9@VI1PR05MB6495.eurprd05.prod.outlook.com>

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.

Carlo

  reply	other threads:[~2022-04-26 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 14:05 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)
2022-04-26 14:49 ` Carlo Marcelo Arenas Belón [this message]
2022-04-26 15:52   ` rsbecker
2022-04-26 21:24   ` brian m. carlson
2022-04-27  6:05     ` AW: " Elektronik (C.Gerhardt GmbH & Co. KG)

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220426144914.nyaohjqqqlotxnnm@carlos-mbp.lan \
    --to=carenas@gmail.com \
    --cc=crm@gerhardt.de \
    --cc=elektronik@gerhardt.de \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).