Date: Sun, 19 Apr 1998 09:54:06 -0600 (MDT) From: Marc Slemko <marcs@znep.com> To: Niall Smart <rotel@indigo.ie> Cc: freebsd-security@FreeBSD.ORG Subject: Re: suid/sgid programs Message-ID: <Pine.BSF.3.95.980419094941.16057k-100000@alive.znep.com> In-Reply-To: <199804191452.PAA00588@indigo.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 Apr 1998, Niall Smart wrote: > On Apr 19, 12:26am, "Fernando P. Schapachnik" wrote: > } Subject: Re: suid/sgid programs > > En un mensaje anterior Robert Watson escribi˘: > > [...] > > > We note also that a fairly large chunk of suid/sgid programs are UUCP > > > programs -- something that a majority of FreeBSD users (I would guess?) do > > > not use. In terms of reducing risk, disabling suid/sgid on these programs > > > > Don't be so sure. FreeBSD boxes are an excellent choice for UUCP servers. > > Actually I have a few running (and planning to install more). > > I think the point he was making was that most users don't use UUCP, and > therefore we shouldn't be shipping UUCP related utilities with set[ug]id > bits. Presumably if you can configure UUCP you can use chmod. Erm... that is an extremely poor policy. Figuring out what needs to be setuid or setgid to what isn't trivial. I'm not sure what you are trying to save here. What is the real issue if someone compromises the user or group uucp? I guess that uucico, which is setgid to dialer, gives them something. If they compromise the uucp uid then they can mess with the uuucp binaries which someone may try to run sometime for some reason, but I really don't see how it is enough to warrant shipping broken programs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980419094941.16057k-100000>