Date: Fri, 30 Jan 2004 15:40:03 +0100 From: Ruben de Groot <mail25@bzerk.org> To: chael@southgate.ph.inter.net Cc: freebsd-questions@freebsd.org Subject: Re: After 4.6 to 4.9, SSH Lockout Message-ID: <20040130144003.GA93799@ei.bzerk.org> In-Reply-To: <001301c3e737$d1d683e0$4b0ea8cb@mrj> References: <001301c3e737$d1d683e0$4b0ea8cb@mrj>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040130144003.GA93799>