From owner-freebsd-stable@FreeBSD.ORG Tue Jan 11 20:29:12 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 D6D5316A4CE; Tue, 11 Jan 2005 20:29:12 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B8C43D31; Tue, 11 Jan 2005 20:29:12 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id D46F611E13; Tue, 11 Jan 2005 21:29:10 +0100 (CET) Date: Tue, 11 Jan 2005 21:29:10 +0100 From: "Simon L. Nielsen" To: freebsd-stable@freebsd.org Message-ID: <20050111202909.GC773@zaphod.nitro.dk> References: <20041112201212.GB772@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline In-Reply-To: <20041112201212.GB772@zaphod.nitro.dk> User-Agent: Mutt/1.5.6i cc: Dag-Erling Smorgrav Subject: [Solved] Re: sshd stops accepting connections 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: Tue, 11 Jan 2005 20:29:13 -0000 --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.12 21:12:12 +0100, Simon L. Nielsen wrote: > Today I suddenly couldn't log in via ssh to a server I upgraded to > FreeBSD 5.3-RELEASE 4 days ago. When I tried connect to port 22 using > telnet(1) the following just happend: >=20 > [simon@zaphod:~] telnet 192.168.3.2 22 > Trying 192.168.3.2... > Connected to jet.nitro.dk. > Escape character is '^]'. > Connection closed by foreign host. [...] For the archives and anybody who may be interested... There is some kind of bug in OpenSSH 3.8.1p1's sshd (the one shipped with 5.3), possibly related to PAM and Privilege Separation. The fix for me was simply to install OpenSSH 3.9 from ports, and I haven't had the problem since. --=20 Simon L. Nielsen --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB5DcVh9pcDSc1mlERAj/WAJ9JugR8REcE28vJWqk7eaepLELv3QCgsmlK xw8TE1RiCPnPBrd/kJCTRZE= =u4Ep -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc--