From owner-freebsd-stable@FreeBSD.ORG  Sun Jan 16 12:12:25 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BE21016A4CE
	for <freebsd-stable@freebsd.org>;
	Sun, 16 Jan 2005 12:12:25 +0000 (GMT)
Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EFDA243D58
	for <freebsd-stable@freebsd.org>;
	Sun, 16 Jan 2005 12:12:24 +0000 (GMT)	(envelope-from ivoras@fer.hr)
Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113])
	by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0GCOn5B022235;
	Sun, 16 Jan 2005 13:24:49 +0100 (MET)
Message-ID: <41EA5A1F.7050407@fer.hr>
Date: Sun, 16 Jan 2005 13:12:15 +0100
From: Ivan Voras <ivoras@fer.hr>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041213)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Dymond <tom@kmem.org>
References: <41E9B02B.5070602@fer.hr>
	<20050116000935.GA95376@xor.obsecurity.org> <41E9B226.40801@fer.hr>
	<20050116003334.GA394@xor.obsecurity.org> <41E9C0D2.3000101@fer.hr>
	<20050116113424.GA35989@ruby.london.kmem.org>
In-Reply-To: <20050116113424.GA35989@ruby.london.kmem.org>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-stable@freebsd.org
Subject: Re: cannot su?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2005 12:12:25 -0000

Thomas Dymond wrote:

> 
> Could this be anything to do with : security.bsd.suser_enabled
> 
> what's yours set to ?

security.bsd.suser_enabled: 1

But, I noticed I've got security.mac.* enabled somehow (it's not my 
kernel...) - could MAC be interfering?