Best not used for security reasons. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Wed, 14 Feb 2024, Karen Lewellen wrote: > One more quick question after I just did a search. > There seems to be a command line option that turns off strict host key > checking. > Where do options go for ssh? > or should I run that command with ssh-keygen instead? > if so, what is the syntax? > Thanks, > Karen > > > > On Tue, 13 Feb 2024, Jude DaShiell wrote: > > > First delete the outdated key since it won't work any longer, then login > > again and a new key will be added for you by the external server. > > ssh-keygen -r hostname > > should get that first task done. > > When you log in without a key you'll be asked if you want to trust the > > system and your answer is yes. > > That adds the new key and you're on your way. > > > > > > -- > > Jude <jdashiel at panix dot com> > > "There are four boxes to be used in defense of liberty: > > soap, ballot, jury, and ammo. > > Please use in that order." > > Ed Howdershelt 1940. > > > > On Tue, 13 Feb 2024, Karen Lewellen wrote: > > > >> Hi all, > >> Will aim to keep this simple. > >> is there an option with ssh from the command line that allows you to update > >> new keys for the known host list? > >> I ssh into my dreamhost office workspace from shellworld, as in > >> ssh email@email.thingy. > >> I provide the password, reaching the dreamhost shell structure for the > >> domains > >> they host on behalf of my employer. > >> dreamhost moved our services to a new server, changing our ip address, not > >> an > >> issue, but also changing the fingertip keys <hope that is the correct term, > >> previously saved for my access from shellworld..who seems to use a strict > >> matching process of some kind. > >> My hope? is that there is an option that tells ssh to update the > >> identifiers > >> used for known hosts? > >> > >> Thanks, > >> Kare > >> > >> > >> > > > > -- You received this message because you are subscribed to the Google Groups "blinux-list@xxxxxxxxxx" group. To unsubscribe from this group and stop receiving emails from it, send an email to blinux-list+unsubscribe@xxxxxxxxxx.