From owner-freebsd-security Mon Mar 19 20:46:22 2001 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B62C937B71B; Mon, 19 Mar 2001 20:46:17 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2K4ehh69973; Mon, 19 Mar 2001 23:40:43 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 19 Mar 2001 23:40:43 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sergey Babkin Cc: security@freebsd.org, Wes Peters , fs@freebsd.org Subject: Re: about common group & user ID space (PR kern/14584) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 19 Mar 2001, Robert Watson wrote: > Personally, I'm a fan of the AFS ACL model, where protections are present > only on directories, hard links are prohibited, and sub-directories > inherit protections on creation. I even had an implementation of this on > FreeBSD at one point, although it's quite dated now. However, ACLs have > a number of things going for them: Just as an aside, btw, AFS uses a common numeric namespace for both users and groups, as well as for remote users from other cells. Users can also allocate and manage groups on demand. The single numeric namespace makes things a lot more consistent :-). (although I think it allocates negative values to groups, and positive ones to users..) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message