From owner-freebsd-bugs@FreeBSD.ORG  Tue Feb 24 11:01:22 2004
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 1556416A4CE; Tue, 24 Feb 2004 11:01:22 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id ED7F643D1D; Tue, 24 Feb 2004 11:01:21 -0800 (PST)
	(envelope-from rwatson@FreeBSD.org)
Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1])
	i1OJ1Lbv099794;	Tue, 24 Feb 2004 11:01:21 -0800 (PST)
	(envelope-from rwatson@freefall.freebsd.org)
Received: (from rwatson@localhost)
	by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1OJ1LIa099790;
	Tue, 24 Feb 2004 11:01:21 -0800 (PST)
	(envelope-from rwatson)
Date: Tue, 24 Feb 2004 11:01:21 -0800 (PST)
From: Robert Watson <rwatson@FreeBSD.org>
Message-Id: <200402241901.i1OJ1LIa099790@freefall.freebsd.org>
To: rwatson@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	rwatson@FreeBSD.org
Subject: Re: kern/63096: [patch] MAC entry point for route manipulation
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: Tue, 24 Feb 2004 19:01:22 -0000

Synopsis: [patch] MAC entry point for route manipulation

Responsible-Changed-From-To: freebsd-bugs->rwatson
Responsible-Changed-By: rwatson
Responsible-Changed-When: Tue Feb 24 11:00:22 PST 2004
Responsible-Changed-Why: 
Take ownership of this as it's a MAC Framework related issue.  My
only comment so far is that it seems reasonable, but we might want
to consider naming it mac_check_route_alter() and use this as a
jumping off point to consider other restrictions in the routing
table, as well as hypothesize about policy routing.


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