From owner-freebsd-security Tue Nov 17 23:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28407 for freebsd-security-outgoing; Tue, 17 Nov 1998 23:52:08 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28400 for ; Tue, 17 Nov 1998 23:52:06 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zg2Op-00036n-00; Wed, 18 Nov 1998 00:51:39 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA15650; Wed, 18 Nov 1998 00:51:19 -0700 (MST) Message-Id: <199811180751.AAA15650@harmony.village.org> To: andrew@squiz.co.nz Subject: Re: groups Cc: freebsd-security@FreeBSD.ORG In-reply-to: Your message of "Wed, 18 Nov 1998 14:43:53 +1300." References: Date: Wed, 18 Nov 1998 00:51:18 -0700 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Andrew McNaughton writes: : Too much of a tangent to to put it into the existing thread: Can someone : give me a description of why we have user and group 'bin'? No. We don't have these group/user. They were removed because they were bogus and negatively added to security, especially when files were exported via nfs. Having files owned by bin doesn't buy you anything except an extra user. This is as of 3.0, the 2.x systems will still have these users. Actually, 3.0 has them also, but it doesn't actually use them except for the ports that haven't been updated. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message