From owner-freebsd-security@FreeBSD.ORG  Thu Jun 30 15:58:48 2011
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 33243106566C
	for <freebsd-security@freebsd.org>;
	Thu, 30 Jun 2011 15:58:48 +0000 (UTC) (envelope-from mike@sentex.net)
Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca
	[IPv6:2607:f3e0:0:1::12])
	by mx1.freebsd.org (Postfix) with ESMTP id EE7788FC0C
	for <freebsd-security@freebsd.org>;
	Thu, 30 Jun 2011 15:58:47 +0000 (UTC)
Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca
	[IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a])
	by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p5UFwh2W026417
	for <freebsd-security@freebsd.org>;
	Thu, 30 Jun 2011 11:58:43 -0400 (EDT) (envelope-from mike@sentex.net)
Message-ID: <4E0C9D26.2050108@sentex.net>
Date: Thu, 30 Jun 2011 11:58:30 -0400
From: Mike Tancsa <mike@sentex.net>
Organization: Sentex Communications
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: freebsd-security@freebsd.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12
Subject: Old SSH bug on RELENG_4
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: Thu, 30 Jun 2011 15:58:48 -0000

I am sure someone has some boxes out there still....

http://lists.grok.org.uk/pipermail/full-disclosure/2011-June/081722.html

A simple work around *seems* to be to disable PAM on sshd. i.e in
/etc/ssh/sshd_config

set the following from yes to no

# Change to no to disable PAM authentication
ChallengeResponseAuthentication no

I wonder if other apps that make use of PAM can trigger the bug as well ?

	---Mike

-- 
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/