From owner-freebsd-fs Mon Oct 27 10:30:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12520 for fs-outgoing; Mon, 27 Oct 1997 10:30:28 -0800 (PST) (envelope-from owner-freebsd-fs) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12505 for ; Mon, 27 Oct 1997 10:30:11 -0800 (PST) (envelope-from guido@gvr.org) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id TAA01989; Mon, 27 Oct 1997 19:28:51 +0100 (MET) From: Guido van Rooij Message-Id: <199710271828.TAA01989@gvr.gvr.org> Subject: Re: disabled symlinks In-Reply-To: <199710271726.KAA13912@usr01.primenet.com> from Terry Lambert at "Oct 27, 97 05:26:08 pm" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 27 Oct 1997 19:28:51 +0100 (MET) Cc: roberto@keltia.freenix.fr, freebsd-fs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > As far as "nosuid" goes, I will note that if root runs a program on > a nosuid mounted volume, the program runs as root. And root can also > "suid" to any user id, and run the program, simulating an "suid" event. > ?? So what. That isn;t the issue here. If root runs rm -rf / things will also break. That has nothing to do with suid. > So if the intent is to make it act like "nosuid", then it should only > affect creation, and being root should override the option (ie: root > can still create symlinks). I still think otherwise. Now that symlinks do have owners, teh same can be achieved by only following symlinks if they are owned by root. -Guido