From owner-freebsd-security@FreeBSD.ORG  Fri Aug 13 10:35:18 2010
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 D13C9106566B
	for <freebsd-security@freebsd.org>;
	Fri, 13 Aug 2010 10:35:18 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
	by mx1.freebsd.org (Postfix) with ESMTP id 9007C8FC1E
	for <freebsd-security@freebsd.org>;
	Fri, 13 Aug 2010 10:35:18 +0000 (UTC)
Received: from ds4.des.no (des.no [84.49.246.2])
	by smtp.des.no (Postfix) with ESMTP id AD42B1FFC36;
	Fri, 13 Aug 2010 10:35:17 +0000 (UTC)
Received: by ds4.des.no (Postfix, from userid 1001)
	id 77A3B8454E; Fri, 13 Aug 2010 12:35:17 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: jhell <jhell@dataix.net>
References: <alpine.BSF.2.00.1008100841350.96753@tiktik.epipe.com>
	<alpine.BSF.2.00.1008101503190.96753@tiktik.epipe.com>
	<201008121302.o7CD2BJv044208@lava.sentex.ca>
	<alpine.BSF.2.00.1008121828360.96753@tiktik.epipe.com>
	<4C64D1EF.6030508@dataix.net>
Date: Fri, 13 Aug 2010 12:35:17 +0200
In-Reply-To: <4C64D1EF.6030508@dataix.net> (jhell@dataix.net's message of
	"Fri, 13 Aug 2010 01:02:39 -0400")
Message-ID: <86r5i2ssuy.fsf@ds4.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@freebsd.org, Janne Snabb <snabb@epipe.com>
Subject: Re: ~/.login_conf mechanism is flawed
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, 13 Aug 2010 10:35:18 -0000

jhell <jhell@dataix.net> writes:
> On the note of using a ~/.login_conf file for setting limits and in this
> case increasing them. when they shouldn't be.
>
> I have been using a ~/.login_conf without generating the
> ~/.login_conf.db through the use of cap_mkdb(1) for quite some time. So
> on that, is it really necessary to look for that .db file at all since
> ~/.login_conf works without it...

It won't make any difference.  The problem is that setusercontext()
applies the user's settings even if it's still running as root.  I have
a patch, but I need to check that it doesn't break anything.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no