>> > Seems that I have problems with secure NFS and "rlogin". After some
>> > hours not logged in on a machine a following "rlogin" (with an entry in
>> > ~/.rhosts, e.g. no password chat) some strange access problems occur
>> > when accessing secure NFS dirs...
>> How do you plan to do a keylogin with no password?
>Mhhh, I don't know the magic behind the scenes but I thougth "rlogin" does
>everytimes do a "keylogin".
If you don't give it a password, then it cannot keylogin.
Quote:>But it seems that "keylogin" is skipped if I enter the machine using rlogin
>with a ~/.rhosts entry ;-( - making the usage of rsh/rlogin/secure NFS very
>problematic (anyway - using ~/.rhosts and secure NFS at the same time is a
>paradoxon from vthe view of a "secure system").
If the home directory uses secure NFS, this is not much of a
problem. If rlogin cannot read your home directory it will not find
the '.rhosts', so you will be asked for a password and then there
will be a keylogin. However, if you are already keylogged in
(keyserv holds your secure nfs key), then your '.rhosts' will be
found, you will be logged in, and no keylogin is required.
What doesn't work is '/etc/hosts.equiv', since that is always visible
even when your home directory is not.
Quote:>To answer you question: I don't know. But it would be nice if someone knows
>a way to do this magic...
>BTW: Does slogin from ssh2 do a keylogin ?
ssh1 will do a keylogin if you use password based authentication.
But ssh2 won't. I believe it is in the wish list of things planned
for the future.
by