From owner-freebsd-security Thu Jun 7 8:47:27 2001 Delivered-To: freebsd-security@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 28EC437B408 for ; Thu, 7 Jun 2001 08:47:23 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f57FlG713299; Thu, 7 Jun 2001 11:47:16 -0400 (EDT) Date: Thu, 7 Jun 2001 11:47:15 -0400 From: Alfred Perlstein To: "Nickolay A. Kritsky" Cc: security@FreeBSD.ORG Subject: Re: SGID make Message-ID: <20010607114714.R1832@superconductor.rush.net> References: <009501c0ef65$23482580$0600a8c0@ibmka.internethelp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <009501c0ef65$23482580$0600a8c0@ibmka.internethelp.ru>; from nkritsky@internethelp.ru on Thu, Jun 07, 2001 at 07:18:42PM +0400 X-all-your-base: are belong to us. 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 * Nickolay A. Kritsky [010607 11:19] wrote: > Can anybody tell me why /usr/local/bin/make in FreeBSD 4.2 is SGID kmem? I thought that make is intended only for compiling > huge C programs, isnt it? > > #ls -l /usr/local/bin/make > -rwxr-sr-x 1 root kmem 445486 May 14 15:58 /usr/local/bin/make As people have stated this isn't our make, it's most likely GNU make installed without using the port. The reason for the sgid'ness is most likely so that the binary can query the system load average to optimize parrallel compliation without overwhelming the system. Although, this is sort of silly as the info should be available via sysctl in FreeBSD. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message