From owner-freebsd-bugs@FreeBSD.ORG  Thu Oct  2 08:27:41 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1624916A4B3; Thu,  2 Oct 2003 08:27:41 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9ED3E43FBF; Thu,  2 Oct 2003 08:27:40 -0700 (PDT)
	(envelope-from roam@FreeBSD.org)
Received: from freefall.freebsd.org (roam@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h92FReFY015532;
	Thu, 2 Oct 2003 08:27:40 -0700 (PDT)
	(envelope-from roam@freefall.freebsd.org)
Received: (from roam@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h92FReYs015528;
	Thu, 2 Oct 2003 08:27:40 -0700 (PDT)
	(envelope-from roam)
Date: Thu, 2 Oct 2003 08:27:40 -0700 (PDT)
From: Peter Pentchev <roam@FreeBSD.org>
Message-Id: <200310021527.h92FReYs015528@freefall.freebsd.org>
To: mdg@secureworks.net, roam@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: 
	Re: conf/57497: [PATCH] no k5passwdd in rc.network, defaults/rc.conf
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Oct 2003 15:27:41 -0000

Synopsis: [PATCH] no k5passwdd in rc.network, defaults/rc.conf

State-Changed-From-To: open->closed
State-Changed-By: roam
State-Changed-When: Thu Oct 2 08:23:59 PDT 2003
State-Changed-Why: 

This is actually done in 4.8-STABLE (soon to be 4.9-RELEASE), but
the change was made after 4.8-RELEASE was out.  If your point is
that this is not present in the 4.8 security branch, you'll have
to talk to the Security Officer team <security-officer@FreeBSD.org>,
but IMHO, since this is not a vulnerability fix per se, but rather
just added functionality, it would not be very likely that they will
approve merging it into the 4.8 security branch, especially as
it *will* be present in the soon-to-come 4.9 release.

Still, thanks for your contribution!

http://www.freebsd.org/cgi/query-pr.cgi?pr=57497