I find it is pretty helpful to read the messages. If the messages are too terse, add verbose or debug flags. Then read what it says.
Is there anything listening on caddis's port nnnnn? On Wed, Apr 19, 2023 at 2:56 PM Rich Shepard <rshep...@appl-ecosys.com> wrote: > On Wed, 19 Apr 2023, Russell Senior wrote: > > > So, you can use an editor to remove the offending line 2, and you'll be > > asked to accept the new hostkey the next time to connect. > > Russell, > > The authorized_keys on both hosts each contains the public key of the > other. > > The known_hosts on the laptop (caddis) contains only a key for salmo > created > at 14:42, when I tried to ssh from caddis to salmo. I could not: > > $ ssh salmo > The authenticity of host '[salmo]:nnnnn ([192.168.55.1]:nnnnn)' can't be > established. > ED25519 key fingerprint is > SHA256:/RInRdtcIMbpPu3LZmpg5wfAWi9ozQwgKLPnTQEDcxg. > This key is not known by any other names > Are you sure you want to continue connecting (yes/no/[fingerprint])? yes > Warning: Permanently added '[salmo]:nnnnn' (ED25519) to the list of known > hosts. > rshepard@salmo: Permission denied (publickey) > > Going the other way, from salmo to caddis (where salmo's known_hosts has > only caddis as an entry) also fails: > > $ ssh caddis > ssh: connect to host caddis port nnnnn: Connection refused > > With only two hosts on the network it shouldn't be this difficult to get > them to communicate. > > What am I still missing? > > Rich >
