From owner-freebsd-questions@FreeBSD.ORG Thu Jan 6 16:41:21 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D8E216A4CE for ; Thu, 6 Jan 2005 16:41:21 +0000 (GMT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id D952D43D5C for ; Thu, 6 Jan 2005 16:41:20 +0000 (GMT) (envelope-from dwinner-lists@worldnet.att.net) Received: from [10.10.100.90] (unknown[216.113.237.29]) by worldnet.att.net (mtiwmhc12) with ESMTP id <2005010616411311200mhqtke> (Authid: duanewinner); Thu, 6 Jan 2005 16:41:13 +0000 Message-ID: <41DD6A28.10306@att.net> Date: Thu, 06 Jan 2005 11:41:12 -0500 From: Duane Winner User-Agent: Mozilla Thunderbird 1.0 (X11/20050104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian McCann References: <2b5f066d05010405413cf48f99@mail.gmail.com> In-Reply-To: <2b5f066d05010405413cf48f99@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD mailinglist Subject: Re: SSH & 5.3 Problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 16:41:21 -0000 Brian McCann wrote: >Hi all. On 5.3 and 5.3 RC1 I have this problem where when I ssh in >using either a FreeBSD 4.3 box or an older PuTTY client (0.52 is one I >experienced it with), I cannot connect. On PuTTY, it asks for a >username, then just exits. On FreeBSD when I put the ssh client into >verbose, it appears it can't agree on an auth method, even though both >are set to accept and attempt keyboard-interactive. Upgrading to a >newer PuTTY fixed the problem, and it seams to work from FreeBSD 4.10. > I've seen some posts from people that upgrading their PuTTY fixed the >problem, but I'm curious if anyone knows the cause of the problem, and >possibly how to fix it, on the server end. > >Thanks, >--Brian McCann >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > For what it's worth, we happen to have some licensed copies of the commercial SSH client (from SSH Communications Inc.) for our Windows boxes. I just tried to reproduce this problem. To ssh into *nix workstations, I've always just used password authentication. On the commercial windows client, after you specify the hostname and username, you pick from a drop-down list Authentication Method: -Password -Public Key -SecureID -PAM -Keyboard Interactive I have ALWAYS just used password to get into my Linux and FreeBSD workstations running sshd. But password no longer works. I started to get nervous, but relaxed when I found out that if I selected "Keyboard Interactive", I could get in. I don't understand what exacactly "keyboard interactive" is and how it differs from "password", but it seems to work. I haven't used PuTTY in a few years, and I don't know if this is something that can be tweaked or not. Cheers, DW