From owner-freebsd-security@FreeBSD.ORG  Wed Sep 17 12:52:53 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 570B716A4C1
	for <freebsd-security@freebsd.org>;
	Wed, 17 Sep 2003 12:52:53 -0700 (PDT)
Received: from aristotle.tamu.edu (Aristotle.tamu.edu [165.91.161.90])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4383F43F75
	for <freebsd-security@freebsd.org>;
	Wed, 17 Sep 2003 12:52:52 -0700 (PDT)
	(envelope-from rasmith@aristotle.tamu.edu)
Received: from aristotle.tamu.edu (localhost [127.0.0.1])
	by aristotle.tamu.edu (8.12.9/8.12.9) with ESMTP id h8HJqmcZ082311
	for <freebsd-security@freebsd.org>;
	Wed, 17 Sep 2003 14:52:48 -0500 (CDT)
	(envelope-from rasmith@aristotle.tamu.edu)
Message-Id: <200309171952.h8HJqmcZ082311@aristotle.tamu.edu>
To: freebsd-security@freebsd.org
In-Reply-To: Message from Matthew Dillon <dillon@apollo.backplane.com> 
	<200309171936.h8HJa2K5012289@apollo.backplane.com> 
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 17 Sep 2003 14:52:48 -0500
From: Robin Smith <rasmith@aristotle.tamu.edu>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:12.openssh 
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2003 19:52:53 -0000

>>>>> "Jacques" == Jacques A Vidrine <nectar@freebsd.org> writes:

    Jacques> I think we'll just not do it quite completely and go with

    Jacques>     # kill `cat /var/run/sshd.pid` 
                 # /usr/sbin/sshd

Doesn't sshd respond to a HUP by re-executing itself rather than
simply re-reading its config files?  That is, wouldn't 
"kill -HUP `cat /var/run/sshd.pid` " do what's wanted (i.e. kill 
and restart the listening daemon while leaving the children for 
established connections alone)?