From owner-freebsd-bugs@FreeBSD.ORG  Sat Jan 26 01:00:43 2008
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 94EE716A419;
	Sat, 26 Jan 2008 01:00:43 +0000 (UTC)
	(envelope-from linimon@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 6568813C455;
	Sat, 26 Jan 2008 01:00:43 +0000 (UTC)
	(envelope-from linimon@FreeBSD.org)
Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0Q10hQY014099;
	Sat, 26 Jan 2008 01:00:43 GMT
	(envelope-from linimon@freefall.freebsd.org)
Received: (from linimon@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0Q10gnL014095;
	Sat, 26 Jan 2008 01:00:42 GMT (envelope-from linimon)
Date: Sat, 26 Jan 2008 01:00:42 GMT
Message-Id: <200801260100.m0Q10gnL014095@freefall.freebsd.org>
To: glebius@cell.sick.ru, linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: linimon@FreeBSD.org
Cc: 
Subject: Re: bin/37733: su(1) does not behave the way it is described in man
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jan 2008 01:00:43 -0000

Synopsis: su(1) does not behave the way it is described in man

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sat Jan 26 00:54:41 UTC 2008
State-Changed-Why: 
It sounds to me like su does indeed describe the current behavior.
If your primary group is 0, then indeed you are in group 0 :-)  I read
it as /etc/groups being _additional_ groups that a user is in.

If there is a need to create a group which can read but not modify
logs, then IMHO that's a local site decision and it should be a group
other than group 0.  Changing the meaning of group 0 would be a POLA
violation (at least at lonesome.com).

http://www.freebsd.org/cgi/query-pr.cgi?pr=37733