From owner-freebsd-questions@FreeBSD.ORG Tue Jan 4 14:14:36 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 C48FF16A4CE for ; Tue, 4 Jan 2005 14:14:36 +0000 (GMT) Received: from sferics.mongueurs.net (sferics.mongueurs.net [81.80.147.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0FC43D49 for ; Tue, 4 Jan 2005 14:14:35 +0000 (GMT) (envelope-from david@landgren.net) Received: from [127.0.0.1] (exo.bpinet.com [81.80.147.206]) by sferics.mongueurs.net (Postfix) with ESMTP id A345EA94C for ; Tue, 4 Jan 2005 15:14:34 +0100 (CET) Message-ID: <41DAA4C9.6010909@landgren.net> Date: Tue, 04 Jan 2005 15:14:33 +0100 From: David Landgren Organization: The Lusty Decadent Delights of Imperial Pompeii User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD mailinglist 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 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:14:36 -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. What error message does sshd emit on the server? David