OT: Root access policy
devin.teske at fisglobal.com
Thu Dec 29 18:05:54 UTC 2011
> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org [mailto:owner-freebsd-
> questions at freebsd.org] On Behalf Of Polytropon
> Sent: Thursday, December 29, 2011 9:58 AM
> To: Carl Johnson
> Cc: freebsd-questions at freebsd.org
> Subject: Re: OT: Root access policy
> On Thu, 29 Dec 2011 09:15:45 -0800, Carl Johnson wrote:
> > Damien Fleuriot <ml at my.gd> writes:
> > > On 12/29/11 10:58 AM, Polytropon wrote:
> > >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote:
> > >>> For the first time, a customer is asking me for root access to
> > >>> said customer's servers.
> > >>
> > <snip>
> > >>> Assuming that I'll be asked to continue administering said
> > >>> servers, I guess I should at least enable accounting...
> > >>
> > >> You could have better success using sudo. Make sure the customer is
> > >> allowed to "sudo <command>". The sudo program will log _all_ things
> > >> the customer does, so you can be sure you can review actions.
> > >> Furthermore you don't need to give him the _real_ root password. He
> > >> won't be able to "su root" or to login as root, _real_ root. But he
> > >> can use the "sudo" prefix to issue commands "with root privileges".
> > >>
> > >
> > > "sudo su -" or "sudo sh" and the customer gets a native root shell
> > > which does *not* log commands !
> > The sudoers manpage mention the noexec option which is designed to
> > help with the first problem. They also show an example using !SHELLS
> > which can help with the second.
> It's also worth mentioning "super" again - as an alternative to "sudo". But
> if restricted in any way, both of them are _not_ requivalent to "full root
> (equals: root + root's password) which the customer initially demanded.
I highly recommend reading audit(4) and then audit(8) (in that order).
This will catch more security instances than simply relying on sudo(8) logging
-- which won't catch any commands once the user has "become root" (ala "sudo su
-" for example).
Once upon a time (RELENG_4), we used a kernel module named "lrexec" which logged
all system calls to exec(3) family of functions, but it was too verbose.
audit(4) replaces our need for lrexec.
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
More information about the freebsd-questions