Hi All, The systems I am using are SCO5.0.5 and Linux RH7.1. I am trying to telnet between systems without the need to enter a logon/password pair. I have looked at Tony's pages and SCO's (oops Caldera) pages without success. I have tried telnet -a -l NAME but I am always asked for a password in SCO and RedHat also asks for a Logon. The user NAME exists on both machines and share the same password. What am I missing? Advice appreciated Serge

The systems I am using are SCO5.0.5 and Linux RH7.1. I am trying to telnet between systems without the need to enter a logon/password pair. I have looked at Tony's pages and SCO's (oops Caldera) pages without success. I have tried telnet -a -l NAME but I am always asked for a password in SCO and RedHat also asks for a Logon. The user NAME exists on both machines and share the same password. What am I missing? try setting up user-equivalency and then using rlogin instead of telnet. for user-equivalency: make sure both boxes have a user account of the same name (like root already exists on both) make sure both hosts have hostnames, if necessary just invent names and define in /etc/hosts, then put the names in /etc/hosts.equiv and ~/.rhosts, then rlogin other-host. on boxa and boxb edit the following files... /etc/hosts:   127.0.0.1 localhost   10.0.0.200 boxa   10.0.0.202 boxb /etc/hosts.equiv   localhost   boxa   boxb ~/.rhosts (do this for each user who needs it)   localhost   boxa   boxb also chmod 600 ~/.rhosts then to login from boxa to boxb without a password, login to boxa as one of the users who has a .rhosts on boxb, then: rlogin boxb this works between a sco box and a linux box too and probably any unix. you might need to verify that rlogin is present in /etc/inetd.conf of the box you are logging in to before it works. It comes setup and enabled out of the box, but some security-conscious admin or consultant may have disabled it at some point. as far as I can tell from the docs, you're not supposed to need both .rhosts and /etc/hosts.equiv. .rhosts applies to a user, hosts.equiv applies to all users, but so far I always need .rhosts in order for it to work. this is a gaping crater of a security hole so I don't set it up very often.

as far as I can tell from the docs, you're not supposed to need both .rhosts and /etc/hosts.equiv. .rhosts applies to a user, hosts.equiv applies to all users, but so far I always need .rhosts in order for it to work. this is a gaping crater of a security hole so I don't set it up very often. You always have to watch out any time you use the word 'all', particularly when used in conjunctions with comptuers as in all users above. In at least one system I've used in the past I've seen doucmentation that indicates that for root only .rhosts is used. This prevents a cracking of a remote system from compromosing root on other systems. The closest I can see here is for the ruserok() used by rcmd