From owner-freebsd-security Fri Oct 19 10:41:40 2001 Delivered-To: freebsd-security@freebsd.org Received: from palanthas.neverending.org (dhcp-167-206-208-144.netmonger.net [167.206.208.144]) by hub.freebsd.org (Postfix) with ESMTP id 8C0C437B401 for ; Fri, 19 Oct 2001 10:41:34 -0700 (PDT) Received: by palanthas.neverending.org (Postfix, from userid 1000) id 35EE226C01; Fri, 19 Oct 2001 13:41:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by palanthas.neverending.org (Postfix) with ESMTP id 2FE0122E02; Fri, 19 Oct 2001 13:41:34 -0400 (EDT) Date: Fri, 19 Oct 2001 13:41:34 -0400 (EDT) From: Frank Tobin To: Will Andrews Cc: security@FreeBSD.ORG Subject: Re: KCheckPass -- make it setuid root or not? In-Reply-To: <20011019120706.T25747@squall.waterspout.com> Message-ID: <20011019133826.O4565-100000@palanthas.neverending.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Will Andrews, at 12:07 -0500 on 2001-10-19, wrote: OK, so I keep getting mail every now and then from people who can't figure out why kcheckpass / kscreensaver won't authenticate their password(s). It's because I decided to play it safe and made kcheckpass non setuid root, which it needs in order to call getpwnam(). Why would you choose to make it non setuid root? Isn't the warning that is associated with all setuid-installed programs enough? Not installing it setuid-root would be like installing sudo without setuid; it's pointless without the bit set. You can't count on the warning messages to get to the user; if someone goes to ports/x11/kde2, and does "make install", the message is going to be buried in the middle of compiling kdelibs, kdebase, kdemultimedia, kdenetwork, etc. -- Frank Tobin http://www.neverending.org/~ftobin/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message