Fwd: Re: Ideas for ssh / sudo

[George Meharry II]

Or another idea still ....

Have "point people" be responsible for their primary
groups ... Say that I belong to a group named agtfof
and have been designated the "group owner". In the
aliases file on our mail server there is a line that
says ...

agtfof::include:/var/mail/malias/agtfof.malias

The ownership of this file is 664 and the ownership is
root:agtfof

Now to administer this "alias" file, I don't have to
be logged into the mailhost, I don't have to be root,
nor do I have to run newalias each time a change is
made to agtfof.malias. All I have to have is access to
the agtfof group and be logged into a machine that is
mounting the "alias" directory.

There is a pitfall to this - when a user account is
removed - there is potential to have bogus entries in
the included alias files; so we have also set up a
cron job to monitor these files.



Note: forwarded message attached.


=====
BEGIN:VCARD
N:Meharry II;George Lewis
TITLE:Infrastructure Analyst
EMAIL;INTERNET:GMeharry at yahoo.com
TEL;WORK:(317) 230-6176
TEL;FAX;WORK:(317) 230-8733
END:VCARD

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
-------------- next part --------------
An embedded message was scrubbed...
From: Paul Lussier <pll at mclinux.com>
Subject: Re: Ideas for ssh / sudo 
Date: Tue, 10 Oct 2000 16:09:03 -0400
Size: 4485
URL: </pipermail/sudo-users/attachments/20001011/d2f1fc8c/attachment.mht>