ssh issues since upgrade to Slack v10
 

Forwarding port 22 to my box. A friend of mine can successfully log on to his account on my system via ssh (he's also using slack 10)... I can ssh out to my school's system successfully, and also ssh into my own system like so "ssh localhost"...

What I've been unable to do since upgrading is to ssh back into my box after having ssh'd out of it... ssh out to school computer then ssh back in to mine to verify everything's working.

The error I receive (and this is only me, not my friend who ssh's in with no problem), is:

Permission denied (publickey,password,keyboard-interactive).

The verbose attempts I've made appear to show all authentication methods being used, except for the last... i'd like to ssh in using just password prompting, but the above error appears before I'm prompted for a password at all.

I've found little help related to this on the web, most of it ending in the user reinstalling ssh, and I'd like not to do that if I don't have to.

Any ideas?

Did you try to move your ~/.ssh directory to say ~/.ssh.back ?

Removing ~/.ssh/ has no effect... have tried that, but just retried to be sure.

/etc/sshd_config seems to be a confusing file also... I've uncommented the line reading

PrintMotd

and changed the value to no to get rid of the motd when ssh'ing in (currently still only able to ssh in via "ssh localhost"), and I've tried both stopping and starting AND rebooting the entire system to get the configuration to change, yet it's still there...

Very annoying... is there some more esoteric manner in which to change the configurations, or am I just misunderstanding the simplicity of all this?

When I see "Permission denied (publickey,password,keyboard-interactive)." I would think that something come wrong with the public key. And where are the public keys ? On both the ~/.ssh directories of the server and the client.

On the client : public key file is generally : ~/.ssh/id_rsa.pub
On the server : public key file is generally : ~/.ssh/authorized_keys2

The public key file of the server may not contains just one public key, that depends what you did with public keys (it can have more than one client publlic key into it).

So for my part I would try to play with the public keys on both sides, client and server.

Step-by-step instructions on how to use public key authentication with SSH:

http://www.edafe.org/slackware/index...authentication

Regards,
Edafe