From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 13:04:51 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BB5EC16A4CE
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 13:04:51 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AAAC343D3F
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 13:04:51 -0800 (PST)	(envelope-from randy@psg.com)
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1Az01T-000GmV-Ft; Thu, 04 Mar 2004 21:04:51 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com)
	by roam.psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1Az01S-000Kut-VN; Thu, 04 Mar 2004 13:04:51 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 4 Mar 2004 13:04:50 -0800
To: "Kevin Oberman" <oberman@es.net>
References: <20040304162300.A50F15D07@ptavv.es.net>
	<20040304205505.A757D5D07@ptavv.es.net>
Message-Id: <20040304210451.AAAC343D3F@mx1.FreeBSD.org>
cc: freebsd-current@freebsd.org
Subject: Re: Breakage in X11 over ssh tunnel 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 04 Mar 2004 21:04:51 -0000

>> i can deal with the -Y or hack my ssh_config.  but i have some
>> windoze users who now seem unable to get in.  they whine
>> 
>>> SSH Secure Shell: "Authentication failed. Most likely the password yo
>>> supplied was incorrect.  The user name might also might be wrong, or the
>>> account might be disabled."
>> 
>> any clues?
> 
> Are they running SSH V2? By default, OpenSSH on FreeBSD only supports
> V2. If your clients on Windows are not configured to do V2 (or don't
> have V2 keys), they will fail.

i stopped allowing/supporting v1 about the end of wwii.  so that's
not the problem.

randy