Have this problem all the time at work. It didn't occur to me to share. We reinstall systems all the time. So much so that I wrote a shell wrapper around ssh-keygen. It has an option to manage known hosts. ssh-keygen -q -v -R ${host}
On Sep 10, 2017 3:47 PM, "Ken Stephens" <k...@cad2cam.com> wrote: > Rich Shepard wrote: > > On Tue, 5 Sep 2017, Rich Shepard wrote: > > > >> I'm out of ideas of what to test so I can fix this issue, and seek > advice > >> from experienced network admins. > > Having tried all suggestions from my thread on LQ I re-read openssh > web > > pages, particularly the sections on authorized_keys and known_hosts. It > > occurred to me that for reasons known only to computers, the server's > entry > > in ~/.ssh/known_hosts was FUBAR. > > > > Yep. That was the problem. Cleaned out all known_host entries on each > > portable, then entered the command $ ssh salmo. Told openssh to connect > to > > the unknown server, correctly entered my passphrase, and the connection > was > > established for each portable. > > > > My web searches did not find any result that suggested cleaning > > known_hosts when a client refuses to connect to a server. This is a > lesson > > I'll not soon forget. > > > > Rich > > > Rich, > > Thanks for sharing your findings. You come up with interesting problems > and solutions in Linux. I > learn from them. > > I find that if I don't find a solution after diligent searching, the > problem is usually something very > obvious that I have missed. My forehead is much flatter after discovering > what I did from the slap > that reflexibly happens at that time. > > Thanks, again, > Ken > _______________________________________________ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug