From owner-freebsd-stable@FreeBSD.ORG Wed May 18 15:39:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B971C16A4CE for ; Wed, 18 May 2005 15:39:24 +0000 (GMT) Received: from alogis.com (firewall2.alogis.com [62.8.223.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D14243D5D for ; Wed, 18 May 2005 15:39:23 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.1/8.13.1) with ESMTP id j4IFdGJV069973; Wed, 18 May 2005 17:39:16 +0200 (CEST) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.1/8.13.1/Submit) id j4IFdGCt069972; Wed, 18 May 2005 17:39:16 +0200 (CEST) (envelope-from hk) Date: Wed, 18 May 2005 17:39:16 +0200 From: Holger Kipp To: freebsd-stable@freebsd.org Message-ID: <20050518153916.GA69149@intserv.int1.b.intern> References: <20050518121953.GA64455@intserv.int1.b.intern> <20050518150308.GA32719@thened.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050518150308.GA32719@thened.net> User-Agent: Mutt/1.4.2.1i cc: alec@thened.net Subject: Re: sshd on 5.4-STABLE broken!? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2005 15:39:24 -0000 On Wed, May 18, 2005 at 11:03:08AM -0400, Alec Berryman wrote: > Kipp Holger on 2005-05-18 14:19:53 +0200: > > > - can I provide any additional data? > > Are you in a position to restart sshd with multiple debug flags and > have it spew to the console? (see sshd man page, options '-D' and > '-d'). That, and connecting with ssh's verbose flag (1-3 '-v's), will > probably give you a good starting point. From what you said in your > email, I don't believe you tried that. True, I didn't. Here it goes: I am using 'sshd -D -d -d -d -p 3333' as server-process and connect with 'ssh -v -v -v -p 3333 blubber@server1' In this case I end up with two 'not_connected' processes: 1927 p9 I+ 0:00,05 sshd: hk [priv] (sshd) 1930 p9 I+ 0:00,00 sshd: hk [pam] (sshd) that both do not time out. Debugging of sshd after pressing ctrl-c is: debug3: mm_sshpam_query: pam_query returned 0 Postponed keyboard-interactive for hk from port 53507 ssh2 Connection closed by debug1: do_cleanup debug1: PAM: cleanup debug3: PAM: sshpam_thread_cleanup entering debug1: do_cleanup debug1: PAM: cleanup and then nothing. Even after waiting for 8 minutes. Connecting again is of course not possible. Is this of any help? I can produce the complete debugging information if that is of interest. Pressing return three times instead of ctrl-c if password is requested, produces an additional debug3: PAM: sshpam_thread_cleanup entering and exits sshd Regards, Holger Kipp