Date: Thu, 5 Apr 2007 04:54:15 -0400 From: Schiz0 <schiz0phrenic21@gmail.com> To: "Pietro Cerutti" <pietro.cerutti@gmail.com> Cc: freebsd-questions@freebsd.org, victor.engmark@gmail.com Subject: Re: Should sudo be used? Message-ID: <8d23ec860704050154j7d0cfed5n631611f4afe32006@mail.gmail.com> In-Reply-To: <e572718c0704050151h5f4a1b5el3359b21936d78b4a@mail.gmail.com> References: <7d4f41f50704050142v9c73a17tb1812f218ea4416@mail.gmail.com> <8d23ec860704050147r7b7daef2k432bb20a27ae8098@mail.gmail.com> <e572718c0704050151h5f4a1b5el3359b21936d78b4a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
True, if that was the case I'd use sudo. But I'm the only user on my systems that I'd trust with root access, so there's no point with my setup. On 4/5/07, Pietro Cerutti <pietro.cerutti@gmail.com> wrote: > > On 4/5/07, Schiz0 <schiz0phrenic21@gmail.com> wrote: > > I don't use sudo. I find it rather pointless. If I need to do something > as > > root, I use su to gain root privileges, then when I'm done, I exit and > > return to the original user. The user running su must be in the group > > "wheel" to be able to su to root. This is a simple yet convenient > security > > system. > > What when you have several people with different privileges wanting to > do stuff that normally only root can? Would you give your root > password to everyone, or rather install sudo and define exactly what a > user can do? > > > -- > Pietro Cerutti > > - ASCII Ribbon Campaign - > against HTML e-mail and > proprietary attachments > www.asciiribbon.org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d23ec860704050154j7d0cfed5n631611f4afe32006>