From owner-freebsd-security@FreeBSD.ORG  Fri Jan  9 06:37:42 2009
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6273A106564A
	for <freebsd-security@freebsd.org>;
	Fri,  9 Jan 2009 06:37:42 +0000 (UTC)
	(envelope-from chris@noncombatant.org)
Received: from strawberry.noncombatant.org (strawberry.noncombatant.org
	[64.142.6.126]) by mx1.freebsd.org (Postfix) with ESMTP id 4D2E58FC13
	for <freebsd-security@freebsd.org>;
	Fri,  9 Jan 2009 06:37:42 +0000 (UTC)
	(envelope-from chris@noncombatant.org)
Received: by strawberry.noncombatant.org (Postfix, from userid 1001)
	id 6DB96866D77; Thu,  8 Jan 2009 22:20:26 -0800 (PST)
Date: Thu, 8 Jan 2009 22:20:26 -0800
From: Chris Palmer <chris@noncombatant.org>
To: freebsd-security@freebsd.org
Message-ID: <20090109062026.GI38127@noncombatant.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Subject: Incorrect (?) documentation for setreuid(2) could lead to security
	issues for user code
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2009 06:37:42 -0000

According to section 6.4.1 of "Setuid Demystified":

http://www.cs.ucdavis.edu/~hchen/paper/usenix02.html

FreeBSD 4.4's setreuid(2) man page is wrong. The man page for FBSD 7 says
the same thing. Is it still wrong, or was the implementation changed to
match the documentation?

This person noticed the same problem for OBSD:

http://www.nabble.com/setreuid()-documentation-is-confusing-and-wrong-td7953251.html