When you try to login using ssh some users might find asking for ssh password is slow here is the solution how to fix this problem.
Solution 1
Edit the /etc/ssh/ssh_config file using the following command
sudo vi /etc/ssh/ssh_config
Commentout the following lines
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
save the file and exit
Solution 2
If you got to System>Administration>Network
Now you should see similar to following screen here click the "General" tab
You need to Uncheck the option that says "Scan for available services and advertise . . ." and close
Now you can try to login using ssh you should see it will prompt for password immediately
10 comments:
Solution 2 disables a handy feature of Feisty: you can address any of the computers on your local network as example:
bob-laptop.local
regardless of the DNS server or what address DHCP has assigned.
Does this have anything to do with my Feisty issues of being unable to SSH from my Kubuntu host to my VMWarePlayer Guest Debian Etch, or from my guest Etch to the host Kubuntu?
These two systems can SSH to anywhere else on or outside our network, and they can ping one another, but they cannot SSH to one another. It's driving me nuts and there hasn't been any activity on the bug report yet.
This seems to have solved a major setback I experienced after moving from Edgy to Feisty. My SAMBA network slowed to a crawl. The network shares that were mounted in my home directory made it almost impossible to access $home. After turning off this option everything seems to be in order. Kudos.
Solution 2 fixed the problem for me! Now ping doesn't take forever and ssh is back to normal...
I have Kubuntu installed but it seems like going to ->System Settings->Network Settings->Zeroconf Service Discovery (item in menu on the left) and unchecking the 'Enable Zeroconf network browsing' and 'Browse local network' options seems to accomplish the same thing.
Thanks so much for this fix. So many things were unbearably slow such as SSH asking for a password and all subversion commands, etc. I was beginning to think I had hardware problems as this is on a new laptop. Now it seems back to normal.
Thanks again!
Actually, the real fix is to add the line "UseDNS no" into your sshd_config and restart.
Tom: that fixed it, thanks :)
Both UseDNS and GSSAPIAuthentication help
on some systems. It varies. I have one
machine where neither setting helped.
UseDNS no
GSSAPIAuthentication no
If I read the article correctly you can
just uncomment the line about
GSSAPIAuthentication, but then it would
still be set to "yes" which is the
default value. Doing this did nothing for
me, but when I set it to "no" the
password-prompt showed immediately, like
you'd expect. Unless I am mistaken I ask
you to please correct the article.
UseDNS no
worked perfectly for me.
Post a Comment