On 02/24/2017 07:33 AM, Rich Shepard wrote: > An attempt to scp directories to a laptop from the workstation failed > because ssh saw a changed public key in known_hosts. How this happened I've > no idea, but it needs fixing, perhaps by copying the correct ecdsa public > key from the workstation to the laptop. > > On stackexchange I read that ecdsa is for key exchange and ed25519 for > data transfers, so I assume that I need to copy both public keys from the > workstation to the laptop. Is this correct? > > Reading man ssh-keyscan suggests that running this (specifying the > workstation host name) will do the job. However, While this adds several > lines to the laptop's ~/.ssh/known_hosts it does not allow me to scp from > the workstation. > > Advice on finding the reason ssh became FUBAR and fixing the problem is > needed. > > Rich
Are you logging in via username/password or ssh key? If so, then just clearing both ~./ssh/known_hosts and then using ssh to log into each box from each box will reset the entries. If you are using ssh key based authentication you will need to check if ~./ssh/authorized_keys still exists on the box you are going to ssh or scp into. If it exists are you using ~/.ssh/id_rsa_pub or a key from ~/.gnupg? Did you set a passphrase for these keys and then forget? I am by no means an expert on this, but if you have the standard rsa keys pairs automatically generated when you installed slackware, via "ssh-keygen -t rsa" you do not need ecdsa vs ed2559 worries. ssh and scp works by default with username/password as long as you keep ~./ssh/known_hosts clean of stale entries. -Ed _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
