RE: Using ssh instead of rsh...

[Curtis, Darren S]

Michael,

The -v helped tons. The problem was that the permissions
on the ~/.ssh/authorization was 664 instead of 600. I
changed the perms and it worked but I had to supply the
passphase. I generated a new key pair (ssh-keygen) and
left the passphrase empty. Now the server refuses the
connection and asks me for the user's login password.

The output is:
debug: Encryption type: 3des
debug: Sent encrypted session key.
debug: Installing crc compensation attack detector.
debug: Received encrypted confirmation.
debug: Trying RSA authentication with key 'user@hostB'
debug: Server refused our key.
debug: Doing password authentication.

Any ideas on how I can type:
ssh hostB date
and get the output without typing a passphrase or password?

Thanks again,

Darren Curtis

-----Original Message-----
RSA authentication can be a bit tricky to set up if you aren't used to
it.  Have you tried running ssh manually as the user in question?  The
-v switch can be really useful when RSA isn't working as expected, as
the output should tell you right where SSH is falling down.



"Curtis, Darren S" wrote:
> 
> Hello,
> 
> I have looked through all the documentation and the FAQs
> and can still not find out a way (that works) to use ssh
> as a direct replacement for rsh.


-- 
Michael Jinks, IB // Technical Entity // Saecos Corporation