From owner-freebsd-current@FreeBSD.ORG  Sun May 27 06:16:25 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 9E17E106566B
	for <current@freebsd.org>; Sun, 27 May 2012 06:16:25 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 3796E14EE0F;
	Sun, 27 May 2012 06:16:23 +0000 (UTC)
Message-ID: <4FC1C6B6.3050308@FreeBSD.org>
Date: Sat, 26 May 2012 23:16:22 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:12.0) Gecko/20120506 Thunderbird/12.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>
References: <86vcjid0zp.fsf@ds4.des.no> <86mx4ucy5y.fsf@ds4.des.no>
In-Reply-To: <86mx4ucy5y.fsf@ds4.des.no>
X-Enigmail-Version: 1.5pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: current@freebsd.org
Subject: Re: WARNING: su(1) broken in head
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 May 2012 06:16:25 -0000

On 05/26/2012 16:36, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav <des@des.no> writes:
>> probably due to an issue in the latest openpam; sudo is not affected
> 
> should be fixed now.

Confirmed, thanks. :)


-- 

    This .signature sanitized for your protection