Date: Fri, 05 Mar 2004 16:34:47 -0600 From: Jon Noack <noackjr@alumni.rice.edu> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-current@freebsd.org Subject: Re: Breakage in X11 over ssh tunnel Message-ID: <40490087.7060108@alumni.rice.edu> In-Reply-To: <xzpsmgngp7u.fsf@dwp.des.no> References: <c23gu9$1fm4$1@kemoauc.mips.inka.de> <20040303225951.6647E5D07@ptavv.es.net> <20040304162258.C1E5043D49@mx1.FreeBSD.org> <xzpoerbk2gi.fsf@dwp.des.no> <20040305133500.79C559B54F@dsa.des.no> <xzpllmfic0r.fsf@dwp.des.no> <20040305173113.1BC7A9B54F@dsa.des.no> <xzpsmgngp7u.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/5/2004 11:48 AM, Dag-Erling Sm=F8rgrav wrote: > Randy Bush <randy@psg.com> writes: >>> Maybe keyboard-interactive defaults to off in the ssh.com client? >> >> i smell pam. here is debug output from sshd -d -p 8022 >=20 > according to the log, the client doesn't even try to authenticate; it > just gives up because it doesn't understand or doesn't want to use > keyboard-interactive. I just downloaded the latest non-commercial version from ssh.com. It=20 looks like keyboard-interactive is not available at all. Perhaps they=20 restrict this to the commercial versions? Here's the (sanitized) log: C:\>ssh2 -v noackjr@example.org <snip> debug: Ssh2Transport: My version: SSH-1.99-3.2.9 SSH Secure Shell=20 Windows Client debug: client supports 2 auth methods: 'publickey,password' <snip> debug: server offers auth methods 'publickey,keyboard-interactive'. debug: Ssh2Common: DISCONNECT received: No further authentication=20 methods available. warning: Authentication failed. Disconnected; no more authentication methods available (No further=20 authentication methods available.). Jon Noack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40490087.7060108>