Login Restrictions

[Hamilton, Andrew]

My immediate response would be to let them have sudo as the common account
user, and not su.  If more than one user can su at a time then if there are
more than one operating as that user then you still won't know who was
responsible for what.  However if you make them sudo as the user to do the
things they need to do then you always know who did what...
 
Regards,
Drew

-----Original Message-----
From: Ted Beaton [mailto:tbeaton at plansysit.com]
Sent: Tuesday, June 01, 2004 2:29 PM
To: redhat-list at redhat.com
Subject: Login Restrictions


I have an application running on a Redhat 9 machine that requires being run
by a certain user.  I also have security requirements that necessitate
logging the actions of all users logged into the system so I can't have two
different people log in with the same user name.  Then I won't know who is
doing what on the system.  What I would like to do is have a separate user
account for each person and then require them to su to the common user
account that needs to run the application.  Then I can track the individual
logins and know who su'd to the common account and when they did it.  Does
anyone know how to disable logins to the common user account while still
allowing the account to be functional for when people need to su to it?
 
Thanks in advance,
 
Ted

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/redhat-list/attachments/20040601/cecf6582/attachment.htm>