From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:48:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A961C16A421 for ; Wed, 31 Oct 2007 14:48:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9600C13C480 for ; Wed, 31 Oct 2007 14:48:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E12E91CC077; Wed, 31 Oct 2007 07:39:44 -0700 (PDT) Date: Wed, 31 Oct 2007 07:39:44 -0700 From: Jeremy Chadwick To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20071031143944.GB21646@eos.sc1.parodius.com> References: <20071027101312.GA42516@eos.sc1.parodius.com> <86bqafxt96.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86bqafxt96.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Rob Zietlow Subject: Re: [7.0-Beta] can no longer ssh into just upgraded host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:48:39 -0000 On Wed, Oct 31, 2007 at 03:18:13PM +0100, Dag-Erling Smørgrav wrote: > Jeremy Chadwick writes: > > On Fri, Oct 26, 2007 at 01:47:07PM -0500, Rob Zietlow wrote: > >> #ssh -vv 192.168.8.163 > >> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 > >> debug1: Reading configuration data /etc/ssh/ssh_config > >> debug1: Applying options for * > >> debug2: ssh_connect: needpriv 0 > >> debug1: Connecting to 192.168.8.163 [192.168.8.163] port 22. > >> debug1: Connection established. > >> debug1: identity file /home/$USER/.ssh/identity type -1 > >> debug1: identity file /home/$USER/.ssh/id_rsa type -1 > >> debug1: identity file /home/$USER/.ssh/id_dsa type -1 > >> ssh_exchange_identification: read: Connection reset by peer > > > > Sounds like it might be a PAM-related problem. Have you looked > > at /var/log/messages or "dmesg -a"? > > What makes you think it might be PAM-related? They don't even get as > far as exchanging version strings. An old -stable post I read is what made me think it might be PAM-related: http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009414.html I don't know what stage PAM is actually induced within sshd (are any PAM-related API calls done before version exchange, etc.). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |