Hi,

I have a Nitrokey Start that has the same problem, but the suggested workaround was not enough for me. After a few attempts, I discovered that I need this in my ssh_config file:

KexAlgorithms [email protected]
HostKeyAlgorithms -ecdsa-sha2-nistp256

Notice that after this change connections to hosts that previously used a ecdsa-sha2-nistp256 host key will fail key verification and trigger the usual scary message about a MITM attack.

Thanks, Giovanni.
--
Giovanni Mascellani <[email protected]>

Reply via email to