From owner-freebsd-security@FreeBSD.ORG  Wed Sep 24 02:16:12 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CF50A16A4C2
	for <security@freebsd.org>; Wed, 24 Sep 2003 02:16:12 -0700 (PDT)
Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za
	[196.31.7.201])	by mx1.FreeBSD.org (Postfix) with ESMTP id B3EAA43FEC
	for <security@freebsd.org>; Wed, 24 Sep 2003 02:16:11 -0700 (PDT)
	(envelope-from sheldonh@starjuice.net)
Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.22)
	id 1A25kh-0005wr-LF; Wed, 24 Sep 2003 11:16:03 +0200
Date: Wed, 24 Sep 2003 11:16:03 +0200
From: Sheldon Hearn <sheldonh@starjuice.net>
To: Haesu <haesu@towardex.com>
Message-ID: <20030924091603.GC22622@starjuice.net>
References: <3F705D4D.4070404@tenebras.com>
	<20030923205318.GB3346@scylla.towardex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030923205318.GB3346@scylla.towardex.com>
User-Agent: Mutt/1.5.4i
Sender: Sheldon Hearn <sheldonh@starjuice.net>
cc: security@freebsd.org
Subject: Re: OpenSSH: multiple vulnerabilities in the new PAM code
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
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: Wed, 24 Sep 2003 09:16:12 -0000

On (2003/09/23 16:53), Haesu wrote:

> Oh jee, here we go again. Hey, at least patched 3.5p1 on FreeBSD
> 4.8/4.9 are not effected :)

Since -CURRENT's using a modified OpenSSH_3.6.1p1, I don't think this
issue affects FreeBSD at all.

Ciao,
Sheldon.