From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 12:55:06 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 A8BDB16A4CF
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 12:55:06 -0800 (PST)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB4043D1F
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 12:55:06 -0800 (PST)	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465;
        Thu, 04 Mar 2004 12:55:05 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id A757D5D07; Thu,  4 Mar 2004 12:55:05 -0800 (PST)
To: Randy Bush <randy@psg.com>
In-reply-to: Your message of "Thu, 04 Mar 2004 08:22:57 PST."
             <20040304162300.A50F15D07@ptavv.es.net> 
Date: Thu, 04 Mar 2004 12:55:05 -0800
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20040304205505.A757D5D07@ptavv.es.net>
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 20:55:06 -0000

> From: Randy Bush <randy@psg.com>
> Date: Thu, 4 Mar 2004 08:22:57 -0800
> 
> 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.

Best to switch them to V2, but you can edit sshd_config and change it to
Protocol 2,1.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634