From owner-freebsd-questions@FreeBSD.ORG Tue Jan 4 13:41:54 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 9FB0116A4CE for ; Tue, 4 Jan 2005 13:41:54 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B77A43D1D for ; Tue, 4 Jan 2005 13:41:54 +0000 (GMT) (envelope-from bjmccann@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so114368wri for ; Tue, 04 Jan 2005 05:41:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=X6GlPmEOnHoE2KImPPCP91VUpGlhcy9b217siJZIunDffsQVpwOk4vnKcNJhSLYxrh4M8z4SXlHXryXOEQnmTJ+gPfb4KAoSR7DSrFR3SmngdP6uhL733Zloq1xdjx37L6D8ggpiVihiwvUsXGRTBfTe+Op9THd4a0LJvKqLPYI= Received: by 10.54.7.62 with SMTP id 62mr87131wrg; Tue, 04 Jan 2005 05:41:53 -0800 (PST) Received: by 10.54.33.61 with HTTP; Tue, 4 Jan 2005 05:41:52 -0800 (PST) Message-ID: <2b5f066d05010405413cf48f99@mail.gmail.com> Date: Tue, 4 Jan 2005 08:41:52 -0500 From: Brian McCann To: FreeBSD mailinglist Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: SSH & 5.3 Problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brian McCann List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 13:41:54 -0000 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