From owner-freebsd-questions@FreeBSD.ORG Tue Jan 4 14:23:50 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 6DDD516A4CE for ; Tue, 4 Jan 2005 14:23:50 +0000 (GMT) Received: from lp1001.snu.ac.kr (lp1001.snu.ac.kr [147.46.70.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E726A43D31 for ; Tue, 4 Jan 2005 14:23:49 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [IPv6:::1] (localhost [127.0.0.1]) (authenticated (0 bits)) by lp1001.snu.ac.kr (8.13.1/8.11.6) with ESMTP id j04ELVa8004466 for ; Tue, 4 Jan 2005 23:21:32 +0900 Message-ID: <41DAA6F4.9000704@yahoo.com> Date: Tue, 04 Jan 2005 23:23:48 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20041226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD References: <2b5f066d05010405413cf48f99@mail.gmail.com> <41DAA4C9.6010909@landgren.net> In-Reply-To: <41DAA4C9.6010909@landgren.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 04 Jan 2005 14:23:50 -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. > Same problem occurred here with other SSH programs for Windows that connect to FreeBSD PC. When upgrading from 4.10 to 5.3, suddenly the Windows PCs could not connect anymore , with a similar error as you get. Upgrading was the solution. I never tried to downgrade the newer SSH version on FreeBSD to handle old versions; I considered the reverse a better way :). Curiously: a nother PC running 4.10 had no problems to connect to 5.3. Only Windows' SSH programs had such problems. Rob.