> ssh CAN replace both rsh and rlogin, To do things as you would with rsh, > you use 'ssh <command>'. The trick is that you must first put the public > keys for each system into either /etc/ssh or your .ssh directory (in the > files ssh_known_keys or known_keys respectively). The easiest way to do > this is to slogin from one machine to the other, and then do the same from > the other machine back again - manually approving authentication each > time (by the way - slogin is just an alias for ssh).
yes, but even then ssh asks for a password, I've tried every authentication method described in the ssh man page, but I couldn't get it to login without manual authentication (with rsa keys it asks for the passphrase). The other thing I don't like about ssh is that it doesn't enforce the /etc/login.access /etc/limits or the comment field in /etc/passwd (which allows you to set the priority at which users processes run at).. As I have no real need to have my sessions encrypted, I see no advantage to using ssh over telnet..
pgphOHNgtWMMF.pgp
Description: PGP signature
