I know rlogin is an antiquated and insecure form of accessing clients, but I was reading up on rlogin. It seems you can control who access your machine by your $HOME/.rhosts and /etc/.hosts.equiv. Supposely, you can use these files to permitt who can and can't enter a machine, ie. establishing one or two way trust.

To permit a user, you would have to add, '+ username', to permit username to access a machine from anymachine, or, 'machinename', to permit anyone from accessing the client from machinename. If you allow this access, you won't get prompted for a pass.

To attempted to try this out by adding myself, then logging-in to confirm if I was prompted for a pass. THe results were I was prompted for a pass - I should have had access.

I'm I missing something? Did they change the rules? or did I do somthing wrong?

do a "+" in your .rhosts in the homedirectory. Now every person shoud be able to connect to your host... if it works or not you can isolate your problem

just my two cents

I did, but I put a '+ myself' ie. allow myself to access the machine from any machine - the '+' is a wildcard right? And the first column represents the machine? and the second the username?

I was thinking I'd have entry without get prompted for a password, but I get prompted one.

this file is for writing the trustet hosts. Write the hostname of your trustet host and you are not promtet for a password! yes + is a wildcard for any hosts on the network

Take a look at the man page. I believe if you are being prompted for a password, .rhosts isn't going to help ya. Youi need to create a .khosts file in the same manner as the usual .rhosts. You shouldn't be prompted for a password at that point.