public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] ssh key type ed25519
@ 2020-11-21 15:22 n952162
  2020-11-22  9:47 ` Michael
  0 siblings, 1 reply; 2+ messages in thread
From: n952162 @ 2020-11-21 15:22 UTC (permalink / raw
  To: gentoo-user

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

I tried to ssh to another machine and got a failing man-in-the-middle
warning.

The fingerprint given to check didn't match that of the target host.  On
closer inspection, the entries in known_hosts are *ecdsa-sha2-nistp256*
and the offending key was of type *ed25519*, as reported by the client.

These are both gentoo machines, relatively recently updated.

Everything on the net talks about how to generate key files of the
appropriate type, but I'm don't want to generate a key file.

Apparently, this is a gentoo configuration issue.  USE flags of openssh
on both machines are the same.

There are two news items related to ssh, but neither seems relevant.

Has there been a changed system-wide determination of the key type and
what would be the best way to make them consistent across all machines?


[-- Attachment #2: Type: text/html, Size: 1125 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-user] ssh key type ed25519
  2020-11-21 15:22 [gentoo-user] ssh key type ed25519 n952162
@ 2020-11-22  9:47 ` Michael
  0 siblings, 0 replies; 2+ messages in thread
From: Michael @ 2020-11-22  9:47 UTC (permalink / raw
  To: gentoo-user

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

On Saturday, 21 November 2020 15:22:03 GMT n952162 wrote:
> I tried to ssh to another machine and got a failing man-in-the-middle
> warning.

When keys have changed at the remote end and the new key is not listed in 
~/.ssh/known_hosts, you will get a warning whether you want to accept the key 
and continue connecting or not.  This is the moment, or ideally in advance of 
this moment, you contact the remote system's sysadmin to find out what the 
fingerprint of the new key might be.


> The fingerprint given to check didn't match that of the target host.  On
> closer inspection, the entries in known_hosts are *ecdsa-sha2-nistp256*
> and the offending key was of type *ed25519*, as reported by the client.
> 
> These are both gentoo machines, relatively recently updated.

Therefore this update seems to have generated new keys and set ed25519 as the 
default.


> Everything on the net talks about how to generate key files of the
> appropriate type, but I'm don't want to generate a key file.
> 
> Apparently, this is a gentoo configuration issue.  USE flags of openssh
> on both machines are the same.
> 
> There are two news items related to ssh, but neither seems relevant.
> 
> Has there been a changed system-wide determination of the key type and
> what would be the best way to make them consistent across all machines?

Take a look in /etc/ssh and/or ~/.ssh/ for the config files to set preferences 
for ssh client and sshd server either generically or per remote host.  
However, you'll need to be reviewing and adjusting these regularly, because 
ciphers and algos become deprecated when vulnerabilities are discovered.

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-11-22  9:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-21 15:22 [gentoo-user] ssh key type ed25519 n952162
2020-11-22  9:47 ` Michael

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox