From owner-cvs-all Thu Oct 19 0:54: 2 2000 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9D10437B65E; Thu, 19 Oct 2000 00:53:59 -0700 (PDT) Received: (from rwatson@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA56722; Thu, 19 Oct 2000 00:53:59 -0700 (PDT) (envelope-from rwatson@FreeBSD.org) Message-Id: <200010190753.AAA56722@freefall.freebsd.org> From: Robert Watson Date: Thu, 19 Oct 2000 00:53:59 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/kern vfs_subr.c src/sys/sys vnode.h src/sys/ufs/ufs ufs_lookup.c ufs_vnops.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rwatson 2000/10/19 00:53:59 PDT Modified files: sys/kern vfs_subr.c sys/sys vnode.h sys/ufs/ufs ufs_lookup.c ufs_vnops.c Log: o Introduce new VOP_ACCESS() flag VADMIN, allowing file systems to perform "administrative" authorization checks. In most cases, the VADMIN test checks to make sure the credential effective uid is the same as the file owner. o Modify vaccess() to set VADMIN as an available right if the uid is appropriate. o Modify references to uid-based access control operations such that they now always invoke VOP_ACCESS() instead of using hard-coded policy checks. o This allows alternative UFS policies to be implemented by replacing only ufs_access() (such as mandatory system policies). o VOP_ACCESS() requires the caller to hold an exclusive vnode lock on the vnode: I believe that new invocations of VOP_ACCESS() are always called with the lock held. o Some direct checks of the uid remain, largely associated with the QUOTA and SUIDDIR code. Reviewed by: eivind Obtained from: TrustedBSD Project Revision Changes Path 1.287 +6 -1 src/sys/kern/vfs_subr.c 1.131 +8 -7 src/sys/sys/vnode.h 1.41 +3 -4 src/sys/ufs/ufs/ufs_lookup.c 1.151 +47 -24 src/sys/ufs/ufs/ufs_vnops.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message