From owner-freebsd-arch@FreeBSD.ORG  Thu Mar 25 04:06:42 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B019F16A4CE; Thu, 25 Mar 2004 04:06:42 -0800 (PST)
Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F37CE43D2D; Thu, 25 Mar 2004 04:06:41 -0800 (PST)
	(envelope-from bde@zeta.org.au)
Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au
	[61.8.0.86])i2PC6e5v018161;	Thu, 25 Mar 2004 23:06:40 +1100
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	i2PC6cGQ022855;	Thu, 25 Mar 2004 23:06:39 +1100
Date: Thu, 25 Mar 2004 23:06:38 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Pawel Jakub Dawidek <pjd@freebsd.org>
In-Reply-To: <20040324235120.GU8930@darkness.comp.waw.pl>
Message-ID: <20040325225342.D36800@gamplex.bde.org>
References: <20040324235120.GU8930@darkness.comp.waw.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-arch@freebsd.org
Subject: Re: SUIDDIR -> security.bsd.suiddir_enable.
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2004 12:06:42 -0000

On Thu, 25 Mar 2004, Pawel Jakub Dawidek wrote:

> Any objection on such exchange?
>
> In p4 pjd_suiddir branch I've a code that replace SUIDDIR kernel option
> with sysctl security.bsd.suiddir_enable sysctl with is turned off by
> default. SUIDDIR option is not removed, but it means now: turn on suiddir
> functionality by default.

Using SUIDDIR is controlled by the MNT_SUIDDIR mount option, so there
shouldn't be another knob to control it.  If there is a security problem
using MNT_SUIDDIR, then MNT_SUIDDIR should be disallowed up front so
that that all the places that implement SUIDDIR don't have to test
both knobs.

> I'm not also sure if security.bsd.* is the right place, maybe vfs.*
> is better?

/dev/null is better :-).

Bruce