Date: Fri, 6 Apr 2007 00:21:41 -0500 From: Erik Osterholm <erik-freebsd@erikosterholm.org> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Should sudo be used? Message-ID: <20070406052141.GA73428@idoru.cepheid.org> In-Reply-To: <4615A83E.9040803@u.washington.edu> References: <7d4f41f50704050142v9c73a17tb1812f218ea4416@mail.gmail.com> <8d23ec860704050147r7b7daef2k432bb20a27ae8098@mail.gmail.com> <e572718c0704050151h5f4a1b5el3359b21936d78b4a@mail.gmail.com> <8d23ec860704050154j7d0cfed5n631611f4afe32006@mail.gmail.com> <14989d6e0704050201s6be99be8m62aa6822299e0e6a@mail.gmail.com> <4615A83E.9040803@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 05, 2007 at 06:54:06PM -0700, Garrett Cooper wrote: > b) sudo can run commands directly instead of having to type in su, and > then run the command from the su'ed shell. >From man su: If the optional args are provided on the command line, they are passed to the login shell of the target login. Note that all command line argu- ments before the target login name are processed by su itself, everything after the target login name gets passed to the login shell. This lets you run commands without obtaining a full shell. > Unless you're trying to get root access and fall under point b., and > this is your own personal machine, there's basically no use in using > sudo. Besides, one less binary on your machine with those sorts of > privileges offers less methods of attacking your machine in order to get > elevated privileges. I like the logging ability. If I fatfinger a command line, I can easily go back and see exactly what I did(in case the output of the command doesn't make it obvious), and when. It's all personal preference, though. > -Garrett Erik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070406052141.GA73428>