From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 13:08:35 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 1B08F16A4CE
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 13:08:35 -0800 (PST)
Received: from postal1.es.net (proxy.es.net [198.128.3.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0CAE243D39
	for <freebsd-current@freebsd.org>;
	Thu,  4 Mar 2004 13:08:35 -0800 (PST)	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465;
        Thu, 04 Mar 2004 13:08:34 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id 6862D5D07; Thu,  4 Mar 2004 13:08:34 -0800 (PST)
To: Randy Bush <randy@psg.com>
In-reply-to: Your message of "Thu, 04 Mar 2004 13:04:50 PST."
             <20040304210454.12BB85D07@ptavv.es.net> 
Date: Thu, 04 Mar 2004 13:08:34 -0800
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20040304210834.6862D5D07@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 21:08:35 -0000

> From: Randy Bush <randy@psg.com>
> Date: Thu, 4 Mar 2004 13:04:50 -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.
> 
> i stopped allowing/supporting v1 about the end of wwii.  so that's
> not the problem.

I don't know about the app on Windows, but can it log? Something
equivalent to 'ssh -v'? You might also set up another sshd with -d on a
special port and have someone connect to that and get more detail on why
it's failing.
-- 
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