UNIX for Advanced & Expert Users

OK!

Do you mean I should remove the id_dsa.pub file (which I had copied over to .ssh/authorized_keys on the remotehost) in .ssh directory on localhost?!?!

I have also the pair of "id_dsa & id_dsa.pub" files in .ssh on remotehost which, of course, belong to the remoteuser. Should I remove them?!?

Finally, I am quite aware of the EUID problem when using ssh and "no" I am logged-in directly on the localhost and thanks for pointing that out.

The local key pair can be left as is..deleting them causes a problem (ie, the remote host's authorized_keys file has nothing to work with... ). The local copy of the id_dsa.pub file is meaningless to the local (or client) side of the authentication, while the remote copy of the id_dsa.pub is part of the authorized_keys file. This serves to authenticate against the local key file (ie, id_dsa).

You can/should get rid of the .pub file on the remote side, once you've cat-ted it into the remote account's ~/.ssh/authorized_keys file. Leaving it around is fine, but best practice's would suggest that you scratch it..just to be safe(r).

Thanks a lot for the detailed explanation.

So, having done all that and complied to all rules and regulations, why on earth it is still asking for the password?

What about ssh_config on the client side?

What about it?

Please keep in mind that exactly the same setting works fine when I connect to a Solaris-10 box. That's why I really think that the problem is either with Solaris-8 (the remote-server) or the OpenSSh's compatibility on 10 & 8!?!?

Well... The only thing that comes to my mind then, is that it could be caused by something related to cyphers and/or crypt libs, key length......... But I'm just guessing, I really have no idea...

ssh -V on each box...