From: <rsbecker@nexbridge.com>
To: "'Carlo Marcelo Arenas Belón'" <carenas@gmail.com>,
"'Elektronik (C.Gerhardt GmbH & Co. KG)'"
<elektronik@gerhardt.de>
Cc: <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 11:52:20 -0400 [thread overview]
Message-ID: <049d01d85985$9ffe3870$dffaa950$@nexbridge.com> (raw)
In-Reply-To: <20220426144914.nyaohjqqqlotxnnm@carlos-mbp.lan>
On April 26, 2022 10:49 AM, Carlo Marcelo Arenas Belón wrote:
>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.
next prev parent reply other threads:[~2022-04-26 15:53 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
2022-04-26 15:52 ` rsbecker [this message]
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='049d01d85985$9ffe3870$dffaa950$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=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).