From: Jason Merrill <jason@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Frank Ch. Eigler via Overseers" <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: Bad server host key: Invalid key length
Date: Mon, 5 Feb 2024 08:26:23 -0500 [thread overview]
Message-ID: <CADzB+2mcPmGAsRVc3O_raPLkr-0os4EBxsncajOLijBoAobxtA@mail.gmail.com> (raw)
In-Reply-To: <20240204203126.GK1583@gnu.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
On Sun, Feb 4, 2024 at 3:31 PM Mark Wielaard <mark@klomp.org> wrote:
> Hi,
>
> On Sun, Feb 04, 2024 at 09:20:33PM +0100, Frank Ch. Eigler via Overseers
> wrote:
> >
> > > I just upgraded my laptop to Fedora 39 CSB, and now ssh to sourceware
> is
> > > rejected with the above error message thanks to the Fedora
> crypto-policies
> > > openssh.config. I can work around this easily enough by setting
> > > RequiredRSASize to 1024 in my .ssh/config, but surely I'm not the
> first to
> > > run into this?
> >
> > You may be the second. Nuke all the sourceware references in your
> .ssh/known_hosts and try again.
>
> Yeah, this is a misleading ssh client warning/error:
> https://inbox.sourceware.org/20230308105633.GI22818@gnu.wildebeest.org/
>
> = openssh update produces misleading invalid key length warning
>
> Connecting to sourceware through ssh with a newer openssh or crypto
> policy might produce a misleading warning about the key length being
> too short:
>
> Bad server host key: Invalid key length
>
> Please don't try to replace your ssh key, there is nothing wrong with
> it. The issue is that you might have an old server key in your
> ~/.ssh/known_hosts file. Simply remove it and reconnect to get the new
> server key:
>
> ssh-keygen -R sourceware.org
> ssh-keygen -R cygwin.com
> ssh-keygen -R gcc.gnu.org
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=2164016
Thanks for pointing me in the right direction, what a terrible diagnostic.
Jason
prev parent reply other threads:[~2024-02-05 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 18:29 Jason Merrill
2024-02-04 20:20 ` Frank Ch. Eigler
2024-02-04 20:31 ` Mark Wielaard
2024-02-05 13:26 ` Jason Merrill [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADzB+2mcPmGAsRVc3O_raPLkr-0os4EBxsncajOLijBoAobxtA@mail.gmail.com \
--to=jason@redhat.com \
--cc=fche@elastic.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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.
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).