Date: Fri, 23 Jul 1999 09:30:54 -0600 From: "Ronald G. Minnich" <rminnich@acl.lanl.gov> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... Message-ID: <Pine.SGI.4.10.9907230913240.181885-100000@acl.lanl.gov> In-Reply-To: <Pine.BSF.4.10.9907231037250.87625-100000@morden.rebel.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Jul 1999, Kris Kennaway wrote: > On Thu, 22 Jul 1999, Ronald G. Minnich wrote: > > Are you saying that as an ordinary user I can mount something on top of > > /tmp, for example? > If the vfs.usermount sysctl is 1, and you have appropriate access to the > thing you're trying to mount (block device, etc). OK, so let's say it is 1. Let's say I have "appropriate access" to /tmp. I mount my own fs on /tmp. I now have read/write access to everything anyone writes to /tmp. Or, let's say I don't have "appropriate access" to /tmp. Pick some other place. I mount my file system there for my files. Now everyone who wants can look for these user mounts and walk them at will. My private stuff is quite public. User mounts are neat. But user mounts that modify the global name space of the machine are not neat. User mounts should be part of a private name space. But thanks for the note. I just now realized that if I add a private name space to v9fs (which is easy), and then turn on user mounts, user processes can have private name spaces on freebsd! thanks ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SGI.4.10.9907230913240.181885-100000>