From owner-freebsd-security Tue Apr 9 10:29: 4 2002 Delivered-To: freebsd-security@freebsd.org Received: from a2.scoop.co.nz (aurora.scoop.co.nz [203.96.152.68]) by hub.freebsd.org (Postfix) with ESMTP id 23FE937B405; Tue, 9 Apr 2002 10:28:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by a2.scoop.co.nz (8.12.2/8.12.2) with ESMTP id g39HSwKE017858; Wed, 10 Apr 2002 05:28:58 +1200 (NZST) (envelope-from andrew@scoop.co.nz) Date: Wed, 10 Apr 2002 05:28:58 +1200 (NZST) From: Andrew McNaughton X-X-Sender: andrew@a2 To: "Jacques A. Vidrine" Cc: X Philius , Subject: Re: Verifying that a security patch has done it's thing... In-Reply-To: <20020409172127.GN19961@madman.nectar.cc> Message-ID: <20020410052724.H12945-100000@a2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 9 Apr 2002, Jacques A. Vidrine wrote: > On Tue, Apr 09, 2002 at 10:18:17AM -0700, X Philius wrote: > [deletia ... thanks for the kind words!] > > > I assume I can find the PID by running ps -x as well, > > correct? It would be the process ID for /usr/sbin/sshd... > > Well, there will be more than one instance of sshd: the master, plus > one for every active SSH connection. You don't want to shoot the > wrong process, especially if SSH is your primary or only means of > accessing the box. :-) In which case you might be well advised to have a cron job which checks on it every so often and attempts to restart if it dies. No help if the server won't start though To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message