From owner-freebsd-security Sun Dec 5 22:36:16 1999 Delivered-To: freebsd-security@freebsd.org Received: from ints.ru (ints.ru [194.67.173.1]) by hub.freebsd.org (Postfix) with ESMTP id AB37D14CB1 for ; Sun, 5 Dec 1999 22:36:03 -0800 (PST) (envelope-from ilmar@ints.ru) Received: (from uucp@localhost) by ints.ru (8.9.2/8.9.2) id JAA05586; Mon, 6 Dec 1999 09:36:02 +0300 (MSK) Received: from ws-ilmar.ints.ru(194.67.173.16) via SMTP by ints.ru, id smtpdsZ5584; Mon Dec 6 09:35:56 1999 Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id JAA60693; Mon, 6 Dec 1999 09:35:54 +0300 (MSK) Date: Mon, 6 Dec 1999 09:35:54 +0300 (MSK) From: "Ilmar S. Habibulin" To: Robert Watson Cc: freebsd-security@FreeBSD.ORG Subject: Re: ACL-0.1.1.tgz: updated for -CURRENT, some bugfixes 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 Sun, 5 Dec 1999, Robert Watson wrote: > > Is -current posix target platform now? [...] > My guess is auditing won't be ready for 4.0, but hopefully will be for > whatever the next major 4.x release is. We might want to get MAC and > Capabilities in around then, although if you're reached final conclusions > on changes to the vnops and syscalls for capabilities we could try and get > them in now. What conclusion should i reach? I just need some space about 17 or let it be 24 bytes. I have all needed syscalls for CAP and MAC. I have freezed the development right now waiting for ACLs inclusion somewhere in the freebsd main source tree. All this posix stuff is very combined(?). MAC is nothing without AUDIT and so on. I would like to include all developed posix stuff in some development brunch, maybe -verrry-current ;-), and continue centralized development. The question is would freebsd project support posix 1e? Do the freebsd team need these extended security features in their OS? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message