Steps To Troubleshoot SSH Error With Wrong Yes/No/Ask Argument
Speed up your PC in minutes
If you’re getting the wrong Yes/No/Ask Argument SSH error code on your PC, take a look at these fix ideas.
Not The Answer You Are Looking For? View Other Questions Tagged SSH Key Authentication Or Ask Your Own Question.
As Chris Adams noted below, in the 6.5 years since this article was written, openssh has seen quite a bit of change, and now there is a new, much safer option than the original advice below:< /p>
* ssh(1): increase size of StrictHostKeyChecking parameter by more than two new ones settings. The first "accept new" is automatically accepted unpublished keys, but partners for modification or rejection Sick home keys. Is this a safe part of the current behavior? relativebut StrictHostKeyChecking=no. The second setting, "off", is synonymous with to see current behavior StrictHostKeyChecking=no: accept again Host key and Continue to connect hosts with host key. In the future, letting go will change the meaning StrictHostKeyChecking=none when accepting a new behavior. bz#2400
Instead of marking
StrictHostKeyChecking no in the manually defined
StrictHostKeyChecking no in
/etc/ssh/ssh_config of your file, leaving the global option used by the user on the server. Or install in your archive
~/.ssh/config where there is an omission to pay only for the current user. Or you can use it in command line terms:
ssh StrictHostKeyChecking=no -o -r "$user" "$host"
Here’s an explanation of how this works best, from Mauvais Oui Non Demander Argument Erreur Ssh
Zly Tak Nie Zapytaj Argument Blad Ssh
Mal Si No Preguntar Argumento Ssh Error
Slecht Ja Nee Vraag Argument Ssh Fout
Plohoj Da Net Sprosit Argument Oshibka Ssh
잘못된 예 아니오 인수 요청 Ssh 오류
Errore Ssh Dell Argomento Si No Ask Errato
Erro De Ssh De Argumento Sim Nao Ask Ruim
Schlechter Ja Nein Frage Argument Ssh Fehler
Daligt Ja Nej Fraga Argument Ssh Fel