rshd /etc/hosts.equiv and 'privileged user'

	Free Downloads, Community Forum, FAQs and Developer Resources

Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums	Register	Login	Search	Subscriptions	My Profile	Inbox
Tool Warehouse	FAQs	Resources	Help	Member List	Address Book	Logout

rshd /etc/hosts.equiv and 'privileged user'

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [SFU / Interix / SUA Technology] >> Interix Advanced Forum >> rshd /etc/hosts.equiv and 'privileged user'

Page: [1]

Message

<< Older Topic Newer Topic >>

rshd /etc/hosts.equiv and 'privileged user' - Apr. 18, '06, 4:11:49 PM

Ron

Posts: 77
Joined: May 21, '03,
Status: offline

I got a domain user account that has been granted local admin rights. I am trying to do a passwordless rsh into this account but it is not reading the /etc/hosts.equiv file; it's only reading the ~/.rhosts file. If I revoke the local admin rights on this account, then it'll read /etc/hosts.equiv.

I've read the rshd man page, is says iruserok is doing the authentication. In the iruserok man page it says that /etc/hosts.equiv is only read if the user is _not_ a privileged user.

My question is, what defines a privileged user in this case?
i.e. what other groups are considered privileged?

Post #: 1

RE: rshd /etc/hosts.equiv and 'privileged user' - Apr. 18, '06, 4:59:50 PM

Rodney

Posts: 3714
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

Note: I'm just the messenger; don't shoot me

The local Administrator account and members of the local Administrators group.
So this will encompass anyone in the domain Administrators group because this
group is a member of the local Administrators group (thus domain Administrator
gets lumped in). You need to check the groups that are part of the local
Administrators group for your machine (and the cascade that'll lump it in).
But specifically speaking just local Admin and local Administrators group.

Originally the iruserok() function would have just been set this way only with root.
But the rshd code has been changed to expand the meaning. My guess is
that it was expanded out so that Administrator and the Administrators group
can create and change /etc/hosts.equiv without it causing a security weakness
(or at least keeping it to a minimum).

(in reply to Ron)