public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh problem
Date: Sun, 26 Dec 2021 18:07:56 +0000	[thread overview]
Message-ID: <2224712.ElGaqSPkdT@lenovo.localdomain> (raw)
In-Reply-To: <20211226170046.1910b1d0@digimed.co.uk>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

On Sunday, 26 December 2021 17:00:46 GMT Neil Bothwick wrote:
> On Sun, 26 Dec 2021 11:42:41 -0500, Philip Webb wrote:
> > I want to login to a remote site <aaaaa.bbbbbbbb.cc> using 'ssh'.
> > The response I get is "Unable to negotiate with <nnn.nnn.nnn.n> port
> > <nn>: no matching host key type found. Their offer: ssh-rsa,ssh-dss".
> 
> > Yesterday, I updated 'openssh' :
> It sounds like the host may be running an old version of sshd that only
> offers ciphers that are now disabled by default in newer releases. You
> can get round this by enabling those ciphers for this host, with
> something like this in ssh_config
> 
> Host aaaaa.bbbbbbbb.cc
>     Ciphers +ssh-rsa

The initial error is about "no matching host key type", so the option needed 
would be:

HostKeyAlgorithms +ssh-rsa

After which another error may pop up, probably about Ciphers.  ;-)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-26 18:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 16:42 [gentoo-user] ssh problem Philip Webb
2021-12-26 16:55 ` Branko Grubić
2021-12-26 17:00 ` Neil Bothwick
2021-12-26 18:07   ` Michael [this message]
2021-12-26 20:11     ` Neil Bothwick
2021-12-27 11:03     ` Philip Webb
2021-12-26 19:20 ` Grant Taylor
  -- strict thread matches above, loose matches on Subject: below --
2019-03-10  7:25 [gentoo-user] Ssh problem Philip Webb
2019-03-10 10:31 ` Nils Freydank
2011-02-22 11:43 [gentoo-user] ssh problem dhk
2011-02-22 12:37 ` Alan McKinnon
2011-02-22 13:24   ` dhk
2011-02-22 13:30     ` Mick
2011-02-22 14:19       ` dhkuhl
2011-02-22 14:51         ` Mick
2011-02-23  8:42           ` Joost Roeleveld
2011-02-24 13:17             ` dhk
2011-02-24 13:53               ` Mick
2011-02-24 18:09                 ` dhk
     [not found]                   ` <201102241201.12178.matt@deploylinux.net>
2011-02-24 21:51                     ` dhk
2011-02-24 23:30                       ` Mick
2011-02-25  1:08                         ` dhk
2011-02-25  2:30                           ` Stroller
2011-02-25 12:09                           ` dhk
2011-02-25 23:08                             ` Mick
2011-02-26  7:49                             ` Adam Carter
2011-02-26  8:13                               ` Mick
2011-02-26 11:05                                 ` dhk
2011-02-26 13:23                                   ` Adam Carter
2011-02-24 23:26                   ` Mick
2011-02-25 10:36 ` Adam Carter
2011-02-25 12:12   ` dhk
2011-02-25 12:45     ` Alex Schuster
2011-02-26  0:09 ` Mark Shields

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=2224712.ElGaqSPkdT@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.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