RE: Login Restrictions

From: Hamilton, Andrew (Andrew.Hamilton_at_afccc.af.mil)
Date: 06/01/04

  • Next message: Benjamin J. Weiss: "How can I help to troubleshoot an ide-scsi / kernel issue?" 
    To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Date: Tue, 1 Jun 2004 14:34:08 -0400

    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@plansysit.com]
    Sent: Tuesday, June 01, 2004 2:29 PM
    To: redhat-list@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 

    


    -- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
  • Next message: Benjamin J. Weiss: "How can I help to troubleshoot an ide-scsi / kernel issue?"

    Relevant Pages

    • Re: disconnected drive link persists
      ... This is setup is used to avoid ... account, thereby leaving the appropriate audit trail while still ... having the advantages of the common account. ... discribe that the drives will be automatically reconnected with no ...
      (microsoft.public.windowsxp.general)
    • Re: disconnected drive link persists
      ... Users have private accounts they access from their desktop. ... account, thereby leaving the appropriate audit trail while still ... having the advantages of the common account. ... Next user opens the common account, goes to recently used file list ...
      (microsoft.public.windowsxp.general)
    • Re: disconnected drive link persists
      ... This is setup is used to avoid ... account, thereby leaving the appropriate audit trail while still ... having the advantages of the common account. ... so the user must supply his private credentials for the ...
      (microsoft.public.windowsxp.general)
    • Re: disconnected drive link persists
      ... users locking others out of shared computers, and to avoid the time- ... account, thereby leaving the appropriate audit trail while still ... having the advantages of the common account. ... so the user must supply his private credentials for the ...
      (microsoft.public.windowsxp.general)
    • Which way is correct to implement sudo
      ... the other is applications) regarding the best way to set up sudo. ... Solaris servers from a remote location normally They are ... I also have an in-house applications group (again a couple of people - with some ... back down to the relevant application account. ...
      (comp.sys.sun.admin)