From owner-freebsd-ports@FreeBSD.ORG  Tue Feb 26 01:31:09 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from notemg.house (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id C62C416A400;
	Tue, 26 Feb 2008 01:31:08 +0000 (UTC)
	(envelope-from mnag@FreeBSD.org)
Message-ID: <47C36BC3.1020106@FreeBSD.org>
Date: Mon, 25 Feb 2008 22:30:43 -0300
From: Marcus Alves Grando <mnag@FreeBSD.org>
Organization: FreeBSD
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Rong-En Fan <rafan@freebsd.org>
References: <20080129032111.GH40423@bunrab.catwhisker.org>
	<20080220020707.GK97111@svm.csie.ntu.edu.tw>
	<20080220021259.GS47504@bunrab.catwhisker.org>
	<20080220021805.GL97111@svm.csie.ntu.edu.tw>
In-Reply-To: <20080220021805.GL97111@svm.csie.ntu.edu.tw>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ports@freebsd.org, David Wolfskill <david@catwhisker.org>
Subject: Re: Fix for FreeBSD-SA-08:01.pty appears to break net/omnitty?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2008 01:31:09 -0000

Fixed.

Thanks

Rong-En Fan wrote:
> Hi,
> 
> On Tue, Feb 19, 2008 at 06:12:59PM -0800, David Wolfskill wrote:
>> On Wed, Feb 20, 2008 at 10:07:07AM +0800, Rong-En Fan wrote:
>>> FYI, this is fixed in omnitty 0.3.0_1.
>> Thanks!
>>
>> Should I file a PR against misc/compat6x (because its version of
>> libutil.so is apparently still subject PTY security advisory)?
> 
> Maintainer is CC'ed.
> 
> I think we should update misc/compat6x to use contents from
> 6.3-RELEASE. And filing a PR is also good. 
> 
> Regards,
> Rong-En Fan
>