Tag Info

New answers tagged

0

Not sure which client you are using, but for some the default settings is to forward SSH agent requests and to ignore the middle-man's key(s). Look in your documentation to disable "agent forwarding", in ssh(1) that is the -a option and the ForwardAgent configuration value.


0

We ran into the same problem and we followed the steps in the answer. But it still did not work for us. Our problem was that login worked from one client but not from another (the .ssh directory was NFS mounted and both clients were using the same keys). So we had to go one step further. By running the ssh command in verbose mode you get a lot of ...


0

It sounds like it still wants you to input the password. When you SSH to HostB from HostA, does it ask for a password? If it does, you will need to change your ssh_config file (/etc/ssh/sshd_config on RHEL/Centos) to have: PasswordAuthentication no If PasswordAuthentication is set to yes, it will always prompt you for a password.


0

My guess would be because you don't have PasswordAuthentication set to yes. PasswordAuthentication yes Add this to the sshd_config on the machines and try again. This should prompt for password. Another solution would be to take the contents of ~/.ssh/id_rsa.pub on HostA and add it to the file ~/.ssh/authorized_keys on the HostB Now that you have ...


0

I just had this same problem, and for me the solution was to set UsePAM to no. See, even with PasswordAuthentication set to no, you'll still get keyboard-interactive, and in my case my local ssh program kept defaulting to that, for some reason. Extra background to help anyone with the same situation: I'm connecting from a host running Dropbear to one ...


0

Just in case, because this happened to me. Get sure you have sshd running in the host! It's a stupid failure, but might be really be your problem.



Top 50 recent answers are included