From owner-freebsd-security Mon Apr 22 20:38:41 2002 Delivered-To: freebsd-security@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-203.zoominternet.net [24.154.28.203]) by hub.freebsd.org (Postfix) with ESMTP id 47CB137B400 for ; Mon, 22 Apr 2002 20:38:34 -0700 (PDT) Received: from topperwein (topperwein [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id g3N3cT369657 for ; Mon, 22 Apr 2002 23:38:29 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Mon, 22 Apr 2002 23:38:24 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD Security Subject: Cleaning suid Binaries (Was: Re: stdio security advisory) In-Reply-To: <20020422181601.C14111-100000@walter> Message-ID: <20020422233549.A69611-100000@topperwein.dyndns.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 On Mon, 22 Apr 2002, Jason Stone wrote: > > does anybody know's which kind of another files should be taken the +s > > option to block this bug ? > > Uh, all of them? Unless you explicitly need the functionality of a > particular setuid binary, you should remove the setuid bit. > > For example, on most of my machines I run something like: > > SETUIDOK='/usr/bin/su|/usr/local/bin/sudo|/usr/bin/passwd' Just FYI, gpg needs to be setuid root in order to lock pages containing cleartext passphrase information in memory; otherwise, they can end up in your swap area. You'll know you're in trouble if gpg blurts out "Warning: Using insecure memory!" right before it prompts you for the passphrase. > [...snip rest of suid cleanup script...] -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message