From owner-freebsd-questions@FreeBSD.ORG Fri Jan 30 06:37:59 2004 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 C0C6916A4CE for ; Fri, 30 Jan 2004 06:37:59 -0800 (PST) Received: from ei.bzerk.org (ei.xs4all.nl [213.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44E1F43D58 for ; Fri, 30 Jan 2004 06:37:52 -0800 (PST) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.12.10/8.12.10) with ESMTP id i0UEe3In094146; Fri, 30 Jan 2004 15:40:03 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.12.10/8.12.10/Submit) id i0UEe3KF094145; Fri, 30 Jan 2004 15:40:03 +0100 (CET) (envelope-from mail25@bzerk.org) X-Authentication-Warning: ei.bzerk.org: bulk set sender to mail25@bzerk.org using -f Date: Fri, 30 Jan 2004 15:40:03 +0100 From: Ruben de Groot To: chael@southgate.ph.inter.net Message-ID: <20040130144003.GA93799@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , chael@southgate.ph.inter.net, freebsd-questions@freebsd.org References: <001301c3e737$d1d683e0$4b0ea8cb@mrj> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c3e737$d1d683e0$4b0ea8cb@mrj> User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: After 4.6 to 4.9, SSH Lockout 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: Fri, 30 Jan 2004 14:37:59 -0000 On Fri, Jan 30, 2004 at 09:49:00PM +0800, chael@southgate.ph.inter.net typed: > Hello, > > After upgrading from 4.6-STABLE to 4.9-STABLE (religiously following the Handbook), I could not login to a second or another ssh session. I still, however, have my current connection to where I performed the make world steps. This is a REMOTE machine and I do not want disconnect this current ssh session because of fear that I may not get a successful ssh connection again. First: did you run mergemaster? I remember somewhere after 4.6 I was experiencing the same problem. It had to do with the PAMification of ssh and caused sshd to refuse any new connections. I believe killing the sshd parent process and restarting it solved it for me, without losing my existing connection. Just for cases like this I usually keep another ssh daemon running (usually the non-commercial version of www.ssh.org) on a nonstandard port or I enable a thouroughly wrapped and firewalled telnetd, just in case. Ruben