From owner-freebsd-hackers Wed Dec 6 21:53:59 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 21:53:58 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 3BC5D37B400 for ; Wed, 6 Dec 2000 21:53:58 -0800 (PST) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id eB75rsh13666 for ; Wed, 6 Dec 2000 22:53:55 -0700 Message-Id: <200012070553.eB75rsh13666@chopper.Poohsticks.ORG> To: hackers@FreeBSD.ORG Subject: Re: sudo [was: Re: your mail] In-reply-to: Your message of "Thu, 07 Dec 2000 15:41:08 +1000." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13662.976168434.1@chopper.Poohsticks.ORG> Date: Wed, 06 Dec 2000 22:53:54 -0700 From: Drew Eckhardt Sender: drew@chopper.Poohsticks.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , gjb@gbch.net writes: >David Talkington wrote: > >> sudo definitely helps if it's carefully administered, but it still >> grants root access to a file, > >This is wrong -- sudo will grant access with whatever user >privileges you wish to grant, maybe root and maybe some other >user. It all depends on the way you set it up. Unlike a potential ACL solution, sudo also logs which privledged commands were executed when and how, thus letting you know who within the hierchy broke what and how... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message